DBMS > Amazon Redshift vs. Blazegraph vs. FatDB vs. KairosDB vs. Quasardb

System Properties Comparison Amazon Redshift vs. Blazegraph vs. FatDB vs. KairosDB vs. Quasardb

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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the 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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Distributed Time Series DBMS based on Cassandra or H2

Distributed, high-performance timeseries database

Primary database model

Relational DBMS

Graph DBMS
RDF store

Document store
Key-value store

Time Series 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	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

aws.amazon.com/redshift

blazegraph.com

github.com/kairosdb/kairosdb

quasar.ai

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

kairosdb.github.io

doc.quasar.ai/master

Developer

Amazon (based on PostgreSQL)

Blazegraph

FatCloud

quasardb

Initial release

2012

2006

2012

2013

2009

Current release

2.1.5, March 2019

1.2.2, November 2018

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

commercial

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Windows

Linux
OS X
Windows

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

does not fully support an SQL-standard

SPARQL is used as query language

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Graphite protocol
HTTP REST
Telnet API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

by using LevelDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

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

Can implement custom security layer via applications

simple password-based access control

Cryptographically strong user authentication and audit trail

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.