DBMS > Atos Standard Common Repository vs. JaguarDB vs. JanusGraph vs. Splunk

System Properties Comparison Atos Standard Common Repository vs. JaguarDB vs. JanusGraph vs. Splunk

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

Performant, highly scalable DBMS for AI and IoT applications

A Graph DBMS optimized for distributed clusters

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

Analytics Platform for Big Data

Primary database model

Document store
Key-value store

Key-value store
Vector DBMS

Graph DBMS

Search engine

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

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

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

www.jaguardb.com

janusgraph.org

www.splunk.com

Technical documentation

www.jaguardb.com/support.html

docs.janusgraph.org

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

DataJaguar, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Splunk Inc.

Initial release

2016

2015

2017

2003

Current release

1703

3.3 July 2023

0.6.3, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition 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

C++

the server part. Clients available in other languages

Java

Server operating systems

Linux

Linux
OS X
Unix
Windows

Linux
OS X
Solaris
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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

Splunk Search Processing Language for search commands

APIs and other access methods

LDAP

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP REST

Supported programming languages

All languages with LDAP bindings

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Clojure
Java
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Atomic execution of specific operations

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

rights management via user accounts

User authentification and security via Rexster Graph Server

Access rights for users and roles

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

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

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.com

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