DBMS > Apache IoTDB vs. Datomic vs. KairosDB vs. PostGIS vs. RocksDB

System Properties Comparison Apache IoTDB vs. Datomic vs. KairosDB vs. PostGIS vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

Spatial extension of PostgreSQL

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Relational DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

iotdb.apache.org

www.datomic.com

github.com/kairosdb/kairosdb

postgis.net

rocksdb.org

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

docs.datomic.com

kairosdb.github.io

postgis.net/documentation

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Cognitect

Facebook, Inc.

Initial release

2018

2012

2013

2005

2013

Current release

1.1.0, April 2023

1.0.7075, December 2023

1.2.2, November 2018

3.4.2, February 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

limited edition free

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

BSD

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

Java, Clojure

Java

C++

Server operating systems

All OS with a Java VM (>= 1.8)

All OS with a Java VM

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

C++ API
Java API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Clojure
Java

Java
JavaScript

Node.js
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

yes

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

But extensive use of caching in the application peers

Sharding

based on Cassandra

yes

based on PostgreSQL

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

But extensive use of caching in the application peers

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

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

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

yes

simple password-based access control

yes

based on PostgreSQL

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.