DBMS > EJDB vs. Microsoft Azure Cosmos DB vs. OpenQM vs. Prometheus

System Properties Comparison EJDB vs. Microsoft Azure Cosmos DB vs. OpenQM vs. Prometheus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Globally distributed, horizontally scalable, multi-model database service

QpenQM is a high-performance, self-tuning, multi-value DBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Multivalue DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

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

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	7.56
Rank	#49	Overall
	#3	Time Series DBMS

Website

github.com/Softmotions/ejdb

azure.microsoft.com/services/cosmos-db

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

prometheus.io

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

Developer

Softmotions

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2012

2014

1993

2015

Current release

3.4-12

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

GPLv2, extended commercial license available

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

Server operating systems

server-less

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

in-process shared library

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

RESTful HTTP/JSON API

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

.Net
Basic
C
Java
Objective C
PHP
Python

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

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

by Federation

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

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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.

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.