DBMS > Google BigQuery vs. Greenplum vs. InfinityDB vs. PouchDB

System Properties Comparison Google BigQuery vs. Greenplum vs. InfinityDB vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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.

A Java embedded Key-Value Store which extends the Java Map interface

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Key-value store

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

cloud.google.com/bigquery

greenplum.org

boilerbay.com

pouchdb.com

Technical documentation

cloud.google.com/bigquery/docs

docs.greenplum.org

boilerbay.com/infinitydb/manual

pouchdb.com/guides

Developer

Google

Pivotal Software Inc.

Boiler Bay Inc.

Apache Software Foundation

Initial release

2010

2005

2002

2012

Current release

7.0.0, September 2023

4.0

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Java

JavaScript

Server operating systems

hosted

Linux

All OS with a Java VM

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

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

via views

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Java
Perl
Python
R

Java

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Optimistic locking for transactions; no isolation for bulk loads

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.