DBMS > H2 vs. Microsoft Azure Data Explorer vs. MySQL vs. Oracle Berkeley DB vs. TerminusDB

System Properties Comparison H2 vs. Microsoft Azure Data Explorer vs. MySQL vs. Oracle Berkeley DB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Fully managed big data interactive analytics platform

Widely used open source RDBMS

Widely used in-process key-value store

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Graph DBMS

Secondary database models

Spatial DBMS

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

Document store
RDF store

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

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.h2database.com

azure.microsoft.com/services/data-explorer

www.mysql.com

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

terminusdb.com

Technical documentation

www.h2database.com/html/main.html

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

dev.mysql.com/doc

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

terminusdb.github.io/terminusdb/#

Developer

Thomas Mueller

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

originally developed by Sleepycat, which was acquired by Oracle

DataChemist Ltd.

Initial release

2005

2019

1995

1994

2018

Current release

2.2.220, July 2023

cloud service with continuous releases

8.4.0, April 2024

18.1.40, May 2020

11.0.0, January 2023

License

Commercial or Open Source

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial license available

Open Source

GPL V3

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

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

Prolog, Rust

Server operating systems

All OS with a Java VM

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

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

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

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

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Java

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.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

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

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

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

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

Multi-source replication
Source-replica replication

Source-replica replication

Journaling Streams

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

no user groups or roles

Role-based access control

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.