DBMS > Amazon DynamoDB vs. EventStoreDB vs. FoundationDB vs. Google Cloud Bigtable vs. Oracle Berkeley DB

System Properties Comparison Amazon DynamoDB vs. EventStoreDB vs. FoundationDB vs. Google Cloud Bigtable vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Ordered key-value store. Core features are complimented by layers.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Widely used in-process key-value store

Primary database model

Document store
Key-value store

Event Store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Key-value store
Wide column store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	0.97
Rank	#191	Overall
	#32	Document stores
	#28	Key-value stores
	#87	Relational DBMS

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Website

aws.amazon.com/dynamodb

www.eventstore.com

github.com/apple/foundationdb

cloud.google.com/bigtable

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

Technical documentation

docs.aws.amazon.com/dynamodb

developers.eventstore.com

apple.github.io/foundationdb

cloud.google.com/bigtable/docs

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

Developer

Amazon

Event Store Limited

FoundationDB

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2013

2015

1994

Current release

21.2, February 2021

6.2.28, November 2020

18.1.40, May 2020

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

commercial

Open Source

commercial license available

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

C++

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

Server operating systems

hosted

Linux
Windows

Linux
OS X
Windows

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

some layers support schemas

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

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

supported in specific SQL layer only

yes

SQL interfaced based on SQLite is available

APIs and other access methods

RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
C++
Go
Java
JavaScript (Node.js)
Python

.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

Server-side scripts

Stored procedures

in SQL-layer only

Triggers

yes

by integration with AWS Lambda

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Linearizable consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

in SQL-layer only

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Atomic single-row 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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.