DBMS > Oracle Berkeley DB vs. OrigoDB vs. Prometheus vs. RocksDB

System Properties Comparison Oracle Berkeley DB vs. OrigoDB vs. Prometheus vs. RocksDB

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

A fully ACID in-memory object graph database

Open-source Time Series DBMS and monitoring system

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

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Object oriented DBMS

Time Series DBMS

Key-value store

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	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

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

Website

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

origodb.com

prometheus.io

rocksdb.org

Technical documentation

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

origodb.com/docs

prometheus.io/docs

github.com/facebook/rocksdb/wiki

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Robert Friberg et al

Facebook, Inc.

Initial release

1994

2009

under the name LiveDB

2015

2013

Current release

18.1.40, May 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

commercial license available

Open Source

Apache 2.0

Open Source

BSD

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

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

Numeric data only

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

can be achieved using .NET

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

.NET Client API
HTTP API
LINQ

RESTful HTTP/JSON API

C++ API
Java 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

.Net

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

only for the SQL API

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

by Federation

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.