Say Goodbye to Microservices, Say Hello to Self-Contained Systems
summary
Argues self-contained systems beat microservices for business apps by bundling UI, logic and storage into larger, autonomous slices; implements an ERP migration using Java and Vaadin, splitting domain into bounded contexts with teams of ~4–5 per SCS. Uses event-based replication and read-only replicated databases with denormalized, contract-driven data copies to avoid synchronous calls and n+1 client problems; prototype UI links across apps, eventual consistency accepted, migration estimated ~7 years but yields independent deploys and simpler ops.
AI-written summary · about
chapters (11)
- 0:00Self-contained systems intro
- 3:54Microservices adoption problems
- 10:14Team size and architecture
- 13:27Avoiding distributed mud
- 18:46Self-contained systems intro
- 21:16Key differences from microservices
- 24:50Communication patterns
- 27:23Team autonomy and modularity
- 31:22Advantages of self-contained systems
- 34:12Monolith modernization
- 45:48Conclusion & Q&A
related talks
43mGoodbye Microservices, Hello Self-Contained Systems
52mI Have a Microservices Architecture and I Didn't Know.
23mWhy You Had a Bad Time With Microservices
26mPros/Cons of Microservices
44mSelf Contained Systems: The Good, the Bad & the Ugly
52mMicroservices & the Inverse Conway Maneuvre
36mJava: Microservices...decisions, decisions, decisions everywhere
44mPragmatic Microservices