DBMS > Amazon DynamoDB vs. Atos Standard Common Repository vs. Dolt vs. RDF4J vs. Yaacomo

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

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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.

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

Primary database model

Document store
Key-value store

Relational DBMS

RDF store

Relational DBMS

Secondary database models

Document store

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Website

aws.amazon.com/dynamodb

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

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

rdf4j.org

yaacomo.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.dolthub.com

rdf4j.org/documentation

Developer

Amazon

Atos Convergence Creators

DoltHub Inc

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

Q2WEB GmbH

Initial release

2012

2016

2018

2004

2009

Current release

1703

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache Version 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

Linux

Linux
macOS
Windows

Linux
OS X
Unix
Windows

Android
Linux
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

yes

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

APIs and other access methods

RESTful HTTP API

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

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

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

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

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

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.