DBMS > Faircom DB vs. FileMaker vs. KeyDB vs. Microsoft Azure Data Explorer vs. SAP HANA

System Properties Comparison Faircom DB vs. FileMaker vs. KeyDB vs. Microsoft Azure Data Explorer vs. SAP HANA

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.

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Fully managed big data interactive analytics platform

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Key-value store
Relational DBMS

column oriented

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

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.claris.com/filemaker

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/services/data-explorer

www.sap.com/products/hana.html

Technical documentation

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

www.claris.com/resources/documentation

docs.keydb.dev

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

help.sap.com/hana

Developer

FairCom Corporation

Claris

a subsidiary of Apple

EQ Alpha Technology Ltd.

Microsoft

SAP

Initial release

1979

1983

2019

2010

Current release

V12, November 2020

19.4.1, November 2021

cloud service with continuous releases

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

BSD-3

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

ANSI C, C++

C++

Server operating systems

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

easily portable to other OSs

iOS

client part only
Linux
OS X
Windows

Linux

hosted

Appliance or cloud-service

Data scheme

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

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

A http query request can return the data in XML format

yes

Secondary indexes

yes

by using the Redis Search module

all fields are automatically indexed

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

via plugins

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

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

Filemaker WebDirect
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

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

JDBC
ODBC

Supported programming languages

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

PHP

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Lua

Yes, possible languages: KQL, Python, R

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

none

Sharding

Implicit feature of the cloud service

yes

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

Source-replica replication, warm standby

since Version 14

Multi-source replication
Source-replica replication

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

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

Eventual Consistency
Strong eventual consistency with CRDTs

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple rights management via user accounts and connection to external directory services

simple password-based access control and ACL

Azure Active Directory Authentication

yes

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.