Hello, I also have a question about scaling but on...
# ask-the-community
Hello, I also have a question about scaling but on a different axis -- what is the expected way to scale Flyte servers horizontally. I can see that scaling the workers can be done by having multiple K8S clusters, but if I have millions or billions of workflows and the primary database and server get overwhelmed, is there a way to shard them? Or do I simply need to have multiple Flyte deployments at that point?
At the moment the core reader database is single
But remember the entire state is stored in etcd, so as you add more k8s clusters you are indeed sharding the state db
We think large number of workflows at runtime only impact the state store, if you need you can share the execution storage service, but that would be needed at very high rate
Happy to jump on a call to discuss
Awesome thanks. I think this is all I need.