DBMS > Drizzle vs. Oracle Berkeley DB vs. Oracle Rdb vs. YottaDB

System Properties Comparison Drizzle vs. Oracle Berkeley DB vs. Oracle Rdb vs. YottaDB

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.

Description

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

Widely used in-process key-value store

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

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

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

yottadb.com

Technical documentation

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

www.oracle.com/database/technologies/related/rdb-doc.html

yottadb.com/resources/documentation

Developer

Drizzle project, originally started by Brian Aker

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Oracle, originally developed by Digital Equipment Corporation (DEC)

YottaDB, LLC

Initial release

2008

1994

1984

2001

Current release

7.2.4, September 2012

18.1.40, May 2020

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

commercial license available

commercial

Open Source

AGPL 3.0

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, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

FreeBSD
Linux
OS X

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

HP Open VMS

Docker
Linux

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

schema-free

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

SQL interfaced based on SQLite is available

yes

by using the Octo plugin

APIs and other access methods

JDBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C++
Java
PHP

.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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

Triggers

hooks for callbacks inside the server can be used.

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

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

Transaction concepts

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

ACID

yes, on a single node

optimistic locking

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.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users and groups based on OS-security mechanisms

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

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, Datanami

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Oracle buys Sleepycat Software
14 February 2006, MarketWatch

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

provided by Google News

Oracle Adds New AI-Enabling Features To MySQL HeatWave
23 March 2023, Forbes

Should we all consolidate databases for the storage benefits? Reg vultures deploy DevOps, zoos, haircuts
18 September 2020, The Register

2013 Data Science Salary Survey – O'Reilly
4 May 2013, O'Reilly Media

provided by Google News

Share this page