DBMS > Amazon Redshift vs. Blazegraph vs. HEAVY.AI

System Properties Comparison Amazon Redshift vs. Blazegraph vs. HEAVY.AI

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

Large scale data warehouse service for use with business intelligence tools

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Primary database model

Relational DBMS

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	15.10
Rank	#38	Overall
	#23	Relational DBMS

Score	0.74
Rank	#219	Overall
	#19	Graph DBMS
	#9	RDF stores

Score	1.40
Rank	#153	Overall
	#71	Relational DBMS

Website

aws.amazon.com/redshift

blazegraph.com

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

docs.heavy.ai

Developer

Amazon (based on PostgreSQL)

Blazegraph

HEAVY.AI, Inc.

Initial release

2012

2006

2016

Current release

2.1.5, March 2019

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

Apache Version 2; enterprise edition 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

Java

C++ and CUDA

Server operating systems

hosted

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

RDF literal 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

SPARQL is used as query language

yes

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

JDBC
ODBC
Thrift
Vega

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

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

Security and Authentication via Web Application Container (Tomcat, Jetty)

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.