Rethinking composable E-Commerce Frontends
summary
Argues for a Post‑SPA e‑commerce frontend that renders HTML on the server with a tiny JSX runtime (nanoweb), serves via Fastify/Node, and wires partial updates to the browser with Hotwire and web components to preserve client state. Shows a running Velocity storefront and connectors to Shopify, Algolia and more, reports ~4–5x faster page renders than Next.js, ~18,075 requests/sec on one node, 58 KB JS bundles and 100 PageSpeed on mobile.
AI-written summary · about
chapters (15)
- 0:00Composable e-commerce frontends
- 1:36Composable architecture today
- 3:40Problems with hybrid frontends
- 5:05Challenges of modern single-page apps
- 6:53State of composable frontends
- 10:22Rethinking server-side rendering for speed
- 12:09Velocity platform concept
- 13:32Optimizing SSR performance
- 17:04HTML over the wire with Hotwire
- 20:34ThoughtWorks on Hotwire
- 21:16Web components for state
- 24:29Proposed architecture demo
- 26:41Personalization via server logic
- 28:29AI product recs demo
- 29:35Closing & Q&A
related talks
45mNext js: Build a State of the Art E commerce in Fullstack React
41mLow-budget JavaScript: composable frontends that are fun and friendly
32mWhy you don’t need a Single Page App
30mComposition, Caching, and Architecture in modern
12mMaking commerce. Faster.
29mQuo vadis, frontend?
51mMicrofrontends and UI Composition - a Code-First Dive
50mComposable decoupled frontends: the Jamstack and beyond