DBMS > EJDB vs. Oracle Berkeley DB vs. Riak KV vs. XTDB

System Properties Comparison EJDB vs. Oracle Berkeley DB vs. Riak KV vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used in-process key-value store

Distributed, fault tolerant key-value store

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

Primary database model

Document store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Document store

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

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

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/Softmotions/ejdb

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

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

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

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

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

www.xtdb.com/docs

Developer

Softmotions

Oracle

originally developed by Sleepycat, which was acquired by Oracle

OpenSource, formerly Basho Technologies

Juxt Ltd.

Initial release

2012

1994

2009

2019

Current release

18.1.40, May 2020

3.2.0, December 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

GPLv2

Open Source

commercial license available

Open Source

Apache version 2, commercial enterprise edition

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)

Erlang

Clojure

Server operating systems

server-less

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

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

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

restricted

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

in-process shared library

HTTP API
Native Erlang Interface

HTTP REST
JDBC

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.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

Clojure
Java

Server-side scripts

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

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

selectable replication factor

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

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

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

yes, using Riak Security

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

Recent citations in the news

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

Margo Seltzer Named ACM Athena Lecturer for Technical and Mentoring Contributions
26 April 2023, Datanami

Oracle buys Sleepycat Software
14 February 2006, MarketWatch

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

Share this page