DBMS > Microsoft Azure Cosmos DB vs. SiteWhere vs. TimescaleDB vs. VelocityDB

System Properties Comparison Microsoft Azure Cosmos DB vs. SiteWhere vs. TimescaleDB vs. VelocityDB

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

M2M integration platform for persisting/querying time series data

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Graph DBMS
Object oriented DBMS

Secondary database models

Spatial DBMS

Relational 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.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

azure.microsoft.com/services/cosmos-db

github.com/sitewhere/sitewhere

www.timescale.com

velocitydb.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

sitewhere1.sitewhere.io/index.html

docs.timescale.com

velocitydb.com/UserGuide

Developer

Microsoft

SiteWhere

Timescale

VelocityDB Inc

Initial release

2014

2010

2017

2011

Current release

2.15.0, May 2024

7.x

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

Apache 2.0

commercial

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

Java

Server operating systems

hosted

Linux
OS X
Windows

Any that supports .NET

Data scheme

schema-free

predefined scheme

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data 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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

HTTP REST

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

.Net

Supported programming languages

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

.Net

Server-side scripts

Stored procedures

JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

JavaScript

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

Source-replica replication with hot standby and reads on replicas

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

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

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

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 can be defined down to the item level

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

Based on Windows Authentication

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.