DBMS > Oracle Berkeley DB vs. RocksDB vs. Splice Machine vs. VelocityDB

System Properties Comparison Oracle Berkeley DB vs. RocksDB vs. Splice Machine vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used in-process key-value store

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Relational DBMS

Graph DBMS
Object oriented DBMS

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

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

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

rocksdb.org

splicemachine.com

velocitydb.com

Technical documentation

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

github.com/facebook/rocksdb/wiki

splicemachine.com/how-it-works

velocitydb.com/UserGuide

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Splice Machine

VelocityDB Inc

Initial release

1994

2013

2014

2011

Current release

18.1.40, May 2020

9.2.1, May 2024

3.1, March 2021

7.x

License

Commercial or Open Source

Open Source

commercial license available

Open Source

BSD

Open Source

AGPL 3.0, commercial license available

commercial

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

Java

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Linux
OS X
Solaris
Windows

Any that supports .NET

Data scheme

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

SQL interfaced based on SQLite is available

yes

APIs and other access methods

C++ API
Java API

JDBC
Native Spark Datasource
ODBC

.Net

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

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

.Net

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

only for the SQL API

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Access rights for users, groups and roles according to SQL-standard

Based on Windows Authentication

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.