DBMS > IBM Db2 Event Store vs. Microsoft Azure Data Explorer vs. Oracle Berkeley DB vs. SQLite vs. TDSQL for MySQL

System Properties Comparison IBM Db2 Event Store vs. Microsoft Azure Data Explorer vs. Oracle Berkeley DB vs. SQLite vs. TDSQL for MySQL

Editorial information provided by DB-Engines

Name

Description

Distributed Event Store optimized for Internet of Things use cases

Fully managed big data interactive analytics platform

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

Primary database model

Event Store
Time Series DBMS

Relational DBMS

column oriented

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store
Spatial DBMS

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

Score	0.18
Rank	#315	Overall
	#2	Event Stores
	#26	Time Series DBMS

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.96
Rank	#192	Overall
	#88	Relational DBMS

Website

www.ibm.com/products/db2-event-store

azure.microsoft.com/services/data-explorer

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

www.sqlite.org

www.tencentcloud.com/products/dcdb

Technical documentation

www.ibm.com/docs/en/db2-event-store

docs.microsoft.com/en-us/azure/data-explorer

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

www.sqlite.org/docs.html

www.tencentcloud.com/document/product/1042

Developer

IBM

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Tencent

Initial release

2017

2019

1994

2000

2013

Current release

2.0

cloud service with continuous releases

18.1.40, May 2020

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

free developer edition available

commercial

Open Source

commercial license available

Open Source

Public Domain

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

hosted

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

yes

not rigid because of 'dynamic typing' concept.

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

only with the Berkeley DB XML edition

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

Kusto Query Language (KQL), SQL subset

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

.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

C
C#
C++
Java
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

yes

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

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

No - written data is immutable

yes

via file-system locks

yes

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

Users with fine-grained authorization concept

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.