Server side routing - No SSR routes

[PEM--]

Event if it's feasible to setup routes with contents only rendered on the client using the asymetricSsr HOC, these routes create specific cached payloads per route. This increases memory usage and server CPU occupation while these routes could be served far more efficiently if they were tagged properly.

[cbilotta]

I suggest we make three "levels" :

1. SSR + initialState.
2. Only initialState (So, tree-walking for data etc, still, but no html rendering).
3. No SSR, no initialState.

What do you think ?

[j-jackson]

Sorry for the noob question guys, but would this mean you could potentially have something like /admin as normal client side react, and then all your public facing routes using SSR?

[PEM--]

@j-jackson As stated in the description, you can already do it with asymetricSsr. This enhancement concerns the cache handling to avoid filling it with already rendered HTML payload.