DBMS > Apache Impala vs. HEAVY.AI vs. LeanXcale vs. MySQL

System Properties Comparison Apache Impala vs. HEAVY.AI vs. LeanXcale vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Widely used open source RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Spatial DBMS

Document store
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

impala.apache.org

github.com/heavyai/heavydb
www.heavy.ai

www.leanxcale.com

www.mysql.com

Technical documentation

impala.apache.org/impala-docs.html

docs.heavy.ai

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

HEAVY.AI, Inc.

LeanXcale

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2016

2015

1995

Current release

4.1.0, June 2022

5.10, January 2022

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; enterprise edition available

commercial

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++

C++ and CUDA

C and C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

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

yes

through Apache Derby

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/Thrift
Python

C
Java
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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

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

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

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

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.