MicroMonolith - Top anti-patterns of distributed systems

on YouTube ↗43m

" summary

Migration from an eight‑year monolith to hundreds of microservices reduces deploy time from 60+ minutes to ~5–10 and enables 400+ daily releases, but reveals concrete anti‑patterns: micro‑monolith, synchronous integration over HTTP, and one DB to rule them all. Practical fixes include introducing a message bus, moving toward database‑per‑service (table/schema first), isolating payment flow, using Greg Young’s EventStore (misused as a message bus early on), and building a custom AWS cost‑monitoring and control pipeline to rein in runaway cloud spend.

AI-written summary · about

" chapters (7)

1. 0:00Introduction and context
2. 2:16Transformation process
3. 6:02Avoiding common pitfalls
4. 11:22Solving integration issues
5. 20:37Database strategies
6. 26:28Controlling cloud costs
7. 31:24Conclusion and Q&A

" related talks

• 48mMicroMonolithMichal Franc · Codemotion Amsterdam 2017
• 53mDon’t Build a Distributed Monolith: How to Avoid Doing Microservices WrongJonathan "J." Tower · NDC Porto 2023
• 43mHow to Avoid Doing Microservices Completely WrongJonathan "J." Tower · Update Conference Krakow 2025
• 42mQ&A - Monolith to MicroservicesSam Newman, Sven Johann · GOTO Oslo 2020
• 01h 04mDon’t Build a Distributed MonolithJonathan "J." Tower · NDC London 2023
• 54mFrom a distributed monolith to a microservices solutionJan de Vries · NDC Sydney 2020
• 01h 03mFrom Monolith to Microservices: Story and PracticeKonstantin Gustov · DotNext 2018 Moscow
• 01h 03mMicroservices vs The Distributed MonolithChris Riley · PHP UK Conference 2024