Extracting a microservice from a 15-year-old monolith: a one-year adventure
summary
A team describes extracting a microservice from a 15-year-old monolith, covering the full year-long process. They explain moving from an initial modular split to solving transaction boundary breaks, handling SQL JOINs, and mitigating async API latency by using event-driven architecture, redesigning the data model, and adding an integration layer.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:16Extracting chat module
- 7:40Breaking monolith links
- 16:04Splitting SQL queries
- 27:53Splitting transactions
- 37:20New service extraction
- 40:51Recommendations and summary
- 41:33Q&A
related talks
32mSplitting the monolith
01h 03mFrom Monolith to Microservices: Story and Practice
48mMicroMonolith
29mMoving from A and B to ~150 microservices, the journey and learnings
41mThe six obstacles of moving to microservices and how to deal with them
54mFrom a distributed monolith to a microservices solution
42mQ&A - Monolith to Microservices
36mMicroservices Lessons Learned
