DBMS > 4D vs. Drizzle vs. H2 vs. Oracle Berkeley DB

System Properties Comparison 4D vs. Drizzle vs. H2 vs. Oracle Berkeley DB

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

Application development environment with integrated database management system

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Widely used in-process 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

Secondary database models

Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

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

Website

www.4d.com

www.h2database.com

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

Technical documentation

developer.4d.com

www.h2database.com/html/main.html

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

Developer

4D, Inc

Drizzle project, originally started by Brian Aker

Thomas Mueller

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

1984

2008

2005

1994

Current release

v20, April 2023

7.2.4, September 2012

2.2.220, July 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

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

Java

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

Server operating systems

OS X
Windows

FreeBSD
Linux
OS X

All OS with a Java VM

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

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

close to SQL 92

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC

JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

C
C++
Java
PHP

Java

.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

Server-side scripts

Stored procedures

yes

Java Stored Procedures and User-Defined Functions

Triggers

yes

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

With clustering: 2 database servers on different computers operate on identical copies of a database

Source-replica replication

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Users and groups

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

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

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

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

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

How to store financial market data for backtesting
26 January 2019, Towards Data Science

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

provided by Google News

Share this page