DBMS > Atos Standard Common Repository vs. Geode vs. Microsoft Azure SQL Database vs. RocksDB vs. Titan

System Properties Comparison Atos Standard Common Repository vs. Geode vs. Microsoft Azure SQL Database vs. RocksDB vs. Titan

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Database as a Service offering with high compatibility to Microsoft SQL Server

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Document store
Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

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

geode.apache.org

azure.microsoft.com/en-us/products/azure-sql/database

rocksdb.org

github.com/thinkaurelius/titan

Technical documentation

geode.apache.org/docs

docs.microsoft.com/en-us/azure/azure-sql

github.com/facebook/rocksdb/wiki

github.com/thinkaurelius/titan/wiki

Developer

Atos Convergence Creators

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

Facebook, Inc.

Aurelius, owned by DataStax

Initial release

2016

2002

2010

2013

2012

Current release

1703

1.1, February 2017

V12

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

BSD

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

C++

Java

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux

Linux
OS X
Unix
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

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

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

LDAP

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

C++ API
Java API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

All languages with LDAP bindings

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

Transact SQL

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes, with always 3 replicas available

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Eventual 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

Atomic execution of specific operations

yes, on a single node

ACID

yes

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

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 per client and object definable

fine grained access rights according to SQL-standard

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.