Goodbye Microservices, Hello Self-Contained Systems
summary
Argues that replacing brittle microservices with larger Self-Contained Systems simplifies migration of a 20+-year Eclipse RCP Java 8 monolith by keeping UI logic and data together, using SymmetricDS replication to denormalize and copy product/customer data, a link database plus single sign‑on for cross-app navigation, Spring Boot, ActiveMQ and Oracle for services, and Vaadin web components for a unified look. Claims 7–8 year phased rewrite avoids synchronous coupling and works in the current wholesale rollout.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:07Software architecture evolution
- 3:14Microservices misconceptions
- 8:36Modularity vs distribution
- 14:33Self-contained systems intro
- 21:00Communication styles in self-contained systems
- 26:49Advantages of self-contained systems over microservices
- 31:03Wholesale company case study
- 36:01Migration with Strangler Fig
- 40:21Conclusion
related talks
47mSay Goodbye to Microservices, Say Hello to Self-Contained Systems
12mTen Things I Hate About Microservices
33mFrom Enterprise Architecture to Software Design - Critical Thinking
36mJava: Microservices...decisions, decisions, decisions everywhere
32mSplitting the monolith
55mIs it Time to Abandon Microservices? Modular Monoliths Rescue Your Wallet!
45mMonolith to Microservices: Modularizing Fineract 1.x
40mSOD Microservices - Daniel Jones, EngineerBetter