Google's Cloud Bigtable is a fully managed, scalable NoSQL database service for large analytical and operational workloads with up to 99.999% availability.
$0.03
per month
Redis™*
Score 9.0 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.
Google Bigtable is ONLY suited for massive data sets which scale PetaBytes and TerraBytes. Anything under this can easily be done via dedicated VMs and open source tools. Google Bigtable is expensive and shall be used wisely. It should be utilised only where it is well suited else you would simply be wasting dollars and not utilizing its full benefits.
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.
Analytics: is at Google's heart. No on can beat Google in this space and BigTable is one of its implementation of this. The insights you gain from BigTable are simply usable in your day to day activities and can help you make real difference.
Speed: Processing TBs and PBs of data under minutes needs real efficient platform which is capable of doing much more than just processing data. All this data cannot be processed by a single machine, but rather huge pairs of machines working in conjuction with each other. BigTable's implementation is one of the finest and allows you achieve great speeds!
Interface: is great. Google has segregated required task under logically placed buttons which takes no time by users to understand and get habituated.
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.
User interface's responsiveness: I understand so much is going on under the hood, but laggyness is acceptable if a workload is running or being processed. In case their is not workload being process, GUI should work blazing fast. I have faced this at times, and this becomes frustrating as well.
Nothing other than this - BigTable is quite efficient platform and does exactly what it is built for.
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.
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.
For big IT firms like us, data is very important and it only holds its value if it can make sense to us. Therefore, Bigtable's usability is priceless when it comes to decision making based on data.
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.
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.
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.
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.
