DBMS > EventStoreDB vs. Oracle Berkeley DB vs. PouchDB vs. SwayDB vs. XTDB

System Properties Comparison EventStoreDB vs. Oracle Berkeley DB vs. PouchDB vs. SwayDB vs. XTDB

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

JavaScript DBMS with an API inspired by CouchDB

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Event Store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Key-value store

Document store

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

Score	1.19
Rank	#173	Overall
	#1	Event Stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.eventstore.com

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

pouchdb.com

swaydb.simer.au

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

developers.eventstore.com

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

pouchdb.com/guides

www.xtdb.com/docs

Developer

Event Store Limited

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation

Simer Plaha

Juxt Ltd.

Initial release

2012

1994

2012

2018

2019

Current release

21.2, February 2021

18.1.40, May 2020

7.1.1, June 2019

1.19, September 2021

License

Commercial or Open Source

Open Source

commercial license available

Open Source

GNU Affero GPL V3.0

Open Source

MIT License

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)

JavaScript

Scala

Clojure

Server operating systems

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less, requires a JavaScript environment (browser, Node.js)

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, extensible-data-notation format

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

via views

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

HTTP REST
JDBC

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

JavaScript

Java
Kotlin
Scala

Clojure
Java

Server-side scripts

Stored procedures

View functions in JavaScript

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

Recent citations in the news

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

What You Need to Know About NoSQL Databases
17 February 2012, Forbes

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

How to store financial market data for backtesting
26 January 2019, Towards Data Science

provided by Google News

Building an Offline First App with PouchDB — SitePoint
10 March 2014, SitePoint

Create Offline Web Apps Using Service Workers & PouchDB — SitePoint
7 March 2017, SitePoint

Getting Started with PouchDB Client-Side JavaScript Database — SitePoint
7 September 2016, SitePoint

3 Reasons To Think Offline First
22 March 2017, ibm.com

Offline-first web and mobile apps: Top frameworks and components
22 January 2019, TechBeacon

provided by Google News

Share this page