SSR cache example is now completly different

[macrozone]

What example does this report relate to?

examples/ssr-caching

What version of Next.js are you using?

11.x

What version of Node.js are you using?

12.x

What browser are you using?

chrome

What operating system are you using?

mac os

How are you deploying your application?

next start

Describe the Bug

The ssr example used to use cacheable-response.

the goal was to cache expensive server side rendering, so subsequent requests could be served from cache.

Many users might require this as switching to static generated pages is not always feasible, as is using a cdn cache.

The new example does not mention anything about ssr caching, it just explains some browser caching. I think that could also be used by CDN, but the example does not mention anything like that.

This is probably because vercel wants to push their own hosting, so alternatives get obfuscated.

This is also apparent when you look at this short discussion that got closed by vercel without providing any explanation: #26540

Expected Behavior

i expect nextjs contributors to not change examples to something completly different and to explain decisions, instead of just closing issues.

I expect to have a ssr-caching example like it previously was that does not require additional knowledge and services.

I expect that when architectural changes like this should be needed, that we get a description to go from the previous approach to the new one

To Reproduce

just check out the example, it won't work like it previously did.

[jukbot]

Agreed with you, the new one got a different approach, I think cacheableResponse is flexible enough to do some pre-calculated response from LRU cache. The document is lacking information when using CDN or the usage of cache strategy.

The new approach should be separated into the new one since the behavior is different from the previous one. The previous one aims to cache globally to all visitors which reduces the cost of computed response, by the way, cacheableResponse can cache responses one by one using the cache key.

In my opinion, the goal of #26540 is the fix from #12019 and striped out additional dependency when working with SSR caching.

[balazsorban44]

The example has been changed because with a custom server, you opt out of many features of Next.js and so it is actively not recommended to use. We will probably not add custom server examples going forward.

From the docs:

Before deciding to use a custom server, please keep in mind that it should only be used when the integrated router of Next.js can't meet your app requirements. A custom server will remove important performance optimizations, like serverless functions and Automatic Static Optimization.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.