Apache Geode vs. Apache HBase

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Geode
Score 7.0 out of 10
N/A
Apache Geode is a distributed in-memory database designed to support low latency, high concurrency solutions, available free and open source since 2002. With it, users can build high-speed, data-intensive applications that elastically meet performance requirements. Apache Geode blends techniques for data replication, partitioning and distributed processing.N/A
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
Pricing
Apache GeodeApache HBase
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache GeodeHBase
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 GeodeApache HBase
Top Pros

No answers on this topic

Top Cons

No answers on this topic

Features
Apache GeodeApache HBase
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache Geode
8.7
1 Ratings
1% below category average
Apache HBase
7.7
5 Ratings
13% below category average
Performance9.01 Ratings7.15 Ratings
Availability10.01 Ratings7.85 Ratings
Concurrency10.01 Ratings7.05 Ratings
Scalability8.01 Ratings8.65 Ratings
Data model flexibility7.01 Ratings7.15 Ratings
Deployment model flexibility8.01 Ratings8.25 Ratings
Security00 Ratings7.85 Ratings
Best Alternatives
Apache GeodeApache HBase
Small Businesses
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache GeodeApache HBase
Likelihood to Recommend
7.0
(1 ratings)
7.7
(10 ratings)
Likelihood to Renew
-
(0 ratings)
7.9
(10 ratings)
Usability
8.0
(1 ratings)
-
(0 ratings)
Support Rating
1.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apache GeodeApache HBase
Likelihood to Recommend
Apache
The biggest advantage of using Apache Geode is DB like consistency. So for applications whose data needs to be in-memory, accessible at low latencies and most importantly writes have to be consistent, should use Apache Geode. For our application quite some amount of data is static which we store in MySQL as it can be easily manipulated. But since this data is large R/w from DB becomes expensive. So we started using Redis. Redis does a brilliant job, but with complex data structures and no query like capability, we have to manage it via code. We are experimenting with Apache Geode and it looks promising as now we can query on complex data-structures and get the required data quickly and also updates consistent.
Read full review
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
Pros
Apache
  • Super Fast data pull/push
  • Provided ACID transactions, so it works like a SQL Database
  • Provides replication & partitioning, so our data is never lost and extraction is super fast. NoSql like properties
Read full review
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
Cons
Apache
  • Needs more supporting languages. Out of box Python, Nodejs adapters would be wonderful
  • Currently it supports just KV Store. But if we could cache documents or timeseries data would be great
  • Needs more community support, documentation.
Read full review
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
Likelihood to Renew
Apache
No answers on this topic
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
Usability
Apache
Still Experimenting. Initial results are good. we need to figure out if we can completely replace Redis. Cost wise if it makes sense to keep both or replacement is feasible.
Read full review
Apache
No answers on this topic
Support Rating
Apache
Never contacted support
Read full review
Apache
No answers on this topic
Alternatives Considered
Apache
Still Experimenting. But looks promising as it has query capabilities over complex data structures
Read full review
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
Return on Investment
Apache
  • Still experimenting so difficult to quote
  • For a small size project/teams might be an overkill as it still has certain learning curve
  • For Medium to large projects with complex Data Structures that need to be queried with a fast o/p it definitely works
Read full review
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
ScreenShots