DBMS > CockroachDB vs. EventStoreDB vs. MySQL vs. SiteWhere

System Properties Comparison CockroachDB vs. EventStoreDB vs. MySQL vs. SiteWhere

Please select another system to include it in the comparison.

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.

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Widely used open source RDBMS

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Event Store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

www.cockroachlabs.com

www.eventstore.com

www.mysql.com

github.com/sitewhere/sitewhere

Technical documentation

www.cockroachlabs.com/docs

developers.eventstore.com

dev.mysql.com/doc

sitewhere1.sitewhere.io/index.html

Developer

Cockroach Labs

Event Store Limited

Oracle

since 2010, originally MySQL AB, then Sun

SiteWhere

Initial release

2015

2012

1995

2010

Current release

24.1.0, May 2024

21.2, February 2021

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Common Public Attribution License Version 1.0

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

C and C++

Java

Server operating systems

Linux
macOS
Windows

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

dynamic schema

yes

predefined scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

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

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

yes

proprietary syntax

Triggers

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

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.