DBMS > Atos Standard Common Repository vs. JanusGraph vs. LeanXcale vs. Transbase

System Properties Comparison Atos Standard Common Repository vs. JanusGraph vs. LeanXcale vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
Name	Atos Standard Common Repository  Xexclude from comparison	JanusGraph successor of Titan  Xexclude from comparison	LeanXcale  Xexclude from comparison	Transbase  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	A Graph DBMS optimized for distributed clusters It was forked from the latest code base of Titan in January 2017	A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities	A resource-optimized, high-performance, universally applicable RDBMS
Primary database model	Document store Key-value store	Graph DBMS	Key-value store Relational DBMS	Relational DBMS
DB-Engines Ranking measures the popularity of database management systems Trend Chart		Score 2.02 Rank #125   Overall #12   Graph DBMS	Score 0.36 Rank #280   Overall #40   Key-value stores #129   Relational DBMS	Score 0.17 Rank #334   Overall #148   Relational DBMS
Website	atos.net/en/convergence-creators/portfolio/standard-common-repository	janusgraph.org	www.leanxcale.com	www.transaction.de/­en/­products/­transbase.html
Technical documentation		docs.janusgraph.org		www.transaction.de/­en/­products/­transbase/­features.html
Developer	Atos Convergence Creators	Linux Foundation; originally developed as Titan by Aurelius	LeanXcale	Transaction Software GmbH
Initial release	2016	2017	2015	1987
Current release	1703	0.6.3, February 2023		Transbase 8.3, 2022
License Commercial or Open Source	commercial	Open Source Apache 2.0	commercial	commercial free development license
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	Java		C and C++
Server operating systems	Linux	Linux OS X Unix Windows		FreeBSD Linux macOS Solaris Windows
Data scheme	Schema and schema-less with LDAP views	yes	yes	yes
Typing predefined data types such as float or date	optional	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	yes through Apache Derby	yes
APIs and other access methods	LDAP	Java API TinkerPop Blueprints TinkerPop Frames TinkerPop Gremlin TinkerPop Rexster	JDBC Kafka Connector ODBC proprietary key/value interface Spark Connector	ADO.NET JDBC ODBC Proprietary native API
Supported programming languages	All languages with LDAP bindings	Clojure Java Python	C Java Scala	C C# C++ Java JavaScript Kotlin Objective-C PHP Python
Server-side scripts Stored procedures	no	yes		yes
Triggers	yes	yes		yes
Partitioning methods Methods for storing different data on different nodes	Sharding cell division	yes depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)
Replication methods Methods for redundantly storing data on multiple nodes	yes	yes		Source-replica replication
MapReduce Offers an API for user-defined Map/Reduce methods		yes via Faunus, a graph analytics engine	no	no
Consistency concepts Methods to ensure consistency in a distributed system	Immediate Consistency or Eventual Consistency depending on configuration	Eventual Consistency Immediate Consistency	Immediate Consistency	Immediate Consistency
Foreign keys Referential integrity	no	yes Relationships in graphs	yes	yes
Transaction concepts Support to ensure data integrity after non-atomic manipulations of data	Atomic execution of specific operations	ACID	ACID	yes
Concurrency Support for concurrent manipulation of data	yes	yes	yes	yes
Durability Support for making data persistent	yes	yes Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast	yes	yes
In-memory capabilities Is there an option to define some or all structures to be held in-memory only.	yes		yes	no
User concepts Access control	LDAP bind authentication	User authentification and security via Rexster Graph Server		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, 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	JanusGraph successor of Titan	LeanXcale	Transbase
Recent citations in the news	Infographic: What makes a Mobile Operator's setup future proof? 10 February 2024, Atos provided by Google News	Database Deep Dives: JanusGraph 8 August 2019, IBM JanusGraph Picks Up Where TitanDB Left Off 13 January 2017, Datanami From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex 30 July 2020, Towards Data Science Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph 3 October 2019, The New Stack The year of the graph: Getting graphic, going native, reshaping the landscape 8 January 2018, ZDNet provided by Google News

Share this page