DBMS > Atos Standard Common Repository vs. OpenQM vs. TerminusDB vs. VoltDB

System Properties Comparison Atos Standard Common Repository vs. OpenQM vs. TerminusDB vs. VoltDB

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Key-value store

Multivalue DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
RDF store

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

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

terminusdb.com

www.voltdb.com

Technical documentation

terminusdb.github.io/terminusdb/#

docs.voltdb.com

Developer

Atos Convergence Creators

Rocket Software, originally Martin Phillips

DataChemist Ltd.

VoltDB Inc.

Initial release

2016

1993

2018

2010

Current release

1703

3.4-12

11.0.0, January 2023

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

GPL V3

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Prolog, Rust

Java, C++

Server operating systems

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Linux
OS X

for development

Data scheme

Schema and schema-less with LDAP views

yes

with some exceptions

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

SQL-like query language (WOQL)

yes

only a subset of SQL 99

APIs and other access methods

LDAP

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Journaling Streams

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory journaling

yes

Snapshots and command logging

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 can be defined down to the item level

Role-based access control

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

Irish start-ups received €28m from Enterprise Ireland in 2021
7 April 2022, SiliconRepublic.com

Bus Terminus Update - April 26th
26 April 2021, Around DB and Life on Lantau

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page