DBMS > Atos Standard Common Repository vs. JanusGraph vs. Linter vs. searchxml

System Properties Comparison Atos Standard Common Repository vs. JanusGraph vs. Linter vs. searchxml

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 Graph DBMS optimized for distributed clusters

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

RDBMS for high security requirements

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store
Key-value store

Graph DBMS

Relational DBMS

Native XML DBMS
Search engine

Secondary database models

Spatial DBMS

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

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

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

janusgraph.org

linter.ru

www.searchxml.net/category/products

Technical documentation

docs.janusgraph.org

www.searchxml.net/support/handouts

Developer

Atos Convergence Creators

Linux Foundation; originally developed as Titan by Aurelius

relex.ru

informationpartners gmbh

Initial release

2016

2017

1990

2015

Current release

1703

0.6.3, February 2023

1.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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

C and C++

C++

Server operating systems

Linux

Linux
OS X
Unix
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

All languages with LDAP bindings

Clojure
Java
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

on the application server

Triggers

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)

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

sychronisation to multiple collections

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

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

LDAP bind authentication

User authentification and security via Rexster Graph Server

fine grained access rights according to SQL-standard

Domain, group and role-based access control at the document level and for application services

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

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

Database Deep Dives: JanusGraph
8 August 2019, IBM

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

Compose for JanusGraph arrives on Bluemix
15 September 2017, IBM

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

provided by Google News

Share this page