What Does a Good Microservice Architecture Look Like?
summary
Shows concrete failures and fixes: a platform with 270 microservices suffers from a shared model-jar anti-pattern; another system has a 463-class cycle hiding ~500k LOC and a 10M LOC codebase with 90 tangled modules. Recommends domain-driven bounded contexts, separate small domain models with intentional data duplication, asynchronous event exchange (weekly-schedule → auditorium-plan), hexagonal core with no reuse across domain cores, and measuring progress with a modularity maturity index using tools like SonarQube, Sonargraph and ArcUnit.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:11Sustainable architecture goals
- 5:59Microservices and legacy systems
- 7:01Modularity vs big ball of mud
- 10:58High cohesion and loose coupling
- 15:11Domain-driven design and teams
- 16:16Pitfalls of microservice architectures
- 22:38Separate domain models per service
- 27:16Avoid one service per entity
- 30:03Subdomains and bounded contexts
- 31:48Event storming and domain storytelling
- 39:58Modularity maturity index
- 42:48Key takeaways and tools
- 44:13Q&A session
related talks
52mI Have a Microservices Architecture and I Didn't Know.
01h 00mMicroservices, Where Did It All Go Wrong?
48mIT Architecture : All your micro-services are wrong PERIOD!
57mEmbracing Microservices
43mHow to Avoid Doing Microservices Completely Wrong
59mDecomposition Patterns
44mMicroservices, Where Did It All Go Wrong
01h 00mPrinciples for Building MicroServices