DBMS > Atos Standard Common Repository vs. Google Cloud Datastore vs. Hazelcast vs. Oracle

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Datastore vs. Hazelcast vs. Oracle

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

A widely adopted in-memory data grid

Widely used RDBMS

Primary database model

Document store
Key-value store

Document store

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Website

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

cloud.google.com/datastore

hazelcast.com

www.oracle.com/database

Technical documentation

cloud.google.com/datastore/docs

hazelcast.org/imdg/docs

docs.oracle.com/en/database

Developer

Atos Convergence Creators

Google

Hazelcast

Oracle

Initial release

2016

2008

1980

Current release

1703

5.3.6, November 2023

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

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

Server operating systems

Linux

hosted

All OS with a Java VM

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Schemaless in JSON and XML columns

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

LDAP

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

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

All languages with LDAP bindings

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

using Google App Engine

yes

Event Listeners, Executor Services

PL/SQL

also stored procedures in Java possible

Triggers

yes

Callbacks using the Google Apps Engine

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

Replicated Map

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

can be realized in PL/SQL

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

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

one or two-phase-commit; repeatable reads; read commited

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

LDAP bind authentication

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

Role-based access control

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.