DBMS > Faircom EDGE vs. Microsoft Azure Data Explorer vs. Snowflake vs. Sphinx vs. Splice Machine

System Properties Comparison Faircom EDGE vs. Microsoft Azure Data Explorer vs. Snowflake vs. Sphinx vs. Splice Machine

Editorial information provided by DB-Engines

Name

Description

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

Cloud-based data warehousing service for structured and semi-structured data

Open source search engine for searching in data from different sources, e.g. relational databases

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

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

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

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

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

www.faircom.com/products/faircom-edge

azure.microsoft.com/services/data-explorer

www.snowflake.com

sphinxsearch.com

splicemachine.com

Technical documentation

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

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

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

splicemachine.com/how-it-works

Developer

FairCom Corporation

Microsoft

Snowflake Computing Inc.

Sphinx Technologies Inc.

Splice Machine

Initial release

1979

2019

2014

2001

2014

Current release

V3, October 2020

cloud service with continuous releases

3.5.1, February 2023

3.1, March 2021

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, commercial license available

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

C++

Java

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

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

Fixed schema with schema-less datatypes (dynamic)

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

ANSI SQL queries

Kusto Query Language (KQL), SQL subset

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

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

CLI Client
JDBC
ODBC

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

Supported programming languages

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

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

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Yes, possible languages: KQL, Python, R

user defined functions

yes

Java

Triggers

yes

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

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

Implicit feature of the cloud service

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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.

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Eventual Consistency
Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

Azure Active Directory Authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users, groups and roles according to SQL-standard

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.