DBMS > Amazon Redshift vs. GridDB vs. Hypertable vs. QuestDB

System Properties Comparison Amazon Redshift vs. GridDB vs. Hypertable vs. QuestDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Scalable in-memory time series database optimized for IoT and Big Data

An open source BigTable implementation based on distributed file systems such as Hadoop

A high performance open source SQL database for time series data

Primary database model

Secondary database models

Key-value store
Relational DBMS

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	2.70
Rank	#105	Overall
	#8	Time Series DBMS

Website

aws.amazon.com/redshift

griddb.net

questdb.io

Technical documentation

docs.aws.amazon.com/redshift

docs.griddb.net

questdb.io/docs

Developer

Amazon (based on PostgreSQL)

Toshiba Corporation

Hypertable Inc.

QuestDB Technology Inc

Initial release

2012

2013

2009

2014

Current release

5.1, August 2022

0.9.8.11, March 2016

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

GNU version 3. Commercial license available

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

C++

Java (Zero-GC), C++, Rust

Server operating systems

hosted

Linux

Linux
OS X
Windows

an inofficial Windows port is available

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

yes

restricted

only exact value or prefix value scans

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL92, SQL-like TQL (Toshiba Query Language)

SQL with time-series extensions

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

C++ API
Thrift

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C++
Java
Perl
PHP
Python
Ruby

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor on file system level

Source-replica replication with eventual consistency

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

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

ACID at container level

ACID for single-table writes

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

through memory mapped files

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Fluid real-time dashboards with Grafana and QuestDB
11 June 2024

QuestDB 8.0: Major Release
23 May 2024

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

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.