DBMS > Atos Standard Common Repository vs. Microsoft Azure Cosmos DB vs. Titan vs. VoltDB

System Properties Comparison Atos Standard Common Repository vs. Microsoft Azure Cosmos DB vs. Titan vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Globally distributed, horizontally scalable, multi-model database service

Titan is a Graph DBMS optimized for distributed clusters.

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

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	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

azure.microsoft.com/services/cosmos-db

github.com/thinkaurelius/titan

www.voltdb.com

Technical documentation

learn.microsoft.com/azure/cosmos-db

github.com/thinkaurelius/titan/wiki

docs.voltdb.com

Developer

Atos Convergence Creators

Microsoft

Aurelius, owned by DataStax

VoltDB Inc.

Initial release

2016

2014

2012

2010

Current release

1703

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache license, version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux

hosted

Linux
OS X
Unix
Windows

Linux
OS X

for development

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

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

only a subset of SQL 99

APIs and other access methods

LDAP

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

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

Clojure
Java
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

Java

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

yes

via pluggable storage backends

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication
Source-replica replication

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

Immediate Consistency or Eventual Consistency depending on configuration

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

Relationships in graph

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

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

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

LDAP bind authentication

Access rights can be defined down to the item level

User authentification and security via Rexster Graph Server

Users and roles with access to stored procedures

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.