DBMS > Faircom EDGE vs. Firebase Realtime Database vs. Microsoft Azure Data Explorer vs. Snowflake vs. Sphinx

System Properties Comparison Faircom EDGE vs. Firebase Realtime Database vs. Microsoft Azure Data Explorer vs. Snowflake vs. Sphinx

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

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.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

www.faircom.com/products/faircom-edge

firebase.google.com/products/realtime-database

azure.microsoft.com/services/data-explorer

www.snowflake.com

sphinxsearch.com

Technical documentation

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

firebase.google.com/docs/database

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

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

FairCom Corporation

Google

acquired by Google 2014

Microsoft

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

1979

2012

2019

2014

2001

Current release

V3, October 2020

cloud service with continuous releases

3.5.1, February 2023

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

GPL version 2, commercial licence 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++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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

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

SQL

Support of SQL

yes

ANSI SQL queries

Kusto Query Language (KQL), SQL subset

yes

SQL-like query language (SphinxQL)

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

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

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

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

Java
JavaScript
Objective-C

.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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

limited functionality with using 'rules'

Yes, possible languages: KQL, Python, R

user defined functions

Triggers

yes

Callbacks are triggered when data changes

yes

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

similar concept for controling cloud resources

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

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

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

Immediate Consistency
Tunable Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes

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

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.

yes, based on authentication and database rules

Azure Active Directory Authentication

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

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.