DBMS > Atos Standard Common Repository vs. Graph Engine vs. JanusGraph vs. Sadas Engine

System Properties Comparison Atos Standard Common Repository vs. Graph Engine vs. JanusGraph vs. Sadas Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Document store
Key-value store

Graph DBMS
Key-value store

Graph DBMS

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	0.00
Rank	#385	Overall
	#159	Relational DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.graphengine.io

janusgraph.org

www.sadasengine.com

Technical documentation

www.graphengine.io/docs/manual

docs.janusgraph.org

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Atos Convergence Creators

Microsoft

Linux Foundation; originally developed as Titan by Aurelius

SADAS s.r.l.

Initial release

2016

2010

2017

2006

Current release

1703

1.0.0, October 2023

8.0

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache 2.0

commercial

free trial version available

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.

Implementation language

Java

.NET and C

Java

C++

Server operating systems

Linux

.NET

Linux
OS X
Unix
Windows

AIX
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC
Proprietary protocol

Supported programming languages

All languages with LDAP bindings

C#
C++
F#
Visual Basic

Clojure
Java
Python

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

managed by 'Learn by Usage'

User concepts

Access control

LDAP bind authentication

User authentification and security via Rexster Graph Server

Access rights for users, groups and roles 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

Recent citations in the news

Trinity
30 October 2010, microsoft.com

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
27 February 2019, Data Science Central

Aerospike Is Now a Graph Database, Too
21 June 2023, Datanami

provided by Google News

Simple Deployment of a Graph Database: JanusGraph
12 October 2020, Towards Data Science

Database Deep Dives: JanusGraph
8 August 2019, ibm.com

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

Compose for JanusGraph arrives on Bluemix
15 September 2017, ibm.com

provided by Google News

Share this page