DBMS > Atos Standard Common Repository vs. EJDB vs. RocksDB vs. Trafodion

System Properties Comparison Atos Standard Common Repository vs. EJDB vs. RocksDB vs. Trafodion

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.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Key-value store

Document store

Key-value store

Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

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

Website

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

github.com/Softmotions/ejdb

rocksdb.org

trafodion.apache.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

github.com/facebook/rocksdb/wiki

trafodion.apache.org/documentation.html

Developer

Atos Convergence Creators

Softmotions

Facebook, Inc.

Apache Software Foundation, originally developed by HP

Initial release

2016

2012

2013

2014

Current release

1703

9.2.1, May 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

BSD

Open Source

Apache 2.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++

C++, Java

Server operating systems

Linux

server-less

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

string, integer, double, bool, date, object_id

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

in-process shared library

C++ API
Java API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Read/Write 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

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.