DBMS > Amazon Redshift vs. BigchainDB vs. Geode vs. Google Cloud Datastore vs. PouchDB

System Properties Comparison Amazon Redshift vs. BigchainDB vs. Geode vs. Google Cloud Datastore vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

JavaScript DBMS with an API inspired by CouchDB

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

aws.amazon.com/redshift

www.bigchaindb.com

geode.apache.org

cloud.google.com/datastore

pouchdb.com

Technical documentation

docs.aws.amazon.com/redshift

bigchaindb.readthedocs.io/en/latest

geode.apache.org/docs

cloud.google.com/datastore/docs

pouchdb.com/guides

Developer

Amazon (based on PostgreSQL)

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Apache Software Foundation

Initial release

2012

2016

2002

2008

2012

Current release

1.1, February 2017

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

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

Python

Java

JavaScript

Server operating systems

hosted

Linux

All OS with a Java VM

the JDK (8 or later) is also required

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

restricted

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (OQL)

SQL-like query language (GQL)

APIs and other access methods

JDBC
ODBC

CLI Client
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

using Google App Engine

View functions in JavaScript

Triggers

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication

Multi-source replication using Paxos

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

yes, on a single node

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Access rights per client and object definable

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.