Skip to content
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

Implement a highly available metadata store #1784

Open
2 of 6 tasks
Tracked by #1675
tillrohrmann opened this issue Aug 5, 2024 · 2 comments
Open
2 of 6 tasks
Tracked by #1675

Implement a highly available metadata store #1784

tillrohrmann opened this issue Aug 5, 2024 · 2 comments
Assignees

Comments

@tillrohrmann
Copy link
Contributor

tillrohrmann commented Aug 5, 2024

To make Restate fully highly available, we also need the metadata store to be highly available. We either find a kv store that provides us with linearizable reads and writes or we need to build it ourselves.

Tasks

Preview Give feedback
  1. muhamadazmy
  2. 0 of 7
  3. igalshilman
  4. bug
  5. documentation
  6. 1 of 7
    tillrohrmann
@tillrohrmann
Copy link
Contributor Author

DynamoDB does not seem to work as a geo replicated highly consistent external meta data store. The problem is that there is no synchronous replication between table running in different regions (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_HowItWorks.html).

@tillrohrmann
Copy link
Contributor Author

What might work for an external metadata store is Google Cloud Spanner (not working for AWS), Azure Cosmos DB with strongest consistency settings (not working for AWS) (https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels) or CockroachDB (https://cockroachlabs.cloud/).

@tillrohrmann tillrohrmann self-assigned this Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant