DBMS > Amazon Redshift vs. Google Cloud Datastore vs. Hawkular Metrics vs. OpenEdge vs. Prometheus

System Properties Comparison Amazon Redshift vs. Google Cloud Datastore vs. Hawkular Metrics vs. OpenEdge vs. Prometheus

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Application development environment with integrated database management system

Open-source Time Series DBMS and monitoring system

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	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.08
Rank	#366	Overall
	#39	Time Series DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Website

aws.amazon.com/redshift

cloud.google.com/datastore

www.hawkular.org

www.progress.com/openedge

prometheus.io

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

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

documentation.progress.com/output/ua/OpenEdge_latest

prometheus.io/docs

Developer

Amazon (based on PostgreSQL)

Google

Community supported by Red Hat

Progress Software Corporation

Initial release

2012

2008

2014

1984

2015

Current release

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

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

Server operating systems

hosted

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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.

yes

Import of XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

yes

close to SQL 92

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST

JDBC
ODBC

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Go
Java
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

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

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

Source-replica replication

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users and groups

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.