DBMS > Atos Standard Common Repository vs. RDF4J vs. VoltDB vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. RDF4J vs. VoltDB vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

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

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

RDF store

Relational DBMS

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

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

rdf4j.org

www.voltdb.com

yaacomo.com

Technical documentation

rdf4j.org/documentation

docs.voltdb.com

Developer

Atos Convergence Creators

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

VoltDB Inc.

Q2WEB GmbH

Initial release

2016

2004

2010

2009

Current release

1703

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

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

commercial

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

Java, C++

Server operating systems

Linux

Linux
OS X
Unix
Windows

Linux
OS X

for development

Android
Linux
Windows

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

yes

APIs and other access methods

LDAP

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Java API
JDBC
RESTful HTTP/JSON API

JDBC
ODBC

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

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica 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

FOREIGN KEY constraints are not supported

yes

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.

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

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

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 Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

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

provided by Google News

Share this page