InfoQ Homepage Presentations Design Microservice Architectures the Right Way
Design Microservice Architectures the Right Way
48:29
Summary
Michael Bryzek highlights specific key decisions that very directly impact the quality and maintainability of a microservice architecture, covering infrastructure, continuous deployment, communication, event streaming, language choice and more, all to ensure that teams and systems remain productive and scale.
Bio
Michael Bryzek 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.
About the conference
Software is changing the world. QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. A practitioner-driven conference, QCon is designed for technical team leads, architects, engineering directors, and project managers who influence innovation in their teams.
Sep 10, 2018
-
Related Sponsored Content
-
Related Sponsor
/filters:no_upscale()/sponsorship/topic/199c5fa7-5ded-446e-b353-89c55b6e83dd/QConSFLogoRSB-1653383003269.png)
Community comments
Amazing stuff
by Richard Richter,
Amazing stuff
by Richard Richter,
Your message is awaiting moderation. Thank you for participating in the discussion.
I'm glad it can be done this way in smaller-than-biggest-unicorns scale. I like how everything is code, so even "API first" is in fact coding (JSON) and it gets built (validated). The presentation was really nice and informative, but I didn't find one thing there - how to deal with any complex domain logic. Most of the things shown were from CRUD domain. But boy, it was still no-fuss CRUD - and I liked that!
What I often fight with when it comes to microservices (or DDD on the other hand) is how to do performant queries with joins and how to perform nontrivial non-CRUD updates into database. I'm sure it must start with DB redesign, not just with building services over existing (slightly partitioned) database our monolith ran on before.