DBMS > Amazon Redshift vs. Apache Impala vs. CouchDB vs. MaxDB vs. PostGIS

System Properties Comparison Amazon Redshift vs. Apache Impala vs. CouchDB vs. MaxDB vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A robust and reliable RDBMS optimized to run all major SAP solutions

Spatial extension of PostgreSQL

Primary database model

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

Relational DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	2.65
Rank	#111	Overall
	#55	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

docs.couchdb.org/en/stable

maxdb.sap.com/documentation

postgis.net/documentation

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

SAP, acquired from Software AG (Adabas-D) in 1997

Initial release

2012

2013

2005

1984

2005

Current release

4.1.0, June 2022

3.3.3, December 2023

7.9.10.12, February 2024

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache version 2

commercial

Limited community edition free

Open Source

GPL v2.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++

Erlang

C++

Server operating systems

hosted

Linux

Android
BSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

restricted

yes

via views

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
WebDAV

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

View functions in JavaScript

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication

yes

based on PostgreSQL

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

yes

based on PostgreSQL

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.