DBMS > Adabas vs. Atos Standard Common Repository vs. Google BigQuery vs. JanusGraph

System Properties Comparison Adabas vs. Atos Standard Common Repository vs. Google BigQuery vs. JanusGraph

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

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Large scale data warehouse service with append-only tables

A Graph DBMS optimized for distributed clusters

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

Primary database model

Multivalue DBMS

Document store
Key-value store

Relational DBMS

Graph DBMS

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

Score	2.64
Rank	#104	Overall
	#1	Multivalue DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

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

cloud.google.com/bigquery

janusgraph.org

Technical documentation

cloud.google.com/bigquery/docs

docs.janusgraph.org

Developer

Software AG

Atos Convergence Creators

Google

Linux Foundation; originally developed as Titan by Aurelius

Initial release

1971

2016

2010

2017

Current release

1703

1.0.0, October 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

hosted

Linux
OS X
Unix
Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

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

with add-on product Adabas SQL Gateway

yes

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

LDAP

RESTful HTTP/JSON API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

Natural

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Clojure
Java
Python

Server-side scripts

Stored procedures

in Natural

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

Sharding

cell division

none

yes

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

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

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Atomic execution of specific operations

Since BigQuery is designed for querying data

ACID

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

In-memory capabilities

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

yes

User concepts

Access control

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

LDAP bind authentication

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

User authentification and security via Rexster Graph Server

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.