DBMS > Microsoft Azure Cosmos DB vs. PostGIS vs. Titan vs. Transwarp ArgoDB

System Properties Comparison Microsoft Azure Cosmos DB vs. PostGIS vs. Titan vs. Transwarp ArgoDB

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

Spatial extension of PostgreSQL

Titan is a Graph DBMS optimized for distributed clusters.

Distributed Analytical Database to replace Hadoop+MPP hybrid architecture

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Relational DBMS

Search engine

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

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.07
Rank	#350	Overall
	#153	Relational DBMS

Website

azure.microsoft.com/services/cosmos-db

postgis.net

github.com/thinkaurelius/titan

www.transwarp.cn/en/product/argodb

Technical documentation

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

github.com/thinkaurelius/titan/wiki

docs.transwarp.cn/#/documents-support/docs?category=ARGODB

Developer

Microsoft

Aurelius, owned by DataStax

Transwarp

Initial release

2014

2005

2012

Current release

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

Apache license, version 2.0

commercial

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

Server operating systems

hosted

Linux
OS X
Unix
Windows

Data scheme

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

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

Clojure
Java
Python

Server-side scripts

Stored procedures

JavaScript

user defined functions

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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

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

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

yes

based on PostgreSQL

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.