DBMS > Amazon Redshift vs. BigObject vs. CouchDB vs. Greenplum

System Properties Comparison Amazon Redshift vs. BigObject vs. CouchDB 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

Analytic DBMS for real-time computations and queries

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

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

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.13
Rank	#342	Overall
	#150	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	9.23
Rank	#47	Overall
	#30	Relational DBMS

Website

aws.amazon.com/redshift

bigobject.io

couchdb.apache.org

greenplum.org

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

docs.couchdb.org/en/stable

docs.greenplum.org

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Apache Software Foundation

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

Pivotal Software Inc.

Initial release

2012

2015

2005

Current release

3.3.3, December 2023

7.0.0, September 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache version 2

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

Erlang

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Android
BSD
Linux
OS X
Solaris
Windows

Linux

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

since Version 4.2

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

fluentd
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

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

C
Java
Perl
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

improved architecture with release 2.0

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

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 can be defined per database

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.