Thirty months of microservices
summary
Thirty months of experience turning legacy estates into a landscape of ~120 small components that each own their data and can be deployed independently; started from 18 million lines of COBOL and a 3.5M-line Visual Basic monolith, pulled functionality out into tiny services, and built CI pipelines for 120 repositories. Concrete lessons: split by bounded contexts using DDD, give each service its own storage (polyglot persistence), automate tests and delivery (developers as testers), and expect a long setup phase before the hockey‑stick speedup.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:20About Sander
- 3:35Monolithic applications
- 4:52The two neighbors
- 5:38Dependencies
- 8:02Integration
- 9:25Microservices
- 11:03History of microservices
- 14:39Definition of microservices
- 22:47The problem
- 26:28Guiding principles
- 28:07Architecture
- 29:57Design
- 32:01Unified Data
- 34:34Single Business Capability
- 36:34Postal Slow
- 41:24Deployment
related talks
45mDesigning, building, testing and deploying microservices
23mOn the road from Monolith to Micro
32mSplitting the monolith
01h 03mThe Magic of Small Things - 10 Years of Microservices
51mBig microservices, small team a painful story
45mBuilding and evolving microservices: lessons from the frontlines
48mMicroMonolith
48mExtracting a microservice from a 15-year-old monolith: a one-year adventure