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

System Properties Comparison Atos Standard Common Repository vs. BigchainDB 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

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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
Key-value store

Document store

RDF store

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

Score	0.76
Rank	#216	Overall
	#36	Document stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Website

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

www.bigchaindb.com

cloud.google.com/datastore

rdf4j.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

rdf4j.org/documentation

Developer

Atos Convergence Creators

Google

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

Initial release

2016

2008

2004

Current release

1703

License

Commercial or Open Source

commercial

Open Source

AGPL v3

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

Python

Java

Server operating systems

Linux

hosted

Linux
OS X
Unix
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

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 (GQL)

APIs and other access methods

LDAP

CLI Client
RESTful HTTP API

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

All languages with LDAP bindings

Go
Haskell
Java
JavaScript
Python
Ruby

.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

yes

selectable replication factor

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 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

via ReferenceProperties or Ancestor paths

Transaction concepts

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

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

yes,with MongoDB ord RethinkDB

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

yes

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

Using BigchainDB: A Database with Blockchain Characteristics
20 January 2022, Open Source For You

Blockchain Database Startup BigchainDB Raises €3 Million
27 September 2016, CoinDesk

7 blockchain firms join Bosch led GAIA-X consortium for vehicle identity
13 September 2022, Ledger Insights

How to use blockchain to build a database solution
2 March 2017, ZDNet

BigchainDB: A Popular and Powerful Database for Blockchain
9 September 2019, Open Source For You

provided by Google News

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Google App Engine
26 April 2024, TechTarget

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Share this page