DBMS > Amazon Redshift vs. Greenplum vs. InfinityDB vs. IRONdb vs. MaxDB

System Properties Comparison Amazon Redshift vs. Greenplum vs. InfinityDB vs. IRONdb vs. MaxDB

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A Java embedded Key-Value Store which extends the Java Map interface

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Secondary database models

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	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Website

aws.amazon.com/redshift

greenplum.org

boilerbay.com

www.circonus.com/solutions/time-series-database/

maxdb.sap.com

Technical documentation

docs.aws.amazon.com/redshift

docs.greenplum.org

boilerbay.com/infinitydb/manual

docs.circonus.com/irondb/category/getting-started

maxdb.sap.com/documentation

Developer

Amazon (based on PostgreSQL)

Pivotal Software Inc.

Boiler Bay Inc.

Circonus LLC.

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

Initial release

2012

2005

2002

2017

1984

Current release

7.0.0, September 2023

4.0

V0.10.20, January 2018

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Limited community edition free

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

Java

C and C++

C++

Server operating systems

hosted

Linux

All OS with a Java VM

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

schema-free

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes

text, numeric, histograms

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

since Version 4.2

Secondary indexes

restricted

yes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

JDBC
ODBC

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

HTTP API

ADO.NET
JDBC
ODBC
WebDAV

Supported programming languages

All languages supporting JDBC/ODBC

C
Java
Perl
Python
R

Java

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

configurable replication factor, datacenter aware

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

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.