DBMS > CockroachDB vs. MySQL vs. OpenQM vs. Rockset

System Properties Comparison CockroachDB vs. MySQL vs. OpenQM vs. Rockset

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.

Widely used open source RDBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS

Key/Value like access via memcached API

Multivalue DBMS

Document store

Secondary database models

Document store
Spatial DBMS

Relational DBMS
Search engine

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

www.cockroachlabs.com

www.mysql.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

rockset.com

Technical documentation

www.cockroachlabs.com/docs

dev.mysql.com/doc

docs.rockset.com

Developer

Cockroach Labs

Oracle

since 2010, originally MySQL AB, then Sun

Rocket Software, originally Martin Phillips

Rockset

Initial release

2015

1995

1993

2019

Current release

24.1.0, May 2024

9.0.0, July 2024

3.4-12

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

GPLv2, extended commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

C++

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted

Data scheme

dynamic schema

yes

with some exceptions

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

Read-only SQL queries, including JOINs

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

.Net
Basic
C
Java
Objective C
PHP
Python

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

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

yes

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

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

Eventual 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

ACID

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

Access rights can be defined down to the item level

Access rights for users and organizations can be defined via Rockset console

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.