DBMS > Apache Druid vs. Faircom DB vs. Microsoft Azure Data Explorer vs. SQLite vs. TerarkDB

System Properties Comparison Apache Druid vs. Faircom DB vs. Microsoft Azure Data Explorer vs. SQLite vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Fully managed big data interactive analytics platform

Widely used embeddable, in-process RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS
Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

column oriented

Relational DBMS

Key-value store

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

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

druid.apache.org

www.faircom.com/products/faircom-db

azure.microsoft.com/services/data-explorer

www.sqlite.org

github.com/bytedance/terarkdb

Technical documentation

druid.apache.org/docs/latest/design

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

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

www.sqlite.org/docs.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation and contributors

FairCom Corporation

Microsoft

Dwayne Richard Hipp

ByteDance, originally Terark

Initial release

2012

1979

2019

2000

2016

Current release

29.0.1, April 2024

V12, November 2020

cloud service with continuous releases

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Restricted, free version available

commercial

Open Source

Public Domain

commercial

restricted open source version available

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

Java

ANSI C, C++

C++

Server operating systems

Linux
OS X
Unix

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

hosted

server-less

Data scheme

yes

schema-less columns are supported

schema free, schema optional, schema required, partial schema,

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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.

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

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

yes, ANSI SQL with proprietary extensions

Kusto Query Language (KQL), SQL subset

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

C++ API
Java API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
Go
Java
JavaScript (Node.js)
PowerShell
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

C++
Java

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Yes, possible languages: KQL, Python, R

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

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

none

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
Tunable consistency per server, database, table, and transaction

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Fine grained access rights according to SQL-standard with additional protections for files

Azure Active Directory Authentication

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.