Feature Description
As a user, I want to create multiple Vitess clusters which are geo-sharded altogether, and specifying which keyspaces I want to be replicated and sharded.
Use Case(s)
As an example, I have a Vitess clusters in the EU, but for performances purposes, I want to deploy a Vitess cluster in the US continent. Some of the keyspaces needs to stay locally and not sharded (such as temporary logs, data specific to the region), some of them needs to be materialized (ex: data injected by a master cluster (EU for exemple) where you’re creating new data and needed to be accessible on other clusters), and some of them needs to be geo-sharded/replicated (example: users, as a Twitch streamer, I want users to connect into a session wherever they are and to the closest access endpoint possible).
Feature Description
As a user, I want to create multiple Vitess clusters which are geo-sharded altogether, and specifying which keyspaces I want to be replicated and sharded.
Use Case(s)
As an example, I have a Vitess clusters in the EU, but for performances purposes, I want to deploy a Vitess cluster in the US continent. Some of the keyspaces needs to stay locally and not sharded (such as temporary logs, data specific to the region), some of them needs to be materialized (ex: data injected by a master cluster (EU for exemple) where you’re creating new data and needed to be accessible on other clusters), and some of them needs to be geo-sharded/replicated (example: users, as a Twitch streamer, I want users to connect into a session wherever they are and to the closest access endpoint possible).