DBMS > EXASOL vs. Hazelcast vs. Ignite vs. SQLite

System Properties Comparison EXASOL vs. Hazelcast vs. Ignite vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted in-memory data grid

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 embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

www.exasol.com/resources

hazelcast.org/imdg/docs

apacheignite.readme.io/docs

www.sqlite.org/docs.html

Developer

Exasol

Hazelcast

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2000

2008

2015

2000

Current release

5.3.6, November 2023

Apache Ignite 2.6

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Public Domain

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

Java

C++, Java, .Net

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

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

yes

SQL-92 is not fully supported

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
Lua
Python
R

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

C#
C++
Java
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

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

Triggers

yes

Events

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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 according to SQL-standard

Role-based access control

Security Hooks for custom implementations

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.