DBMS > Amazon Redshift vs. Badger vs. Blueflood vs. Greenplum

System Properties Comparison Amazon Redshift vs. Badger vs. Blueflood vs. Greenplum

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Scalable TimeSeries DBMS based on Cassandra

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.

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Website

aws.amazon.com/redshift

github.com/dgraph-io/badger

blueflood.io

greenplum.org

Technical documentation

docs.aws.amazon.com/redshift

godoc.org/github.com/dgraph-io/badger

github.com/rax-maas/blueflood/wiki

docs.greenplum.org

Developer

Amazon (based on PostgreSQL)

DGraph Labs

Rackspace

Pivotal Software Inc.

Initial release

2012

2017

2013

2005

Current release

7.0.0, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache 2.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

Java

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

predefined scheme

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

since Version 4.2

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

HTTP REST

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C
Java
Perl
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

based on Cassandra

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

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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.