DBMS > Apache Impala vs. Geode vs. HyperSQL vs. MySQL

System Properties Comparison Apache Impala vs. Geode vs. HyperSQL vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Widely used open source RDBMS

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	3.90
Rank	#85	Overall
	#46	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

geode.apache.org/docs

hsqldb.org/web/hsqlDocsFrame.html

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2002

2001

1995

Current release

4.1.0, June 2022

1.1, February 2017

2.7.2, June 2023

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

based on BSD license

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Java

C and C++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (OQL)

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
All JVM based languages
C++
Groovy
Java
Scala

All languages supporting JDBC/ODBC
Java

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

Java, SQL

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

yes, on a single node

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 per client and object definable

fine grained access rights according to SQL-standard

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.