Delivering commerce experiences at scale
summary
Performance tests run on an AEM Venia site using the Commerce Integration Framework to a headless Adobe Commerce Cloud (GraphQL + Fastly) show that concrete config changes prevent publisher overload and 503s under surge traffic. Key fixes: set max http connections = 200, switch CIF GraphQL requests to GET to enable Fastly caching, use stat file level = 4 with grace period = 2s, ignore marketing URL params, cache expensive GraphQL components (navigation 100 entries/10m, search 100/1h), enable origin shielding and image proxying, and consider MySQL read slaves or split-tier nodes for heavy load.
AI-written summary · about
chapters (10)
- 0:00Introduction to project
- 1:06Commerce integration framework
- 3:56Caching strategy planning
- 5:59AEM dispatcher optimizations
- 11:36AEM publisher optimizations
- 14:43Adobe Commerce optimizations
- 17:11Infrastructure optimizations
- 20:00Load balancer settings
- 21:24Split tier architecture
- 22:07Conclusion and resources
related talks
17mMaintaining performance across a highly dynamic commerce site
44mTop 10 Tips to Speed Up Your Adobe Experience Manager Site
28mUnderstand GraphQL API performance options and query optimizations
36mPerformance tuning in EC site with GraphQL
01h 00mBuilding next gen composable services with Experience Manager
24mCache for Commerce Performance and Optimization for High Volume Sales
36mMake It Fast
45mSurviving a Prime Time TV Commercial