DBMS > EsgynDB vs. Oracle Berkeley DB vs. Riak TS vs. RocksDB

System Properties Comparison EsgynDB vs. Oracle Berkeley DB vs. Riak TS vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Widely used in-process key-value store

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Key-value store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

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

Website

www.esgyn.cn

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

rocksdb.org

Technical documentation

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

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

github.com/facebook/rocksdb/wiki

Developer

Esgyn

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Open Source, formerly Basho Technologies

Facebook, Inc.

Initial release

2015

1994

2015

2013

Current release

18.1.40, May 2020

3.0.0, September 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

commercial license available

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

Erlang

C++

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

Linux

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

restricted

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes, limited

APIs and other access methods

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.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

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

Triggers

yes

only for the SQL API

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

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.