DBMS > Amazon Redshift vs. Blazegraph vs. Sqrrl vs. TigerGraph

System Properties Comparison Amazon Redshift vs. Blazegraph vs. Sqrrl vs. TigerGraph

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

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.

Adaptable, secure NoSQL built on Apache Accumulo

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

Primary database model

Relational DBMS

Graph DBMS
RDF store

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

blazegraph.com

sqrrl.com

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Blazegraph

Amazon

originally Sqrrl Data, Inc.

Initial release

2012

2006

2012

2017

Current release

2.1.5, March 2019

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

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

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

Atomic updates per row, document, or graph entity

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)

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.