DBMS > Apache IoTDB vs. Datomic vs. RocksDB vs. SAP SQL Anywhere vs. Transbase

System Properties Comparison Apache IoTDB vs. Datomic vs. RocksDB vs. SAP SQL Anywhere vs. Transbase

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

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

iotdb.apache.org

www.datomic.com

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

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

Technical documentation

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

docs.datomic.com

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

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

Developer

Apache Software Foundation

Cognitect

Facebook, Inc.

SAP

formerly Sybase

Transaction Software GmbH

Initial release

2018

2012

2013

1992

1987

Current release

1.1.0, April 2023

1.0.6735, June 2023

8.11.4, April 2024

17, July 2015

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

limited edition free

Open Source

BSD

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

Java, Clojure

C++

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

All OS with a Java VM

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

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

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Clojure
Java

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Transaction Functions

yes, in C/C++, Java, .Net or Perl

yes

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

horizontal partitioning

none

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

yes

Source-replica replication

Database mirroring

Source-replica replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

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.