DBMS > DolphinDB vs. Faircom DB vs. Microsoft Azure Data Explorer vs. ObjectBox vs. SQLite

System Properties Comparison DolphinDB vs. Faircom DB vs. Microsoft Azure Data Explorer vs. ObjectBox vs. SQLite

Editorial information provided by DB-Engines

Name

Description

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

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

Extremely fast embedded database for small devices, IoT and Mobile

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

column oriented

Object oriented DBMS

Relational DBMS

Secondary database models

Relational 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

Time Series DBMS

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

Score	4.23
Rank	#82	Overall
	#6	Time Series DBMS

Score	0.24
Rank	#311	Overall
	#44	Key-value stores
	#140	Relational DBMS

Score	5.16
Rank	#69	Overall
	#37	Relational DBMS

Score	1.22
Rank	#172	Overall
	#5	Object oriented DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

www.dolphindb.com

www.faircom.com/products/faircom-db

azure.microsoft.com/services/data-explorer

objectbox.io

www.sqlite.org

Technical documentation

docs.dolphindb.cn/en/help200/index.html

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

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

docs.objectbox.io

www.sqlite.org/docs.html

Developer

DolphinDB, Inc

FairCom Corporation

Microsoft

ObjectBox Limited

Dwayne Richard Hipp

Initial release

2018

1979

2019

2017

2000

Current release

v2.00.4, January 2022

V12, November 2020

cloud service with continuous releases

3.45.2 (12 March 2024), March 2024

License

Commercial or Open Source

commercial

free community version available

commercial

Restricted, free version available

commercial

Open Source

Apache License 2.0

Open Source

Public Domain

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++

ANSI C, C++

C and C++

Server operating systems

Linux
Windows

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

easily portable to other OSs

hosted

Android
iOS
Linux
macOS
Windows

server-less

Data scheme

yes

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

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

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-like query language

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
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

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

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

.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++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

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

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

horizontal partitioning

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

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.

online/offline synchronization between client and server

none

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

Immediate Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Administrators, Users, Groups

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

Azure Active Directory Authentication

yes

More information provided by the system vendor

News

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

Vector Database Release for Flutter / Dart + Python
13 June 2023

SQLite and SQLite alternatives – a comprehensive overview
7 June 2023

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.