DBMS > Amazon Aurora vs. EXASOL vs. Hazelcast vs. OrigoDB vs. RocksDB

System Properties Comparison Amazon Aurora vs. EXASOL vs. Hazelcast vs. OrigoDB vs. RocksDB

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 fully ACID in-memory object graph database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Key-value store

Document store
Object oriented DBMS

Key-value 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	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.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

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

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Amazon

Exasol

Hazelcast

Robert Friberg et al

Facebook, Inc.

Initial release

2015

2000

2008

2009

under the name LiveDB

2013

Current release

5.3.6, November 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

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

Linux
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
HTTP API
LINQ

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

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Replicated Map

Source-replica replication

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

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.