Server-side rendering with Angular—be faster and more SEO, CDN and user-friendly!
summary
Server-side rendering with Angular claims to deliver richer HTML and a faster first meaningful paint while offloading rendering to Node so pages and bots get full content; setup uses ng toolkit or the official CLI schematics, an Express + ngExpress engine, and a transfer state cache to avoid duplicate API calls. Implementations include a filesystem translate loader for ngXTranslate, HTTP interceptors, a half‑second watchdog to skip slow APIs, and deployment to AWS lambda (cold starts up to ~1 minute); examples and articles are linked.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:11Outline
- 3:16Common SPA problem
- 5:03Server Side Rendering
- 6:46Angular Universal
- 8:00How to start?
- 9:09Adjust your modules
- 11:08Under the hood
- 13:36Browser vs Server
- 14:31is server? is browser?
- 15:04Wrapper services
- 17:30Server/Browser specific code
- 18:09Server/Browser specific elements
- 21:42HttpCache Module
- 22:20HTTP_INTERCEPTOR
- 28:24It's not only SSR
- 30:57Let's go Serverless!
- 34:07Summary
related talks
24mAngular 2 Server Side Rendering
28mServer-side rendering with Angular 2
26mServer Side Rendering with Angular Universal
22mAngular Pre Rendering for SEO, Speed, and Happy Users
21mStrategies for Server Side Rendering Angular Applications
15mA journey to Server Side Rendering with Angular
19mA plethora of rendering ideas
51mThe Jedi Path to Angular Universal