Learn to live with a legacy monolith (or not)
summary
Practical strategies for living with and improving legacy monoliths without a big-bang rewrite: discusses refactoring, testing, and progressive migration techniques to evolve toward better architectures. Covers approaches from micro to macro design, showing realistic, incremental solutions and examples in multiple programming languages to avoid repeatedly replacing monoliths with new “v2/v3” monsters.
AI-written summary · about
chapters (17)
- 0:00Learn to live with a legacy monolith (or not)
- 0:53What this talk is about
- 9:17How we managed to stabilize the platform
- 12:06The problem of slow delivery
- 14:32How we messed up with Cake
- 18:01New task
- 19:15White labels
- 20:47System evolution
- 25:11How to make it a success story
- 26:31General log
- 30:06New acquisitions
- 31:20The competition
- 33:33The synchronizer
- 38:27The problem
- 40:39Tip 3: DB triggers
- 43:48Tip 4: Domain events
- 44:50Talk summary
related talks
23mDevOps and Legacy Code
52mMy Monolith Is Really Cool
01h 03mFrom Monolith to Microservices: Story and Practice
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
49mWhat Does a Legacy System Teach Us?
43mHow to Innovate in a Legacy
52mOMG, What a Beautiful Legacy
41mLegacy, for lack of a better word, is good