DBMS > Atos Standard Common Repository vs. OrigoDB vs. Titan vs. Trafodion

System Properties Comparison Atos Standard Common Repository vs. OrigoDB vs. Titan vs. Trafodion

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.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A fully ACID in-memory object graph database

Titan is a Graph DBMS optimized for distributed clusters.

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Key-value store

Document store
Object oriented DBMS

Graph DBMS

Relational DBMS

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

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

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

origodb.com

github.com/thinkaurelius/titan

trafodion.apache.org

Technical documentation

origodb.com/docs

github.com/thinkaurelius/titan/wiki

trafodion.apache.org/documentation.html

Developer

Atos Convergence Creators

Robert Friberg et al

Aurelius, owned by DataStax

Apache Software Foundation, originally developed by HP

Initial release

2016

2009

under the name LiveDB

2012

2014

Current release

1703

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache license, version 2.0

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++, Java

Server operating systems

Linux

Linux
Windows

Linux
OS X
Unix
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

.NET Client API
HTTP API
LINQ

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

.Net

Clojure
Java
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

client side managed; servers are not synchronized

yes

via pluggable storage backends

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Relationships in graph

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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.

yes

User concepts

Access control

LDAP bind authentication

Role based authorization

User authentification and security via Rexster Graph Server

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, Matthias Gelbmann

show all

Recent citations in the news

Amazon DynamoDB Storage Backend for Titan: Distributed Graph Database
24 August 2015, AWS Blog

DataStax acquires Aurelius, the startup behind the Titan graph database
3 February 2015, VentureBeat

DSE Graph review: Graph database does double duty
14 November 2019, InfoWorld

Beyond Titan: The Evolution of DataStax’s New Graph Database
21 June 2016, Datanami

Database Deep Dives: JanusGraph
8 August 2019, IBM

provided by Google News

Share this page