DBMS > Amazon Redshift vs. Apache Phoenix vs. Dgraph vs. JanusGraph vs. TigerGraph

System Properties Comparison Amazon Redshift vs. Apache Phoenix vs. Dgraph vs. JanusGraph vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A scale-out RDBMS with evolutionary schema built on Apache HBase

Distributed and scalable native Graph DBMS

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Primary database model

Relational DBMS

Graph DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Dgraph Labs, Inc.

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2012

2014

2016

2017

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

0.6.3, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

Java

C++

Server operating systems

hosted

Linux
Unix
Windows

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

JDBC

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

Clojure
Java
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Synchronous replication via Raft

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

yes

Relationships 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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Planned for future releases

User authentification and security via Rexster Graph Server

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.