DBMS > Atos Standard Common Repository vs. Google Cloud Datastore
System Properties Comparison Atos Standard Common Repository vs. Google Cloud Datastore
Please select another system to include it in the comparison.
Our visitors often compare Atos Standard Common Repository and Google Cloud Datastore with MongoDB, MySQL and Microsoft SQL Server.
|Editorial information provided by DB-Engines|
|Name||Atos Standard Common Repository Xexclude from comparison||Google Cloud Datastore Xexclude from comparison|
|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|
|Primary database model||Document store|
|Developer||Atos Convergence Creators|
|License Commercial or Open Source||commercial||commercial|
|Cloud-based only Only available as a cloud service||no||yes|
|DBaaS offerings (sponsored links) Database as a Service|
Providers of DBaaS offerings, please contact us to be listed.
|Server operating systems||Linux||hosted|
|Data scheme||Schema and schema-less with LDAP views||schema-free|
|Typing predefined data types such as float or date||optional||yes, details here|
|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|
|SQL Support of SQL||no||SQL-like query language (GQL)|
|APIs and other access methods||LDAP||gRPC (using protocol buffers) API|
RESTful HTTP/JSON API
|Supported programming languages||All languages with LDAP bindings||.Net|
|Server-side scripts Stored procedures||no||using Google App Engine|
|Triggers||yes||Callbacks using the Google Apps Engine|
|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||Multi-source replication using Paxos|
|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.|
|Foreign keys Referential integrity||no||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|
|Concurrency Support for concurrent manipulation of data||yes||yes|
|Durability Support for making data persistent||yes||yes|
|In-memory capabilities Is there an option to define some or all structures to be held in-memory only.||yes||no|
|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,
Related products and services
We invite representatives of vendors of related products to contact us for presenting information about their offerings here.
|Atos Standard Common Repository||Google Cloud Datastore|
|Recent citations in the news|
Dan Benjamin on Cloud Data Security and Data Detection and ...
Analysis of 7 single-vendor SASE platforms
AdRem NetCrunch 13 review: Great network monitoring for time ...
NetApp pushes ONTAP into VMware's Google Cloud Engine ...
Where Is Our Data? Why Data Location Discovery Is Hard
provided by Google News
Customer Engineer, Small/Medium Business, Apigee, Google Cloud
Staff Data Engineer
Share this page