DBMS > Atos Standard Common Repository vs. BigchainDB vs. Sequoiadb vs. Snowflake vs. SQream DB

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Sequoiadb vs. Snowflake vs. SQream DB

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

NewSQL database with distributed OLTP and SQL

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Document store
Key-value store

Document store

Document store
Relational 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	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

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

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

Atos Convergence Creators

Sequoiadb Ltd.

Snowflake Computing Inc.

SQream Technologies

Initial release

2016

2013

2014

2017

Current release

1703

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Server: AGPL; Client: Apache V2

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

C++

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux

hosted

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

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

yes

Typing

predefined data types such as float or date

optional

yes

oid, date, timestamp, binary, regex

yes

yes, ANSI Standard SQL Types

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

SQL-like query language

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

proprietary protocol using JSON

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

JavaScript

user defined functions

user defined functions in Python

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

Document is locked during a transaction

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

simple password-based access control

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.