DBMS > Amazon Aurora vs. EXASOL vs. Google Cloud Datastore vs. HarperDB vs. Snowflake

System Properties Comparison Amazon Aurora vs. EXASOL vs. Google Cloud Datastore vs. HarperDB vs. Snowflake

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.

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/rds/aurora

www.exasol.com

cloud.google.com/datastore

www.harperdb.io

www.snowflake.com

Technical documentation

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

www.exasol.com/resources

cloud.google.com/datastore/docs

docs.harperdb.io/docs

docs.snowflake.net/manuals/index.html

Developer

Amazon

Exasol

Google

HarperDB

Snowflake Computing Inc.

Initial release

2015

2000

2008

2017

2014

Current release

3.1, August 2021

License

Commercial or Open Source

commercial

free community edition available

commercial

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

Node.js

Server operating systems

hosted

Linux
OS X

hosted

Data scheme

yes

schema-free

dynamic schema

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

yes, details here

yes

JSON data types

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GQL)

SQL-like data manipulation statements

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

CLI Client
JDBC
ODBC

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
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

using Google App Engine

Custom Functions

since release 3.1

user defined functions

Triggers

yes

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

A table resides as a whole on one (or more) nodes in a cluster

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

yes

the nodes on which a table resides can be defined

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.