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.

Sign up for GitHub

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

Jump to bottom

Assess backend database options #8

Closed
olivercodes opened this issue Jul 27, 2023 · 2 comments
Closed

Assess backend database options #8

olivercodes opened this issue Jul 27, 2023 · 2 comments
Labels
PSK-TEAMS-API

Comments

@olivercodes
Copy link
Member

olivercodes commented Jul 27, 2023 •
edited
Loading

Assess whether DynamoDB is right choice. Could be a managed service backend (that's on the cluster, for example)

Everybody ships SQL, for example
Or POSTgres local to cluster, Mongo local cluster, etc.

OSS options as well

TiKV / TiDB
Vitess

Related to #2
@olivercodes olivercodes added the enhancement New feature or request label Jul 27, 2023
This was referenced Jul 27, 2023
Closed
Open
@olivercodes olivercodes added PSK-TEAMS-API and removed enhancement New feature or request labels Aug 4, 2023
@olivercodes
Copy link
Member Author

Came to the conclusion that using GORM https://github.com/go-gorm/gorm is the best option. This allows us to consume just about any major database protocol without code changes.

For Global availability, the open source database options are CockroachDB and YugabyteDB. For a vendor specific approach, there's DynamoDB, GCP Spanner, and Azure CosmosDB.

@olivercodes
Copy link
Member Author

Update to global available db's

Google Cloud SQL. AWS Aurora v2 (global, and postgres compat). Azure Database for Postgres.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
PSK-TEAMS-API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@olivercodes