DBMS > Amazon Redshift vs. Blueflood vs. Geode vs. Hawkular Metrics vs. Infobright

System Properties Comparison Amazon Redshift vs. Blueflood vs. Geode vs. Hawkular Metrics vs. Infobright

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Scalable TimeSeries DBMS based on Cassandra

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Website

aws.amazon.com/redshift

blueflood.io

geode.apache.org

www.hawkular.org

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

docs.aws.amazon.com/redshift

github.com/rax-maas/blueflood/wiki

geode.apache.org/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

Developer

Amazon (based on PostgreSQL)

Rackspace

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Community supported by Red Hat

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2012

2013

2002

2014

2005

Current release

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Server operating systems

hosted

Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

predefined scheme

schema-free

yes

Typing

predefined data types such as float or date

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

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC

HTTP REST

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
All JVM based languages
C++
Groovy
Java
Scala

Go
Java
Python
Ruby

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Cache Event Listeners

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Multi-source replication

selectable replication factor

based on Cassandra

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes, on a single node

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

Access rights per client and object definable

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.