Yes, you are correct for stateless workloads. For stateful workloads, you are correct, we would need to have multiple volume replication, which is something we don't have at the moment. This is why we have the HA templates to let you have those follower replicas be geo synced.

However, I think we can do something here- I am raising this thread to the developer of this feature but candidly I think we will need a lot of work to do on our storage story.

- Angelo

Thanks Angelo, this is what I figured.

However, not quite sure I understand this:

> This is why we have the HA templates to let you have those follower replicas be geo synced

Are you saying the followers can serve read requests and are load balanced via request geo? Or did I misunderstand this? My assumption was that the HA templates are multi-region for availability reasons, not for actually serving geo-load-balanced traffic.

You are correct, but you could, in-theory, modify the config where the shards are serving traffic and then you attempt to sync the state of the data post facto. (Easier said than done.)

Long story short, expect to see more of our Geo-HA offerings.