MicroMonolith

on YouTube ↗48m

" summary

A team migrates a .NET monolith with one huge database and ~20–30 engineers into hundreds of services over a few years, cutting a 60‑minute deployment cycle to daily releases but creating a tangled distributed monolith where services call one another synchronously. Root causes include synchronous HTTP integration, a single relational DB forcing shared schemas, and lack of domain boundaries. Practical fixes: RabbitMQ messaging, CDC from the DB to build per‑service read stores, eventual consistency and schema‑per‑service migrations.

AI-written summary · about

" chapters (6)

1. 0:00Introduction to the topic
2. 5:12Legacy system transformation
3. 11:12Anti-pattern: Micromonolith
4. 21:34Integration strategies
5. 28:50Managing distributed data
6. 37:19Conclusion and Q&A

" related talks

• 43mMicroMonolith - Top anti-patterns of distributed systemsMichal Franc · NDC Oslo 2016
• 42mQ&A - Monolith to MicroservicesSam Newman, Sven Johann · GOTO Oslo 2020
• 54mFrom a distributed monolith to a microservices solutionJan de Vries · NDC Sydney 2020
• 23mOn the road from Monolith to MicroChristoph Moser · WeAreDevelopers Conference Vienna 2016
• 32mSplitting the monolithJimmy Bogard · LeadDev Austin 2019
• 42mDo proper monoliths before you do microservices!Jan de Vries · Future Tech 2019
• 36mDo Proper Monoliths before You Do Microservices!Jan de Vries · DevDays Europe 2019
• 35mLegacy Monolith to MicroservicesSmit Thakkar · DevConf.CZ 2019