DBMS > Atos Standard Common Repository vs. Citus vs. etcd vs. RocksDB vs. SiteWhere

System Properties Comparison Atos Standard Common Repository vs. Citus vs. etcd vs. RocksDB vs. SiteWhere

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

A distributed reliable key-value store

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

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Document store

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

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

www.citusdata.com

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

rocksdb.org

github.com/sitewhere/sitewhere

Technical documentation

docs.citusdata.com

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

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

Developer

Atos Convergence Creators

Facebook, Inc.

SiteWhere

Initial release

2016

2010

2013

2010

Current release

1703

8.1, December 2018

3.4, August 2019

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

Open Source

Apache Version 2.0

Open Source

BSD

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Java

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

Linux

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

predefined scheme

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

APIs and other access methods

LDAP

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

gRPC
JSON over HTTP

C++ API
Java API

HTTP REST

Supported programming languages

All languages with LDAP bindings

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

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

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

yes

selectable replication factor

based on HBase

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.