DBMS > Amazon Redshift vs. Apache Impala vs. Microsoft Azure Table Storage vs. VictoriaMetrics vs. XTDB

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Microsoft Azure Table Storage vs. VictoriaMetrics 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

A Wide Column Store for rapid development using massive semi-structured datasets

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

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

Primary database model

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

impala.apache.org

azure.microsoft.com/en-us/services/storage/tables

victoriametrics.com

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

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Microsoft

VictoriaMetrics

Juxt Ltd.

Initial release

2012

2013

2012

2018

2019

Current release

4.1.0, June 2022

v1.91, May 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2.0

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

hosted

FreeBSD
Linux
macOS
OpenBSD

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Synchronous 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

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

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

Access rights based on private key authentication or shared access signatures

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.