DBMS > Google BigQuery vs. Hazelcast vs. Percona Server for MongoDB vs. PouchDB

System Properties Comparison Google BigQuery vs. Hazelcast vs. Percona Server for MongoDB 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

A widely adopted in-memory data grid

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Key-value store

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

cloud.google.com/bigquery

hazelcast.com

www.percona.com/mongodb/software/percona-server-for-mongodb

pouchdb.com

Technical documentation

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

docs.percona.com/percona-distribution-for-mongodb

pouchdb.com/guides

Developer

Google

Hazelcast

Percona

Apache Software Foundation

Initial release

2010

2008

2015

2012

Current release

5.3.6, November 2023

3.4.10-2.10, November 2017

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL Version 2

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

C++

JavaScript

Server operating systems

hosted

All OS with a Java VM

Linux

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

Data scheme

yes

schema-free

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

the object must implement a serialization strategy

Secondary indexes

yes

via views

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

proprietary protocol using JSON

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

JavaScript

View functions in JavaScript

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

one or two-phase-commit; repeatable reads; read commited

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

via In-Memory Engine

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

Access rights for users and roles

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.