DBMS > Amazon Redshift vs. GigaSpaces vs. Hawkular Metrics vs. KairosDB vs. Prometheus

System Properties Comparison Amazon Redshift vs. GigaSpaces vs. Hawkular Metrics vs. KairosDB vs. Prometheus

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

Distributed Time Series DBMS based on Cassandra or H2

Open-source Time Series DBMS and monitoring system

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Time Series DBMS

Secondary database models

Graph DBMS
Search engine

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

aws.amazon.com/redshift

www.gigaspaces.com

www.hawkular.org

github.com/kairosdb/kairosdb

prometheus.io

Technical documentation

docs.aws.amazon.com/redshift

docs.gigaspaces.com/latest/landing.html

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

kairosdb.github.io

prometheus.io/docs

Developer

Amazon (based on PostgreSQL)

Gigaspaces Technologies

Community supported by Red Hat

Initial release

2012

2000

2014

2013

2015

Current release

15.5, September 2020

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache 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, C++, .Net

Java

Server operating systems

hosted

Linux
macOS
Solaris
Windows

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

XML can be used for describing objects metadata

Import of XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-99 for query and DML statements

APIs and other access methods

JDBC
ODBC

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

HTTP REST

Graphite protocol
HTTP REST
Telnet API

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C++
Java
Python
Scala

Go
Java
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes, event driven architecture

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

selectable replication factor

based on Cassandra

selectable replication factor

based on Cassandra

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

none

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

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

Role-based access control

simple password-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.