DBMS > Adabas vs. Apache Drill vs. RocksDB vs. Sequoiadb vs. Transbase

System Properties Comparison Adabas vs. Apache Drill vs. RocksDB vs. Sequoiadb vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

used typically together with the Natural programming platform

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

NewSQL database with distributed OLTP and SQL

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Multivalue DBMS

Document store
Relational DBMS

Key-value store

Document store
Relational DBMS

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.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

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

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

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

drill.apache.org

rocksdb.org

www.sequoiadb.com

www.transaction.de/en/products/transbase.html

Technical documentation

drill.apache.org/docs

github.com/facebook/rocksdb/wiki

www.sequoiadb.com/en/index.php?m=Files&a=index

www.transaction.de/en/products/transbase/features.html

Developer

Software AG

Apache Software Foundation

Facebook, Inc.

Sequoiadb Ltd.

Transaction Software GmbH

Initial release

1971

2012

2013

1987

Current release

1.20.3, January 2023

8.11.4, April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

BSD

Open Source

Server: AGPL; Client: Apache V2

commercial

free development license

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

C++

C and C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL SELECT statement is SQL:2003 compliant

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

JDBC
ODBC
RESTful HTTP API

C++ API
Java API

proprietary protocol using JSON

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Natural

C++

C
C++
Go
Java
Perl
Python
Ruby

.Net
C++
Java
PHP
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

in Natural

user defined functions

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

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Document is locked during a transaction

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

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

Depending on the underlying data source

simple password-based access control

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.