DBMS > Amazon DynamoDB vs. Dgraph vs. EDB Postgres vs. Tarantool vs. Tibero

System Properties Comparison Amazon DynamoDB vs. Dgraph vs. EDB Postgres vs. Tarantool vs. Tibero

Editorial information provided by DB-Engines

Name

Description

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

Distributed and scalable native Graph DBMS

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store
Key-value store

Graph DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	1.91
Rank	#130	Overall
	#60	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

aws.amazon.com/dynamodb

dgraph.io

www.enterprisedb.com

www.tarantool.io

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/dynamodb

dgraph.io/docs

www.enterprisedb.com/docs

www.tarantool.io/en/doc

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon

Dgraph Labs, Inc.

EnterpriseDB

TmaxSoft

Initial release

2012

2016

2005

2008

2003

Current release

14, December 2021

2.10.0, May 2022

6, April 2015

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

commercial

BSD for PostgreSQL-components

Open Source

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

commercial

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 and C++

C and Assembler

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

BSD
Linux
macOS

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard with numerous extensions

Full-featured ANSI SQL support

yes

APIs and other access methods

RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Open binary protocol

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Lua, C and SQL stored procedures

Persistent Stored Procedure (PSM)

Triggers

yes

by integration with AWS Lambda

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning

by hash, list or range

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

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

Multi-source replication

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

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

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

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes, cooperative multitasking

yes

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, full featured in-memory storage engine with persistence

planned for next version

User concepts

Access control

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

Planned for future releases

fine grained access rights according to SQL-standard

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.