DBMS > Atos Standard Common Repository vs. Google Cloud Datastore vs. SpaceTime vs. Yanza

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Datastore vs. SpaceTime vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Atos Standard Common Repository  Xexclude from comparison	Google Cloud Datastore  Xexclude from comparison	SpaceTime  Xexclude from comparison	Yanza  Xexclude from comparison
	This system has been discontinued and will be removed from the DB-Engines ranking.			Yanza seems to be discontinued. Therefore it is excluded 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	SpaceTime is a spatio-temporal DBMS with a focus on performance.	Time Series DBMS for IoT Applications
Primary database model	Document store Key-value store	Document store	Spatial DBMS	Time Series DBMS
Secondary database models			Relational DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart		Score 4.47 Rank #76   Overall #12   Document stores	Score 0.00 Rank #383   Overall #7   Spatial DBMS
Website	atos.net/en/convergence-creators/portfolio/standard-common-repository	cloud.google.com/­datastore	www.mireo.com/­spacetime	yanza.com
Technical documentation		cloud.google.com/­datastore/­docs
Developer	Atos Convergence Creators	Google	Mireo	Yanza
Initial release	2016	2008	2020	2015
Current release	1703
License Commercial or Open Source	commercial	commercial	commercial	commercial free version available
Cloud-based only Only available as a cloud service	no	yes	no	no but mainly used as a service provided by Yanza
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	Java		C++
Server operating systems	Linux	hosted	Linux	Windows
Data scheme	Schema and schema-less with LDAP views	schema-free	yes	schema-free
Typing predefined data types such as float or date	optional	yes, details here	yes	no
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	no	no	no
Secondary indexes	yes	yes	no	no
SQL Support of SQL	no	SQL-like query language (GQL)	A subset of ANSI SQL is implemented	no
APIs and other access methods	LDAP	gRPC (using protocol buffers) API RESTful HTTP/JSON API	RESTful HTTP API	HTTP API
Supported programming languages	All languages with LDAP bindings	.Net Go Java JavaScript (Node.js) PHP Python Ruby	C# C++ Python	any language that supports HTTP calls
Server-side scripts Stored procedures	no	using Google App Engine	no	no
Triggers	yes	Callbacks using the Google Apps Engine	no	yes Timer and event based
Partitioning methods Methods for storing different data on different nodes	Sharding cell division	Sharding	Fixed-grid hypercubes	none
Replication methods Methods for redundantly storing data on multiple nodes	yes	Multi-source replication using Paxos	Real-time block device replication (DRBD)	none
MapReduce Offers an API for user-defined Map/Reduce methods		yes using Google Cloud Dataflow	no	no
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	Immediate Consistency
Foreign keys Referential integrity	no	yes via ReferenceProperties or Ancestor paths	no	no
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	no	no
Concurrency Support for concurrent manipulation of data	yes	yes	yes	yes
Durability Support for making data persistent	yes	yes	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes	no	no
User concepts Access control	LDAP bind authentication	Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)	yes	no
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
	Atos Standard Common Repository	Google Cloud Datastore	SpaceTime	Yanza
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 Best cloud storage of 2024 21 May 2024, TechRadar 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 Why Google is waiving egress fees for disgruntled customers ditching GCP 11 January 2024, The Register provided by Google News

Share this page