What users are saying about
30 Ratings
30 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.3 out of 101

Likelihood to Recommend

HBase

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.
Vinaybabu Raghunandha Naidu profile photo

Feature Rating Comparison

NoSQL Databases

HBase
7.9
Performance
HBase
7.6
Availability
HBase
7.9
Concurrency
HBase
7.2
Security
HBase
7.8
Scalability
HBase
8.2
Data model flexibility
HBase
8.2
Deployment model flexibility
HBase
8.7

Pros

HBase

  • 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.
No photo available

Cons

HBase

  • 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.
RAVI MISHRA profile photo

Likelihood to Renew

HBase

HBase 8.3
Based on 10 answers
HBase is open source so I suggest it and it is one of the best databases to store real-time data with security but a lot more improvements are required to include the SQL queries functionalities for the data analysis purpose.
RAVI MISHRA profile photo

Alternatives Considered

HBase

Hbase is more robust and scalable than other DBs around
Bharadwaj (Brad) Chivukula profile photo

Return on Investment

HBase

  • As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data.
  • 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.
  • The way data is printed on console is not so user-friendly. So we had to use some abstraction over HBase (eg apache phoenix) which means there is one new component to handle.
Bharadwaj (Brad) Chivukula profile photo

Pricing Details

HBase

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

Add comparison