DBMS > Atos Standard Common Repository vs. IBM Cloudant vs. Postgres-XL vs. Prometheus vs. RocksDB

System Properties Comparison Atos Standard Common Repository vs. IBM Cloudant vs. Postgres-XL vs. Prometheus vs. RocksDB

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

Database as a Service offering based on Apache CouchDB

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Open-source Time Series DBMS and monitoring system

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

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

www.ibm.com/products/cloudant

www.postgres-xl.org

prometheus.io

rocksdb.org

Technical documentation

cloud.ibm.com/docs/Cloudant

www.postgres-xl.org/documentation

prometheus.io/docs

github.com/facebook/rocksdb/wiki

Developer

Atos Convergence Creators

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Facebook, Inc.

Initial release

2016

2010

2014

since 2012, originally named StormDB

2015

2013

Current release

1703

10 R1, October 2018

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

Apache 2.0

Open Source

BSD

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

C++

Server operating systems

Linux

hosted

Linux
macOS

Linux
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

Numeric data only

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

XML type, but no XML query functionality

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

LDAP

RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

by Federation

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

none

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 document possible

ACID

MVCC

yes

Concurrency

Support for concurrent manipulation of data

yes

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

fine grained access rights according to SQL-standard

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.