Google Cloud Datastore
Rating: 7 out of 10
IncentivizedUse Cases and Deployment Scope
We're using Google Cloud Datastore as part of an application deployed to Google AppEngine, which is all running entirely in the Google Cloud Platform. Since our application is using Google AppEngine, we wanted to use a datastore which was simple to set up and didn't require managing servers or deployments/configurations for. Because Google Cloud Datastore is part of the Google Cloud Platform, it really simplified billing and management.
Pros
- Automatically handles shards and replication.
- Schema-less & NoSQL.
- Fully managed.
Cons
- Part of the Google Cloud Platform walled garden.
- Pay for read/writes to the datastore, in addition to storage.
- Not many libraries exist.
Likelihood to Recommend
Using Google Cloud Datastore in conjunction with Google AppEngine was a very seamless integration and much easier than using other datastores since so much of the configuration is abstracted for you. Because of this, creating simple applications is very easy and getting Google Cloud Datastore to power the backend ties everything together. If we were using Google Compute Engine, I'd imagine the same seamless experience would be there as well.
Vetted Review
4 years of experience