DBMS > CockroachDB vs. GeoMesa vs. Hazelcast vs. MySQL vs. SWC-DB

System Properties Comparison CockroachDB vs. GeoMesa vs. Hazelcast vs. MySQL vs. SWC-DB

Editorial information provided by DB-Engines

Name

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.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A widely adopted in-memory data grid

Widely used open source RDBMS

A high performance, scalable Wide Column DBMS

Primary database model

Key/Value like access via memcached API

Wide column store

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

Time Series DBMS

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.01
Rank	#378	Overall
	#13	Wide column stores

Website

www.cockroachlabs.com

www.geomesa.org

hazelcast.com

www.mysql.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.cockroachlabs.com/docs

www.geomesa.org/documentation/stable/user/index.html

hazelcast.org/imdg/docs

dev.mysql.com/doc

Developer

Cockroach Labs

CCRi and others

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

Alex Kashirin

Initial release

2015

2014

2008

1995

2020

Current release

24.1.0, May 2024

5.0.1, July 2024

5.3.6, November 2023

9.0.0, July 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

Scala

Java

C and C++

C++

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

dynamic schema

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

SQL-like query language

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol
Thrift

Supported programming languages

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

.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

C++

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

yes

Events

yes

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

depending on storage layer

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

depending on storage layer

yes

Replicated Map

Multi-source 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

depending on storage layer

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

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.

depending on storage layer

yes

User concepts

Access control

Role-based access control

yes

depending on the DBMS used for storage

Role-based access control

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.