DBMS > AlaSQL vs. ITTIA vs. Microsoft Azure Cosmos DB vs. SiteWhere

System Properties Comparison AlaSQL vs. ITTIA 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

Edge Time Series DBMS with Real-Time Stream Processing

Globally distributed, horizontally scalable, multi-model database service

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	0.44
Rank	#267	Overall
	#23	Time Series DBMS

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

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

alasql.org

www.ittia.com

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

Technical documentation

github.com/AlaSQL/alasql

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

Developer

Andrey Gershun & Mathias R. Wulff

ITTIA L.L.C.

Microsoft

SiteWhere

Initial release

2014

2007

2014

2010

Current release

8.7

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

C and C++

Java

Server operating systems

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

Linux
Windows

hosted

Linux
OS X
Windows

Data scheme

schema-free

Fixed schema

schema-free

predefined scheme

Typing

predefined data types such as float or date

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

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.

yes

SQL-like query language

APIs and other access methods

JavaScript API

JDBC
ODBC
RESTful HTTP API
WebSocket

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

HTTP REST

Supported programming languages

JavaScript

C
C++
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

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

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate 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

yes

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

Database file passwords

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.