DBMS > MonetDB vs. MySQL vs. VoltDB vs. WakandaDB

System Properties Comparison MonetDB vs. MySQL vs. VoltDB vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A relational database management system that stores data in columns

Widely used open source RDBMS

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

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.72
Rank	#135	Overall
	#62	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

Technical documentation

www.monetdb.org/Documentation

dev.mysql.com/doc

docs.voltdb.com

wakanda.github.io/doc

Developer

MonetDB BV

Oracle

since 2010, originally MySQL AB, then Sun

VoltDB Inc.

Wakanda SAS

Initial release

2004

1995

2010

2012

Current release

Dec2023 (11.49), December 2023

9.0.0, July 2024

11.3, April 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Mozilla Public License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

Open Source

AGPLv3, extended commercial license available

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

Java, C++

C++, JavaScript

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

for development

Linux
OS X
Windows

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL 2003 with some extensions

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

JavaScript

Server-side scripts

Stored procedures

yes, in SQL, C, R

yes

proprietary syntax

Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding via remote tables

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication available in experimental status

Multi-source replication
Source-replica replication

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

not for MyISAM storage engine

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users with fine-grained authorization concept

no user groups or roles

Users and roles with access to stored procedures

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.