DBMS > Atos Standard Common Repository vs. RocksDB vs. Transwarp KunDB vs. WakandaDB

System Properties Comparison Atos Standard Common Repository vs. RocksDB vs. Transwarp KunDB vs. WakandaDB

Please select another system to include it in the comparison.

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

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

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Object oriented DBMS

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

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

Score	0.14
Rank	#341	Overall
	#149	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

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

rocksdb.org

www.transwarp.cn/en/product/kundb

wakanda.github.io

Technical documentation

github.com/facebook/rocksdb/wiki

wakanda.github.io/doc

Developer

Atos Convergence Creators

Facebook, Inc.

Transwarp

Wakanda SAS

Initial release

2016

2013

2012

Current release

1703

9.2.1, May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Open Source

AGPLv3, extended commercial license available

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

C++, JavaScript

Server operating systems

Linux

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

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

C++ API
Java API

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

C
C++
Go
Java
Perl
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

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

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.