DBMS > Drizzle vs. Microsoft Azure AI Search vs. MySQL vs. Oracle Berkeley DB vs. WakandaDB

System Properties Comparison Drizzle vs. Microsoft Azure AI Search vs. MySQL vs. Oracle Berkeley DB vs. WakandaDB

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.

Search-as-a-service for web and mobile app development

Widely used open source RDBMS

Widely used in-process key-value store

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

Search engine

Relational DBMS

Key/Value like access via memcached API

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Object oriented DBMS

Secondary database models

Vector DBMS

Document store
Spatial DBMS

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

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

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

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

azure.microsoft.com/en-us/services/search

www.mysql.com

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

wakanda.github.io

Technical documentation

learn.microsoft.com/en-us/azure/search

dev.mysql.com/doc

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

wakanda.github.io/doc

Developer

Drizzle project, originally started by Brian Aker

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Wakanda SAS

Initial release

2008

2015

1995

1994

2012

Current release

7.2.4, September 2012

8.4.0, April 2024

18.1.40, May 2020

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial license available

Open Source

AGPLv3, extended commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

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

C++, JavaScript

Server operating systems

FreeBSD
Linux
OS X

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Windows

Data scheme

yes

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

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

C
C++
Java
PHP

C#
Java
JavaScript
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
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

JavaScript

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

hooks for callbacks inside the server can be used.

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

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

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

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

using Azure authentication

Users with fine-grained authorization concept

no user groups or roles

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.