DBMS > Drizzle vs. MariaDB vs. Oracle Berkeley DB vs. Riak TS vs. Sphinx

System Properties Comparison Drizzle vs. MariaDB vs. Oracle Berkeley DB vs. Riak TS vs. Sphinx

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.

Description

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

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

Widely used in-process key-value store

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.oracle.com/database/technologies/related/berkeleydb.html

sphinxsearch.com

Technical documentation

mariadb.com/kb/en/library

docs.oracle.com/cd/E17076_05/html/index.html

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

sphinxsearch.com/docs

Developer

Drizzle project, originally started by Brian Aker

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Open Source, formerly Basho Technologies

Sphinx Technologies Inc.

Initial release

2008

2009

Fork of MySQL, which was first released in 1995

1994

2015

2001

Current release

7.2.4, September 2012

11.3.2, February 2024

18.1.40, May 2020

3.0.0, September 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

commercial license available

Open Source

GPL version 2, commercial licence 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++

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Erlang

C++

Server operating systems

FreeBSD
Linux
OS X

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Dynamic columns are supported

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

yes, limited

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

Proprietary protocol

Supported programming languages

C
C++
Java
PHP

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

Erlang

Triggers

hooks for callbacks inside the server can be used.

yes

only for the SQL API

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

several options for horizontal partitioning and Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

selectable replication factor

none

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

not for MyISAM storage engine

links between datasets can be stored

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

with MEMORY storage engine

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

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.