DBMS > Amazon Redshift vs. Blazegraph vs. Cachelot.io vs. CouchDB

System Properties Comparison Amazon Redshift vs. Blazegraph vs. Cachelot.io vs. CouchDB

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.

In-memory caching system

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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	0.00
Rank	#396	Overall
	#64	Key-value stores

Score	10.26
Rank	#45	Overall
	#7	Document stores

Website

aws.amazon.com/redshift

blazegraph.com

cachelot.io

couchdb.apache.org

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

docs.couchdb.org/en/stable

Developer

Amazon (based on PostgreSQL)

Blazegraph

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Initial release

2012

2006

2015

2005

Current release

2.1.5, March 2019

3.3.3, December 2023

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

Simplified BSD License

Open Source

Apache version 2

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

Erlang

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X

Android
BSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

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

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SPARQL is used as query language

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Memcached protocol

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in Python

yes

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

improved architecture with release 2.0

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

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

none

Eventual 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

atomic operations within a single document possible

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

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.