DBMS > Amazon DynamoDB vs. Dgraph vs. GridDB vs. Vitess

System Properties Comparison Amazon DynamoDB vs. Dgraph vs. GridDB vs. Vitess

Please select another system to include it in the comparison.

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

Scalable in-memory time series database optimized for IoT and Big Data

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Graph DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

aws.amazon.com/dynamodb

dgraph.io

griddb.net

vitess.io

Technical documentation

docs.aws.amazon.com/dynamodb

dgraph.io/docs

docs.griddb.net

vitess.io/docs

Developer

Amazon

Dgraph Labs, Inc.

Toshiba Corporation

The Linux Foundation, PlanetScale

Initial release

2012

2016

2013

Current release

5.1, August 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

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

Server operating systems

hosted

Linux
OS X
Windows

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

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

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

yes

proprietary syntax

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

Source-replica replication

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)

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

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 at container level

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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)

Planned for future releases

Access rights for users can be defined per database

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.