DBMS > Microsoft Azure Data Explorer vs. Oracle Berkeley DB vs. Quasardb vs. SQLite vs. TimescaleDB

System Properties Comparison Microsoft Azure Data Explorer vs. Oracle Berkeley DB vs. Quasardb vs. SQLite vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Fully managed big data interactive analytics platform

Widely used in-process key-value store

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

column oriented

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Relational DBMS

Time Series 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

Relational DBMS

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

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

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

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

azure.microsoft.com/services/data-explorer

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

quasar.ai

www.sqlite.org

www.timescale.com

Technical documentation

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

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

doc.quasar.ai/master

www.sqlite.org/docs.html

docs.timescale.com

Developer

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

quasardb

Dwayne Richard Hipp

Timescale

Initial release

2019

1994

2009

2000

2017

Current release

cloud service with continuous releases

18.1.40, May 2020

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Public Domain

Open Source

Apache 2.0

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

C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

BSD
Linux
OS X
Windows

server-less

Linux
OS X
Windows

Data scheme

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

integer and binary

yes

not rigid because of 'dynamic typing' concept.

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

Secondary indexes

all fields are automatically indexed

yes

with tags

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

SQL interfaced based on SQLite is available

SQL-like query language

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

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

Sharding

consistent hashing

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

Source-replica replication

Source-replica replication with selectable replication factor

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

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

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Azure Active Directory Authentication

Cryptographically strong user authentication and audit trail

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.