DBMS > AlaSQL vs. Firebase Realtime Database vs. Microsoft Azure Data Explorer vs. SQLite vs. Vitess

System Properties Comparison AlaSQL vs. Firebase Realtime Database vs. Microsoft Azure Data Explorer vs. SQLite vs. Vitess

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

column oriented

Relational DBMS

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

Document store
Spatial DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

alasql.org

firebase.google.com/products/realtime-database

azure.microsoft.com/services/data-explorer

www.sqlite.org

vitess.io

Technical documentation

github.com/AlaSQL/alasql

firebase.google.com/docs/database

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

www.sqlite.org/docs.html

vitess.io/docs

Developer

Andrey Gershun & Mathias R. Wulff

Google

acquired by Google 2014

Microsoft

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2014

2012

2019

2000

2013

Current release

cloud service with continuous releases

3.46.0 (23 May 2024), May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses 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

JavaScript

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

server-less

Docker
Linux
macOS

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

yes

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

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

Kusto Query Language (KQL), SQL subset

yes

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

JavaScript API

Android
iOS
JavaScript API
RESTful HTTP API

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript

Java
JavaScript
Objective-C

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

Triggers

yes

Callbacks are triggered when data changes

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Sharding

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.

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

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

yes

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

yes, based on authentication and database rules

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

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.