-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat(flags): Enable caching for resilient responses #13708
Conversation
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.
Great shout!
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.
Minor comments
@@ -15,4 +16,5 @@ | |||
"Role", | |||
"RoleMembership", | |||
"EnterprisePropertyDefinition", | |||
"FeatureFlagRoleAccess", |
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.
@liyiy this is the reason when running tests locally you'd get the ee_ffroleaccess
table doesn't exist, even when it existed in the test db. Wasn't registered in django
@EDsCODE lmk if you have any pending comments, will merge this now so I can babysit in Cloud. |
This reverts commit 0a1831b.
Problem
Part of #13601
In this PR:
Introduce caching of team and feature flags. This allows for zero downtime on decide when postgres goes down.
What's in a follow up:
Changes
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
How did you test this code?
Lots of unit tests.
Also, run locally, check decide, make database go down, see decide still works.