How to escape Legacy Hell
summary
Shows a concrete migration path: replace customer-facing pages first with a new PHP front end (three months of dev, half a year to launch), route via chain of responsibility (nginx fallback) and cache rendered pages in redis cache, then extract services using CQRS and branch by extraction, move basket and checkout incrementally, use events for eventual consistency. Legacy Magento remains the datastore during transition. Result is a much faster site and a legacy system that becomes a backend only — the approach proves practicable.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:55Hooray. It's a monolith!
- 15:50Chain of Responsibility
- 21:46Branch by Abstraction
- 24:46Reverse the coupling?
- 25:46Events to the rescue?
- 27:53Mind the Leaves
- 33:15Escape Plan
related talks
11mThe monster under the bed - working with legacy code
47mFrom Legacy to High-Load: Evolution of a Web Application
36mTransforming a PHP Team into PWA Superheroes
43mCustomer-Focused Replatforming of an Existing Shop Monolith
22mOptimization strategies for a performant, headless storefront
11mA Failed Project and the Technical Architecture That Saved It
17mMaintaining performance across a highly dynamic commerce site
33mSPAs, full-stack, micro-frontends, enterprise migrations, what the quack?