DBMS > Atos Standard Common Repository vs. Lovefield vs. Sequoiadb vs. WakandaDB

System Properties Comparison Atos Standard Common Repository vs. Lovefield vs. Sequoiadb vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Atos Standard Common Repository  Xexclude from comparison	Lovefield  Xexclude from comparison	Sequoiadb  Xexclude from comparison	WakandaDB  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	Embeddable relational database for web apps written in pure JavaScript	NewSQL database with distributed OLTP and SQL	WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data
Primary database model	Document store Key-value store	Relational DBMS	Document store Relational DBMS	Object oriented DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart		Score 0.33 Rank #286   Overall #131   Relational DBMS	Score 0.50 Rank #258   Overall #41   Document stores #120   Relational DBMS	Score 0.10 Rank #356   Overall #16   Object oriented DBMS
Website	atos.net/en/convergence-creators/portfolio/standard-common-repository	google.github.io/­lovefield	www.sequoiadb.com	wakanda.github.io
Technical documentation		github.com/­google/­lovefield/­blob/­master/­docs/­spec_index.md	www.sequoiadb.com/­en/­index.php?m=Files&a=index	wakanda.github.io/­doc
Developer	Atos Convergence Creators	Google	Sequoiadb Ltd.	Wakanda SAS
Initial release	2016	2014	2013	2012
Current release	1703	2.1.12, February 2017		2.7.0 (April 29, 2019), April 2019
License Commercial or Open Source	commercial	Open Source Apache 2.0	Open Source Server: AGPL; Client: Apache V2	Open Source AGPLv3, extended commercial license available
Cloud-based only Only available as a cloud service	no	no	no	no
DBaaS offerings (sponsored links) Database as a Service Providers of DBaaS offerings, please contact us to be listed.
Implementation language	Java	JavaScript	C++	C++, JavaScript
Server operating systems	Linux	server-less, requires a JavaScript environment (browser, Node.js) tested with Chrome, Firefox, IE, Safari	Linux	Linux OS X Windows
Data scheme	Schema and schema-less with LDAP views	yes	schema-free	yes
Typing predefined data types such as float or date	optional	yes	yes oid, date, timestamp, binary, regex	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	no	no	no
Secondary indexes	yes	yes	yes
SQL Support of SQL	no	SQL-like query language via JavaScript builder pattern	SQL-like query language	no
APIs and other access methods	LDAP		proprietary protocol using JSON	RESTful HTTP API
Supported programming languages	All languages with LDAP bindings	JavaScript	.Net C++ Java PHP Python	JavaScript
Server-side scripts Stored procedures	no	no	JavaScript	yes
Triggers	yes	Using read-only observers	no	yes
Partitioning methods Methods for storing different data on different nodes	Sharding cell division	none	Sharding	none
Replication methods Methods for redundantly storing data on multiple nodes	yes	none	Source-replica replication	none
MapReduce Offers an API for user-defined Map/Reduce methods		no	no	no
Consistency concepts Methods to ensure consistency in a distributed system	Immediate Consistency or Eventual Consistency depending on configuration		Eventual Consistency	Immediate Consistency
Foreign keys Referential integrity	no	yes	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	Atomic execution of specific operations	ACID	Document is locked during a transaction	ACID
Concurrency Support for concurrent manipulation of data	yes	yes	yes	yes
Durability Support for making data persistent	yes	yes, by using IndexedDB or the cloud service Firebase Realtime Database	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes	yes using MemoryDB	no	no
User concepts Access control	LDAP bind authentication	no	simple password-based access control	yes
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	Lovefield	Sequoiadb	WakandaDB
Recent citations in the news	Infographic: What makes a Mobile Operator's setup future proof? 10 February 2024, Atos provided by Google News

Share this page