DBMS > Atos Standard Common Repository vs. BigchainDB vs. SAP Adaptive Server vs. Snowflake vs. TinkerGraph

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. SAP Adaptive Server vs. Snowflake vs. TinkerGraph

Editorial information provided by DB-Engines

Name

This system has been discontinued and 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

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Cloud-based data warehousing service for structured and semi-structured data

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	37.12
Rank	#25	Overall
	#17	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

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

www.bigchaindb.com

www.sap.com/products/technology-platform/sybase-ase.html

www.snowflake.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

bigchaindb.readthedocs.io/en/latest

help.sap.com/docs/SAP_ASE

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

SAP, Sybase

Snowflake Computing Inc.

Initial release

2016

1987

2014

2009

Current release

1703

16.0

License

Commercial or Open Source

commercial

Open Source

AGPL v3

commercial

Open Source

Apache 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

Python

C and C++

Java

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Unix
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

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

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

CLI Client
JDBC
ODBC

TinkerPop 3

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

C
C++
Cobol
Java
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

Groovy
Java

Server-side scripts

Stored procedures

Java and Transact-SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

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

yes,with MongoDB ord RethinkDB

yes

optional

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.