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 9)

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.

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!!!

Rating: 8 out of 10
December 13, 2018
AA
Vetted Review
Verified User
Apache HBase
5 years of experience
HBase is used as part of the company's main revenue generating platform. We're using it store data with usages of mapreduce, generates locational information for advertising business and location analytics. Storage wise, it made sense to use HBASE over Cassandra, as well as for read performance with avro data with geospatial information in the data
  • Excellent for read performance
  • Great store of file format of avro
  • Easy integration into mapreduce
  • Replication ability
Cons
  • Write performance
  • Performance support for parquet file format. supports, but performance wise still not there
  • API / library availability for spark, rather than creating a new library for it
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.

HBase as the brother of big data

Rating: 7 out of 10
March 16, 2019
RM
Vetted Review
Verified User
Apache HBase
3 years of experience
I use HBase because it is a NoSQL database and it is open sourced and can store big data. We can store any structured, semi-structured and unstructured data easily. One other major benefit is, it is a columnar database so no need to specify any schema. I generally use it when I store the streaming data, the analysis is also faster after connecting the HBase with Spark. HBase is a mature database so we can connect HBase with various execution engine and other component using JDBC.
  • HBase stores the big data in a great manner and it is horizontally scalable.
  • Another major reason is security, we can secure the HBase database using Atlas, Ranger.
  • Store any format of data like structured, semi-structured and unstructured.
  • Consistency
  • Strongly consistent reads and writes are provided by HBase, we use it for high-speed requirements if we do not need RDBMS-supported features such as full transaction support or typed columns.
Cons
  • There are very few commands in HBase.
  • Stored procedures functionality is not available so it should be implemented.
  • HBase is CPU and Memory intensive with large sequential input or output access while as Map Reduce jobs are primarily input or output bound with fixed memory. HBase integrated with Map-reduce jobs will result in random latencies.
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.

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.
Return to navigation