DBMS > CockroachDB vs. Drizzle vs. Hazelcast vs. MySQL vs. UniData,UniVerse

System Properties Comparison CockroachDB vs. Drizzle vs. Hazelcast vs. MySQL vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A widely adopted in-memory data grid

Widely used open source RDBMS

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

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Multivalue DBMS

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	6.15
Rank	#55	Overall
	#33	Relational DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

www.cockroachlabs.com

hazelcast.com

www.mysql.com

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

Technical documentation

www.cockroachlabs.com/docs

hazelcast.org/imdg/docs

dev.mysql.com/doc

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

Developer

Cockroach Labs

Drizzle project, originally started by Brian Aker

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

Rocket Software

Initial release

2015

2008

1995

1985

Current release

23.1.1, May 2023

7.2.4, September 2012

5.3.6, November 2023

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C++

Java

C and C++

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

dynamic schema

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

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

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Java API

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

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

C
C++
Java
PHP

.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

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Events

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

yes

Replicated Map

Multi-source replication
Source-replica replication

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

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

ACID

configurable

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

Role-based access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role-based access control

Users with fine-grained authorization concept

no user groups or 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.