DBMS > Amazon Aurora vs. Coveo vs. EXASOL vs. Hazelcast vs. SAP HANA

System Properties Comparison Amazon Aurora vs. Coveo vs. EXASOL vs. Hazelcast vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

A widely adopted in-memory data grid

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

aws.amazon.com/rds/aurora

www.coveo.com

www.exasol.com

hazelcast.com

www.sap.com/products/hana.html

Technical documentation

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

docs.coveo.com

www.exasol.com/resources

hazelcast.org/imdg/docs

help.sap.com/hana

Developer

Amazon

Coveo

Exasol

Hazelcast

SAP

Initial release

2015

2012

2000

2008

2010

Current release

5.3.6, November 2023

2.0 SPS07 (April 4, 2023), April 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

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

Appliance or cloud-service

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

yes

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

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

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

C#
Java
JavaScript
Python

Java
Lua
Python
R

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

Server-side scripts

Stored procedures

yes

user defined functions

yes

Event Listeners, Executor Services

SQLScript, R

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

yes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

granular access controls, API key management, content filters

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

Role-based access control

yes

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.