DBMS > Apache IoTDB vs. EJDB vs. LevelDB vs. RocksDB vs. Tkrzw

System Properties Comparison Apache IoTDB vs. EJDB vs. LevelDB vs. RocksDB vs. Tkrzw

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Time Series DBMS

Document store

Key-value store

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

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

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

iotdb.apache.org

github.com/Softmotions/ejdb

github.com/google/leveldb

rocksdb.org

dbmx.net/tkrzw

Technical documentation

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

github.com/Softmotions/ejdb/blob/master/README.md

github.com/google/leveldb/blob/main/doc/index.md

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Softmotions

Google

Facebook, Inc.

Mikio Hirabayashi

Initial release

2018

2012

2011

2013

2020

Current release

1.1.0, April 2023

1.23, February 2021

9.2.1, May 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

Open Source

BSD

Open Source

BSD

Open Source

Apache Version 2.0

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

C++

Server operating systems

All OS with a Java VM (>= 1.8)

server-less

Illumos
Linux
OS X
Windows

Linux

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, 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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

JDBC
Native API

in-process shared library

C++ API
Java API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

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

yes

none

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

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

User concepts

Access control

yes

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.