DBMS > Hazelcast vs. Memcached vs. MySQL vs. Tarantool vs. UniData,UniVerse

System Properties Comparison Hazelcast vs. Memcached vs. MySQL vs. Tarantool vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

In-memory key-value store, originally intended for caching

Widely used open source RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Multivalue DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

hazelcast.org/imdg/docs

github.com/memcached/memcached/wiki

dev.mysql.com/doc

www.tarantool.io/en/doc

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Hazelcast

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Oracle

since 2010, originally MySQL AB, then Sun

Rocket Software

Initial release

2008

2003

1995

2008

1985

Current release

5.3.6, November 2023

1.6.25, March 2024

8.3.0, January 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD license

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

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

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
macOS

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

optional

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

Full-featured ANSI SQL support

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Open binary protocol

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

Lua, C and SQL stored procedures

yes

Triggers

yes

Events

yes

yes, before/after data modification events, on replication events, client session events

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

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

ACID

not for MyISAM storage engine

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Role-based access control

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

Access rights according to SQL-standard and operating system based

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.