DBMS > Atos Standard Common Repository vs. Google Cloud Datastore vs. RocksDB vs. Stardog

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Datastore vs. RocksDB vs. Stardog

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

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Document store
Key-value store

Document store

Key-value store

Graph DBMS
RDF store

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

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

cloud.google.com/datastore

rocksdb.org

www.stardog.com

Technical documentation

cloud.google.com/datastore/docs

github.com/facebook/rocksdb/wiki

docs.stardog.com

Developer

Atos Convergence Creators

Google

Facebook, Inc.

Stardog-Union

Initial release

2016

2008

2013

2010

Current release

1703

8.11.4, April 2024

7.3.0, May 2020

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Java

Server operating systems

Linux

hosted

Linux

Linux
macOS
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language (GQL)

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

LDAP

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

C++ API
Java API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

All languages with LDAP bindings

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

C
C++
Go
Java
Perl
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

using Google App Engine

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

Callbacks using the Google Apps Engine

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

Multi-source replication in HA-Cluster

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.

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

relationships in graphs

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users and roles

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.