DBMS > Amazon Redshift vs. Apache Impala vs. Infobright vs. Rockset vs. Vitess

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Infobright vs. Rockset vs. Vitess

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

Relational DBMS
Search engine

Document store
Spatial DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	0.88
Rank	#198	Overall
	#92	Relational DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

aws.amazon.com/redshift

impala.apache.org

ignitetech.com/softwarelibrary/infobrightdb

rockset.com

vitess.io

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

docs.rockset.com

vitess.io/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Ignite Technologies Inc.; formerly InfoBright Inc.

Rockset

The Linux Foundation, PlanetScale

Initial release

2012

2013

2005

2019

2013

Current release

4.1.0, June 2022

15.0.2, December 2022

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

Apache Version 2.0, commercial licenses available

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

Server operating systems

hosted

Linux

Linux
Windows

hosted

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

restricted

yes

Knowledge Grid Technology used instead

all fields are automatically indexed

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

Read-only SQL queries, including JOINs

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

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

Go
Java
JavaScript (Node.js)
Python

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

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

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

yes

Multi-source replication
Source-replica replication

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

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users and organizations can be defined via Rockset console

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.