Cache for Commerce Performance and Optimization for High Volume Sales
summary
Architecture uses Next.js server rendering with serverless functions and CDN caching to cut load times while keeping correctness. Pages and some APIs use the stale-while-revalidate header (set via getServerSideProps) so cached HTML serves instantly and background revalidation updates the CDN. Practical numbers: content uses 120s / 1 day limits, product APIs stay uncached while client refreshes inventory via react-query 60s, and sales flip to 10s max-age to avoid blink — approach proves fast and usable.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:08Caching and Commerce
- 3:04Cache Overview
- 4:36stale-while-revalidate
- 10:47Caching for Content
- 14:16Caching for Products
- 18:15Caching for Sales
- 21:51Headless Commerce and CDN Cache
related talks
15mDon't Go South With Next.js Caching – Supercharging Performance
16mHigh-speed personalization with Next.js
08mAdvanced SSR Caching with React
25mCaching strategies on https://dev.to
21mCaching GraphQL APIs
29mLove your cache: Optimize for the second load
22mOptimally using third-party services with Next.js
12mNext.js, BigCommerce & the Future of Performance in Ecommerce