Bol.com and the Accelerated Legacy Challenge
summary
Bol.com moves a monolith to a managed-service architecture by strangling pieces out, duplicating only the interfaces teams need and deprecating parts once callers migrate. Concrete example: the product domain splits into an ingest/process/perform pipeline, using Oracle and JMS historically but letting teams pick the best tech per stage to handle Black Friday spikes. Key claims: focus on the system’s role in context, use strangler pattern with data sync, build small services, migrate callers incrementally and kill deprecated modules when traffic drops.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:30Metaphor of Dorian Gray
- 2:19What is Legacy
- 3:14Why do we get Legacy
- 4:07Bolcom history
- 4:37The accelerator legacy
- 5:31Why legacy doesnt work
- 7:16The process
- 10:20The service architecture
- 12:36Legacy mindset
- 13:37Dont fear legacy
related talks
24mModernise your monolith using strangler pattern
43mPatterns of Legacy Displacement
23mOn the road from Monolith to Micro
23mDevOps and Legacy Code
43mBeyond Strangler Fig: Effective Patterns for Architectural Modernization
01h 29mMonolithic Delivery
58mLegacy modernization made practical: A live coding example of modernization patterns
18mUnlocking Value from Legacy Technology