DBMS > Apache IoTDB vs. OpenEdge vs. Oracle Berkeley DB vs. SAP Adaptive Server vs. SQLite

System Properties Comparison Apache IoTDB vs. OpenEdge vs. Oracle Berkeley DB vs. SAP Adaptive Server vs. SQLite

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

Application development environment with integrated database management system

Widely used in-process key-value store

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	1.19
Rank	#176	Overall
	#15	Time Series DBMS

Score	3.75
Rank	#88	Overall
	#47	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	37.12
Rank	#25	Overall
	#17	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

www.progress.com/openedge

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

www.sap.com/products/technology-platform/sybase-ase.html

www.sqlite.org

Technical documentation

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

documentation.progress.com/output/ua/OpenEdge_latest

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

help.sap.com/docs/SAP_ASE

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Progress Software Corporation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SAP, Sybase

Dwayne Richard Hipp

Initial release

2018

1984

1994

1987

2000

Current release

1.1.0, April 2023

OpenEdge 12.2, March 2020

18.1.40, May 2020

16.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

commercial license available

commercial

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

Server operating systems

All OS with a Java VM (>= 1.8)

AIX
HP-UX
Linux
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

AIX
HP-UX
Linux
Solaris
Unix
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

close to SQL 92

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Progress proprietary ABL (Advanced Business Language)

.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

C
C++
Cobol
Java
Java
Perl
PHP
Python

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

Java and Transact-SQL

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)

horizontal partitioning

since Version 11.4

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

Source-replica replication

Multi-source replication
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

Immediate Consistency

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

Users and groups

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.