DBMS > MaxDB vs. Postgres-XL vs. RocksDB vs. Yanza

System Properties Comparison MaxDB vs. Postgres-XL vs. RocksDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A robust and reliable RDBMS optimized to run all major SAP solutions

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

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

Website

maxdb.sap.com

www.postgres-xl.org

rocksdb.org

yanza.com

Technical documentation

maxdb.sap.com/documentation

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

SAP, acquired from Software AG (Adabas-D) in 1997

Facebook, Inc.

Yanza

Initial release

1984

2014

since 2012, originally named StormDB

2013

2015

Current release

7.9.10.12, February 2024

10 R1, October 2018

9.2.1, May 2024

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

Mozilla public license

Open Source

BSD

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS

Linux

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

HTTP API

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

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

yes

Transaction concepts

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

ACID

MVCC

yes

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

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.