DBMS > Atos Standard Common Repository vs. FatDB vs. Graph Engine vs. Machbase Neo

System Properties Comparison Atos Standard Common Repository vs. FatDB vs. Graph Engine vs. Machbase Neo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Atos Standard Common Repository  Xexclude from comparison	FatDB  Xexclude from comparison	Graph Engine former name: Trinity  Xexclude from comparison	Machbase Neo Former name was Infiniflux  Xexclude from comparison
	This system has been discontinued and will be removed from the DB-Engines ranking.	FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.
Description	Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks	A .NET NoSQL DBMS that can integrate with and extend SQL Server.	A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine	TimeSeries DBMS for AIoT and BigData
Primary database model	Document store Key-value store	Document store Key-value store	Graph DBMS Key-value store	Time Series DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart			Score 0.67 Rank #232   Overall #21   Graph DBMS #34   Key-value stores	Score 0.17 Rank #337   Overall #30   Time Series DBMS
Website	atos.net/en/convergence-creators/portfolio/standard-common-repository		www.graphengine.io	machbase.com
Technical documentation			www.graphengine.io/­docs/­manual	machbase.com/­dbms
Developer	Atos Convergence Creators	FatCloud	Microsoft	Machbase
Initial release	2016	2012	2010	2013
Current release	1703			V8.0, August 2023
License Commercial or Open Source	commercial	commercial	Open Source MIT License	commercial free test version 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	C#	.NET and C	C
Server operating systems	Linux	Windows	.NET	Linux macOS Windows
Data scheme	Schema and schema-less with LDAP views	schema-free	yes	yes
Typing predefined data types such as float or date	optional	yes	yes	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
Secondary indexes	yes	yes		yes
SQL Support of SQL	no	no Via inetgration in SQL Server	no	SQL-like query language
APIs and other access methods	LDAP	.NET Client API LINQ RESTful HTTP API RPC Windows WCF Bindings	RESTful HTTP API	gRPC HTTP REST JDBC MQTT (Message Queue Telemetry Transport) ODBC
Supported programming languages	All languages with LDAP bindings	C#	C# C++ F# Visual Basic	C C# C++ Go Java JavaScript PHP via ODBC Python R via ODBC Scala
Server-side scripts Stored procedures	no	yes via applications	yes	no
Triggers	yes	yes via applications	no	no
Partitioning methods Methods for storing different data on different nodes	Sharding cell division	Sharding	horizontal partitioning	Sharding
Replication methods Methods for redundantly storing data on multiple nodes	yes	selectable replication factor		selectable replication factor
MapReduce Offers an API for user-defined Map/Reduce methods		yes		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	no	no	no
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	Atomic execution of specific operations	no	no	no
Concurrency Support for concurrent manipulation of data	yes	yes	yes	yes
Durability Support for making data persistent	yes	yes	optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage	no
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes		yes	yes volatile and lookup table
User concepts Access control	LDAP bind authentication	no Can implement custom security layer via applications		simple password-based access control
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	FatDB	Graph Engine former name: Trinity	Machbase Neo Former name was Infiniflux
Recent citations in the news	Infographic: What makes a Mobile Operator's setup future proof? 10 February 2024, Atos provided by Google News		Trinity 30 October 2010, Microsoft Open source Microsoft Graph Engine takes on Neo4j 13 February 2017, InfoWorld IBM releases Graph, a service that can outperform SQL databases 27 July 2016, GeekWire The graph analytics landscape 2019 - DataScienceCentral.com 27 February 2019, Data Science Central Aerospike Is Now a Graph Database, Too 21 June 2023, Datanami provided by Google News

Share this page