Server Side Rendering from the trenches
summary
Claims SSR speeds first meaningful paint and improves SEO and accessibility, and shows React, Vue, Next and Nuxt examples plus the concrete tradeoffs of running client code on Node. Describes the universal addons.mozilla.org build (React + Redux, i18n, CSP), bugs encountered—double render vs getInitialProps, encoding and back‑button glitches, random ID and locale leaks—how tests expose them, and operational cost: cluster sizing jumps from 8 to 40 servers because renderToString blocks the event loop.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:27Xml Httprequest
- 4:06Facebook Released React
- 4:42Flux
- 8:36What Are the Benefits of Doing Server-Side Rendering
- 11:11Drawbacks
- 13:44Data Fetching before Rendering
- 17:04Server Code
- 23:54Internationalisation and Localization
- 24:57Double Render
- 27:25Secondary Data
- 30:02Error Handling
- 40:43Security Consideration
related talks
30mServer Side Rendering — The Eyes Fear, the Hands Do- 30mServer Side Rendering: Scared Eyes, Working Hands
04mA few things to know about SSR
21mImplementation and use cases of modern rendering patterns
45mGive Me Back My Frontend!
08mLightning fast SSR React apps with top perceived performance and no (client side) JavaScript
06mDemystifying server-rendered React apps: Performance & Security
30m50 shades of React rendering with Next.js