DBMS > Amazon CloudSearch vs. Google BigQuery vs. H2 vs. HyperSQL vs. PouchDB

System Properties Comparison Amazon CloudSearch vs. Google BigQuery vs. H2 vs. HyperSQL vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Large scale data warehouse service with append-only tables

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Search engine

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

aws.amazon.com/cloudsearch

cloud.google.com/bigquery

www.h2database.com

hsqldb.org

pouchdb.com

Technical documentation

docs.aws.amazon.com/cloudsearch

cloud.google.com/bigquery/docs

www.h2database.com/html/main.html

hsqldb.org/web/hsqlDocsFrame.html

pouchdb.com/guides

Developer

Amazon

Google

Thomas Mueller

Apache Software Foundation

Initial release

2012

2010

2005

2001

2012

Current release

2.2.220, July 2023

2.7.2, June 2023

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

based on BSD license

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

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

via views

SQL

Support of SQL

yes

APIs and other access methods

HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

HTTP API

JDBC via HTTP
JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

All languages supporting JDBC/ODBC
Java

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java Stored Procedures and User-Defined Functions

Java, SQL

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

With clustering: 2 database servers on different computers operate on identical copies of a database

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

authentication via encrypted signatures

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.