DBMS > Amazon Aurora vs. EXASOL vs. Hazelcast vs. Rockset vs. Snowflake

System Properties Comparison Amazon Aurora vs. EXASOL vs. Hazelcast vs. Rockset 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.

A widely adopted in-memory data grid

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Relational DBMS
Search engine

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	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/rds/aurora

Technical documentation

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

www.exasol.com/resources

hazelcast.org/imdg/docs

docs.rockset.com

docs.snowflake.net/manuals/index.html

Developer

Amazon

Exasol

Hazelcast

Rockset

Snowflake Computing Inc.

Initial release

2015

2000

2008

2019

2014

Current release

5.3.6, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses 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

Java

C++

Server operating systems

hosted

All OS with a Java VM

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

Read-only SQL queries, including JOINs

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP REST

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
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Role-based access control

Access rights for users and organizations can be defined via Rockset console

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.