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

Learn from top reviewers

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?

24 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 HCL Zen Edge Data Management?

HCL Zen Edge Data Management (formerly Actian Zen) is a NoSQL and SQL (fully ANSI compliant) embedded database that runs on Windows, Linux, Android, iOS, macOS, in VMs and Containers with AES 256-bit encryption. Version footprints range from 5MB (client only) to 50 MB (embedded client-server) to…

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 Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-5 of 7)

No SQL Database to Support Near Real Time Analytics

Rating: 8 out of 10
April 19, 2018
HBase was used in my previous organization(PayPal) where we needed a database for storing and retrieving records in near real time. It was used within consumer analytics and other sub-teams. It supported our near real-time use analytical cases by proving a faster lookup of records with consistency reads/writes. Apart from that, helped in querying the records much faster than other NoSQL databases.
  • Faster lookup of records using the row keys. It helped to fetch thousands of records in a much faster way using the row keys
  • As it is a columnar data store, helped us to improve the query performance and aggregations
  • Sharding helps us to optimize the data storage and retrieval. HBase provides automatic or manually sharding of tables.
  • Dynamic addition of columns and column family helped us to modify the schema with ease.
Cons
  • Identified issues with Hmaster when handling a huge number of nodes
  • Cannot have multiple indexes as row key is the only column which could be indexed.
  • HBase does not support partial row keys which limit its query performance.
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.

HBase, The Only Enterprise NoSQL Choice

Rating: 10 out of 10
April 06, 2018
HBase is being used by multiple organizations and internally it is used company-wide. it solves a large range of problems and provides unique solutions when we need a NoSQL store.

HBase provides the best of breed solutions for any NoSQL storage needs. One of the main important features is it is part of the HDP Hortonworks stack so it is installed by default so there's nothing else to install or configure. It is easy to administer with Ambari and scales to any size I need. It runs on top of HDFS so my data is safe, secure and scalable.

I use it as a store for data that is ingested via various streaming mechanisms including Apache NiFi, Apache Storm, Apache Spark Streaming, Apache Flink and Streaming Analytics Manager. It provides an easy key-value type store with fast scans for data access. I also run Apache Phoenix on top to provide a fast clean SQL interface to all of my data.
  • 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.
Cons
  • Not for small data
  • Requires a cluster
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.

Support for HBase

Rating: 7 out of 10
April 04, 2017
It is used as a data store that consolidates the updates from the upstream key-value store where upstream store only stores the updates that meet the high qps and low latency. HBase is the secondary layer of the storage that consolidate all the updates for a given row key and serves as a upstream for hive table.
  • Good write throughput
  • Good horizontal scalability
  • Easy to operate on
Cons
  • Better tool for investigating the key-value content for data validation.
  • Better tool for row key monitoring since our key contains timestamps.
  • Better tool for system-level metric monitoring.
Not good for extremely low latency online application, in particular read heavy app.

HBase

Rating: 10 out of 10
September 13, 2017
Vetted Review
Apache HBase
3 years of experience
HBase solves problems of scalability and management of multi-terabyte applications. It makes scaling to +1 nodes very easy, especially through Ambari. It is built with fault tolerance and availability in mind. You can use it on a single node but it shines on multi-node infrastructure. With high data access speed and resiliency, I wouldn't recommend any other NoSQL database for general use.
  • HBase data access and retrieval only gets better with larger scale.
  • Fault tolerance is built in, if you have unreliable hardware, HBase will make every effort to keep your data online.
  • Extremely fast key lookups and write throughput.
Cons
  • Multi-tenancy is still work in progress
  • Usability and beginner friendliness
  • It has a bad reputation of being complex
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.

HBase - good for UI performance from a Hadoop cluster

Rating: 7 out of 10
April 14, 2017
ZR
Vetted Review
Verified User
Apache HBase
3 years of experience
HBase makes it possible to provide sub-second UI responsiveness when querying very large data sets. This is in contrast to something like Hive, which could take many minutes.
  • Very fast query capability
  • Resilient: by leveraging hdfs, hbase can handle server failure pretty well
Cons
  • Very schema dependent - you have to carefully choose your schema and key strategy in order to get good distribution and performance.
  • Over aggressive rebalancing - if you have to bounce your system - for example - hbase will spend quite a while trying to rebalance all the data as each server comes online.
When you need very fast query responsiveness from very large data sets
Return to navigation