DBMS > Adabas vs. Atos Standard Common Repository vs. Qdrant vs. RocksDB vs. Teradata Aster

System Properties Comparison Adabas vs. Atos Standard Common Repository vs. Qdrant vs. RocksDB vs. Teradata Aster

Editorial information provided by DB-Engines

Name

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

Teradata Aster has been integrated into other Teradata systems and therefore 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 high-performance vector database with neural network or semantic-based matching

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Platform for big data analytics on multistructured data sources and types

Primary database model

Multivalue DBMS

Document store
Key-value store

Vector DBMS

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	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

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

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

github.com/qdrant/qdrant
qdrant.tech

rocksdb.org

Technical documentation

qdrant.tech/documentation

github.com/facebook/rocksdb/wiki

Developer

Software AG

Atos Convergence Creators

Qdrant

Facebook, Inc.

Teradata

Initial release

1971

2016

2021

2013

2005

Current release

1703

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

BSD

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

Rust

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

Docker
Linux
macOS
Windows

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

optional

Numbers, Strings, Geo, Boolean

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

in Aster File Store

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Natural

All languages with LDAP bindings

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

in Natural

R packages

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

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Collection-level replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency, tunable consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Atomic execution of specific operations

yes

ACID

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

User concepts

Access control

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

LDAP bind authentication

Key-based authentication

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.