DBMS > Apache Impala vs. Datomic vs. Ignite vs. MySQL

System Properties Comparison Apache Impala vs. Datomic vs. Ignite vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

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.76
Rank	#145	Overall
	#66	Relational DBMS

Score	3.64
Rank	#89	Overall
	#13	Key-value stores
	#48	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

docs.datomic.com

apacheignite.readme.io/docs

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Cognitect

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2012

2015

1995

Current release

4.1.0, June 2022

1.0.6735, June 2023

Apache Ignite 2.6

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

Open Source

Apache 2.0

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, Clojure

C++, Java, .Net

C and C++

Server operating systems

Linux

All OS with a Java VM

Linux
OS X
Solaris
Windows

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

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C#
C++
Java
PHP
Python
Ruby
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

Transaction Functions

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax

Triggers

By using transaction functions

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

But extensive use of caching in the application peers

yes (replicated cache)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes (compute grid and hadoop accelerator)

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Security Hooks for custom implementations

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.