DBMS > Oracle Berkeley DB vs. Percona Server for MySQL vs. RocksDB vs. Vitess vs. VoltDB

System Properties Comparison Oracle Berkeley DB vs. Percona Server for MySQL vs. RocksDB vs. Vitess vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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	2.10
Rank	#119	Overall
	#57	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

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

www.percona.com/software/mysql-database/percona-server

rocksdb.org

vitess.io

www.voltdb.com

Technical documentation

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

www.percona.com/downloads/Percona-Server-LATEST

github.com/facebook/rocksdb/wiki

vitess.io/docs

docs.voltdb.com

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Percona

Facebook, Inc.

The Linux Foundation, PlanetScale

VoltDB Inc.

Initial release

1994

2008

2013

2010

Current release

18.1.40, May 2020

8.0.36-28, 2024

9.2.1, May 2024

15.0.2, December 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

commercial license available

Open Source

GPL version 2

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses available

Open Source

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

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

C and C++

C++

Java, C++

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Docker
Linux
macOS

Linux
OS X

for development

Data scheme

schema-free

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
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

Server-side scripts

Stored procedures

yes

proprietary syntax

Java

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication
XtraDB Cluster

yes

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

Eventual Consistency across shards
Immediate Consistency within a shard

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

yes

ACID at shard level

ACID

Transactions are executed single-threaded within stored procedures

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

Durability

Support for making data persistent

yes

Snapshots and command logging

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 with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

no user groups or roles

Users and roles with access to stored procedures

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.