DBMS > Amazon DynamoDB vs. Oracle Berkeley DB vs. Stardog vs. Tarantool vs. Vitess

System Properties Comparison Amazon DynamoDB vs. Oracle Berkeley DB vs. Stardog vs. Tarantool vs. Vitess

Editorial information provided by DB-Engines

Name

Description

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

Widely used in-process key-value store

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Graph DBMS
RDF store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

Document store
Spatial 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	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

aws.amazon.com/dynamodb

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

www.stardog.com

www.tarantool.io

vitess.io

Technical documentation

docs.aws.amazon.com/dynamodb

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

docs.stardog.com

www.tarantool.io/en/doc

vitess.io/docs

Developer

Amazon

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Stardog-Union

The Linux Foundation, PlanetScale

Initial release

2012

1994

2010

2008

2013

Current release

18.1.40, May 2020

7.3.0, May 2020

2.10.0, May 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

commercial license available

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache Version 2.0, commercial licenses 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, Java, C++ (depending on the Berkeley DB edition)

Java

C and C++

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS
Windows

BSD
Linux
macOS

Docker
Linux
macOS

Data scheme

schema-free

schema-free and OWL/RDFS-schema support

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

Full-featured ANSI SQL support

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Open binary protocol

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions and aggregates, HTTP Server extensions in Java

Lua, C and SQL stored procedures

yes

proprietary syntax

Triggers

yes

by integration with AWS Lambda

yes

only for the SQL API

yes

via event handlers

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication in HA-Cluster

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency in HA-Cluster

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

relationships in graphs

yes

not for MyISAM storage engine

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

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 and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

Users with fine-grained authorization concept

no user groups or roles

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.