DBMS > ArcadeDB vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. RDF4J

System Properties Comparison ArcadeDB vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. RDF4J

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Document store
Key-value store

Document store

RDF store

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

Score	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Website

arcadedb.com

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

cloud.google.com/datastore

rdf4j.org

Technical documentation

docs.arcadedb.com

cloud.google.com/datastore/docs

rdf4j.org/documentation

Developer

Arcade Data

Atos Convergence Creators

Google

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

Initial release

2021

2016

2008

2004

Current release

September 2021

1703

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

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

All OS with a Java VM

Linux

hosted

Linux
OS X
Unix
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

optional

yes, details here

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

SQL-like query language, no joins

SQL-like query language (GQL)

APIs and other access methods

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

LDAP

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Java

All languages with LDAP bindings

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

relationship in graphs

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Google Cloud Platform: Professional Data Engineer certification prep
11 June 2024, oreilly.com

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
4 June 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

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

Share this page