DBMS > Oracle Berkeley DB vs. Riak KV vs. RocksDB vs. TimescaleDB

System Properties Comparison Oracle Berkeley DB vs. Riak KV vs. RocksDB vs. TimescaleDB

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

Distributed, fault tolerant key-value store

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

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

with links between data sets and object tags for the creation of secondary indexes

Key-value store

Time Series DBMS

Secondary database models

Relational 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	4.10
Rank	#82	Overall
	#9	Key-value stores

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

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

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

rocksdb.org

www.timescale.com

Technical documentation

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

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

docs.timescale.com

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

OpenSource, formerly Basho Technologies

Facebook, Inc.

Timescale

Initial release

1994

2009

2013

2017

Current release

18.1.40, May 2020

3.2.0, December 2022

8.11.4, April 2024

2.13.0, November 2023

License

Commercial or Open Source

Open Source

commercial license available

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

Open Source

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

Erlang

C++

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

restricted

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP API
Native Erlang Interface

C++ API
Java API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Erlang

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

only for the SQL API

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

horizontal partitioning

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

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

yes, using Riak Security

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.