DBMS > Adabas vs. Infobright vs. RisingWave vs. RocksDB vs. VoltDB

System Properties Comparison Adabas vs. Infobright vs. RisingWave vs. RocksDB vs. VoltDB

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

Score	2.79
Rank	#102	Overall
	#2	Multivalue DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.64
Rank	#238	Overall
	#110	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

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

ignitetech.com/softwarelibrary/infobrightdb

www.risingwave.com/database

rocksdb.org

www.voltdb.com

Technical documentation

docs.risingwave.com/docs/current/intro

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Software AG

Ignite Technologies Inc.; formerly InfoBright Inc.

RisingWave Labs

Facebook, Inc.

VoltDB Inc.

Initial release

1971

2005

2022

2013

2010

Current release

1.2, September 2023

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache Version 2.0

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Rust

C++

Java, C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
Windows

Docker
Linux
macOS

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Standard SQL-types and JSON

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

only a subset of SQL 99

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

ADO.NET
JDBC
ODBC

JDBC
PostgreSQL wire protocol

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Natural

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

in Natural

UDFs in Python or Java

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

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

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Source-replica replication

yes

Multi-source replication
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

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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)

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Users and Roles

Users and roles with access to stored procedures

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.