DBMS > Amazon DynamoDB vs. EsgynDB vs. Oracle Berkeley DB vs. ToroDB vs. Trafodion

System Properties Comparison Amazon DynamoDB vs. EsgynDB vs. Oracle Berkeley DB vs. ToroDB vs. Trafodion

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Widely used in-process key-value store

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Relational DBMS

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

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

aws.amazon.com/dynamodb

www.esgyn.cn

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

github.com/torodb/server

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

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

trafodion.apache.org/documentation.html

Developer

Amazon

Esgyn

Oracle

originally developed by Sleepycat, which was acquired by Oracle

8Kdata

Apache Software Foundation, originally developed by HP

Initial release

2012

2015

1994

2016

2014

Current release

18.1.40, May 2020

2.3.0, February 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

commercial license available

Open Source

AGPL-V3

Open Source

Apache 2.0

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++, Java

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

Java

C++, Java

Server operating systems

hosted

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

All OS with a Java 7 VM

Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

.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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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)

fine grained access rights according to SQL-standard

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.