DBMS > CockroachDB vs. eXtremeDB vs. MySQL vs. SAP HANA

System Properties Comparison CockroachDB vs. eXtremeDB vs. MySQL vs. SAP HANA

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.

Natively in-memory DBMS with options for persistency, high-availability and clustering

Widely used open source RDBMS

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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.79
Rank	#212	Overall
	#100	Relational DBMS
	#18	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

www.cockroachlabs.com

www.mcobject.com

www.mysql.com

www.sap.com/products/hana.html

Technical documentation

www.cockroachlabs.com/docs

www.mcobject.com/docs/extremedb.htm

dev.mysql.com/doc

help.sap.com/hana

Developer

Cockroach Labs

McObject

Oracle

since 2010, originally MySQL AB, then Sun

SAP

Initial release

2015

2001

1995

2010

Current release

24.1.0, May 2024

8.2, 2021

9.0.0, July 2024

2.0 SPS07 (April 4, 2023), April 2023

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

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

Server operating systems

Linux
macOS
Windows

AIX
HP-UX
Linux
macOS
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

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.

support of XML interfaces available

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

with the option: eXtremeSQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

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

.Net
C
C#
C++
Java
Lua
Python
Scala

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

SQLScript, R

Triggers

yes

by defining 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

horizontal partitioning / sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

Multi-source replication
Source-replica replication

yes

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

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

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

yes

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.