-
Notifications
You must be signed in to change notification settings - Fork 812
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
docstore/gcpdatastore: Add support for Google Firestore in Datastore mode #2713
Comments
Quoting: https://cloud.google.com/datastore/docs/firestore-or-datastore
Which is why I chose it. Since one would expect this Go package to mostly be used on servers, I think Datastore is something that would benefit many. |
Firestore in Datastore mode is the correct mode for most server applications, and is a closer match to the other DBs supported by https://cloud.google.com/datastore/docs/firestore-or-datastore#choosing_a_database_mode
|
It looks like the APIs supported for Datastore mode vs Native mode are completely independent (https://cloud.google.com/datastore/docs/firestore-or-datastore#feature_comparison). So this is basically a request for a new |
example.zip
Is your feature request related to a problem? Please describe.
The docstore API cannot be used with Google Cloud Firestore in Datastore mode.
The
docstore/gcpfirestore
driver is not sufficient for this -- trying to results in an error:See the attached example program.
It uses GCP application default credentials.
It expects a GCP project name in the
GCP_PROJECT_NAME
environment variable.Describe the solution you'd like
A driver implementation for Google Cloud Firestore in Datastore mode.
Describe alternatives you've considered
Using a different backing service or cloud provider.
Additional context
The GCP Firestore documentation mentions Native Mode has a limit of 10k writes/s.
This makes it unsuitable for write-heavy workloads at certain scales.
While Docstore Mode does not have an exact figure for it's upper writes/s limit it indicates the limit isn't as low.
The text was updated successfully, but these errors were encountered: