DBMS > Amazon Redshift vs. BigObject vs. Greenplum vs. Riak KV vs. Valentina Server

System Properties Comparison Amazon Redshift vs. BigObject vs. Greenplum vs. Riak KV vs. Valentina Server

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

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.

Distributed, fault tolerant key-value store

Object-relational database and reports server

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

aws.amazon.com/redshift

bigobject.io

greenplum.org

www.valentina-db.net

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

docs.greenplum.org

www.tiot.jp/riak-docs/riak/kv/latest

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Pivotal Software Inc.

OpenSource, formerly Basho Technologies

Paradigma Software

Initial release

2012

2015

2005

2009

1999

Current release

7.0.0, September 2023

3.2.0, December 2022

5.7.5

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

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)

Linux

Linux
OS X

Linux
OS X
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

since Version 4.2

Secondary indexes

restricted

yes

restricted

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

JDBC
ODBC

HTTP API
Native Erlang Interface

ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C
Java
Perl
Python
R

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

links between data sets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

yes, using Riak Security

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.