DBMS > Citus vs. Hazelcast vs. MySQL vs. Riak KV

System Properties Comparison Citus vs. Hazelcast vs. MySQL vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted in-memory data grid

Widely used open source RDBMS

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	2.15
Rank	#123	Overall
	#60	Relational DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

www.citusdata.com

hazelcast.com

www.mysql.com

Technical documentation

docs.citusdata.com

hazelcast.org/imdg/docs

dev.mysql.com/doc

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

OpenSource, formerly Basho Technologies

Initial release

2010

2008

1995

2009

Current release

8.1, December 2018

5.3.6, November 2023

8.3.0, January 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache version 2, commercial enterprise edition

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 and C++

Erlang

Server operating systems

Linux

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Data scheme

yes

schema-free

yes

schema-free

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

restricted

SQL

Support of SQL

yes

standard, with numerous extensions

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

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

Supported programming languages

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

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

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

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

yes

Event Listeners, Executor Services

yes

proprietary syntax

Erlang

Triggers

yes

Events

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes

Replicated Map

Multi-source replication
Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between data sets can be stored

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

yes

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

yes, using Riak Security

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.