DBMS > Microsoft Azure Cosmos DB vs. Prometheus vs. RocksDB vs. SpatiaLite vs. Tkrzw

System Properties Comparison Microsoft Azure Cosmos DB vs. Prometheus vs. RocksDB vs. SpatiaLite vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Globally distributed, horizontally scalable, multi-model database service

Open-source Time Series DBMS and monitoring system

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Spatial extension of SQLite

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

Relational 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	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

azure.microsoft.com/services/cosmos-db

prometheus.io

rocksdb.org

www.gaia-gis.it/fossil/libspatialite/index

dbmx.net/tkrzw

Technical documentation

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

github.com/facebook/rocksdb/wiki

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Microsoft

Facebook, Inc.

Alessandro Furieri

Mikio Hirabayashi

Initial release

2014

2015

2013

2008

2020

Current release

8.11.4, April 2024

5.0.0, August 2020

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Apache Version 2.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

C++

Server operating systems

hosted

Linux
Windows

Linux

server-less

Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

by Federation

yes

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

none

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

yes

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

using specific database classes

User concepts

Access control

Access rights can be defined down to the item level

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.