DBMS > Amazon Redshift vs. Firebase Realtime Database vs. Heroic vs. Microsoft Azure Data Explorer vs. Yanza

System Properties Comparison Amazon Redshift vs. Firebase Realtime Database vs. Heroic vs. Microsoft Azure Data Explorer vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Fully managed big data interactive analytics platform

Time Series DBMS for IoT Applications

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	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Website

aws.amazon.com/redshift

firebase.google.com/products/realtime-database

github.com/spotify/heroic

azure.microsoft.com/services/data-explorer

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

firebase.google.com/docs/database

spotify.github.io/heroic

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

Developer

Amazon (based on PostgreSQL)

Google

acquired by Google 2014

Spotify

Microsoft

Yanza

Initial release

2012

2014

2019

2015

Current release

cloud service with continuous releases

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

Windows

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

schema-free

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

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

restricted

yes

via Elasticsearch

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

Kusto Query Language (KQL), SQL subset

APIs and other access methods

JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript
Objective-C

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

limited functionality with using 'rules'

Yes, possible languages: KQL, Python, R

Triggers

Callbacks are triggered when data changes

yes

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

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

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

informational only, not enforced by the system

Transaction concepts

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

ACID

yes

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Azure Active Directory 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.