DBMS > AlaSQL vs. Amazon DocumentDB vs. Microsoft Azure Cosmos DB vs. SiteWhere

System Properties Comparison AlaSQL vs. Amazon DocumentDB vs. Microsoft Azure Cosmos DB vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Globally distributed, horizontally scalable, multi-model database service

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

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	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

alasql.org

aws.amazon.com/documentdb

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

Technical documentation

github.com/AlaSQL/alasql

aws.amazon.com/documentdb/resources

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Microsoft

SiteWhere

Initial release

2014

2019

2014

2010

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Common Public Attribution License Version 1.0

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

Java

Server operating systems

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

hosted

Linux
OS X
Windows

Data scheme

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

JSON 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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

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

SQL-like query language

APIs and other access methods

JavaScript API

proprietary protocol using JSON (MongoDB compatible)

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

HTTP REST

Supported programming languages

JavaScript

Go
Java
JavaScript (Node.js)
PHP
Python

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

Server-side scripts

Stored procedures

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

yes

only for local storage and DOM-storage

Atomic single-document operations

Multi-item ACID transactions with snapshot isolation within a partition

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

User concepts

Access control

Access rights for users and roles

Access rights can be defined down to the item level

Users with fine-grained authorization concept

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.