DBMS > EventStoreDB vs. Oracle Berkeley DB vs. RocksDB vs. SwayDB vs. TimescaleDB

System Properties Comparison EventStoreDB vs. Oracle Berkeley DB vs. RocksDB vs. SwayDB vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Widely used in-process key-value store

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

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

Primary database model

Event Store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	1.10
Rank	#179	Overall
	#1	Event 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.00
Rank	#382	Overall
	#59	Key-value stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

www.eventstore.com

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

rocksdb.org

swaydb.simer.au

www.timescale.com

Technical documentation

developers.eventstore.com

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

github.com/facebook/rocksdb/wiki

docs.timescale.com

Developer

Event Store Limited

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Simer Plaha

Timescale

Initial release

2012

1994

2013

2018

2017

Current release

21.2, February 2021

18.1.40, May 2020

8.11.4, April 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

commercial license available

Open Source

BSD

Open Source

GNU Affero GPL V3.0

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)

C++

Scala

Server operating systems

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

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

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

full PostgreSQL SQL syntax

APIs and other access methods

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

C
C++
Go
Java
Perl
Python
Ruby

Java
Kotlin
Scala

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Atomic execution of operations

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

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.