Apache HBase vs. Apache Derby

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
Apache Derby
Score 7.0 out of 10
N/A
Apache Derby is an embedded relational database management system, originally developed by IBM and called IBM Cloudscape.N/A
Pricing
Apache HBaseApache Derby
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
HBaseApache Derby
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
Features
Apache HBaseApache Derby
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache HBase
7.7
5 Ratings
13% below category average
Apache Derby
-
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 HBaseApache Derby
Small Businesses
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
SQLite
SQLite
Score 9.1 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
SQLite
SQLite
Score 9.1 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
SQLite
SQLite
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache HBaseApache Derby
Likelihood to Recommend
7.7
(10 ratings)
7.0
(3 ratings)
Likelihood to Renew
7.9
(10 ratings)
-
(0 ratings)
User Testimonials
Apache HBaseApache Derby
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
Apache
If you need a SQL-capable database-like solution that is file-based and embeddable in your existing Java Virtual Machine processes, Apache Derby is an open-source, zero cost, robust and performant option. You can use it to store structured relational data but in small files that can be deployed right alongside with your solution, such as storing a set of relational master data or configuration settings inside your binary package that is deployed/installed on servers or client machines.
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
Apache
  • Apache Derby is SMALL. Compared to an enterprise scale system such as MSSQL, it's footprint is very tiny, and it works well as a local database.
  • The SPEED. I have found that Apache Derby is very fast, given the environment I was developing in.
  • Based in JAVA (I know that's an obvious thing to say), but Java allows you to write some elegant Object Oriented structures, thus allowing for fast, Agile test cases against the database.
  • Derby is EASY to implement and can be accessed from a console with little difficulty. Making it appropriate for everything from small embedded systems (i.e. just a bash shell and a little bit of supporting libraries) to massive workstations.
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
Apache
  • It may not scale as well as some more mature database products.
  • Used it primarily from the command line with openjpa and jdbc, and from third-party clients such as Squirrel.
  • May benefit by providing more sophisticated tools to optimize query performance.
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
Apache
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
Apache
SQLite is another open-source zero-cost file-based SQL-capable database solution and is a good alternative to Apache Derby, especially for non-Java-based solutions. We chose Apache Derby as it is Java-based, and so is the solution we embedded it in. However, SQLite has a similar feature set and is widely used in the industry to serve the same purposes for native solutions such as C or C++-based products.
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
Apache
  • Being Open source, the resources spent on the purchase of the product are ZERO.
  • Contrary to popular belief, open source software CAN provide support, provided that the developers/contributors are willing to answer your emails.
  • Overall, the ROI was positive: being able to experiment with an open source technology that could perform on par with the corporate products was promising, and gave us much information about how to proceed in the future.
Read full review
ScreenShots