You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can see, one needs SSR when wanting to release features to only some of one's users, for example only logged in users should get the new features, or only 10% of the users, etc. We are using this all the time to make sure we make stuff that users actually use.
The problem with this is of course not being able to take advantage of caching of static pages, i.e. it will be a small number of variants for each page which actually should be easy to cache.
Does anybody have a good solution in Next.js for this use case?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
For info on feature toggles: https://en.wikipedia.org/wiki/Feature_toggle
As far as I can see, one needs SSR when wanting to release features to only some of one's users, for example only logged in users should get the new features, or only 10% of the users, etc. We are using this all the time to make sure we make stuff that users actually use.
The problem with this is of course not being able to take advantage of caching of static pages, i.e. it will be a small number of variants for each page which actually should be easy to cache.
Does anybody have a good solution in Next.js for this use case?
Beta Was this translation helpful? Give feedback.
All reactions