DBMS > Citus vs. GridGain vs. Hazelcast vs. Linter vs. MySQL

System Properties Comparison Citus vs. GridGain vs. Hazelcast vs. Linter vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

A widely adopted in-memory data grid

RDBMS for high security requirements

Widely used open source RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

Document store
Spatial DBMS

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

docs.citusdata.com

www.gridgain.com/docs/index.html

hazelcast.org/imdg/docs

dev.mysql.com/doc

Developer

GridGain Systems, Inc.

Hazelcast

relex.ru

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2010

2007

2008

1990

1995

Current release

8.1, December 2018

GridGain 8.5.1

5.3.6, November 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java, C++, .Net

Java

C and C++

Server operating systems

Linux

Linux
OS X
Solaris
Windows

All OS with a Java VM

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

specific XML type available, but no XML query functionality

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

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

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

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

yes

Event Listeners, Executor Services

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

Triggers

yes

yes (cache interceptors and events)

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes (replicated cache)

yes

Replicated Map

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

ACID

one or two-phase-commit; repeatable reads; read commited

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

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

Role-based access control

fine grained access rights according to SQL-standard

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.