Strangling The Monolith: Applied Patterns & Practices From The Trenches
summary
A nine‑year modernization at Flixbus moves a monolith from 170k to 11.2M LOC and 12 to 175 developers into an iterative migration using a five‑step process: Wardley mapping and domain modelling, team topologies and explicit ownership, behavioral + static analysis, collaborative API design with event storming, and a Strangler facade implemented with a transactional outbox and observability (OpenTelemetry traces). The approach incrementally replaces components, keeps legacy in sync via events, and proves effective though slow and error‑prone in practice.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:56Small History Tour
- 5:18MVC
- 11:28Anemic Domains
- 16:50Weak Boundary
- 22:23Feedback Loops
- 26:54New Path
- 27:34FiveStep Improvement Process
- 31:04Wadley Mapping
- 38:57Team Topologies Domain Driven Design
- 42:08InverseConvey maneuver
- 49:48Static code analysis
- 53:49Collaborative Discovery
- 55:01Trace Use Case Entry Points
- 56:27Rich Models
- 57:10Strength
related talks
47mFrom Monolith to Microservices With the Strangler Pattern
28m193 Easy Steps to DevOpsing Your Monolith
32mSplitting the monolith
52mTools to Slay the Fire Breathing Monoliths in Your Enterprise - Kelapure, Anderson, Szodfridt
07mMonolith to over 60 Services
48mMicroMonolith
23mOn the road from Monolith to Micro
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
