DBMS > Elasticsearch vs. Firebase Realtime Database vs. Ignite vs. Microsoft Azure Data Explorer vs. Snowflake

System Properties Comparison Elasticsearch vs. Firebase Realtime Database vs. Ignite vs. Microsoft Azure Data Explorer vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Fully managed big data interactive analytics platform

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

Primary database model

Search engine

Document store

Key-value store
Relational DBMS

Relational DBMS

column oriented

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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	135.35
Rank	#7	Overall
	#1	Search engines

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.elastic.co/elasticsearch

firebase.google.com/products/realtime-database

ignite.apache.org

azure.microsoft.com/services/data-explorer

www.snowflake.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

firebase.google.com/docs/database

apacheignite.readme.io/docs

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

docs.snowflake.net/manuals/index.html

Developer

Elastic

Google

acquired by Google 2014

Apache Software Foundation

Microsoft

Snowflake Computing Inc.

Initial release

2010

2012

2015

2019

2014

Current release

8.6, January 2023

Apache Ignite 2.6

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Elastic License

commercial

Open Source

Apache 2.0

commercial

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++, Java, .Net

Server operating systems

All OS with a Java VM

hosted

Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

Fixed schema with schema-less datatypes (dynamic)

yes

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

Typing

predefined data types such as float or date

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 search fields are automatically indexed

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

Android
iOS
JavaScript API
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
JavaScript
Objective-C

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

yes (compute grid and cache interceptors can be used instead)

Yes, possible languages: KQL, Python, R

user defined functions

Triggers

yes

by using the 'percolation' feature

Callbacks are triggered when data changes

yes (cache interceptors and events)

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

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

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

ES-Hadoop Connector

yes (compute grid and hadoop accelerator)

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Memcached and Redis integration

yes

User concepts

Access control

yes, based on authentication and database rules

Security Hooks for custom implementations

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.