DBMS > EsgynDB vs. Microsoft Azure Cosmos DB vs. Prometheus vs. QuestDB

System Properties Comparison EsgynDB vs. Microsoft Azure Cosmos DB vs. Prometheus vs. QuestDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Globally distributed, horizontally scalable, multi-model database service

Open-source Time Series DBMS and monitoring system

A high performance open source SQL database for time series data

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

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

Score	7.56
Rank	#49	Overall
	#3	Time Series DBMS

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Website

www.esgyn.cn

azure.microsoft.com/services/cosmos-db

prometheus.io

questdb.io

Technical documentation

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

questdb.io/docs

Developer

Esgyn

Microsoft

QuestDB Technology Inc

Initial release

2015

2014

2015

2014

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 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++, Java

Java (Zero-GC), C++, Rust

Server operating systems

Linux

hosted

Linux
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

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

SQL

Support of SQL

yes

SQL-like query language

SQL with time-series extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

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

RESTful HTTP/JSON API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

Implicit feature of the cloud service

yes

by Federation

Source-replica replication with eventual consistency

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID for single-table writes

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

through memory mapped files

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 2024

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.