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

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

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Large scale data warehouse service with append-only tables

Primary database model

Multivalue DBMS

Document store
Key-value store

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Website

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

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

www.elastic.co/elasticsearch

cloud.google.com/bigquery

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

cloud.google.com/bigquery/docs

Developer

Software AG

Atos Convergence Creators

Elastic

Google

Initial release

1971

2016

2010

Current release

1703

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Elastic License

commercial

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

All OS with a Java VM

hosted

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language

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

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

Supported programming languages

Natural

All languages with LDAP bindings

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

in Natural

yes

user defined functions

in JavaScript

Triggers

yes

by using the 'percolation' feature

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

Sharding

none

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

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

Memcached and Redis integration

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)

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.