DBMS > AlaSQL vs. Google BigQuery vs. Microsoft Azure Cosmos DB vs. XTDB

System Properties Comparison AlaSQL vs. Google BigQuery vs. Microsoft Azure Cosmos DB vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service with append-only tables

Globally distributed, horizontally scalable, multi-model database service

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

alasql.org

cloud.google.com/bigquery

azure.microsoft.com/services/cosmos-db

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

learn.microsoft.com/azure/cosmos-db

www.xtdb.com/docs

Developer

Andrey Gershun & Mathias R. Wulff

Google

Microsoft

Juxt Ltd.

Initial release

2014

2010

2014

2019

Current release

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

MIT License

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

Clojure

Server operating systems

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

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes, extensible-data-notation format

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

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

yes

SQL-like query language

limited SQL, making use of Apache Calcite

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP REST
JDBC

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

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

Since BigQuery is designed for querying data

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights can be defined down to the item level

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.