Google Cloud Spanner vs. Redis™*

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Google Cloud Spanner
Score 6.3 out of 10
N/A
Google Cloud Spanner is a cloud database-as-a-service product offered as a service on Google Cloud Platform (GCP).N/A
Redis™*
Score 9.0 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.
$388
per month
Pricing
Google Cloud SpannerRedis™*
Editions & Modules
No answers on this topic
Cloud
$388.00
per month
Offerings
Pricing Offerings
Google Cloud SpannerRedis™*
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
Google Cloud SpannerRedis™*
Top Pros
Top Cons
Features
Google Cloud SpannerRedis™*
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
Google Cloud Spanner
7.8
2 Ratings
11% below category average
Redis™*
-
Ratings
Automatic software patching8.82 Ratings00 Ratings
Database scalability8.82 Ratings00 Ratings
Automated backups10.01 Ratings00 Ratings
Database security provisions5.82 Ratings00 Ratings
Monitoring and metrics5.82 Ratings00 Ratings
Automatic host deployment7.62 Ratings00 Ratings
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Google Cloud Spanner
-
Ratings
Redis™*
9.2
69 Ratings
5% above category average
Performance00 Ratings10.069 Ratings
Availability00 Ratings9.069 Ratings
Concurrency00 Ratings9.068 Ratings
Security00 Ratings8.063 Ratings
Scalability00 Ratings9.469 Ratings
Data model flexibility00 Ratings9.962 Ratings
Deployment model flexibility00 Ratings9.362 Ratings
Best Alternatives
Google Cloud SpannerRedis™*
Small Businesses
SingleStore
SingleStore
Score 9.7 out of 10
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
Medium-sized Companies
SingleStore
SingleStore
Score 9.7 out of 10
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
Enterprises
SingleStore
SingleStore
Score 9.7 out of 10
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Google Cloud SpannerRedis™*
Likelihood to Recommend
7.4
(2 ratings)
8.0
(76 ratings)
Likelihood to Renew
-
(0 ratings)
8.7
(12 ratings)
Usability
-
(0 ratings)
8.2
(5 ratings)
Support Rating
-
(0 ratings)
8.7
(5 ratings)
Implementation Rating
-
(0 ratings)
7.3
(1 ratings)
User Testimonials
Google Cloud SpannerRedis™*
Likelihood to Recommend
Google
Google Cloud Spanner is suited for limitless horizontal scaling while maintaining strong consistency which needs to support ACID. NoSQL databases work in scaling but no ACID support. RDBMS support ACID, but horizontal scaling is not as great. The API it provides result in some limitations to related areas of the code, such as connection pools or database linking framework. So high # of connection pools can vary.
Read full review
Redis Labs
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
Read full review
Pros
Google
  • Super high availability
  • Scales automatically
  • High standard SLA
Read full review
Redis Labs
  • 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
Google
  • Support for Views
  • Support for more databases (schemas).
  • More index types that can be supported (Functional)
  • Backups (ie table/data backup) if data is deleted or truncate by accident.
Read full review
Redis Labs
  • We had some difficulty scaling Redis without it becoming prohibitively expensive.
  • Redis has very simple search capabilities, which means its not suitable for all use cases.
  • Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
Read full review
Likelihood to Renew
Google
No answers on this topic
Redis Labs
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
Google
No answers on this topic
Redis Labs
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
Google
No answers on this topic
Redis Labs
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
Google
No answers on this topic
Redis Labs
Whitelisting of the AWS lambda functions.
Read full review
Alternatives Considered
Google
At that point, we were looking at something [that] can hold our relational database, [...] provide stable connection, and maintain high ACID transition. BigTable is for nonrelational database so it was out of our [sight] very quickly. BigQuery is a data warehouse that can hold huge amount of data but not ideal for transition. AWS RDS is [...] similar to Spanner but because most of our services are already on GCP, so we went with Spanner.
Read full review
Redis Labs
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
Read full review
Return on Investment
Google
  • Backups specifically if transactional data is deleted. Restoring made us lose time.
  • Sharding on Horizontal level was quick and easy. Deployment and increasing nodes is easy
  • Large dataset handling.
  • ACID compliance
Read full review
Redis Labs
  • Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
  • Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
  • Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
Read full review
ScreenShots

Redis™* Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of