Feature: Geographically spread cluster via Kubernetes

[itsezc]

Is your feature request related to a problem?

While there is a Kubernetes deployment guide, this doesn't cover how Surreal could be deployed in a geographically distributed way.

Describe the solution

A clear guide and best practices for how Surreal could be deployed in a Kubernetes cluster that is geographically separated, perhaps at a database and namespace level.

This could be blocked by functionality within Surreal and dependent on the storage backend used, namely TikV and soon SurrealKV.

Alternative methods

N/A

Contact Details

No response

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[itsezc]

Now that SurrealKV is in the picture, this now becomes a little more interesting. The ideal deployment now should be SurrealKV running as PODs and SurrealDB running on a separate POD in cluster mode, again geographically spread out.