DBMS > Cloudflare Workers KV vs. HarperDB vs. Oracle Berkeley DB vs. RocksDB vs. Transbase

System Properties Comparison Cloudflare Workers KV vs. HarperDB vs. Oracle Berkeley DB vs. RocksDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

A global, low-latency, key-value store for applications on Cloudflare with exceptionally high read volumes and low-latency.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Widely used in-process key-value store

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Key-value store

Document store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Relational DBMS

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

Score	0.32
Rank	#283	Overall
	#40	Key-value stores

Score	0.55
Rank	#248	Overall
	#38	Document stores

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.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.cloudflare.com/developer-platform/workers-kv

www.harperdb.io

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

rocksdb.org

www.transaction.de/en/products/transbase.html

Technical documentation

developers.cloudflare.com/kv/api

docs.harperdb.io/docs

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

github.com/facebook/rocksdb/wiki

www.transaction.de/en/products/transbase/features.html

Developer

Cloudflare

HarperDB

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Transaction Software GmbH

Initial release

2018

2017

1994

2013

1987

Current release

3.1, August 2021

18.1.40, May 2020

8.11.4, April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

commercial license available

Open Source

BSD

commercial

free development license

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Node.js

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

C++

C and C++

Server operating systems

hosted

Linux
OS X

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

dynamic schema

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL-like data manipulation statements

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

HTTP REST
Proprietary protocol

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.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#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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 and roles

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.