Apache HBase vs. Oracle NoSQL Database

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
HBase
Score 7.3 out of 10
N/A
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.N/A
Oracle NoSQL Database
Score 10.0 out of 10
N/A
Oracle offers a NoSQL Database.N/A
Pricing
Apache HBaseOracle NoSQL Database
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
HBaseOracle NoSQL Database
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache HBaseOracle NoSQL Database
Top Pros
Top Cons
Features
Apache HBaseOracle NoSQL Database
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache HBase
7.7
5 Ratings
13% below category average
Oracle NoSQL Database
-
Ratings
Performance7.15 Ratings00 Ratings
Availability7.85 Ratings00 Ratings
Concurrency7.05 Ratings00 Ratings
Security7.85 Ratings00 Ratings
Scalability8.65 Ratings00 Ratings
Data model flexibility7.15 Ratings00 Ratings
Deployment model flexibility8.25 Ratings00 Ratings
Best Alternatives
Apache HBaseOracle NoSQL Database
Small Businesses
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache HBaseOracle NoSQL Database
Likelihood to Recommend
7.7
(10 ratings)
7.3
(1 ratings)
Likelihood to Renew
7.9
(10 ratings)
-
(0 ratings)
User Testimonials
Apache HBaseOracle NoSQL Database
Likelihood to Recommend
Apache
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.
Read full review
Oracle
Oracle NoSQL Database is well-suited for you if your data formats are not consistent, if you have limited hardware resources, if you higher data throughput (whether the database is on the cloud or running locally), and if you don't need a declarative query language to maintain a standardized schema of your data. If you need reduced data redundancy and require ACID compliance, you are better off finding an SQL database solution.
Read full review
Pros
Apache
  • 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.
Read full review
Oracle
  • Data-model flexibility. Unlike RDBMS solutions, Oracle NoSQL does not restrict you to a predefined set of data types.
  • Ability to Handle an Increased Amount of Traffic. As Oracle NoSQL can process queries much quicker than Oracle Database, Oracle NoSQL is able to respond to a lot more queries in the same amount of time.
  • Data-model simplicity. In SQL-oriented databases, there is a learning curve in learning the relationship between databases, tables, rows, and keys. On the other hand, Oracle NoSQL's key-value based storage is much easier to get the hang of.
Read full review
Cons
Apache
  • 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.
Read full review
Oracle
  • Fewer analytical functions to choose from. When compared to Oracle Database, there is significant difference in the amount of built-in analytical functions.
  • Eventual data consistency. It is not guaranteed that a write or delete query will be immediately visible for subsequent queries.
  • Data redundancy. As there are no mechanisms that insure data integrity, users are more likely to have redundant data across their documents.
Read full review
Likelihood to Renew
Apache
There's really not anything else out there that I've seen comparable for my use cases. HBase has never proven me wrong. Some companies align their whole business on HBase and are moving all of their infrastructure from other database engines to HBase. It's also open source and has a very collaborative community.
Read full review
Oracle
No answers on this topic
Alternatives Considered
Apache
Cassandra os great for writes. But with large datasets, depending, not as great as HBASE. Cassandra does support parquet now. HBase still performance issues. Cassandra has use cases of being used as time series. HBase, it fails miserably. GeoSpatial data, Hbase does work to an extent. HA between the two are almost the same.
Read full review
Oracle
I have not used any other types of NoSQL databases.
Read full review
Return on Investment
Apache
  • 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.
Read full review
Oracle
  • We pay less for computing resources, as Oracle NoSQL databases respond quicker than our previous SQL databases.
  • Our database administrators and software developers do not need to worry about "data massaging" and can focus on perfecting application logic.
  • Oracle NoSQL has built-in integration to other Oracle products, so we didn't not need to spend money on building custom integrators or higher additional developers.
Read full review
ScreenShots