QCon New York June 15-19, 2020 | | Design Microservice Architectures the Right Way

Track: Microservices: Patterns & Practices

Location: Broadway Ballroom North, 6th fl.

Duration: 4:10pm - 5:00pm

Day of week:

Slides: Download SlidesNEW!

Level: Intermediate

Persona: Architect, CTO/CIO/Leadership, Developer, General Software

This presentation is now available to view on InfoQ.com

Watch video

What You’ll Learn

Understand from first-hand experience the many critical decisions you make in designing your microservice architecture.
Learn first hand what decisions are critical; and which will lead to paralyzing technical debt over time.
Hear a step by step use case of building a successful microservice platform with all the critical points along the way.

Abstract

Learn from first hand, deep experience, the most critical decisions we face in building successful microservice architectures: how to think about the tradeoffs that impact the productivity of our teams and the quality of our software. In particular, understand how to avoid creating an architecture that eventually (and sometimes quickly) paralyzes our ability to execute. This talk highlights specific key decisions that very directly impact the quality and maintainability of a micro service architecture, covering infrastructure, continuous deployment, communication, event streaming, language choice and more, all to ensure that our teams and systems remain productive as we scale.

Question:

Can you give us a teaser of what to expect in this talk?

Answer:

We will go step by step and talk about the investment needed to run a successful microservice platform, touching on everything from contracts, events, data structure, shared libraries, deployment, isolation, monitoring, etc.

Our primary thesis is to reinforce that a microservice architecture requires significant investment (as do all architectures) to be successful - and then to drive home a few points: microservice != polyglot, importance of continuous delivery and high-quality dev tools, and the usefulness of isolation as a core strategy to manage risk while scaling teams.

Question:

What is the level of experience someone attending this talk should have?

Answer:

Approachable for all; probably most useful for people thinking about creating a microservice architecture or who are suffering from the consequences of a poorly design distributed monolith.

Speaker: Michael Bryzek

Cofounder & CTO @Flow.io, previously Co-Founder & CTO @Gilt

Michael is the CTO and co-founder of Flow Commerce, an enterprise SAAS platform that is the world’s most advanced solution for global ecommerce. Prior, he was the cofounder and CTO of Gilt Groupe, an innovative online shopping destination offering. Gilt was an early adopted of microservice architectures at scale and the positive and negative lessons learned have informed directly the micro service architecture behind Flow. Michael holds a BSc and Masters in computer science from the Massachusetts Institute of Technology.