DBMS > HBase vs. Oracle Berkeley DB vs. RocksDB vs. STSdb

System Properties Comparison HBase vs. Oracle Berkeley DB vs. RocksDB vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

Widely used in-process key-value store

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

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

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

hbase.apache.org

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

rocksdb.org

github.com/STSSoft/STSdb4

Technical documentation

hbase.apache.org/book.html

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

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

STS Soft SC

Initial release

2008

1994

2013

2011

Current release

2.3.4, January 2021

18.1.40, May 2020

8.11.4, April 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

commercial license available

Open Source

BSD

Open Source

GPLv2, commercial license available

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

Java

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Windows

Data scheme

schema-free, schema definition possible

schema-free

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

yes

primitive types and user defined types (classes)

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

APIs and other access methods

Java API
RESTful HTTP API
Thrift

C++ API
Java API

.NET Client API

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

.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#
Java

Server-side scripts

Stored procedures

yes

Coprocessors in Java

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Single row ACID (across millions of columns)

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.