Running JS on the Server at Scale — What Can Go Wrong
summary
Describes problems encountered when moving rendering from server-side HTML to client-side JavaScript at LinkedIn, focusing on performance trade-offs for users with slow networks, older browsers, or weak devices. Explains the architectural shift to servers delivering data while markup is rendered and cached on the client or at the edge, and discusses practical issues and mitigations for making client-side rendering work at scale.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:09Infrastructure evolution
- 9:08JS server challenges
- 15:57Performance bottlenecks
- 22:30JS pitfalls
- 26:31Sandboxing & security
- 28:49Memory leaks & GC
- 31:58Execution optimization
- 33:19Architecture overview
- 33:47Q&A
related talks
32mJavaScript on the Server: To Be or Not To Be?
56mThe Inevitability of the Thin Client
47mAdventures in Rendering Off the Main Thread
44mServer Side Rendering from the trenches
33mRendering on the Web: Performance Implications of Application Architecture
39mTowards Universal JavaScript
25mServer-side JavaScript the untold story
04mA few things to know about SSR