DBMS > Atos Standard Common Repository vs. BigchainDB vs. Coveo vs. Microsoft Azure SQL Database vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. BigchainDB vs. Coveo vs. Microsoft Azure SQL Database 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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Database as a Service offering with high compatibility to Microsoft SQL Server

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

Primary database model

Document store
Key-value store

Document store

Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	2.34
Rank	#117	Overall
	#11	Search engines

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.bigchaindb.com

www.coveo.com

azure.microsoft.com/en-us/products/azure-sql/database

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.coveo.com

docs.microsoft.com/en-us/azure/azure-sql

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Coveo

Microsoft

Snowflake Computing Inc.

Initial release

2016

2012

2010

2014

Current release

1703

V12

License

Commercial or Open Source

commercial

Open Source

AGPL v3

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++

Server operating systems

Linux

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

SQL

Support of SQL

yes

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

C#
Java
JavaScript
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

yes, with always 3 replicas available

yes

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

yes

Transaction concepts

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

Atomic execution of specific operations

yes

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

granular access controls, API key management, content filters

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.