DBMS > Atos Standard Common Repository vs. BigchainDB vs. Heroic vs. Microsoft Azure Cosmos DB vs. Teradata Aster

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Heroic vs. Microsoft Azure Cosmos DB vs. Teradata Aster

Editorial information provided by DB-Engines

Name

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

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Globally distributed, horizontally scalable, multi-model database service

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store
Key-value store

Document store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Website

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

www.bigchaindb.com

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

Technical documentation

bigchaindb.readthedocs.io/en/latest

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

Developer

Atos Convergence Creators

Spotify

Microsoft

Teradata

Initial release

2016

2014

2005

Current release

1703

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache 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

Python

Java

Server operating systems

Linux

hosted

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

via Elasticsearch

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

JavaScript

R packages

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

Implicit feature of the cloud service

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

yes

Access rights can be defined down to the item level

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.