DBMS > EsgynDB vs. MaxDB vs. Riak KV vs. Sequoiadb

System Properties Comparison EsgynDB vs. MaxDB vs. Riak KV vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Distributed, fault tolerant key-value store

NewSQL database with distributed OLTP and SQL

Primary database model

Relational DBMS

Key-value store

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

Document store
Relational DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

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

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

Website

www.esgyn.cn

maxdb.sap.com

www.sequoiadb.com

Technical documentation

maxdb.sap.com/documentation

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

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

Developer

Esgyn

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

OpenSource, formerly Basho Technologies

Sequoiadb Ltd.

Initial release

2015

1984

2009

2013

Current release

7.9.10.12, February 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

Apache version 2, commercial enterprise edition

Open Source

Server: AGPL; Client: Apache V2

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++, Java

C++

Erlang

C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

restricted

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

HTTP API
Native Erlang Interface

proprietary protocol using JSON

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
Java
Perl
PHP
Python

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Erlang

JavaScript

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

selectable replication factor

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

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Document is locked during a transaction

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.

User concepts

Access control

fine grained access rights according to SQL-standard

yes, using Riak Security

simple password-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

SAP Content Server High Availability using Amazon EFS and SUSE | Amazon Web Services
30 December 2020, AWS Blog

SAP Aligns Mainstream Maintenance Commitments Across Its Enterprise Solutions
11 August 2020, SAP News

What is SAP S/4HANA?
21 March 2022, TechTarget

Dear SAP, Why Don't You Make Hana A Success?
28 July 2021, E3-Magazin

Alibaba Cloud Offers Access to SAP Software for Customers
5 June 2018, Alizila

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page