DBMS > Apache HBase vs. GridGain vs. MySQL

System Properties Comparison Apache HBase vs. GridGain vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used open source RDBMS

Primary database model

Wide column store

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	24.75
Rank	#26	Overall
	#2	Wide column stores

Score	1.31
Rank	#157	Overall
	#1	Columnar
	#26	Key-value stores
	#3	Object oriented DBMS
	#70	Relational DBMS

Score	998.15
Rank	#2	Overall
	#2	Relational DBMS

Website

hbase.apache.org

www.gridgain.com

www.mysql.com

Technical documentation

hbase.apache.org/book.html

www.gridgain.com/docs/index.html

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

GridGain Systems, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2008

2007

1995

Current release

2.3.4, January 2021

GridGain 8.5.1

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial, open source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, C++, .Net, Python, REST, SQL

C and C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Linux
OS X
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
Thrift

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes (replicated cache)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Single row ACID (across millions of columns)

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Role-based access control
Security Hooks for custom implementations

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.