DBMS > Amazon Redshift vs. Apache HugeGraph

System Properties Comparison Amazon Redshift vs. Apache HugeGraph

Please select another system to include it in the comparison.

Our visitors often compare Amazon Redshift and Apache HugeGraph with PostgreSQL, Neo4j and DuckDB.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A fast-speed and highly-scalable Graph DBMS

Primary database model

Relational DBMS

Graph DBMS

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

Score	14.21
Rank	#38	Overall
	#23	Relational DBMS

Score	0.27
Rank	#295	Overall
	#24	Graph DBMS

Website

aws.amazon.com/redshift

github.com/hugegraph
hugegraph.apache.org

Technical documentation

docs.aws.amazon.com/redshift

hugegraph.apache.org/docs

Developer

Amazon (based on PostgreSQL)

Baidu

Initial release

2012

2018

Current release

0.9

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

Server operating systems

hosted

Linux
macOS
Unix

Data scheme

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

also supports composite index and range index

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
TinkerPop Gremlin

Supported programming languages

All languages supporting JDBC/ODBC

Groovy
Java
Python

Server-side scripts

Stored procedures

user defined functions

in Python

asynchronous Gremlin script jobs

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on used storage backend, e.g. Cassandra and HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

edges in graph

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

Users, roles and permissions

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.