DBMS > Microsoft Azure Cosmos DB vs. MonetDB vs. SiteWhere vs. SQLite

System Properties Comparison Microsoft Azure Cosmos DB vs. MonetDB vs. SiteWhere vs. SQLite

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

A relational database management system that stores data in columns

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

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

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

www.monetdb.org

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

learn.microsoft.com/azure/cosmos-db

www.monetdb.org/Documentation

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

Microsoft

MonetDB BV

SiteWhere

Dwayne Richard Hipp

Initial release

2014

2004

2010

2000

Current release

Dec2023 (11.49), December 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Mozilla Public License 2.0

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

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

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

JSON types

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language

yes

SQL 2003 with some extensions

yes

SQL-92 is not fully supported

APIs and other access methods

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

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

JavaScript

yes, in SQL, C, R

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding via remote tables

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

Source-replica replication available in experimental status

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*

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

via file-system locks

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

fine grained access rights according to SQL-standard

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.