DBMS > Microsoft Azure Cosmos DB vs. Quasardb vs. SiteWhere vs. SQL.JS

System Properties Comparison Microsoft Azure Cosmos DB vs. Quasardb vs. SiteWhere vs. SQL.JS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

Distributed, high-performance timeseries database

M2M integration platform for persisting/querying time series data

Port of SQLite to JavaScript

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

quasar.ai

github.com/sitewhere/sitewhere

sql.js.org

Technical documentation

learn.microsoft.com/azure/cosmos-db

doc.quasar.ai/master

sitewhere1.sitewhere.io/index.html

sql.js.org/documentation/index.html

Developer

Microsoft

quasardb

SiteWhere

Alon Zakai

enhancements implemented by others

Initial release

2014

2009

2010

2012

Current release

3.14.1, January 2024

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Common Public Attribution License Version 1.0

Open Source

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

C++

Java

JavaScript

Server operating systems

hosted

BSD
Linux
OS X
Windows

Linux
OS X
Windows

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

Data scheme

schema-free

predefined scheme

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

integer and binary

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

yes

with tags

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

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

HTTP API

HTTP REST

JavaScript API

Supported programming languages

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

consistent hashing

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication with selectable replication factor

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of 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 LevelDB

yes

except by serializing a db to a file

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

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.