DBMS > Ehcache vs. Elasticsearch vs. Ignite vs. SQLite

System Properties Comparison Ehcache vs. Elasticsearch vs. Ignite vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Key-value store

Search engine

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	132.83
Rank	#7	Overall
	#1	Search engines

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.ehcache.org

www.elastic.co/elasticsearch

ignite.apache.org

www.sqlite.org

Technical documentation

www.ehcache.org/documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

apacheignite.readme.io/docs

www.sqlite.org/docs.html

Developer

Terracotta Inc, owned by Software AG

Elastic

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2009

2010

2015

2000

Current release

3.10.0, March 2022

8.6, January 2023

Apache Ignite 2.6

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Elastic License

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

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

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

JCache

Java API
RESTful HTTP/JSON 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

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

yes

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

Triggers

yes

Cache Event Listeners

yes

by using the 'percolation' feature

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

Memcached and Redis integration

yes

User concepts

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.