DBMS > AlaSQL vs. Amazon DynamoDB vs. Firebase Realtime Database vs. Microsoft Azure Data Explorer vs. Tarantool

System Properties Comparison AlaSQL vs. Amazon DynamoDB vs. Firebase Realtime Database vs. Microsoft Azure Data Explorer vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

column oriented

Document store
Key-value store
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

Spatial DBMS

with Tarantool/GIS extension

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	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

alasql.org

aws.amazon.com/dynamodb

firebase.google.com/products/realtime-database

azure.microsoft.com/services/data-explorer

www.tarantool.io

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/dynamodb

firebase.google.com/docs/database

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

www.tarantool.io/en/doc

Developer

Andrey Gershun & Mathias R. Wulff

Amazon

Google

acquired by Google 2014

Microsoft

Initial release

2014

2012

2019

2008

Current release

cloud service with continuous releases

2.10.0, May 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

free tier for a limited amount of database operations

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

BSD
Linux
macOS

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

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

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

JavaScript API

RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

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

Open binary protocol

Supported programming languages

JavaScript

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java
JavaScript
Objective-C

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Yes, possible languages: KQL, Python, R

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

Callbacks are triggered when data changes

yes

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

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

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.

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency
Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

ACID across one or more tables within a single AWS account and region

yes

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

yes, based on authentication and database rules

Azure Active Directory Authentication

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.