DBMS > Apache Impala vs. etcd vs. Hazelcast vs. SAP HANA

System Properties Comparison Apache Impala vs. etcd vs. Hazelcast vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A distributed reliable key-value store

A widely adopted in-memory data grid

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

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	7.64
Rank	#54	Overall
	#5	Key-value stores

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

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

impala.apache.org

etcd.io
github.com/etcd-io/etcd

hazelcast.com

www.sap.com/products/hana.html

Technical documentation

impala.apache.org/impala-docs.html

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

hazelcast.org/imdg/docs

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Hazelcast

SAP

Initial release

2013

2008

2010

Current release

4.1.0, June 2022

3.4, August 2019

5.3.6, November 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Cloud-based only

Only available as a cloud service

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

C++

Java

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

All OS with a Java VM

Appliance or cloud-service

Data scheme

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

SQL-like DML and DDL statements

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

gRPC
JSON over HTTP

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Event Listeners, Executor Services

SQLScript, R

Triggers

yes, watching key changes

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

Replicated Map

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.