DBMS > Amazon Redshift vs. Apache Impala vs. Infobright vs. PlanetScale vs. XTDB

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Infobright vs. PlanetScale vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store

Secondary database models

Document store

Document store
Spatial 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.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

impala.apache.org

ignitetech.com/softwarelibrary/infobrightdb

planetscale.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

planetscale.com/docs

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Ignite Technologies Inc.; formerly InfoBright Inc.

PlanetScale

Juxt Ltd.

Initial release

2012

2013

2005

2020

2019

Current release

4.1.0, June 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

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

commercial

Open Source

MIT License

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++

Clojure

Server operating systems

hosted

Linux

Linux
Windows

Docker
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Users with fine-grained authorization concept

no user groups or roles

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.