DBMS > Amazon Redshift vs. Apache Impala vs. Axibase vs. Infobright vs. TimescaleDB

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Axibase vs. Infobright vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Document store

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

aws.amazon.com/redshift

impala.apache.org

axibase.com/docs/atsd/finance

ignitetech.com/softwarelibrary/infobrightdb

www.timescale.com

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

docs.timescale.com

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Axibase Corporation

Ignite Technologies Inc.; formerly InfoBright Inc.

Timescale

Initial release

2012

2013

2005

2017

Current release

4.1.0, June 2022

15585

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

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

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

Server operating systems

hosted

Linux

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

Secondary indexes

restricted

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

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 Apache Sentry and Kerberos

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

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.