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

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

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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Oracles in-memory data grid solution

Primary database model

Document store
Key-value store

Document store

Key-value store

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Website

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

cloud.google.com/datastore

www.oracle.com/java/coherence

Technical documentation

cloud.google.com/datastore/docs

docs.oracle.com/en/middleware/standalone/coherence

Developer

Atos Convergence Creators

FatCloud

Google

Oracle

Initial release

2016

2012

2008

2007

Current release

1703

14.1, August 2023

License

Commercial or Open Source

commercial

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

Linux

Windows

hosted

All OS with a Java VM

Data scheme

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

optional

yes

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

Via inetgration in SQL Server

SQL-like query language (GQL)

APIs and other access methods

LDAP

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

JCache
JPA
RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

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

.Net
C++
Java

Server-side scripts

Stored procedures

yes

via applications

using Google App Engine

Triggers

yes

via applications

Callbacks using the Google Apps Engine

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication using Paxos

yes, with selectable consistency level

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

Eventual Consistency
Immediate Consistency

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.

Eventual Consistency
Immediate Consistency

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

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

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

Can implement custom security layer via applications

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

authentification to access the cache via certificates or http basic authentication

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

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

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

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

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

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Customize your deployment of Oracle Banking Digital Experience
10 May 2023, blogs.oracle.com

New solutions for Oracle WebLogic on Azure Virtual Machines
1 April 2021, azure.microsoft.com

GridGain: Product Overview and Analysis
5 June 2019, eWeek

Hazelcast takes on proprietary Oracle in the In-Memory arena
17 June 2014, DatacenterDynamics

Oracle launches Oracle Banking Cloud Services - ThePaypers
8 February 2023, The Paypers

provided by Google News

Share this page