DBMS > Microsoft Azure Cosmos DB vs. OrientDB vs. PouchDB vs. Tigris

System Properties Comparison Microsoft Azure Cosmos DB vs. OrientDB vs. PouchDB vs. Tigris

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

Multi-model DBMS (Document, Graph, Key/Value)

JavaScript DBMS with an API inspired by CouchDB

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Graph DBMS
Key-value store

Document store

Document store
Key-value store
Search engine
Time Series 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	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

azure.microsoft.com/services/cosmos-db

orientdb.org

pouchdb.com

www.tigrisdata.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

www.orientdb.com/docs/last/index.html

pouchdb.com/guides

www.tigrisdata.com/docs

Developer

Microsoft

OrientDB LTD; CallidusCloud; SAP

Apache Software Foundation

Tigris Data, Inc.

Initial release

2014

2010

2012

2022

Current release

3.2.29, March 2024

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Java

JavaScript

Server operating systems

hosted

All OS with a Java JDK (>= JDK 6)

server-less, requires a JavaScript environment (browser, Node.js)

Linux
macOS
Windows

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

via views

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language, no joins

APIs and other access methods

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

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

JavaScript

Java, Javascript

View functions in JavaScript

Triggers

JavaScript

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

could be achieved with distributed queries

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes, using FoundationDB

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

Access rights for users and roles; record level security configurable

Access rights for users and roles

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.