DBMS > Faircom DB vs. Faircom EDGE vs. Microsoft Azure Data Explorer vs. SQLite vs. YottaDB

System Properties Comparison Faircom DB vs. Faircom EDGE vs. Microsoft Azure Data Explorer vs. SQLite vs. YottaDB

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.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Fully managed big data interactive analytics platform

Widely used embeddable, in-process RDBMS

A fast and solid embedded Key-value store

Primary database model

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

Relational DBMS

using the Octo plugin

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

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

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.faircom.com/products/faircom-db

www.faircom.com/products/faircom-edge

azure.microsoft.com/services/data-explorer

www.sqlite.org

yottadb.com

Technical documentation

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

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

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

www.sqlite.org/docs.html

yottadb.com/resources/documentation

Developer

FairCom Corporation

Microsoft

Dwayne Richard Hipp

YottaDB, LLC

Initial release

1979

2019

2000

2001

Current release

V12, November 2020

V3, October 2020

cloud service with continuous releases

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Restricted, free version available

commercial

Open Source

Public Domain

Open Source

AGPL 3.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++

Server operating systems

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

easily portable to other OSs

Android
Linux

ARM, x86
Raspbian
Windows

hosted

server-less

Docker
Linux

Data scheme

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

Flexible Schema (defined schema, partial schema, schema free)

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes, ANSI Standard SQL Types

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

yes, ANSI SQL with proprietary extensions

yes

ANSI SQL queries

Kusto Query Language (KQL), SQL subset

yes

SQL-92 is not fully supported

by using the Octo plugin

APIs and other access methods

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

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

.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
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

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

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

File partitioning

Customizable business rules for partitioning

Sharding

Implicit feature of the cloud service

none

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).

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

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

none

yes

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
Tunable Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

via file-system locks

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 user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Azure Active Directory Authentication

Users and groups based on OS-security mechanisms

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.