Download as PDF, PPTX
Uploaded byAdam L Barrett
Server side rendering for any JS framework
The document discusses server-side rendering (SSR) for JavaScript frameworks, outlining its functionality, benefits, and a specific project involving SSR and incremental rendering. It also raises concerns about the practicality of SSR, suggesting there may be better alternatives such as HTTP2 and service workers. A recap emphasizes the pros and cons of using SSR and introduces a tool called Velocirender for implementing it.
![[CocoaHeads Tricity] Michał Zygar - Consuming API](https://cdn.slidesharecdn.com/ss_thumbnails/chmichazygar-consumingapi-150706113126-lva1-app6891-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Server side rendering for any JS framework
- 1. SERVER-SIDE RENDERING for anyJS Framework
- 2. WHAT IS SSR? Server-SideRendering
- 3. 3 THINGS TODAY •Talk about what SSR is and how it works • Talk about our project (SSR any SPA and incremental rendering) • Talk you out of using it… (no really)
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 14.
- 17.
- 18.
- 19.
- 20.
- 21. BUT, DON’T USEIT…? 😈
- 22.
- 23.
- 24. IT SOLVES AVERY PARTICULAR PROBLEM 😈
- 25. DON’T SSR ATALL…? 😈
- 26. ARE THERE BETTEROPTIONS? 😈
- 27.
- 28.
- 29.
- 30.
- 31. WHY SSR ATALL…? 😈
- 32. WHEN YOU CANJAM? 😈
- 33. 😈 Did you justmake this up?
- 34.
- 35. QUICK RECAP • Wetalked about SSR, the benefits and how it works • We talked about Velocirender, the easiest way to add SSR and incremental rendering to your SPA • We talked about why you most likely shouldn’t be SSR’ing at all!
- 36. QUESTIONS? SERVER-SIDE RENDERING For anyJavaScript Framework @adamlbarrett BigAB