DBMS > Faircom DB vs. H2 vs. Microsoft Azure Data Explorer vs. RocksDB vs. SiteWhere

System Properties Comparison Faircom DB vs. H2 vs. Microsoft Azure Data Explorer vs. RocksDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

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

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

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

M2M integration platform for persisting/querying time series data

Primary database model

Key-value store
Relational DBMS

Relational DBMS

column oriented

Key-value store

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

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

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

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.faircom.com/products/faircom-db

www.h2database.com

azure.microsoft.com/services/data-explorer

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

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

www.h2database.com/html/main.html

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

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

FairCom Corporation

Thomas Mueller

Microsoft

Facebook, Inc.

SiteWhere

Initial release

1979

2005

2019

2013

2010

Current release

V12, November 2020

2.2.220, July 2023

cloud service with continuous releases

8.11.4, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

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

commercial

Open Source

BSD

Open Source

Common Public Attribution License Version 1.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

ANSI C, C++

Java

C++

Java

Server operating systems

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

easily portable to other OSs

All OS with a Java VM

hosted

Linux

Linux
OS X
Windows

Data scheme

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

yes

Fixed schema with schema-less datatypes (dynamic)

schema-free

predefined scheme

Typing

predefined data types such as float or date

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

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

yes, ANSI SQL with proprietary extensions

yes

Kusto Query Language (KQL), SQL subset

APIs and other access methods

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

JDBC
ODBC

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

C++ API
Java API

HTTP REST

Supported programming languages

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

Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Java Stored Procedures and User-Defined Functions

Yes, possible languages: KQL, Python, R

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

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

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.

yes

selectable replication factor

based on HBase

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

Immediate 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

tunable from ACID to Eventually Consistent

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

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

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

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.