DBMS > Atos Standard Common Repository vs. EventStoreDB vs. RDF4J vs. SAP HANA vs. VoltDB

System Properties Comparison Atos Standard Common Repository vs. EventStoreDB vs. RDF4J vs. SAP HANA vs. VoltDB

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

Industrial-strength, open-source database solution built from the ground up for event sourcing.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

In-memory, column based data store. Available as appliance or cloud service

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

Event Store

RDF store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

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

www.eventstore.com

rdf4j.org

www.sap.com/products/hana.html

www.voltdb.com

Technical documentation

developers.eventstore.com

rdf4j.org/documentation

help.sap.com/hana

docs.voltdb.com

Developer

Atos Convergence Creators

Event Store Limited

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

SAP

VoltDB Inc.

Initial release

2016

2012

2004

2010

Current release

1703

21.2, February 2021

2.0 SPS07 (April 4, 2023), April 2023

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

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

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, C++

Server operating systems

Linux

Linux
Windows

Linux
OS X
Unix
Windows

Appliance or cloud-service

Linux
OS X

for development

Data scheme

Schema and schema-less with LDAP views

yes

RDF Schemas

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

only a subset of SQL 99

APIs and other access methods

LDAP

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

Java
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

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

Isolation support depends on the API used

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 storage is supported as well

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

yes

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.