DBMS > Amazon DynamoDB vs. Dgraph vs. PlanetScale vs. Teradata Aster vs. TigerGraph

System Properties Comparison Amazon DynamoDB vs. Dgraph vs. PlanetScale vs. Teradata Aster vs. TigerGraph

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

Distributed and scalable native Graph DBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Platform for big data analytics on multistructured data sources and types

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Document store
Key-value store

Graph DBMS

Relational DBMS

Graph DBMS

Secondary database models

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.59
Rank	#151	Overall
	#70	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/dynamodb

dgraph.io

planetscale.com

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/dynamodb

dgraph.io/docs

planetscale.com/docs

docs.tigergraph.com

Developer

Amazon

Dgraph Labs, Inc.

PlanetScale

Teradata

Initial release

2012

2016

2020

2005

2017

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

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

Server operating systems

hosted

Linux
OS X
Windows

Docker
Linux
macOS

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

Typing

predefined data types such as float or date

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (GSQL)

APIs and other access methods

RESTful HTTP API

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

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET
JDBC
ODBC
OLE DB

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
Go
Java
JavaScript (Node.js)
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

C
C#
C++
Java
Python
R

C++
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

R packages

yes

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

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

SQL Map-Reduce Framework

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

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 shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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)

Planned for future releases

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Role-based access control

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.