Google Cloud Datastore vs. Redis Software

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Google Cloud Datastore
Score 8.5 out of 10
N/A
Google Cloud Datastore is a NoSQL "schemaless" database as a service, supporting diverse data types. The database is managed; Google manages sharding and replication and prices according to storage and activity.N/A
Redis Software
Score 8.4 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.N/A
Pricing
Google Cloud DatastoreRedis Software
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Google Cloud DatastoreRedis Software
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
Google Cloud DatastoreRedis Software
Features
Google Cloud DatastoreRedis Software
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Google Cloud Datastore
10.0
Ratings
12% above category average
Redis Software
8.6
Ratings
3% below category average
Performance10.00 Ratings9.00 Ratings
Availability10.00 Ratings7.00 Ratings
Concurrency10.00 Ratings9.00 Ratings
Security10.00 Ratings8.00 Ratings
Scalability10.00 Ratings9.00 Ratings
Data model flexibility10.00 Ratings9.00 Ratings
Deployment model flexibility9.90 Ratings9.00 Ratings
Best Alternatives
Google Cloud DatastoreRedis Software
Small Businesses
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Google Cloud DatastoreRedis Software
Likelihood to Recommend
9.9
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
8.7
(0 ratings)
Usability
-
(0 ratings)
9.0
(0 ratings)
Support Rating
-
(0 ratings)
8.7
(0 ratings)
Implementation Rating
-
(0 ratings)
7.3
(0 ratings)
User Testimonials
Google Cloud DatastoreRedis Software
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.
Read full review
Perfect solution for caching needs. If you have a bottleneck due to frequent data access to your database, then Redis can really help you by diverting those traffic away from your database. Its key/value pair structure also makes data lookup very efficient, providing excellent performance.
Read full review
Pros
  • It is hosted in GCP, our primary cloud provider.
  • It integrates with all the services we use in GCP.
Read full review
  • Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
  • Reliable. With a proper multi-node configuration, it can handle failover instantly.
  • Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
  • Fast. We process tens of thousands of RPS and it doesn't skip a beat.
Read full review
Cons
  • Part of the Google Cloud Platform walled garden.
  • Pay for read/writes to the datastore, in addition to storage.
  • Not many libraries exist.
Read full review
  • Redis is super fast but it comes with a cost. Whole dataset resides in RAM. So it can be costly as primary memory is more costly, then secondary ones.
  • Persistence issues: To achieve it, Redis uses a memory dump to create a persistence snapshot, that's cool. But it requires some Linux Kernel tweaking to avoid performance degradation while the Redis server process is forking. This further causes latency.
  • Master-slave structure side effect: Master-slave architecture comes with its own side effects. Please note that there will be only one master with multiple slaves for replication. All writing goes to the master, which creates more load on the master node. So, when the master goes down, the whole architecture does.
Read full review
Likelihood to Renew
I give Google Cloud a full score because it satisfies our needs so well. We host most of our infrastructure on Google Cloud and using Google Cloud Datastore helps us to solve our NoSQL storage problem. and Google Cloud Datastore is so scalable and elastic. It saves us lots of time to maintain and saves us money.
Read full review
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
Read full review
Usability
No answers on this topic
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
Read full review
Support Rating
No answers on this topic
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
Read full review
Implementation Rating
No answers on this topic
Whitelisting of the AWS lambda functions.
Read full review
Alternatives Considered
We selected Google Cloud Datastore as one of our candidates for our NoSQL data is because it is provided by Google Cloud, which fits our needs. Most of our infrastructure is on Google Cloud, so when we think about the NoSQL database, the first thing we thought about is Google Cloud Datastore. And it proves itself.
Read full review
UI isn't that great compared to the other competitors. The management of our memcached cluster was becoming pretty complicated as the application grew in size. Redis is a much better option compared to memcached. Redis is bit unreliable compared to the alternative RabbitMQ especially when it needs to be integrated with Celery.
Read full review
Return on Investment
  • Simple billing part of Google Cloud Platform
  • No time spent configuring and maintaining Google Cloud Datastore.
  • Very good uptime for our applications.
Read full review
  • Existing tools like Redisson that were built over Redis reduced dev time in solving challenging problems, which had a positive impact on ROI.
  • We initially misused Redis for persistent storage which had a negative impact on ROI because we were paying a lot for inactive users.
  • The increased performance we achieved using Redis in areas like locking helped us improve the performance of our system reducing the likelihood of system timeouts.
Read full review
ScreenShots

Redis Software Screenshots

Screenshot of Database configurationScreenshot of Database metricsScreenshot of DatabasesScreenshot of NodesScreenshot of Alerts