What users are saying about
30 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
178 Ratings
30 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.1 out of 100

Redis

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
178 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.9 out of 100

Likelihood to Recommend

HBase

Hbase is well suited for large organizations with millions of operations performing on tables, real-time lookup of records in a table, range queries, random reads and writes and online analytics operations.Hbase cannot be replaced for traditional databases as it cannot support all the features, CPU and memory intensive. Observed increased latency when using with MapReduce job joins.
Vinaybabu Raghunandha Naidu | TrustRadius Reviewer

Redis

Redis is great at at reducing your reliance on SQL and the cost associated with running a SQL infrastructure.We have been able to scale out and improve performance on database requests. Reliability has also great improved over running a SQL infrastructure
Anonymous | TrustRadius Reviewer

Feature Rating Comparison

NoSQL Databases

HBase
7.7
Redis
8.3
Performance
HBase
7.3
Redis
9.2
Availability
HBase
7.8
Redis
8.7
Concurrency
HBase
6.8
Redis
8.5
Security
HBase
7.7
Redis
6.8
Scalability
HBase
8.3
Redis
8.6
Data model flexibility
HBase
7.8
Redis
8.0
Deployment model flexibility
HBase
8.5
Redis
8.2

Pros

HBase

  • Scalability. HBase can scale to trillions of records.
  • Fast. HBase is extremely fast to scan values or retrieve individual records by key.
  • HBase can be accessed by standard SQL via Apache Phoenix.
  • Integrated. I can easily store and retrieve data from HBase using Apache Spark.
  • It is easy to set up DR and backups.
  • Ingest. It is easy to ingest data into HBase via shell, Java, Apache NiFi, Storm, Spark, Flink, Python and other means.
Timothy Spann | TrustRadius Reviewer

Redis

  • 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.
David Sommers | TrustRadius Reviewer

Cons

HBase

  • There are very few commands in HBase.
  • Stored procedures functionality is not available so it should be implemented.
  • HBase is CPU and Memory intensive with large sequential input or output access while as Map Reduce jobs are primarily input or output bound with fixed memory. HBase integrated with Map-reduce jobs will result in random latencies.
RAVI MISHRA | TrustRadius Reviewer

Redis

  • 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.
Eric Mason | TrustRadius Reviewer

Likelihood to Renew

HBase

HBase 8.3
Based on 10 answers
There's really not anything else out there that I've seen comparable for my use cases. HBase has never proven me wrong. Some companies align their whole business on HBase and are moving all of their infrastructure from other database engines to HBase. It's also open source and has a very collaborative community.
Anonymous | TrustRadius Reviewer

Redis

Redis 9.6
Based on 12 answers
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.
Rahul Chaudhary | TrustRadius Reviewer

Usability

HBase

No score
No answers yet
No answers on this topic

Redis

Redis 8.3
Based on 3 answers
Redis has been around for very long and it is good at what it does. It proved to be very valuable in my use case for interfacing between two applications with very little code as it has drivers for almost every language out there and the community support is really good.
Anonymous | TrustRadius Reviewer

Support

HBase

No score
No answers yet
No answers on this topic

Redis

Redis 7.6
Based on 2 answers
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.
Gene Baker | TrustRadius Reviewer

Implementation

HBase

No score
No answers yet
No answers on this topic

Redis

Redis 7.3
Based on 1 answer
Whitelisting of the AWS lambda functions.
Anonymous | TrustRadius Reviewer

Alternatives Considered

HBase

Cassandra os great for writes. But with large datasets, depending, not as great as HBASE. Cassandra does support parquet now. HBase still performance issues. Cassandra has use cases of being used as time series. HBase, it fails miserably. GeoSpatial data, Hbase does work to an extent. HA between the two are almost the same.
Anson Abraham | TrustRadius Reviewer

Redis

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.
Anonymous | TrustRadius Reviewer

Return on Investment

HBase

  • As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data.
  • Not having the feature of primary or a composite primary key is an issue as the architecture to be defined cannot be the same legacy type. Also the transaction concept is not applicable here.
  • The way data is printed on console is not so user-friendly. So we had to use some abstraction over HBase (eg apache phoenix) which means there is one new component to handle.
Bharadwaj (Brad) Chivukula | TrustRadius Reviewer

Redis

  • 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.
Anonymous | TrustRadius Reviewer

Screenshots

Pricing Details

HBase

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Redis

General

Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Optional

Rating Summary

Add comparison