DBMS > Atos Standard Common Repository vs. Ehcache vs. Google Cloud Datastore vs. STSdb

System Properties Comparison Atos Standard Common Repository vs. Ehcache vs. Google Cloud Datastore vs. STSdb

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

A widely adopted Java cache with tiered storage options

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Key-value store

Key-value store

Document store

Key-value store

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

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

www.ehcache.org

cloud.google.com/datastore

github.com/STSSoft/STSdb4

Technical documentation

www.ehcache.org/documentation

cloud.google.com/datastore/docs

Developer

Atos Convergence Creators

Terracotta Inc, owned by Software AG

Google

STS Soft SC

Initial release

2016

2009

2008

2011

Current release

1703

3.10.0, March 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPLv2, commercial license 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

Server operating systems

Linux

All OS with a Java VM

hosted

Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

yes, details here

yes

primitive types and user defined types (classes)

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

JCache

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

.NET Client API

Supported programming languages

All languages with LDAP bindings

Java

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

C#
Java

Server-side scripts

Stored procedures

using Google App Engine

Triggers

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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)

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

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

provided by Google News

Best cloud storage of 2024
21 May 2024, TechRadar

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

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

Share this page