DBMS > Microsoft Azure Cosmos DB vs. OrientDB vs. TerminusDB vs. Titan

System Properties Comparison Microsoft Azure Cosmos DB vs. OrientDB vs. TerminusDB vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Globally distributed, horizontally scalable, multi-model database service

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Graph DBMS
Key-value store

Graph DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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

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

Score	3.02
Rank	#88	Overall
	#16	Document stores
	#6	Graph DBMS
	#12	Key-value stores

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

azure.microsoft.com/services/cosmos-db

orientdb.org

terminusdb.com

github.com/thinkaurelius/titan

Technical documentation

learn.microsoft.com/azure/cosmos-db

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

terminusdb.github.io/terminusdb/#

github.com/thinkaurelius/titan/wiki

Developer

Microsoft

OrientDB LTD; CallidusCloud; SAP

DataChemist Ltd.

Aurelius, owned by DataStax

Initial release

2014

2010

2018

2012

Current release

3.2.29, March 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

GPL V3

Open Source

Apache license, 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

Prolog, Rust

Java

Server operating systems

hosted

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

Linux

Linux
OS X
Unix
Windows

Data scheme

schema-free

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

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

SQL

Support of SQL

SQL-like query language

SQL-like query language, no joins

SQL-like query language (WOQL)

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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
Python

Clojure
Java
Python

Server-side scripts

Stored procedures

JavaScript

Java, Javascript

yes

Triggers

JavaScript

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Graph Partitioning

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Multi-source replication

Journaling Streams

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

via Faunus, a graph analytics engine

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

yes

Relationships in graph

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

in-memory journaling

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

User concepts

Access control

Access rights can be defined down to the item level

Access rights for users and roles; record level security configurable

Role-based access control

User authentification and security via Rexster Graph Server

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.