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

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

Editorial information provided by DB-Engines

Name

Description

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

A Java embedded Key-Value Store which extends the Java Map interface

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

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	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.00
Rank	#378	Overall
	#57	Key-value 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

firebase.google.com/products/realtime-database

boilerbay.com

azure.microsoft.com/services/data-explorer

www.snowflake.com

sphinxsearch.com

Technical documentation

firebase.google.com/docs/database

boilerbay.com/infinitydb/manual

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

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Google

acquired by Google 2014

Boiler Bay Inc.

Microsoft

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2012

2002

2019

2014

2001

Current release

4.0

cloud service with continuous releases

3.5.1, February 2023

License

Commercial or Open Source

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

Java

C++

Server operating systems

hosted

All OS with a Java VM

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

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

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

all fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

SQL-like query language (SphinxQL)

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

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

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

Java
JavaScript
Objective-C

Java

.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

limited functionality with using 'rules'

Yes, possible languages: KQL, Python, R

user defined functions

Triggers

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

none

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

none

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

yes

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

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.