DBMS > Apache Impala vs. EXASOL vs. GigaSpaces vs. MySQL

System Properties Comparison Apache Impala vs. EXASOL vs. GigaSpaces vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Graph DBMS
Search engine

Document store
Spatial DBMS

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

Score	0.91
Rank	#197	Overall
	#33	Document stores
	#7	Object oriented DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

www.exasol.com/resources

docs.gigaspaces.com/latest/landing.html

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Exasol

Gigaspaces Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2000

1995

Current release

4.1.0, June 2022

15.5, September 2020

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2; Commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java, C++, .Net

C and C++

Server operating systems

Linux

Linux
macOS
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

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.

XML can be used for describing objects metadata

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-99 for query and DML statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

.Net
C++
Java
Python
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

yes

proprietary syntax

Triggers

yes

yes, event driven architecture

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Hadoop integration

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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.