DBMS > Riak KV vs. SAP Advantage Database Server vs. SAP HANA vs. WakandaDB

System Properties Comparison Riak KV vs. SAP Advantage Database Server vs. SAP HANA vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed, fault tolerant key-value store

Low-cost RDBMS with access to ISAM and FoxPro data structures

In-memory, column based data store. Available as appliance or cloud service

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.sap.com/products/advantage-database-server.html

www.sap.com/products/hana.html

wakanda.github.io

Technical documentation

www.tiot.jp/riak-docs/riak/kv/latest

help.sap.com/hana

wakanda.github.io/doc

Developer

OpenSource, formerly Basho Technologies

Sybase, SAP

SAP

Wakanda SAS

Initial release

2009

1993

2010

2012

Current release

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

AGPLv3, extended commercial license available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

C++, JavaScript

Server operating systems

Linux
OS X

Linux
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

schema-free

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC

RESTful HTTP API

Supported programming languages

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Delphi
Perl
PHP

JavaScript

Server-side scripts

Stored procedures

Erlang

yes

SQLScript, R

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

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.

caching of (temporary) tables can be configured

yes

User concepts

Access control

yes, using Riak Security

fine grained access rights according to SQL-standard

yes

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.