DBMS > Apache IoTDB vs. EJDB vs. IBM Db2 vs. SQLite

System Properties Comparison Apache IoTDB vs. EJDB vs. IBM Db2 vs. SQLite

Please select another system to include it in the comparison.

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)

Common in IBM host environments, 2 different versions for host and Windows/Linux

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	123.05
Rank	#9	Overall
	#6	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

github.com/Softmotions/ejdb

www.ibm.com/products/db2

www.sqlite.org

Technical documentation

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

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

www.ibm.com/docs/en/db2

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Softmotions

IBM

Dwayne Richard Hipp

Initial release

2018

2012

1983

host version

2000

Current release

1.1.0, April 2023

12.1, October 2016

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

free version is available

Open Source

Public Domain

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 and C++

Server operating systems

All OS with a Java VM (>= 1.8)

server-less

AIX
HP-UX
Linux
Solaris
Windows
z/OS

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

in-process shared library

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

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

Sharding

only with Windows/Unix/Linux Version

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

with separate tools (MQ, InfoSphere)

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

via file-system locks

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

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.