A Failed Project and the Technical Architecture That Saved It
summary
A multimillion transformation stalls after 2.5 years and a barely working festival checkout. Rescue replaces the tight Salesforce–Sitecore coupling with Salesforce as master record, strips Sitecore to CMS and auth, and adds React components in Sitecore backed by an API and consolidated on SQL Server for legacy and transactional data with AutoFix just-in-time sync to decouple systems. The e-commerce checkout is rebuilt in ~4 months, ships two months early, and each component remains independently deployable so legacy parts can be retired.
AI-written summary · about
chapters (4)
- 0:00Start
- 3:07What Could Possibly Go Wrong
- 5:53Architectural Principle
- 6:48Describe Architecture Principles
related talks
17mMaintaining performance across a highly dynamic commerce site
51mCompleting the Rewrite from Hell: Five Years of Technical Debt and How We Escaped
46mHow to escape Legacy Hell
22mOptimization strategies for a performant, headless storefront
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
18mMaking what you have enough
16mYou Can't Outrun Complexity - But You Can Orchestrate It.
27mBig Rewrite Strikes Again