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

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

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Multivalue DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
RDF store

Document store
Spatial DBMS

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	0.82
Rank	#209	Overall
	#97	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

vitess.io

Technical documentation

terminusdb.github.io/terminusdb/#

vitess.io/docs

Developer

Atos Convergence Creators

Rocket Software, originally Martin Phillips

DataChemist Ltd.

The Linux Foundation, PlanetScale

Initial release

2016

1993

2018

2013

Current release

1703

3.4-12

11.0.0, January 2023

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses 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

Prolog, Rust

Server operating systems

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Docker
Linux
macOS

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

with proprietary extensions

APIs and other access methods

LDAP

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

in-memory journaling

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page