-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DO NOT MERGE] chore: FE caching (Redis) #525
base: main
Are you sure you want to change the base?
Conversation
|
||
const globalBanner = await getGlobalBanner() | ||
const getBanner = cache(getGlobalBanner) | ||
const getFlag = cache(getFeatureFlag) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does the workflow for this look like when we wanna switch a flag in the FE, is it something like:
- Switch flag
- Flush caches
- Restart containers
But what if the flag value is cached in the frontend cache between steps 1 and 2? Does that mean when we flush caches, the CDN crawler will hit the frontend showing the stale value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arguably the crawler always fills the redis cache first so there would be enough time between the 2. So maybe this is okay
Quality Gate passedIssues Measures |
Description
cross-fetch
14.2.14
cache
and parallel requests in root layout, homepage and dynamic page rendererssr: false
flag for dynamic import