DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. SiriDB vs. Titan vs. Yaacomo

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. SiriDB vs. Titan vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Large scale data warehouse service for use with business intelligence tools

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

Open Source Time Series DBMS

Titan is a Graph DBMS optimized for distributed clusters.

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Document store
Key-value store

Time Series DBMS

Graph DBMS

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/redshift

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

siridb.com

github.com/thinkaurelius/titan

yaacomo.com

Technical documentation

docs.aws.amazon.com/redshift

docs.siridb.com

github.com/thinkaurelius/titan/wiki

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Cesbit

Aurelius, owned by DataStax

Q2WEB GmbH

Initial release

2012

2016

2017

2012

2009

Current release

1703

License

Commercial or Open Source

commercial

Open Source

MIT License

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

Linux
OS X
Unix
Windows

Android
Linux
Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

yes

Numeric data

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

LDAP

HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

via pluggable storage backends

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graph

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

LDAP bind authentication

simple rights management via user accounts

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.