Try our new research platform with insights from 80,000+ expert users

Apache HBase vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 14, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Apache HBase
Ranking in NoSQL Databases
10th
Average Rating
7.2
Reviews Sentiment
5.1
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Redis
Ranking in NoSQL Databases
7th
Average Rating
8.8
Reviews Sentiment
5.7
Number of Reviews
23
Ranking in other categories
Managed NoSQL Databases (9th), In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (10th)
 

Mindshare comparison

As of December 2025, in the NoSQL Databases category, the mindshare of Apache HBase is 5.1%, up from 4.8% compared to the previous year. The mindshare of Redis is 8.7%, up from 2.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Market Share Distribution
ProductMarket Share (%)
Redis8.7%
Apache HBase5.1%
Other86.2%
NoSQL Databases
 

Featured Reviews

Ephrem Sisay - PeerSpot reviewer
DevOps Engineer (M-PESA) at Safaricom Ethiopia plc
In-memory processing and integration capabilities have optimized query performance
Apache HBase could be improved by optimizing the integration with Apache Phoenix; sometimes the abstraction and lookup jobs lead to issues when there are too many requests. Resource optimization isn't always as successful as it should be, which can cause some query and lookup jobs to fail. For instance, during eligibility checks for credit, if there are many requests on the database, it might fail, and after such a failure, it doesn't allow us to run queries from the moment they stop. If there could be optimization to require less resource usage and allow those jobs and queries to pick up from where they stopped, that would be a great addition to the tool.
reviewer2005650 - PeerSpot reviewer
Data Engineer at a photography company with 1,001-5,000 employees
Optimize AI projects with reliable data processing while addressing scaling challenges
There are a few areas where Redis could improve. The pub-sub capabilities could be optimized to handle network sessions better, as there are challenges with maintaining sessions between clients and systems. Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active. There's a need for better migration tools to support data movements in a hybrid environment. Concerns exist about licensing and community engagement due to changes in Redis and its forks.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable part is the column family structure."
"The in-memory processing lets us optimize our queries and helps us run concurrent queries and other jobs such as the lookup jobs we always use Apache HBase for."
"Apache HBase is a database used for data storage."
"The in-memory processing lets us optimize our queries and helps us run concurrent queries and other jobs such as the lookup jobs we always use Apache HBase for."
"The best features of Apache HBase include being embedded, making it very fast; when it's linking, it operates with virtually no delay, and all of the queries are very fast too due to some internal optimization which makes it very sufficient and efficient."
"I use Redis mostly to cache repeated data that is required."
"Redis has multiple valuable features such as being a free and reliable open-source tool."
"It is particularly efficient for cloud-based storage and operations."
"Redis is a simple, powerful, and fast solution."
"Redis is good for distributed caching management."
"The ability to fetch and save data quickly is valuable."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"Redis acts as an in-memory search tool that improves the speed of operations."
 

Cons

"Apache HBase could be improved by optimizing the integration with Apache Phoenix; sometimes the abstraction and lookup jobs lead to issues when there are too many requests."
"Apache HBase could be improved by optimizing the integration with Apache Phoenix; sometimes the abstraction and lookup jobs lead to issues when there are too many requests."
"We've seen performance issues."
"The setup of Apache HBase needs a lot of time, and the linkage is not the program itself, but the activation and connecting to the NYPD engine always takes considerable time."
"I don't like using Apache HBase to store huge amounts of data because of many performance issues."
"For the PubSub feature, we had to create our own tools to monitor the events."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"Redis presents a single point of failure and lacks fault tolerance."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"It's actually quite expensive."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
 

Pricing and Cost Advice

Information not available
"The tool is open-source. There are no additional costs."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"Redis is an open-source solution. There are not any hidden fees."
"We saw an ROI. It made the processing of our transactions faster."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
879,259 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Manufacturing Company
10%
Comms Service Provider
9%
Computer Software Company
9%
Financial Services Firm
26%
Computer Software Company
11%
Comms Service Provider
7%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise3
Large Enterprise8
 

Questions from the Community

What needs improvement with Apache HBase?
Apache HBase could be improved by optimizing the integration with Apache Phoenix; sometimes the abstraction and lookup jobs lead to issues when there are too many requests. Resource optimization is...
What advice do you have for others considering Apache HBase?
I'm working for a corporate that uses Apache HBase for their Big Data platform and I'm a Big Data engineer there. We're using a version of Apache HBase that is compatible with the other Big Data to...
What is your experience regarding pricing and costs for Apache HBase?
The cost depends on the EC2 instances and the size of the data you're indexing.
What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
The disadvantage of Redis is that it's a little bit hard to have too many clusters or too many nodes and create the clusters. The sync between the nodes is easier to implement with Couchbase, for e...
What is your primary use case for Redis?
Redis is used for a part of a booking engine for travel, specifically for the front part to get some sessions and information about the sessions. If a customer or user is using the sites in differe...
 

Comparisons

 

Also Known As

HBase
Redis Enterprise
 

Overview

 

Sample Customers

Bloomberg, Wells Fargo, Apple, Capital One, NVIDIA
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about Apache HBase vs. Redis and other solutions. Updated: December 2025.
879,259 professionals have used our research since 2012.