DBMS > CockroachDB vs. Datomic vs. KairosDB vs. SQLite vs. Transbase

System Properties Comparison CockroachDB vs. Datomic vs. KairosDB vs. SQLite vs. Transbase

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

Distributed Time Series DBMS based on Cassandra or H2

Widely used embeddable, in-process RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Time Series DBMS

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	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.cockroachlabs.com

www.datomic.com

github.com/kairosdb/kairosdb

www.sqlite.org

www.transaction.de/en/products/transbase.html

Technical documentation

www.cockroachlabs.com/docs

docs.datomic.com

kairosdb.github.io

www.sqlite.org/docs.html

www.transaction.de/en/products/transbase/features.html

Developer

Cockroach Labs

Cognitect

Dwayne Richard Hipp

Transaction Software GmbH

Initial release

2015

2012

2013

2000

1987

Current release

23.1.1, May 2023

1.0.6735, June 2023

1.2.2, November 2018

3.45.3 (15 April 2024), April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

Open Source

Apache 2.0

Open Source

Public Domain

commercial

free development license

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

Java

C and C++

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

Linux
OS X
Windows

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

dynamic schema

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Clojure
Java

Java
JavaScript

Node.js
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

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

Sharding

based on Cassandra

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

selectable replication factor

based on Cassandra

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

simple password-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.