DBMS > CockroachDB vs. KairosDB vs. Microsoft SQL Server vs. Prometheus vs. ToroDB

System Properties Comparison CockroachDB vs. KairosDB vs. Microsoft SQL Server vs. Prometheus vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded 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.

Distributed Time Series DBMS based on Cassandra or H2

Microsofts flagship relational DBMS

Open-source Time Series DBMS and monitoring system

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

www.cockroachlabs.com

github.com/kairosdb/kairosdb

www.microsoft.com/en-us/sql-server

prometheus.io

github.com/torodb/server

Technical documentation

www.cockroachlabs.com/docs

kairosdb.github.io

learn.microsoft.com/en-US/sql/sql-server

prometheus.io/docs

Developer

Cockroach Labs

Microsoft

8Kdata

Initial release

2015

2013

1989

2015

2016

Current release

23.1.1, May 2023

1.2.2, November 2018

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

AGPL-V3

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Java

C++

Java

Server operating systems

Linux
macOS
Windows

Linux
OS X
Windows

Linux
Windows

All OS with a Java 7 VM

Data scheme

dynamic schema

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

string, integer, double, boolean, date, object_id

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

JDBC

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP/JSON API

Supported programming languages

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

Java
JavaScript

Node.js
PHP
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

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

based on Cassandra

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

selectable replication factor

based on Cassandra

yes, but depending on the SQL-Server Edition

yes

by Federation

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

simple password-based access control

fine grained access rights according to SQL-standard

Access rights for users and 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.