DBMS > CockroachDB vs. EsgynDB vs. MySQL vs. ReductStore

System Properties Comparison CockroachDB vs. EsgynDB vs. MySQL vs. ReductStore

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Widely used open source RDBMS

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

Primary database model

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	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Website

www.cockroachlabs.com

www.esgyn.cn

www.mysql.com

github.com/reductstore
www.reduct.store

Technical documentation

www.cockroachlabs.com/docs

dev.mysql.com/doc

www.reduct.store/docs

Developer

Cockroach Labs

Esgyn

Oracle

since 2010, originally MySQL AB, then Sun

ReductStore LLC

Initial release

2015

1995

2023

Current release

24.1.0, May 2024

9.0.0, July 2024

1.9, March 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Business Source License 1.1

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

C and C++

C++, Rust

Server operating systems

Linux
macOS
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Data scheme

dynamic schema

yes

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

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

C++
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

Java 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

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication between multi datacenters

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

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

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

fine grained access rights according to SQL-standard

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.