DBMS > Atos Standard Common Repository vs. BigchainDB vs. EJDB vs. Snowflake vs. Yanza

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. EJDB vs. Snowflake vs. Yanza

Editorial information provided by DB-Engines

Name

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

Yanza seems to be discontinued. Therefore it is excluded 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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Time Series DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.bigchaindb.com

github.com/Softmotions/ejdb

www.snowflake.com

yanza.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

github.com/Softmotions/ejdb/blob/master/README.md

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Softmotions

Snowflake Computing Inc.

Yanza

Initial release

2016

2012

2014

2015

Current release

1703

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

GPLv2

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Python

Server operating systems

Linux

server-less

hosted

Windows

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

string, integer, double, bool, date, object_id

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

in-process shared library

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

JavaScript (Node.js)
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

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.