[sylvain_kerkour]

Honestly? I believe that the new hype of Server Side Rendering (SSR) frameworks is only a matter of vendor lock-in: when you have SSR, you *NEED* edge rendering, which only a few vendors can provide today.

Single Page Applications (SPA) are totally fine. My blog is an SPA (https://kerkour.com) and has no problem being indexed by the major search engines.

It's actually way faster than most webapps using new shiny new SSR frameworks as I can cache with precision the different chunks/assets.

Finally, everything is served from a server than barely uses more than 50 MB of RAM even under high load. Last time I looked, Next apps needed around 500MB-1GB of RAM to serve only a few visitors.

[listenallyall]

Your web site is serving up static, pre-rendered content. Further, it's actually more SSR-ish than SPA -- each request for a blog post returns the new page, except it is encoded as a JSON object which your front-end must interpret and convert to HTML, instead of just returning the updated HTML fragment itself.

[report-to-trees]

Why would you need edge rendering for ssr? What's wrong with a regular server?

[IanHalbwachs]

>has no problem being indexed by the major search engines

Naively, I never really questioned that SSR was better for SEO; what about your app do you attribute its successful indexing to?

[plugin-baby]

> Next apps needed around 500MB-1GB of RAM to serve only a few visitors.

Not sure why you’re getting downvoted - your comment seems to add valid points like this to the discussion.