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

Apache HBase vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 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
11th
Average Rating
7.2
Reviews Sentiment
5.1
Number of Reviews
4
Ranking in other categories
No ranking in other categories
InfluxDB
Ranking in NoSQL Databases
6th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), Network Monitoring Software (13th), IT Infrastructure Monitoring (14th)
 

Mindshare comparison

As of May 2026, in the NoSQL Databases category, the mindshare of Apache HBase is 5.2%, down from 5.8% compared to the previous year. The mindshare of InfluxDB is 5.2%, down from 9.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
InfluxDB5.2%
Apache HBase5.2%
Other89.6%
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.
Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.

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."
"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."
"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."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"My advice for others looking into using InfluxDB is to use it the same way I did, because it is really stable, easy and friendly to use, and it is a great product overall."
"It helps me maintain my solution easily because it is very reliable, so we didn't face any performance issues or crashes regarding our queries; we can get the results very fast."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"InfluxDB positively impacts my organization because I have optimized my database storage, and by using powerful queries, I am able to find my data logs efficiently and also manage logging."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"Overall, InfluxDB delivered excellent performance, stability, and simplicity for telemetry-driven use cases."
 

Cons

"I don't like using Apache HBase to store huge amounts of data because of many performance issues."
"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."
"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."
"The error logging capability can be improved because the logs are not very informative."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"The solution doesn't have much of a user interface."
"The solution doesn't have much of a user interface."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"The solution's UI can be more user-friendly."
"I haven't seen a return on investment; unfortunately, I cannot share relevant metrics such as time saved, fewer employees needed, or money saved."
 

Pricing and Cost Advice

Information not available
"InfluxDB is open-source, but there are additional costs for scaling."
"InfluxDB recently increased its price. It is very expensive now."
"The tool is an open-source product."
"We are using the open-source version of InfluxDB."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
892,646 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Comms Service Provider
9%
University
9%
Educational Organization
7%
Financial Services Firm
13%
Manufacturing Company
10%
Comms Service Provider
9%
Construction Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
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 needs improvement with InfluxDB?
InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage. InfluxDB is not suitable for relational databases lik...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is storing a time series database and analyzing data changes over time. I use InfluxDB to store my infrastructure and application metrics, logs, events, and data, and ...
What advice do you have for others considering InfluxDB?
I would advise others looking into using InfluxDB that if they want to store a time series database for monitoring, logging, and event-based tasks, and also want long-term retention of the database...
 

Comparisons

 

Also Known As

HBase
No data available
 

Overview

 

Sample Customers

Bloomberg, Wells Fargo, Apple, Capital One, NVIDIA
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Apache HBase vs. InfluxDB and other solutions. Updated: April 2026.
892,646 professionals have used our research since 2012.