DBMS > Amazon Redshift vs. Dgraph vs. EsgynDB vs. HarperDB vs. HyperSQL

System Properties Comparison Amazon Redshift vs. Dgraph vs. EsgynDB vs. HarperDB vs. HyperSQL

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

docs.harperdb.io/docs

hsqldb.org/web/hsqlDocsFrame.html

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

Esgyn

HarperDB

Initial release

2012

2016

2015

2017

2001

Current release

3.1, August 2021

2.7.2, June 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free community edition available

Open Source

based on BSD license

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

Node.js

Java

Server operating systems

hosted

Linux
OS X
Windows

Linux

Linux
OS X

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Data scheme

yes

schema-free

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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 data manipulation statements

yes

APIs and other access methods

JDBC
ODBC

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

ADO.NET
JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HTTP API

JDBC via HTTP
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

All languages supporting JDBC/ODBC
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

Custom Functions

since release 3.1

Java, SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes

the nodes on which a table resides can be defined

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Planned for future releases

fine grained access rights according to SQL-standard

Access rights for users and roles

fine grained access rights according to SQL-standard

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.