DBMS > AlaSQL vs. Firebase Realtime Database vs. Google Cloud Datastore vs. Microsoft Azure Data Explorer vs. Oracle

System Properties Comparison AlaSQL vs. Firebase Realtime Database vs. Google Cloud Datastore vs. Microsoft Azure Data Explorer vs. Oracle

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Fully managed big data interactive analytics platform

Widely used RDBMS

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
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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.47
Rank	#76	Overall
	#12	Document stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

alasql.org

firebase.google.com/products/realtime-database

cloud.google.com/datastore

azure.microsoft.com/services/data-explorer

www.oracle.com/database

Technical documentation

github.com/AlaSQL/alasql

firebase.google.com/docs/database

cloud.google.com/datastore/docs

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

docs.oracle.com/en/database

Developer

Andrey Gershun & Mathias R. Wulff

Google

acquired by Google 2014

Google

Microsoft

Oracle

Initial release

2014

2012

2008

2019

1980

Current release

cloud service with continuous releases

23c, September 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

restricted free version is 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

C and C++

Server operating systems

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

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

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

SQL-like query language (GQL)

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

APIs and other access methods

JavaScript API

Android
iOS
JavaScript API
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

JavaScript

Java
JavaScript
Objective-C

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

limited functionality with using 'rules'

using Google App Engine

Yes, possible languages: KQL, Python, R

PL/SQL

also stored procedures in Java possible

Triggers

yes

Callbacks are triggered when data changes

Callbacks using the Google Apps Engine

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

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

yes

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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

can be realized in PL/SQL

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

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

yes, based on authentication and database rules

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

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.