Choosing a Rendering Architecture
This page helps you pick the right rendering strategy for your project. For detailed descriptions of each approach and their trade-offs, see Rendering Architectures.
Decision Guideโ
Pick the default based on product type first (app vs content), then adjust only if specific requirements demand it.
- Start with CSR (SPA) for highly interactive applications like dashboards or admin panels where SEO is not a concern.
- Choose SSR when pages require per-request personalization, real-time data, or user-specific content that can't be pre-built.
- Use Islands (Astro) when you need selective interactivity on an otherwise static site. See Astro.
- Use SSG for content sites, docs, blogs, and marketing pages when your pages can be pre-built.
tip
Modern frameworks let you combine strategies within a single project. Use the strategy that fits each route's needs, and mix CSR/SSR/Islands/SSG where appropriate.
Project Recipesโ
For practical implementations of these rendering strategies, see the project cookbooks:
- React SPA on Cloud Run โ client-side rendered CRUD application with REST API
- React SPA with Firebase โ client-side rendered app with Firebase BaaS
- Astro Starlight on GitHub Pages โ static documentation site with SSG