DBMS > CockroachDB vs. Datomic vs. mSQL vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison CockroachDB vs. Datomic vs. mSQL vs. RocksDB vs. SAP SQL Anywhere

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.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

mSQL (Mini SQL) is a simple and lightweight RDBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.cockroachlabs.com

www.datomic.com

hughestech.com.au/products/msql

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

www.cockroachlabs.com/docs

docs.datomic.com

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Cockroach Labs

Cognitect

Hughes Technologies

Facebook, Inc.

SAP

formerly Sybase

Initial release

2015

2012

1994

2013

1992

Current release

23.1.1, May 2023

1.0.6735, June 2023

4.4, October 2021

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

commercial

free licenses can be provided

Open Source

BSD

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.

Implementation language

Java, Clojure

C++

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

dynamic schema

yes

schema-free

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

JDBC

RESTful HTTP API

JDBC
ODBC

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

Clojure
Java

C
C++
Delphi
Java
Perl
PHP
Tcl

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes, in C/C++, Java, .Net or Perl

Triggers

By using transaction functions

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

none

But extensive use of caching in the application peers

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

none

But extensive use of caching in the application peers

none

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Role-based access control

fine grained access rights according to SQL-standard

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.