DBMS > Adabas vs. Atos Standard Common Repository vs. Google BigQuery vs. Interbase vs. Yaacomo

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

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Yaacomo seems to be discontinued and is 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

Light-weight proven RDBMS

originally from Borland

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Multivalue DBMS

Document store
Key-value store

Relational DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Website

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

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

cloud.google.com/bigquery

www.embarcadero.com/products/interbase

yaacomo.com

Technical documentation

cloud.google.com/bigquery/docs

docs.embarcadero.com/products/interbase

Developer

Software AG

Atos Convergence Creators

Google

Embarcadero

Q2WEB GmbH

Initial release

1971

2016

2010

1984

2009

Current release

1703

InterBase 2020, December 2019

License

Commercial or Open Source

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

hosted

Android
iOS
Linux
OS X
Windows

Android
Linux
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

export as XML data possible

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

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

Natural

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

Server-side scripts

Stored procedures

in Natural

user defined functions

in JavaScript

yes

Interbase procedure and trigger language

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Interbase Change Views

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

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

Multiversion concurreny control

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

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)

fine grained access rights 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.