DBMS > KairosDB vs. Microsoft Azure Cosmos DB vs. Splice Machine vs. TerarkDB

System Properties Comparison KairosDB vs. Microsoft Azure Cosmos DB vs. Splice Machine vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

Globally distributed, horizontally scalable, multi-model database service

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

github.com/kairosdb/kairosdb

azure.microsoft.com/services/cosmos-db

splicemachine.com

github.com/bytedance/terarkdb

Technical documentation

kairosdb.github.io

learn.microsoft.com/azure/cosmos-db

splicemachine.com/how-it-works

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Microsoft

Splice Machine

ByteDance, originally Terark

Initial release

2013

2014

2016

Current release

1.2.2, November 2018

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

AGPL 3.0, commercial license available

commercial

restricted open source version available

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

Java

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
Native Spark Datasource
ODBC

C++ API
Java API

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

C++
Java

Server-side scripts

Stored procedures

JavaScript

yes

Java

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Implicit feature of the cloud service

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

simple password-based access control

Access rights can be defined down to the item level

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