-
Notifications
You must be signed in to change notification settings - Fork 186
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
Deploying Flagr Architecture #139
Comments
The flagr image or flagr binary with static UI asset has everything you need to run, which includes "Flagr Manager" and "Flagr Evaluator". Analytics is not included here, since I can't assume everyone's data pipeline. For scalable installation, you can deploy as many as flagr nodes as you want behind a load balancer, for example, Kubernetes' DNS, or nginx gateway. Moreover, every node can serve the traffic for both evaluation and CRUD. |
Brilliant! Would you recommend deploying this image as a DaemonSet in K8s? |
Good catch! I originally planned to use Redis, but in production, directly read from the DB works for our scale without problems - it's a periodic read with eager loading, and most DB already has the cache for this use case, so I didn't implement the Redis cache yet, which also means one less dependency. Will update the figure in the doc soon. |
Thanks for the information. Is it possible to share the scale you are able to serve with this approach? |
Of course, here are some stats in our production
Definitely try it out and benchmark it on your end. |
Thank you very much for your help and information. |
Flagr Architecture references many components: UI, Flagr, Sync Worker, Evaluator, ...
https://checkr.github.io/flagr/#/flagr_overview?id=flagr-architecture
However, the doc about deployment and configuration is about a single docker image that seem to correspond to the Flagr Manager tier.
It is possible to deploy a scalable installation as the one described in this document?
Where can I find any documentation on how to do so?
Thanks
The text was updated successfully, but these errors were encountered: