DBMS > Greenplum vs. IBM Cloudant vs. Riak TS vs. SiteWhere

System Properties Comparison Greenplum vs. IBM Cloudant vs. Riak TS vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Database as a Service offering based on Apache CouchDB

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

greenplum.org

www.ibm.com/products/cloudant

github.com/sitewhere/sitewhere

Technical documentation

docs.greenplum.org

cloud.ibm.com/docs/Cloudant

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

sitewhere1.sitewhere.io/index.html

Developer

Pivotal Software Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Open Source, formerly Basho Technologies

SiteWhere

Initial release

2005

2010

2015

2010

Current release

7.0.0, September 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Common Public Attribution License Version 1.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

Java

Server operating systems

Linux

hosted

Linux
OS X

Linux
OS X
Windows

Data scheme

yes

schema-free

predefined scheme

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

yes

restricted

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

HTTP REST

Supported programming languages

C
Java
Perl
Python
R

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

yes

View functions (Map-Reduce) in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

Users with fine-grained authorization concept

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

1. Introducing the Greenplum Database - Data Warehousing with Greenplum [Book]
6 December 2018, O'Reilly Media

VMware Greenplum on AWS: Parallel Postgres for Enterprise Analytics at Scale | Amazon Web Services
9 September 2019, AWS Blog

RSA: EMC integrates Hadoop with Greenplum database
26 February 2013, DatacenterDynamics

Greenplum 6 ventures outside the analytic box | ZDNET
19 March 2019, ZDNet

Greenplum 6 review: Jack of all trades, master of some
7 November 2019, InfoWorld

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page