DBMS > Atos Standard Common Repository vs. Google BigQuery vs. RethinkDB vs. TerminusDB

System Properties Comparison Atos Standard Common Repository vs. Google BigQuery vs. RethinkDB vs. TerminusDB

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

Large scale data warehouse service with append-only tables

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Graph DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

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

cloud.google.com/bigquery

rethinkdb.com

terminusdb.com

Technical documentation

cloud.google.com/bigquery/docs

rethinkdb.com/docs

terminusdb.github.io/terminusdb/#

Developer

Atos Convergence Creators

Google

The Linux Foundation

since July 2017

DataChemist Ltd.

Initial release

2016

2010

2009

2018

Current release

1703

2.4.1, August 2020

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GPL V3

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

C++

Prolog, Rust

Server operating systems

Linux

hosted

Linux
OS X
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

string, binary, float, bool, date, geometry

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

SQL-like query language (WOQL)

APIs and other access methods

LDAP

RESTful HTTP/JSON API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

range based

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Atomic execution of specific operations

Since BigQuery is designed for querying data

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

Durability

Support for making data persistent

yes

in-memory journaling

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

users and table-level permissions

Role-based access control

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.