DBMS > Microsoft Azure Cosmos DB vs. OpenQM vs. Percona Server for MongoDB vs. Transbase

System Properties Comparison Microsoft Azure Cosmos DB vs. OpenQM vs. Percona Server for MongoDB vs. Transbase

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

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Multivalue DBMS

Document store

Relational DBMS

Secondary database models

Spatial 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.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

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

www.percona.com/mongodb/software/percona-server-for-mongodb

www.transaction.de/en/products/transbase.html

Technical documentation

learn.microsoft.com/azure/cosmos-db

docs.percona.com/percona-distribution-for-mongodb

www.transaction.de/en/products/transbase/features.html

Developer

Microsoft

Rocket Software, originally Martin Phillips

Percona

Transaction Software GmbH

Initial release

2014

1993

2015

1987

Current release

3.4-12

3.4.10-2.10, November 2017

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

GPL Version 2

commercial

free development license

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++

C and C++

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

with some exceptions

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON 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

APIs and other access methods

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

proprietary protocol using JSON

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

Eventual Consistency
Immediate 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

yes

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

via In-Memory Engine

User concepts

Access control

Access rights can be defined down to the item level

Access rights for users and roles

fine grained access rights according to SQL-standard

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.