DBMS > Amazon Redshift vs. AnzoGraph DB vs. Dgraph vs. TerarkDB

System Properties Comparison Amazon Redshift vs. AnzoGraph DB vs. Dgraph vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

Distributed and scalable native Graph DBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

cambridgesemantics.com/anzograph

dgraph.io

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

dgraph.io/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Cambridge Semantics

Dgraph Labs, Inc.

ByteDance, originally Terark

Initial release

2012

2018

2016

Current release

2.3, January 2021

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache 2.0

commercial

restricted open source version 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

Linux
OS X
Windows

Data scheme

yes

Schema-free and OWL/RDFS-schema support

schema-free

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SPARQL and SPARQL* as primary query language. Cypher preview.

APIs and other access methods

JDBC
ODBC

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

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

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
Python

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

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions and aggregates

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication in MPP-Cluster

Synchronous replication via Raft

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

not needed in graphs

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

fine grained access rights according to SQL-standard

Access rights for users and roles

Planned for future releases

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.