React SSR in the Wild: yes, we can (when we should)
summary
Describes building a production e‑commerce site for pharmacies using React + Redux server‑side rendering (SSR) instead of prerendering, with webpack/Babel for bundling and caching via Redis and materialized views. Covers practical pitfalls and fixes: protecting initial state from XSS, handling SSR performance tradeoffs (single‑threaded rendering and bundle size), and reports concrete benefits such as 98.5% shared code and delivery by a four‑person team.
AI-written summary · about
chapters (9)
- 0:00Start
- 7:27Isomorphic, universal...?
- 15:58Rendering
- 16:57SSR Routing Example
- 21:10State Management
- 24:10Configuration Module
- 25:36Performance API
- 26:40Client Performance
- 28:35Bundle Optimization
related talks
44mServer Side Rendering from the trenches
25mServer-side Rendering with ReactJS: Win or Lose
30mServer Side Rendering — The Eyes Fear, the Hands Do
25mThe Costs & Benefits of React Server Components
12mReact Server Components and SSR: How it Fits
30mServer Side Rendering: Scared Eyes, Working Hands
30m50 shades of React rendering with Next.js
08mAdvanced SSR Caching with React
