DBMS > Amazon Redshift vs. Hawkular Metrics vs. Infobright vs. OrigoDB vs. PostGIS

System Properties Comparison Amazon Redshift vs. Hawkular Metrics vs. Infobright vs. OrigoDB vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

A fully ACID in-memory object graph database

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Document store
Object oriented DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

aws.amazon.com/redshift

www.hawkular.org

ignitetech.com/softwarelibrary/infobrightdb

origodb.com

postgis.net

Technical documentation

docs.aws.amazon.com/redshift

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

origodb.com/docs

postgis.net/documentation

Developer

Amazon (based on PostgreSQL)

Community supported by Red Hat

Ignite Technologies Inc.; formerly InfoBright Inc.

Robert Friberg et al

Initial release

2012

2014

2005

2009

under the name LiveDB

2005

Current release

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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

Open Source

GPL v2.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

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

restricted

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

HTTP REST

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
Python
Ruby

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

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

Triggers

yes

via Hawkular Alerting

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

horizontal partitioning

client side managed; servers are not synchronized

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Source-replica replication

yes

based on PostgreSQL

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

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

depending on model

yes

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

Write ahead log

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

exploiting MySQL or PostgreSQL frontend capabilities

Role based authorization

yes

based on PostgreSQL

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.