DBMS > GridGain vs. Hazelcast vs. Memcached vs. SQLite

System Properties Comparison GridGain vs. Hazelcast vs. Memcached vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

A widely adopted in-memory data grid

In-memory key-value store, originally intended for caching

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Key-value store

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.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	20.74
Rank	#32	Overall
	#4	Key-value stores

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

www.gridgain.com/docs/index.html

hazelcast.org/imdg/docs

github.com/memcached/memcached/wiki

www.sqlite.org/docs.html

Developer

GridGain Systems, Inc.

Hazelcast

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Dwayne Richard Hipp

Initial release

2007

2008

2003

2000

Current release

GridGain 8.5.1

5.3.6, November 2023

1.6.25, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD license

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++, .Net

Java

Server operating systems

Linux
OS X
Solaris
Windows

All OS with a Java VM

FreeBSD
Linux
OS X
Unix
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

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

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

JCache
JPA
Memcached protocol
RESTful HTTP API

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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 (compute grid and cache interceptors can be used instead)

yes

Event Listeners, Executor Services

Triggers

yes (cache interceptors and events)

yes

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 cache)

yes

Replicated Map

none

Repcached, a Memcached patch, provides this functionallity

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

Security Hooks for custom implementations

Role-based access control

yes

using SASL (Simple Authentication and Security Layer) protocol

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.