DBMS > Atos Standard Common Repository vs. Hyprcubd vs. Yaacomo
System Properties Comparison Atos Standard Common Repository vs. Hyprcubd vs. Yaacomo
Please select another system to include it in the comparison.
|Editorial information provided by DB-Engines
|Atos Standard Common Repository Xexclude from comparison
|Hyprcubd Xexclude from comparison
|Yaacomo Xexclude from comparison
|This system has been discontinued and will be removed from the DB-Engines ranking.
|Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.
|Yaacomo seems to be discontinued and is removed from the DB-Engines ranking
|Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks
|Serverless Time Series DBMS
|OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing
|Primary database model
|Time Series DBMS
|Atos Convergence Creators
|License Commercial or Open Source
|Cloud-based only Only available as a cloud service
|DBaaS offerings (sponsored links) Database as a Service
Providers of DBaaS offerings, please contact us to be listed.
|Server operating systems
|Schema and schema-less with LDAP views
|Typing predefined data types such as float or date
|yes time, int, uint, float, string
|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.
|SQL Support of SQL
|SQL-like query language
|APIs and other access methods
|Supported programming languages
|All languages with LDAP bindings
|Server-side scripts Stored procedures
|Partitioning methods Methods for storing different data on different nodes
|Sharding cell division
|Replication methods Methods for redundantly storing data on multiple nodes
|MapReduce Offers an API for user-defined Map/Reduce methods
|Consistency concepts Methods to ensure consistency in a distributed system
|Immediate Consistency or Eventual Consistency depending on configuration
|Foreign keys Referential integrity
|Transaction concepts Support to ensure data integrity after non-atomic manipulations of data
|Atomic execution of specific operations
|Concurrency Support for concurrent manipulation of data
|Durability Support for making data persistent
|In-memory capabilities Is there an option to define some or all structures to be held in-memory only.
|User concepts Access control
|LDAP bind authentication
|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,
Related products and services
We invite representatives of vendors of related products to contact us for presenting information about their offerings here.
Share this page