No more typing reviews! Try our Samantha, our new voice AI agent.

Apache HBase vs Redis comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

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
12th
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
3rd
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (4th), AI Software Development (9th)
 

Mindshare comparison

As of September 2026, in the NoSQL Databases category, the mindshare of Apache HBase is 5.0%, down from 5.4% compared to the previous year. The mindshare of Redis is 8.0%, down from 8.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.0%
Apache HBase5.0%
Other87.0%
NoSQL Databases
 

Featured Reviews

Ephrem Sisay - PeerSpot reviewer
Senior Software Engineer at a computer software company with 501-1,000 employees
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.
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.

Quotes from Members

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

Pros

"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 most valuable part is the column family structure."
"Apache HBase is a database used for data storage."
"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."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"The online interface is very fast and easy to use."
"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 use Redis efficiently."
"The solution is fast, provides good performance, and is not too expensive."
"Redis is good for distributed caching management."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"Redis is a simple, powerful, and fast solution."
"The product offers fast access to my database."
 

Cons

"I don't like using Apache HBase to store huge amounts of data because of many 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."
"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."
"There is a lack of documentation on the scalability of the solution."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources."
"It's actually quite expensive."
"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."
"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."
"Making management easier, especially for teams operating large Redis clusters, would be helpful."
"The first challenge is memory limitations, as Redis is primarily in-memory, making memory usage a key constraint."
 

Pricing and Cost Advice

Information not available
"Redis is not an overpriced solution."
"Redis is an open-source product."
"The tool is open-source. There are no additional costs."
"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.
913,683 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Comms Service Provider
14%
University
7%
Construction Company
7%
Financial Services Firm
22%
Computer Software Company
9%
Comms Service Provider
7%
University
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
 

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 primary use case for Apache HBase?
We are using Apache HBase as a lookup database for queries that require doing lookups on customer data and eligibility checks for different kinds of customers. The customer data is stored in the Ap...
What needs improvement with Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

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: September 2026.
913,683 professionals have used our research since 2012.