Skip to main content
TrustRadius
HBase

HBase

Overview

What is HBase?

The Apache HBase project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable.

Read more
Recent Reviews

TrustRadius Insights

HBase has established itself as a crucial tool for various organizations, including PayPal, to store and retrieve records in near real …
Continue reading

HBase

10 out of 10
September 13, 2017
Incentivized
HBase solves problems of scalability and management of multi-terabyte applications. It makes scaling to +1 nodes very easy, especially …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 7 features
  • Availability (5)
    7.8
    78%
  • Security (5)
    7.8
    78%
  • Performance (5)
    7.1
    71%
  • Concurrency (5)
    7.0
    70%
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is HBase?

The Apache HBase project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

20 people also want pricing

Alternatives Pricing

What is MarkLogic Server?

MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. The vendor states it is the most secure multi-model database, and it’s deployable in any environment. They state it is an ideal database to power a data hub.

What is Couchbase Capella?

The Couchbase Capella product is a fully managed DBaaS automating setup and ongoing operations.

Return to navigation

Product Demos

Apache Hbase Tutorial | Hadoop Hbase | Hbase Training | Intellipaat

YouTube
Return to navigation

Features

NoSQL Databases

NoSQL databases are designed to be used across large distrusted systems. They are notably much more scalable and much faster and handling very large data loads than traditional relational databases.

7.7
Avg 8.8
Return to navigation

Product Details

HBase Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

The Apache HBase project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable.

Reviewers rate Scalability highest, with a score of 8.6.

The most common users of HBase are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(32)
Loading...

Attribute Ratings

Reviews

(1-10 of 10)
Companies can't remove reviews or game the system. Here's why
RAVI MISHRA | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
While we have a variable schema with slightly different rows and when you are going for a key dependent access to our stored data, we prefer to use HBase. No requirement of relational features. If we do not need features like transaction, triggers, complex query, complex joins etc. then go for HBase.
December 14, 2018

An Amazing Experience

Bharadwaj (Brad) Chivukula | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Suited for storing bulk data in a tabular manner, I would recommend Hadoop HBase, but for a small amount of data, I personally would not suggest the use of this tool. We are moving from a traditional file system to a Hadoop file system, and to store the data in a tabular manner, we are using HBase. As the data is increasing day by day, the need to manage the same is also required, which is incorporated by Hadoop.

December 13, 2018

HBASE!!!

Anson Abraham | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
It does depend on the use case scenario. It works really well if your schema doesn't really need relational features. It's really good for that. If you want to run as transactional, not a good idea. Relational analytics is not good for this, as well as edge network data. If you're using PB of data, then HBASE is best suited in this case as well.
Vinaybabu Raghunandha Naidu | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
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.
Timothy Spann | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
ResellerIncentivized
HBase is well suited for streaming ingest, fast lookups, massive datasets, data warehouse lookup tables, RDBMS replacement, MongoDB replacement, key-value store, data scans, logs, JSON storage and some binary storage.

My preferred use case is for storing data points like time series or data produced by sensors.

I often use HBase when I need data available immediately and I am not looking for transactions. This is a great store for really wide tables with tons of columns. It is also great if you are not sure what type of data you are going to have. It really excels at sparse data.
September 13, 2017

HBase

Score 10 out of 10
Vetted Review
ResellerIncentivized
HBase typically fits well in low latency, tight SLA scenarios. It is not recommended to be used in situations where a relational database would fit better. So in essence, if you're trying to do a lot of analytical workloads or joins, HBase wouldn't fit so well. If primary key access is sufficient, then HBase is a good fit.
Rekha Joshi | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
The key questions I ask when choosing NoSQL distributed database:

  • What is the application's inherent need? Does this component fit well in the design?
  • Does it provide high data security?
  • How does it assure there is no data loss?
  • How can I make sure it is a highly available system, and no downtime for customer?
  • Does it give me the best linear scalability?
  • What kind of tuning parameters does it allow the user to configure?
  • How does it stack up against other NoSQL variants on features, scalability, ease of use/contribute to and maturity of product?
  • What throughput can it attain under different kinds of workloads?
Return to navigation