DBMS > Amazon Aurora vs. EXASOL vs. Google BigQuery vs. Hazelcast vs. PouchDB

System Properties Comparison Amazon Aurora vs. EXASOL vs. Google BigQuery vs. Hazelcast vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

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	8.50
Rank	#49	Overall
	#31	Relational DBMS

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	2.35
Rank	#116	Overall
	#22	Document stores

Website

aws.amazon.com/rds/aurora

www.exasol.com

cloud.google.com/bigquery

hazelcast.com

pouchdb.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

www.exasol.com/resources

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

pouchdb.com/guides

Developer

Amazon

Exasol

Google

Hazelcast

Apache Software Foundation

Initial release

2015

2000

2010

2008

2012

Current release

5.3.6, November 2023

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

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

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

ADO.NET
JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

JavaScript

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

View functions in JavaScript

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

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

Hadoop integration

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

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

Google Cloud Identity & Access Management (IAM)

Role-based access control

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.