DBMS > Apache IoTDB vs. Oracle Berkeley DB vs. SpatiaLite vs. SQLite

System Properties Comparison Apache IoTDB vs. Oracle Berkeley DB vs. SpatiaLite 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

Widely used in-process key-value store

Spatial extension of SQLite

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

www.oracle.com/database/technologies/related/berkeleydb.html

www.gaia-gis.it/fossil/libspatialite/index

www.sqlite.org

Technical documentation

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

docs.oracle.com/cd/E17076_05/html/index.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Alessandro Furieri

Dwayne Richard Hipp

Initial release

2018

1994

2008

2000

Current release

1.1.0, April 2023

18.1.40, May 2020

5.0.0, August 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

commercial license available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

All OS with a Java VM (>= 1.8)

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

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

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

Source-replica replication

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

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

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.