DBMS > Apache Drill vs. Datomic vs. Faircom DB vs. Microsoft Azure Data Explorer vs. RocksDB

System Properties Comparison Apache Drill vs. Datomic vs. Faircom DB vs. Microsoft Azure Data Explorer vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

column oriented

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	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

drill.apache.org

www.datomic.com

www.faircom.com/products/faircom-db

azure.microsoft.com/services/data-explorer

rocksdb.org

Technical documentation

drill.apache.org/docs

docs.datomic.com

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

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

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Cognitect

FairCom Corporation

Microsoft

Facebook, Inc.

Initial release

2012

1979

2019

2013

Current release

1.20.3, January 2023

1.0.6735, June 2023

V12, November 2020

cloud service with continuous releases

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

commercial

Restricted, free version available

commercial

Open Source

BSD

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, Clojure

ANSI C, C++

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

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

easily portable to other OSs

hosted

Linux

Data scheme

schema-free

yes

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

Fixed schema with schema-less datatypes (dynamic)

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

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes, ANSI SQL with proprietary extensions

Kusto Query Language (KQL), SQL subset

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP 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

C++ API
Java API

Supported programming languages

C++

Clojure
Java

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

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

yes

.Net, JavaScript, C/C++

Yes, possible languages: KQL, Python, R

Triggers

By using transaction functions

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

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.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

ACID

tunable from ACID to Eventually Consistent

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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.

Depending on the underlying data source

yes

recommended only for testing and development

yes

User concepts

Access control

Depending on the underlying data source

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.