--- title: Hbase Reviews meta_title: 'Hbase Reviews 2026: Details, Pricing, & Features | G2' meta_description: Filter 114 reviews by the users' company size, role or industry to find out how Hbase works for a business like yours. aggregate_rating: rating_value: 4.2 review_count: 114 scale: '5' date_modified: '2026-07-12' parent_category: name: NoSQL Databases url: https://www.g2.com/categories/nosql-databases --- # Hbase Reviews **Vendor:** The Apache Software Foundation **Category:** [Wide Column Database Software](https://www.g2.com/categories/wide-column-database) **Average Rating:** 4.2/5.0 **Total Reviews:** 114 ## About Hbase A scalable, distributed database that supports structured data storage for large tables. Use HBase when you need random, realtime read/write access to Big Data. ## Hbase Reviews ### 1. Hbase benefits:- **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer & Network Security | Mid-Market (51-1000 emp.) **Reviewed Date:** April 01, 2020 **What do you like best about Hbase?** We can store large amount of data sets and it’s very flexible to use. It supports variable schema i.e. we can add and remove columns dynamically. **What do you dislike about Hbase?** It’s not a complete replacement of relational database. **Recommendations to others considering Hbase:** Good tool to use **What problems is Hbase solving and how is that benefiting you?** We have stored huge amount of data into Hbase on daily basis ### 2. We have been using hbase in our Big Data sta. **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Music | Enterprise (> 1000 emp.) **Reviewed Date:** March 29, 2020 **What do you like best about Hbase?** Because of its schema less feature and high performance in applications which involves huge read and write operations. **What do you dislike about Hbase?** Query optimization need to be done effectively **What problems is Hbase solving and how is that benefiting you?** We are using hbase as a NoSql data base in our spark jobs to handle real time data. We have observed fast processing in reading. ### 3. Great for ML models **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** April 06, 2020 **What do you like best about Hbase?** The failover support is the best thing and processing time is very low **What do you dislike about Hbase?** No transaction support in Hbase which I miss. **Recommendations to others considering Hbase:** Nothing recommended as of now **What problems is Hbase solving and how is that benefiting you?** Can store a huge amount of data. A relatable use case is detection of frauds in transactions in banks ### 4. Fast non-sql DB with realtime monitoring **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer & Network Security | Enterprise (> 1000 emp.) **Reviewed Date:** April 03, 2020 **What do you like best about Hbase?** HBase gives you great TPS when doing batch insert and bulk scan. This is really important when doing big data processing **What do you dislike about Hbase?** The HBase cluster management and performance tuning is not intuitive and sometimes need a lot of domain experience. **What problems is Hbase solving and how is that benefiting you?** For real time monitoring of network metrics ### 5. Very useful tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** April 02, 2020 **What do you like best about Hbase?** We are currently using hbase for storing a large amount of documents (TBs). It is very scalable. We never had an scaling issue with it. Easy to use Java API for client access. **What do you dislike about Hbase?** There is nothing that I dislike about hbase. **What problems is Hbase solving and how is that benefiting you?** Automatic sharding of tables ### 6. Storing data and running a query to find a cluster over it is being more efficient through the hbase **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Apparel & Fashion | Small-Business (50 or fewer emp.) **Reviewed Date:** April 12, 2020 **What do you like best about Hbase?** Efficiently helping in processing over a large number of dataset **What do you dislike about Hbase?** takes a little more to run query and process it on the datatsets. **What problems is Hbase solving and how is that benefiting you?** A large number of fashion stuff is stored and finding the particular one using ML. ### 7. High performance **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** April 07, 2020 **What do you like best about Hbase?** It has high performance, extensible, quick scan **What do you dislike about Hbase?** Query syntax is not SQL like. Column family concept is not easy to understand for a beginner **What problems is Hbase solving and how is that benefiting you?** I migrate our customer data from sql to hbase for better performance and scability ### 8. A comfortable to use db, yet very resilient and fast. **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Education Management | Small-Business (50 or fewer emp.) **Reviewed Date:** April 06, 2020 **What do you like best about Hbase?** The interface and the APIs exposed were really easy to use. **What do you dislike about Hbase?** It was little difficult to setup, would have liked a smoother interface. **What problems is Hbase solving and how is that benefiting you?** Keeping a database of a common library where people buy memberships to read books again. ### 9. Good **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Banking | Small-Business (50 or fewer emp.) **Reviewed Date:** March 20, 2020 **What do you like best about Hbase?** This is the very good tool ans it can handle the in structured data as well. All the json related file it can handle. Indexing is the best future **What do you dislike about Hbase?** Stored under hdfs..if we have any other solution it will be easy **Recommendations to others considering Hbase:** Good **What problems is Hbase solving and how is that benefiting you?** Nothing ### 10. Using hbase is easy fast and fits in hadood framework but it is not widely used as like mongodb and **Rating:** 2.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** April 13, 2020 **What do you like best about Hbase?** Easy to use and fast fits good in Hadoop framework **What do you dislike about Hbase?** Less documentation makes it difficult to debug **What problems is Hbase solving and how is that benefiting you?** Using it to migrate database centric application to no SQL dabase ### 11. Highly recommended **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in E-Learning | Small-Business (50 or fewer emp.) **Reviewed Date:** April 02, 2020 **What do you like best about Hbase?** Ease of usability, integration with Hadoop hortonworks etc. **What do you dislike about Hbase?** Nothing much, I enjoy every much of hbase **Recommendations to others considering Hbase:** Nothing much, hbase is currently very good and accessible **What problems is Hbase solving and how is that benefiting you?** We are using it to store huge data ### 12. Amazing platform **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** April 09, 2020 **What do you like best about Hbase?** Very helpful for large datasets. Easy to start with. **What do you dislike about Hbase?** Nothing to dislike yet. If found any I will let you know **What problems is Hbase solving and how is that benefiting you?** Great for analytics in association with Hadoop MapReduce. ### 13. Use of HBase **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Telecommunications | Enterprise (> 1000 emp.) **Reviewed Date:** April 05, 2020 **What do you like best about Hbase?** Mechanism of Rowkey to distribute huge data in all regions properly **What do you dislike about Hbase?** Data fetching from Hbase takes a time lot **What problems is Hbase solving and how is that benefiting you?** Fetching huge data efficiently by using Fuzzy filter ### 14. The best NoSQL db **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Banking | Enterprise (> 1000 emp.) **Reviewed Date:** March 11, 2020 **What do you like best about Hbase?** Basic data operations are easier to perform. **What do you dislike about Hbase?** There is nothing you can dislike about it. **Recommendations to others considering Hbase:** Go for it.as it is cheaper, easy to maintain and easy to use **What problems is Hbase solving and how is that benefiting you?** As a cheper and Non structured data storage. ### 15. HBase NoSQL evaluation **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Banking | Mid-Market (51-1000 emp.) **Reviewed Date:** March 23, 2020 **What do you like best about Hbase?** Ease of useof HQueries. No MapReduce need **What do you dislike about Hbase?** No standards in queries. Not very popular **Recommendations to others considering Hbase:** Good manage queries on data maintained on HDFS datalakes. **What problems is Hbase solving and how is that benefiting you?** Big queries from data lakes on HDFS ### 16. Amazing Database **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** March 22, 2020 **What do you like best about Hbase?** I like easy of usability.It was easy switching from SQL. **What do you dislike about Hbase?** A little configuration but rest everything is good. **Recommendations to others considering Hbase:** Yes, please use it. **What problems is Hbase solving and how is that benefiting you?** I imported a sql databse and analyzed results. ### 17. Hbase is mature enough technology **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Small-Business (50 or fewer emp.) **Reviewed Date:** April 08, 2020 **What do you like best about Hbase?** Integration in Hadoop ecosystem (supported by major Hadoop vendors). **What do you dislike about Hbase?** Need to tune a lot to achieve good performance. **What problems is Hbase solving and how is that benefiting you?** Storing unstructured Key-Values ### 18. One of best tool in Hadoop Stack **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Accounting | Small-Business (50 or fewer emp.) **Reviewed Date:** April 08, 2020 **What do you like best about Hbase?** Speed and the performance of Hbase is best **What do you dislike about Hbase?** Issues faced because of regions in transition **What problems is Hbase solving and how is that benefiting you?** Speed and accuracy solved the issues ### 19. Slight learning curve and highly efficient data store **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Mid-Market (51-1000 emp.) **Reviewed Date:** March 31, 2020 **What do you like best about Hbase?** Easy random access, providing quick reads/writes **What do you dislike about Hbase?** Transactions not supported like In a traditional DBMS **What problems is Hbase solving and how is that benefiting you?** Stored around 15m records. Big data processing seems well integrated ### 20. It is good tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Banking | Enterprise (> 1000 emp.) **Reviewed Date:** March 23, 2020 **What do you like best about Hbase?** Hbase speed and it is colum oriented data base **What do you dislike about Hbase?** We can some more parameter so it is more familiar **What problems is Hbase solving and how is that benefiting you?** Using in hadoop cluster ### 21. Very good NoSQL DB **Rating:** 4.0/5.0 stars **Reviewed by:** Gubendran L. | Senior Java J2EE BigData Consultant @ Petra Systems Inc, Computer Software, Mid-Market (51-1000 emp.) **Reviewed Date:** June 09, 2015 **What do you like best about Hbase?** The best with Hbase is data stored in hadoop cluster. The read is much faster. Data is replicated in clusters. Region Transition upon server failures is faster. Version based storage as defined. RDBMS (MySQL) we use need to maintain version data like history. Defining FamilyName helps grouping set of qualifiers (Columns) in a given row is good to fetch only certain group of columns data. Filters (RowFilter, SingleColumnFilter API) is flexible to fetch data based on requirement by filtering pattern. **What do you dislike about Hbase?** SQL like Query language missing in hbase. Like Hive we need Query support. Binary data based storage. Every time in code we need to encrypt / decrypt data into Binary format and store it in DB. Lot of code we need to write.Update record is missing. So, we need to delete and put every-time or we may fetch rowId, version, timestamp to override the value in update. **Recommendations to others considering Hbase:** When you evaluate NoSQL for your organization / product, its worth to evaluate HBase for your requirements. **What problems is Hbase solving and how is that benefiting you?** We are storing huge amount of reporting data from energy utilities and other utilities data into Hbase on a daily / hourly basis and we have Map/Reduce framework to do analyse data from Hbase. We felt Hbase is perfect to work with Hadoop Map/Reduce framework. Reading data from Hbase was really faster and we could read huge data from reporting table where we couldn't read from MySQL. Replication, Scalability, Performance overall for NoSQL Hbase is good. ### 22. excellent bigdata storage **Rating:** 5.0/5.0 stars **Reviewed by:** tousif k. | Senior Software Engineer, Computer Software, Enterprise (> 1000 emp.) **Reviewed Date:** January 10, 2016 **What do you like best about Hbase?** nosql architecture ,ease of scaling up to several nodes and easy retrieval of information, best suited for unstructured data. **What do you dislike about Hbase?** very complex software and requires monitoring for performance **Recommendations to others considering Hbase:** An amazing database to store structured/unstructred data **What problems is Hbase solving and how is that benefiting you?** bigdata solutions and data crunching. ### 23. NO Sql database **Rating:** 4.0/5.0 stars **Reviewed by:** Rupesh A. | system engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** September 08, 2017 **What do you like best about Hbase?** Best thing is we can store large amount of data in it and related data are stored closely so that can be retrieved quickly. Column family helps me to segregate similar data . So , they can be extracted fastly. it has a very good support from community of hortanworks. So, it is a very good product to handle big data solution. **What do you dislike about Hbase?** the way data is printed on console is not so user friendly. So we had to use some abstraction over hbase (eg apache phoenix) so there is one new component to handle. **Recommendations to others considering Hbase:** Hbase can be helpful for few scenarios where you need a lot of data in db and also u want it to be accessed easily on basis of similarity of data. Like personal information are stored close by. **What problems is Hbase solving and how is that benefiting you?** We are using it to store email files directly by bulkloading and then retrieving it using apache phoenix. Apache hbase helps us to store data by making hfiles and directly uploading those hfiles to region servers. Instead of having large number of tables in hbase , we are creating a single table for all email types and then in phoenix we are making views on top of that table and firing queries by phoenix. ### 24. Big Data No SQL Storage **Rating:** 4.5/5.0 stars **Reviewed by:** Roshan M. | System Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** June 23, 2017 **What do you like best about Hbase?** Hbase can easily manage, bulk amount of data in an efficient and robust manner. It is considered to be a powerful NoSQL tool, which helps in data management, and provides an ease in fast retrieval and manipulation of the same. It is better than traditional file system, because of the efficiency, which it provides for the same amount of system, and major advantage is the use of commodity hardware, to store the data. Also it is fault tolerant, as it keeps replica of the data stored, so in case of failure, the replica can be used. **What do you dislike about Hbase?** Hbase is not recommended for small amount of data, as it will take, some time in processing, making it not very efficient for that. It has a single point of failure, i.e., HMaster, so if H Master fails, Hbase goes down, and we will not be able to perform any operations, until problem is resolved. We cannot easily perform joins on Hbase, making it a complex tool to perform basic operations. **Recommendations to others considering Hbase:** For storing bulk datain a tabular manner, I would recommend Hadoop Hbase, but for small amount of data, I personally would not suggest the use of this tool. **What problems is Hbase solving and how is that benefiting you?** We are moving from traditional file system to 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. ### 25. Store huge amount of data with ease **Rating:** 4.5/5.0 stars **Reviewed by:** Nikhila D. | System Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** September 06, 2017 **What do you like best about Hbase?** 1) Creating a table with any number of column family names, or any number of columns is easy 2) Map Reduce program helps in loading bulk amount of data in a very short span of time 3) The way we can view the tables and querying the table is very easy as its a NOSQL database 4)It has its own scheduler i.e OOZIE scheduler which is built on yarn user. 5) Kerborization is one big advantage which is supported by HBASE. This ensures the data is secure 6)To maintain the data integrity of data the checksum is used to check corrupted data. This API of HBASE is very helpful **What do you dislike about Hbase?** 1) The only way to identify the individual records is through the row key, there is no other alternative 2) As it is a NOSQL, joins is not supported when we query for multiple tables **Recommendations to others considering Hbase:** Yes definitely **What problems is Hbase solving and how is that benefiting you?** 1) To store the data related to banking services 2) Emails, chats, fax data between customers and the bank are stored in HBASE under different tables 3) The investor profile details, are stored in HBASE 4) The jobs are scheduled using the OOZIE scheduler by cron expressions 5)Used to update the mutation records as well ### 26. Data Encyclopedia **Rating:** 4.0/5.0 stars **Reviewed by:** swetha m. | Senior System Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** September 04, 2017 **What do you like best about Hbase?** 1) Speed- Hbase helps in running map reduce programs which can load peta bytes of data to Hbase in parallel which speeds our work. 2) NoSQL Database- As Hbase is a noSQL database,we can store data in terms of key-value pairs in list of column families,this helps in quering faster and can have multiple values in a column 3) Storage- Hbase can store both metadata as well as content which reduces multiple resources in use. 4) Oozie Scheduler- Hbase has its own built in oozie scheduler which can schedule jobs using specified cron expression,Oozie has its own UI where in you can see the status of the job and refer to logs as well in case of failures which is very helpful. 4) Hadoop eco system also has distributed file sytem which partitions data among different data nodes which helps in storing huge files. I have used to store hfiles in HDFS and finally load them to Hbase using map reduce program in java. 5)Phoenix which supports sql on Hbase, We are using this to query Hbase which is fastens the scan of tables. 6) we are also using checksum to check for whether the data entered the base is corrupted or not which helps in tracking and reconciliation of data. **What do you dislike about Hbase?** 1) As Hbase is a noSQL database,quering with joins is not possible. 2) When we map phoenix with Hbase table, we are unable to create a column other than in Hbase and update it, Only vice versa is possible. 3) The restriction of Oozie scheduler which can be run only by yarn users and can pick files only from HDFS. **Recommendations to others considering Hbase:** 1) Hbase- NoSql database which helps in storage of big data and even helps in quering. 2) Supports parallel programming using map reduce which fastens our work. 3) Phoenix runs SQL on Hbase which scans faster. 4) Has built in scheduler-oozie **What problems is Hbase solving and how is that benefiting you?** 1) Hbase has helped in loading peta bytes of data using map reduce programs in java .We were able to load metadata as well as content to Hbase. 2) We are able to apply retention policy on records by scanning multiple tables using phoenix. 3) We have used Kerborisation to enhance the security of our modules in Hadoop eco system as well. ### 27. Hadoop NoSQL Database **Rating:** 4.0/5.0 stars **Reviewed by:** Prashanth P. | System Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** June 19, 2017 **What do you like best about Hbase?** Hadoop Hbase is a fault tolerance No SQL data base, which can be used for analysis. It makes replica of the data which is loaded, which makes it more reliable. It has out of box features like, auto - sharding and auto - failover. It can be integrated with Hadoop Hive, which is also a component of Hadoop, to use SQL like queries. **What do you dislike about Hbase?** The major drawback of Hbase is that is does not have transaction support. We cannot perform joins in Hbase easily, to perform joins we have to either write complex map - reduce code, or integrate with Hadoop Hive. **Recommendations to others considering Hbase:** To store bulk amount of data, I would suggest Hbase. But is the amount of data to be stored is less, then it is not recommended. Also if we do not require transaction support, with huge amount of data, then we can always go for Hbase. **What problems is Hbase solving and how is that benefiting you?** We are using Hbase to store all the data from old file system i.e., traditional file system to Hadoop. As we are aware that data is growing day by day, so we need better products to store and manage this data, which is easily achievable by Hbase. So we are moving all our data into Hadoop storage in a tabular form in Hbase tables. ### 28. Big Data NoSQL database **Rating:** 4.0/5.0 stars **Reviewed by:** prabhudayal a. | Senior Software Engineering, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** June 02, 2017 **What do you like best about Hbase?** 1.The capacity, storage and processing of bulk data, in such a robust manner. 2.Flexible schema as we can add n numbers of attributes in a column family at run time without declaring them at the time of table creation. 3.Fault tolerance- As we know mapReduce runs internally for all kind of operation, In case of failure scenarios mapper and reducer job handles it. 4.Versioning of records- Default feature for versioning is available. If that is enabled, hbase updates the record and also keeps the old record data. **What do you dislike about Hbase?** 1.Transaction concept is not applicable.-as its a noSQL database 2.No other primary key can be defined other than the row key. 3-Indexing of row key is a feature by default- but we can not explicitly index any other value, as we can not have any primary key other than row key itself. **Recommendations to others considering Hbase:** Surely, but for NoSQL database **What problems is Hbase solving and how is that benefiting you?** We are storing data from csv into Hbase after making an HFile .. Java implementation of map reduce is done for the same. ### 29. A good new NoSQL: HBase **Rating:** 4.0/5.0 stars **Reviewed by:** Saugandh K. | Software Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** June 19, 2017 **What do you like best about Hbase?** The robustness of the application in terms of capacity, storage and processing of bulk data is the best. Also not having a table schema helps a lot which allows us to have as many columns as possible on the go without defining them. The concept of versioning of the records helps us to compare data properly and also store both the data if required. **What do you dislike about Hbase?** Not having the feature of primary or a composite primary key is an issue as the architecture to be defined cannot be the same legacy type. Also the transaction concept is not applicable here. **Recommendations to others considering Hbase:** Highly recommend if dealing with bulk and variety of data as no schema is required during DDL. **What problems is Hbase solving and how is that benefiting you?** In our business we are using it to store data and metadata of the complete Content Management System of our client. ### 30. Big Data - NoSQL DB **Rating:** 4.0/5.0 stars **Reviewed by:** Sushant D. | System Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** June 09, 2017 **What do you like best about Hbase?** Hbase is a noSQL database which can handle, large amount of data easily. It is also fault tolerance. The schema of Hbase is also very flexible and at any point of time we can add new columns to the table. Only column families need to be defined initially. **What do you dislike about Hbase?** As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data. In Hbase joins are not supported, we need to connect it ti either hive to do so. **Recommendations to others considering Hbase:** To store, huge volume of data, and if no transaction support is required, then I'd surely recommend this component of Hadoop. **What problems is Hbase solving and how is that benefiting you?** We are storing all the data after converting it to a CSV to Hbase, as the amount of data is increasing day by day, and the traditional storage system cannot suffice the need. ### 31. NoSQL Hadoop Storage **Rating:** 4.0/5.0 stars **Reviewed by:** Dhharvi S. | System Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** June 17, 2017 **What do you like best about Hbase?** Hbase can efficiently handle huge amount of data. It is fault tolerance. This is an out of box component of Hadoop, so we do not have to purchase it. **What do you dislike about Hbase?** The major drawback of Hbase is that we cannot perform joins in it, that is a very basic thing expected in a database. Here we have single point of failure i.e., Hbase Master, on failure of which the whole hbase stops functioning. **Recommendations to others considering Hbase:** Hbase is highly recommended, if we want to store bulk data and are not expecting to fetch SQL like results. Though nowadays, we have tools coming up which can fetch data from hbase and then we can perform our normal transnational queries. **What problems is Hbase solving and how is that benefiting you?** We are storing all the data from traditional file system to Big data, and storing in Hbase at the end of the day. ### 32. No SQL Storage **Rating:** 4.5/5.0 stars **Reviewed by:** Souvik D. | Senior Software Engineer, Information Technology and Services, Enterprise (> 1000 emp.) **Reviewed Date:** June 01, 2017 **What do you like best about Hbase?** Storing bulk data on Hadoop file system, using NoSQL database. Ease of handling bulk data **What do you dislike about Hbase?** As it is a NoSQL tool, we cannot fire normal SQL queries, to fetch data from the same **Recommendations to others considering Hbase:** For loading huge data, I'd recommend, where we are not in a need to do analysis on a daily basis **What problems is Hbase solving and how is that benefiting you?** Loading huge amount of data from CSV into a Hadoop, in a tabular manner. ### 33. High scalable and nice architecture **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Internet | Enterprise (> 1000 emp.) **Reviewed Date:** November 09, 2017 **What do you like best about Hbase?** Scaling capability to 100 of nodes and super fast **What do you dislike about Hbase?** Two many processes makes it hard to manage **What problems is Hbase solving and how is that benefiting you?** Salesforce Big Objects ### 34. HBase is better than Oracle. **Rating:** 5.0/5.0 stars **Reviewed by:** Suraj Kumar D. | Senior Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** May 11, 2017 **What do you like best about Hbase?** It is open source, written in Java, and it is non-relational. **What do you dislike about Hbase?** SQL integration layer is a bit complex, and it runs particularly on UNIX **Recommendations to others considering Hbase:** Surely go for it as it is the future **What problems is Hbase solving and how is that benefiting you?** We had the schema metadata to be moved to the HBASE, so we were trying to store the metadata. ### 35. Experience with HBase **Rating:** 4.0/5.0 stars **Reviewed by:** Tuan T. | Research Engineer, Research, Mid-Market (51-1000 emp.) **Reviewed Date:** July 09, 2016 **What do you like best about Hbase?** HBase is a good solution if you are kind of SQL guy and you work in Hadoop ecosystem, and you don't want to write a lot of code to handle the low-level HDFS I/O. HBase is really fast, and can store a very big data with hundreds of columns. Also, HBase is bundled in Cloudera, and has a very active community of supporters. You can easily find answers for your questions in StackOverflow or elsewhere. **What do you dislike about Hbase?** HBase takes many extra hard-disk, because it builds many index for one table. Also, you have to be careful if you want to get the best trade-offs between writing and querying - fine tuning is necessary. HBase is also too level to support some kind of data schema such as time series. For that, you usually need to install other database on top of it, such as OpenTSDB **Recommendations to others considering Hbase:** If you are just beginning to use Hadoop, and you are looking for something similar to SQL database to work with, HBase is an easy solution. It is built-in in many Hadoop vendor, which makes your life easier setting things up **What problems is Hbase solving and how is that benefiting you?** I need to store my data extracted from raw Web archives to be able to easily query it later, and for my colleagues who are more familiar with SQL to work with. HBase seems to be a proper option, since we have Cloudera in our house anyway. ### 36. Hbase : Hadoop DB **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** June 20, 2017 **What do you like best about Hbase?** The query and structured storage of big data. Can be connected via different platform or programming language. **What do you dislike about Hbase?** I have not found anything to dislike in hbase . Sequential processing takes more time for big data and as data size increases. **Recommendations to others considering Hbase:** NA **What problems is Hbase solving and how is that benefiting you?** Banking applications. Easy for big data storage and transactions ### 37. The right solution only for the right use cases **Rating:** 3.0/5.0 stars **Reviewed by:** Verified User in Newspapers | Enterprise (> 1000 emp.) **Reviewed Date:** October 18, 2016 **What do you like best about Hbase?** With HBase, you get what you asked for. HBase is great because it's an open-source, well-known Apache project. As a result, the community and documentation are well-developed -- most likely, any issue you run into will be on StackOverflow. **What do you dislike about Hbase?** Unless you're buying into a fully-managed, bare-metal Hadoop environment, I'd say you should first look into what cloud-providers offer in terms of HBase-like, columnar databases. Check out Google Cloud Platform or Amazon Web Services before ever installing HBase from Apache, Cloudera, HortonWorks, etc., and even then, know that cloud instances are expensive. In addition, I'd make sure that a columnar database is even what you need. In most cases, a traditional relational database is probably just fine for your use case, as you'll later find exporting data from HBase or using HBase for a variety of queries is a lot of work. **Recommendations to others considering Hbase:** First consider if you need a columnar database. If you're absolutely sure that the benefits outweigh the price, then look into cloud providers with fully-managed columnar databases. **What problems is Hbase solving and how is that benefiting you?** I've used HBase for both look-ups and time-series data. It's great for when you know what your queries will be, but exporting data, especially for regulatory requirements, was more complex than it needed to be. ### 38. hbase CDH **Rating:** 2.5/5.0 stars **Reviewed by:** Anson A. | Data Czar, Mid-Market (51-1000 emp.) **Reviewed Date:** January 12, 2017 **What do you like best about Hbase?** Easy to set up, and easy to use. Fact that it sits on top of hdfs is even better **What do you dislike about Hbase?** not very easy to diagnose issues. GC tuning is a real p.i.t.a. **What problems is Hbase solving and how is that benefiting you?** Using HBASE in pipeline flow to reduce time and storage of reads necessary. ### 39. It is a very helpful product **Rating:** 3.5/5.0 stars **Reviewed by:** Verified User in Non-Profit Organization Management | Mid-Market (51-1000 emp.) **Reviewed Date:** October 24, 2016 **What do you like best about Hbase?** HBase is very much a developer-centric database. Hbase is built on Hadoop ecosystem, stored procedures through coprocessors and consistent **What do you dislike about Hbase?** Doesn't have a easy query language like SQL, too complex and too many variable parts, mostly can only be used with single node cluster **What problems is Hbase solving and how is that benefiting you?** We work with large datasets and use social media mining. Hbase is very compatible with Hadoop so it is very useful for our existing system. ### 40. Open source NoSQL database providing consistency and partitioning **Rating:** 4.5/5.0 stars **Reviewed by:** Guy T. | Software Engineer, Internet, Mid-Market (51-1000 emp.) **Reviewed Date:** January 26, 2016 **What do you like best about Hbase?** High performance overall. Open source nature makes it easy to contribute and review the internals of the project. Also makes it easy for tools adding functionality to be built and integrated on top. Costs nothing. Well supported by PAAS providers such as AWS. Consistency ensures correct results will be found, though they may take longer. Can use SQL like language through integration with Apache Hive, allowing users new to NoSQL databases to limit the initial learning curve. **What do you dislike about Hbase?** Choice of consistency and partitioning at the expense of availability results in some queries taking longer than necessary. Ability to use SQL like language can lead users to view it as suitable for traditional relational DB use cases when this is not the case. **Recommendations to others considering Hbase:** If availability is not your number one priority and you are looking for a well established, stable and easy to use NoSQL columnar database this is probably the best option out there. However if heading into the cloud vendors' own solutions (ie AWS' DynamoDB) may be worth examining first. **What problems is Hbase solving and how is that benefiting you?** NoSQL database capable of integrating with Hadoop mapreduce jobs. Partitioning for scalability as the number 1 concern allowing for simple future expansion due to running on top of HDFS. ### 41. Stable Database **Rating:** 5.0/5.0 stars **Reviewed by:** Milad N. | Mid-Market (51-1000 emp.) **Reviewed Date:** May 21, 2016 **What do you like best about Hbase?** Stability and scaleability are the most important features in this software which I like. I deployed it over more than 20 servers it was easy to deploy and add new nodes. **What do you dislike about Hbase?** I have a little issue with its rest web service and also zookeeper sometimes crashes but its native clients where great **Recommendations to others considering Hbase:** easy of deployment **What problems is Hbase solving and how is that benefiting you?** I deployed a central database for a big IDS and sensor network it stores more than 10Gbps data every date and lots of other components is connected to it for processing jobs ### 42. HBase **Rating:** 5.0/5.0 stars **Reviewed by:** Timothy S. | Principal Developer Advocate, Enterprise (> 1000 emp.) **Reviewed Date:** January 07, 2016 **What do you like best about Hbase?** HBase is part of the Hadoop stack makes it a no brainer for usage if you have a Hadoop cluster setup already. Running on top of your existing HDFS makes for an easy install and use. For most people using Hortonworks, Cloudera or MapR this is part of your default install. HBase works well with Apache Spark as well and makes for a great NOSQL solution for many use cases. It is very well documented and there's tons of articles on uses and tutorials. http://hbase.apache.org/book.html#jvm **What do you dislike about Hbase?** It could use a better query language. I would prefer if Phoenix was better integrated with HBase. Also they should include cell level security like Accumulo. Otherwise there's not much to dislike, it fits into the hadoop cluster and is easy to manage with Hue or Ambari. **Recommendations to others considering Hbase:** If you have Hadoop, install it through Ambari or your Hadoop console and give it a try. if you don't have Hadoop, I would say try something else. Try it for some use cases in place of another cache, kv store or NoSQL. If you already have Accumulo or Cassandra, then you probably don't have too many uses for HBase, but some OOTB solutions use it. It doesn't hurt to have it installed as it proves to be a useful utility for many options. **What problems is Hbase solving and how is that benefiting you?** We were using it to quickly access Key-Value type data for front-end applications. Basically a sampling of massive datasets stored in HDFS. ### 43. HBase for Big Data **Rating:** 3.5/5.0 stars **Reviewed by:** Anshorimuslim S. | Platform Developer, Information Technology and Services, Small-Business (50 or fewer emp.) **Reviewed Date:** March 14, 2016 **What do you like best about Hbase?** Low Latency, versioning row, consistency, Java API, interoperability with another software **What do you dislike about Hbase?** Tuning, compaction, configuration and settings **Recommendations to others considering Hbase:** Consider HBase if you need timeseries storage **What problems is Hbase solving and how is that benefiting you?** Social Media Analytics ### 44. HBase has proven to be a very robust, flexible and feature-rich distributed data store. **Rating:** 5.0/5.0 stars **Reviewed by:** Gerry E. | Senior Database Developer & Architect, Enterprise (> 1000 emp.) **Reviewed Date:** June 16, 2015 **What do you like best about Hbase?** - build from the ground up with strict consistency in mind, with the flexibility to relax the consistency level on an as-needed basis. - easy to use shell provides both DML and DDL commands - Java APIs are easy to use - table and column family attributes can be customized per the use case - built in auto-sharding capabilities - replication is easy to setup and maintain - native in-memory option - native row versioning \ history capabilities - fault-tolerant and self-healing - plenty of good documentation, resources, blogs, etc **What do you dislike about Hbase?** - no known, full-featured, management GUI (stand-alone or web application) seems to exist at this time - DDL and DML via shell is easy for simple operations, but becomes syntactically awkward for more complex operations **What problems is Hbase solving and how is that benefiting you?** - storing and aggregating hundred of millions time-series data points - master data management: designing a single source of truth for storing and serving business data to internal and external applications and\or platforms ### 45. HBase is good for doing RangeScans, storing HistoricalData and providing Strong Consistency. **Rating:** 4.5/5.0 stars **Reviewed by:** Anil G. | Senior Software Developer, Internet, Enterprise (> 1000 emp.) **Reviewed Date:** June 15, 2015 **What do you like best about Hbase?** 1. Highly Scalable. 2. Out of the box load balancing. 3. Doing short RangeScans 4. Support for Coprocessors(Server side UDF's) 5. Strong Consistency. 6. Rich set of Filters. 7. Support for storing historical data. 8. Deep Intergration with Hadoop Platform. 9. Huge Community support. 10. Provides cell level security. **What do you dislike about Hbase?** HBase needs to integrate with Apache Phoenix OOTB so that users dont need to bother about reading and writing byte[] to and from HBase. OR It should provide high level constructs to read and write columns with DataType(like int, bigdecimal, short, etc..) Its Documentation website can be improved and made more visual. **Recommendations to others considering Hbase:** Data Modeling is KEY to successful HBase implementation. Make sure you get it right. Tune HBase as per your workload. Avoid using HBase for full table scan type of workload. **What problems is Hbase solving and how is that benefiting you?** I have been using HBase for last 4 years. I have used it for two different use cases: 1. To store credit card transaction in HBase at Intuit. 2. To store Images of Cars in HBase at Truecar.com Here are the benefits: 1. Its strongly consistent. 2. Integrates very well with Hadoop/MapReduce. 3. RangeScan 4. Can be used to store small files in HDFS/Hadoop. 5. Good community support. 6. Support for storing historical data. ### 46. Used the feature Hive-HBase integration **Rating:** 3.5/5.0 stars **Reviewed by:** Anuroopa G. | Application Developer, Financial Services, Enterprise (> 1000 emp.) **Reviewed Date:** June 15, 2015 **What do you like best about Hbase?** Even though we cannot use it as a replacement of RDBMS,it suits number of use cases in Big Data space.In one among the use cases, the number of version for Hbase was kept as 1 (to simulate rdbms feature of maintaining only single version,not the version history of 3(default)) and used the feature Hive Hbase integration to read the Hbase table from Hive.So the application updates the Hbase table,and we used this table in etl flow along with other hive tables. Note:Even if the version is greater than 1,Hive table which points to the Hbase table displays only the latest version **What do you dislike about Hbase?** You need to monitor all the Hbase daemons along with the other services in the ETL/Hadoop Cluster .And the rowkey definition should be done with at-most care,as the rowkey defines the performance of Hbase. **What problems is Hbase solving and how is that benefiting you?** As other big data eoc system tools are not permitting any updates on data stored in HDFS,we can use Hbase to simulate this feature using its "version" mechanism,and still leverage the capabilities of Hadoop ### 47. HBase as storage is good for data Minning **Rating:** 3.5/5.0 stars **Reviewed by:** Isaac Z. | Product Specialist, Small-Business (50 or fewer emp.) **Reviewed Date:** January 07, 2016 **What do you like best about Hbase?** 1. Highly Scalable. 2. Rich set of data type. 3. API support multiple language. **What do you dislike about Hbase?** 1. It is difficult to configure 2. Its Documentation website can be improved and made more visual. **Recommendations to others considering Hbase:** 1. Highly scalable. 2. Storage is cheep. **What problems is Hbase solving and how is that benefiting you?** 1. Data Analysis 1. Story history log ### 48. An Amazing Experience **Rating:** 5.0/5.0 stars **Reviewed by:** Bharadwaj (Brad) C. | Director Of Engineering/Head of Reliability Engineering, Enterprise (> 1000 emp.) **Reviewed Date:** June 10, 2015 **What do you like best about Hbase?** HBase is the right DB for any non-relational usecase. HBase operations run in real-time on its database rather than MapReduce jobs. It scales linearly to support billions of rows with millions of columns. Reliable and Fast **What do you dislike about Hbase?** Difficult for people who are building custom tools for SQL like purposes to understand HBase. Cannot be used for transactional datasets **Recommendations to others considering Hbase:** Make sure you absolutely need it. If your problem can be solved using relational db, use it. And, understand that the support is through the community distributions **What problems is Hbase solving and how is that benefiting you?** Scalable and truly non-relational data ### 49. HBase Database - The good and the bad **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Higher Education | Enterprise (> 1000 emp.) **Reviewed Date:** April 14, 2015 **What do you like best about Hbase?** It's really fast and quite reliable. We manually instilled multiple namenode failures but it still worked flawlessly. **What do you dislike about Hbase?** People coming from traditional relational databases will have a hard time wrapping their heads around how HBase works. The lack of a stronger query language might cause other people to not use it. **Recommendations to others considering Hbase:** Keep in mind that it's an OpenSource project. So support is only through email lists. Also, it's not a RDBMS. So don't try to use it like one. It'll hurt more than it'll help. Try to denormalize your existing data if you are switching from an RDBMS. Also, if you have good hardware and want better support, try using the Cloudera or Hortonworks distribution. I have experience with the Cloudera distribution and the Apache one as well. As far as I know, Cloudera's is free for smaller clusters. Also, it's very easy to install it that way. **What problems is Hbase solving and how is that benefiting you?** We found out that while serving content through HBase it's fault tolerance was very handy. We killed multiple namenodes and it kept serving. ### 50. Awesome **Rating:** 4.0/5.0 stars **Reviewed by:** Will H. | Founder, Design, Mid-Market (51-1000 emp.) **Reviewed Date:** January 13, 2016 **What do you like best about Hbase?** The speed. The complexity. The money saved. **What do you dislike about Hbase?** The configuration. The arbitrality of parameters. **Recommendations to others considering Hbase:** Research. **What problems is Hbase solving and how is that benefiting you?** Increased productivity. ## Hbase Discussions - [In HBase, we cannot implement any cross data operations and joining operations, of course, we can implement the joining operations using MapReduce, which would take a lot of time to designing and development. How we can improve this??](https://www.g2.com/discussions/25674-in-hbase-we-cannot-implement-any-cross-data-operations-and-joining-operations-of-course-we-can-implement-the-joining-operations-using-mapreduce-which-would-take-a-lot-of-time-to-designing-and-development-how-we-can-improve-this) - 1 comment, 1 upvote - [View Hbase pricing details and edition comparison](https://www.g2.com/products/hbase/reviews?page=2§ion=pricing&secure%5Bexpires_at%5D=2026-07-16+08%3A16%3A51+-0500&secure%5Bsession_id%5D=dc313a0d-ff71-4f8d-99c1-d74663cde12e&secure%5Btoken%5D=a12f4dace7dbd82a3b1da9e4213540f5952b8a9e87dfdb87e19dff93e748b34a&format=llm_user) ## Hbase Features **Storage** - Data Model - Data Types **Storage** - Data Storage Method **Availability** - Auto Sharding - Auto Recovery - Data Replication **Scalability** - Database Scalability - Auto Sharding **Performance** - Integrated Cache **Security** - Order Preserving Encryption **Security** - Role-Based Authorization - Authentication - Audit Logs - Encryption **Support** - Data Types Support - Different Operating Systems - Multi model Database Support **Support** - Multi-Model - Operating Systems **Agentic AI - Wide Column Database** - Decision Making **Database Features** - Storage - Availability - Stability - Scalability - Security - Data Manipulation - Query Language ## Top Hbase Alternatives - [Snowflake](https://www.g2.com/products/snowflake/reviews) - 4.5/5.0 (707 reviews) - [Google Cloud BigTable](https://www.g2.com/products/google-cloud-bigtable/reviews) - 4.4/5.0 (37 reviews) - [Google Cloud BigQuery](https://www.g2.com/products/google-cloud-bigquery/reviews) - 4.5/5.0 (1,144 reviews)