Architecting a Seamless E-commerce Platform Transition
summary
Migration uses Adobe Commerce / Magento, Redis, RabbitMQ, Elasticsearch, Composer, Fastly and New Relic and targets AWS PaaS with specific cutover steps and rollback. Discovery finds exotic PHP extensions, oversized Redis (example causes 32 GB hot cache), and a 500 GB database with ~400 GB of removable logs leading to reduced DB from 500GB to 100GB. Team shift from dev-led to architect-reviewed planning reduces surprises; operational rules include move data server-to-server and scale up source node for faster transfer.
AI-written summary · about
chapters (7)
- 0:00E-commerce migration intro
- 3:48Adobe Commerce Cloud overview
- 5:39Migration flow evolution
- 11:28Discovery process deep dive
- 15:10Cutover plan execution
- 18:26Pitfalls and optimization tips
- 23:29Summary & Q&A
related talks
22mOptimization strategies for a performant, headless storefront
28mStories of Success: Merchant Panel
17mElevating Developer Experience at the Speed of Sound
41mA Developer’s Survival Guide for the Microservices Era
12mMaking commerce. Faster.
07mAccelerating Composable Commerce with Strapi
35mFlip the Switch Slowly
01h 06mRewriting Legacy Code