DBMS > Amazon Redshift vs. Blazegraph vs. etcd vs. IBM Cloudant vs. MonetDB

System Properties Comparison Amazon Redshift vs. Blazegraph vs. etcd vs. IBM Cloudant vs. MonetDB

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 distributed reliable key-value store

Database as a Service offering based on Apache CouchDB

A relational database management system that stores data in columns

Primary database model

Secondary database models

Document store
Spatial 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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Website

aws.amazon.com/redshift

blazegraph.com

etcd.io
github.com/etcd-io/etcd

www.ibm.com/products/cloudant

www.monetdb.org

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

cloud.ibm.com/docs/Cloudant

www.monetdb.org/Documentation

Developer

Amazon (based on PostgreSQL)

Blazegraph

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

MonetDB BV

Initial release

2012

2006

2010

2004

Current release

2.1.5, March 2019

3.4, August 2019

Dec2023 (11.49), December 2023

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla Public License 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

Erlang

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
Windows

experimental

hosted

FreeBSD
Linux
OS X
Solaris
Windows

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

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

gRPC
JSON over HTTP

RESTful HTTP/JSON API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

View functions (Map-Reduce) in JavaScript

yes, in SQL, C, R

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication
Source-replica replication

none

Source-replica replication available in experimental status

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

Eventual Consistency

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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)

Access rights for users can be defined per database

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.