DBMS > CockroachDB vs. MySQL vs. QuestDB vs. STSdb vs. TempoIQ

System Properties Comparison CockroachDB vs. MySQL vs. QuestDB vs. STSdb vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

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

A high performance open source SQL database for time series data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Key-value store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

www.cockroachlabs.com

www.mysql.com

questdb.io

github.com/STSSoft/STSdb4

tempoiq.com (offline)

Technical documentation

www.cockroachlabs.com/docs

dev.mysql.com/doc

questdb.io/docs

Developer

Cockroach Labs

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

STS Soft SC

TempoIQ

Initial release

2015

1995

2014

2011

2012

Current release

24.1.0, May 2024

9.0.0, July 2024

4.0.8, September 2015

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

Apache 2.0

Open Source

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

Java (Zero-GC), C++, Rust

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Windows

Data scheme

dynamic schema

yes

schema-free via InfluxDB Line Protocol

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL with time-series extensions

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

.NET Client API

HTTP API

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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C#
Java

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Realtime Alerts

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

horizontal partitioning (by timestamps)

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

none

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

ACID for single-table writes

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

through memory mapped files

User concepts

Access control

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

simple authentication-based access control

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 2024

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.