DBMS > Atos Standard Common Repository vs. CouchDB vs. etcd vs. Microsoft Azure Table Storage vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. CouchDB vs. etcd vs. Microsoft Azure Table Storage 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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A distributed reliable key-value store

A Wide Column Store for rapid development using massive semi-structured datasets

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

Primary database model

Document store
Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

couchdb.apache.org

etcd.io
github.com/etcd-io/etcd

azure.microsoft.com/en-us/services/storage/tables

www.snowflake.com

Technical documentation

docs.couchdb.org/en/stable

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Microsoft

Snowflake Computing Inc.

Initial release

2016

2005

2012

2014

Current release

1703

3.3.3, December 2023

3.4, August 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Erlang

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
Windows

experimental

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

via views

SQL

Support of SQL

yes

APIs and other access methods

LDAP

RESTful HTTP/JSON API

gRPC
JSON over HTTP

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

Triggers

yes

yes, watching key changes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

improved architecture with release 2.0

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

atomic operations within a single document possible

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

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

Access rights for users can be defined per database

Access rights based on private key authentication or shared access signatures

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.