DBMS > Amazon Redshift vs. Blazegraph vs. MonetDB vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Blazegraph vs. MonetDB vs. TerminusDB

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 relational database management system that stores data in columns

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.77
Rank	#222	Overall
	#20	Graph DBMS
	#8	RDF stores

Score	1.72
Rank	#148	Overall
	#68	Relational DBMS

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

aws.amazon.com/redshift

blazegraph.com

www.monetdb.org

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

www.monetdb.org/Documentation

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Blazegraph

MonetDB BV

DataChemist Ltd.

Initial release

2012

2006

2004

2018

Current release

2.1.5, March 2019

Dec2023 (11.49), December 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

Mozilla Public License 2.0

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
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

SQL 2003 with some extensions

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

yes, in SQL, C, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication available in experimental status

Journaling Streams

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in Graphs

yes

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 journaling

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

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.