DBMS > ArcadeDB vs. Atos Standard Common Repository vs. OpenQM vs. XTDB

System Properties Comparison ArcadeDB vs. Atos Standard Common Repository vs. OpenQM vs. XTDB

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

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Document store
Key-value store

Multivalue DBMS

Document store

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

Score	0.09
Rank	#355	Overall
	#48	Document stores
	#37	Graph DBMS
	#52	Key-value stores
	#34	Time Series DBMS

Score	0.33
Rank	#286	Overall
	#10	Multivalue DBMS

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

arcadedb.com

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

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.arcadedb.com

www.xtdb.com/docs

Developer

Arcade Data

Atos Convergence Creators

Rocket Software, originally Martin Phillips

Juxt Ltd.

Initial release

2021

2016

1993

2019

Current release

September 2021

1703

3.4-12

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPLv2, extended commercial license available

Open Source

MIT License

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

Clojure

Server operating systems

All OS with a Java VM

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

with some exceptions

schema-free

Typing

predefined data types such as float or date

yes

optional

yes, extensible-data-notation format

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, no joins

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

LDAP

HTTP REST
JDBC

Supported programming languages

Java

All languages with LDAP bindings

.Net
Basic
C
Java
Objective C
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.

Share this page