DBMS > Atos Standard Common Repository vs. Dolt vs. RDF4J vs. ToroDB vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Dolt vs. RDF4J vs. ToroDB vs. Yaacomo

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded 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

A MySQL compatible DBMS with Git-like versioning of data and schema

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

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

Primary database model

Document store
Key-value store

Secondary database models

Document store

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

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Website

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

github.com/dolthub/dolt
www.dolthub.com

rdf4j.org

github.com/torodb/server

yaacomo.com

Technical documentation

docs.dolthub.com

rdf4j.org/documentation

Developer

Atos Convergence Creators

DoltHub Inc

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

8Kdata

Q2WEB GmbH

Initial release

2016

2018

2004

2016

2009

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

AGPL-V3

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

Server operating systems

Linux

Linux
macOS
Windows

Linux
OS X
Unix
Windows

All OS with a Java 7 VM

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

RDF Schemas

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

LDAP

CLI Client
HTTP REST

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

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

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

none

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

Only one user is configurable, and must be specified in the config file at startup

Access rights for users and roles

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

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

25 Hot New Data Tools and What They DON’T Do
14 May 2020, Towards Data Science

Solve your MLOps Problems with an Open Source Data Science Stack
2 June 2021, Towards Data Science

provided by Google News

Share this page