DBMS > Atos Standard Common Repository vs. BigchainDB vs. Dgraph vs. HugeGraph vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Dgraph vs. HugeGraph vs. Snowflake

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

Distributed and scalable native Graph DBMS

A fast-speed and highly-scalable Graph DBMS

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

Primary database model

Document store
Key-value store

Document store

Graph DBMS

Relational DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.bigchaindb.com

dgraph.io

github.com/hugegraph
hugegraph.apache.org

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

dgraph.io/docs

hugegraph.apache.org/docs

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Dgraph Labs, Inc.

Baidu

Snowflake Computing Inc.

Initial release

2016

2018

2014

Current release

1703

0.9

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache 2.0

Open Source

Apache 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

Python

Java

Server operating systems

Linux

Linux
OS X
Windows

Linux
macOS
Unix

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

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

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

also supports composite index and range index

SQL

Support of SQL

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Java API
RESTful HTTP API
TinkerPop Gremlin

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

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

Groovy
Java
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

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

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Synchronous replication via Raft

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges 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

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

Planned for future releases

Users, roles and permissions

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.