DBMS > Drizzle vs. MaxDB vs. Riak KV vs. ToroDB

System Properties Comparison Drizzle vs. MaxDB vs. Riak KV vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Distributed, fault tolerant key-value store

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Key-value store

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

Document store

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

Score	2.65
Rank	#111	Overall
	#55	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

maxdb.sap.com

github.com/torodb/server

Technical documentation

maxdb.sap.com/documentation

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

Developer

Drizzle project, originally started by Brian Aker

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

OpenSource, formerly Basho Technologies

8Kdata

Initial release

2008

1984

2009

2016

Current release

7.2.4, September 2012

7.9.10.12, February 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Limited community edition free

Open Source

Apache version 2, commercial enterprise edition

Open Source

AGPL-V3

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

Erlang

Java

Server operating systems

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
WebDAV

HTTP API
Native Erlang Interface

Supported programming languages

C
C++
Java
PHP

.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

Server-side scripts

Stored procedures

yes

Erlang

Triggers

hooks for callbacks inside the server can be used.

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
Source-replica replication

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

Eventual Consistency
Immediate 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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

yes, using Riak Security

Access rights for users and roles

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

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

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

SIOS looks to boost SAP HANA automated replication
29 March 2023, TechTarget

Remotely Exploitable Vulnerabilities in SAP Compression Algorithms
13 May 2015, Threatpost

Your SAP HANA Cheat Sheet: Milestones, Terms and More
14 May 2012, SiliconANGLE News

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page