Search code examples
javascriptnext.jsserver-side-renderingastrojs

Does Astro js fallback to SSR when cache is not available?

In Next.js, when the cache is not available Next.js is going to SSR the page and show it (based on the preferred fallback approach true or blocking).

I wonder what approach Astro.jd takes in this scenario. I'm going to create a dynamic blog website and users can create blogs rapidly.

Do I have to build the static pages each time or it's better to take Astro.js SSR approach?

Solution

  • Astro does not cache the SSR, the rendering modes are fixed from the start

    • SSG Mode : all pages are static, so you need rebuild to update, not suited for a dynamic blog and permenent access to users.
    • SSR Mode : all pages are dynamic and built on fetch time.
    • hybrid mode : is SSR but you can fix some pages to be static.

    It is possible to think of ideas and suggestions but for a clear answer to the question, Astro does not fallback on cache as there's no such Incremental Static Regeneration or Incremental build as of Today but could be something for the future.

    The hybrid mode is quite useful when you have a highly dynamic site, and yet you want to have great seo performance on some pages that do not need to change like landing page or some fixed doc.

    Note that after all the difference between SSG and SSR is the caching, so you could

    • CDN caching pages as mentioned by TheOtterlord
    • custom caching : you decide on your own which content does not require a new fetch and can be stored locally.

    Custom caching, depending on your deployment you could do this in memory for maximum performance or in files, but these solutions can't run in serverless.

    References