DBMS > GridGain vs. Hazelcast vs. JaguarDB vs. Linter

System Properties Comparison GridGain vs. Hazelcast vs. JaguarDB vs. Linter

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

Performant, highly scalable DBMS for AI and IoT applications

RDBMS for high security requirements

Primary database model

Key-value store
Relational DBMS

Key-value store

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#14	Vector DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Website

Technical documentation

www.gridgain.com/docs/index.html

hazelcast.org/imdg/docs

www.jaguardb.com/support.html

Developer

GridGain Systems, Inc.

Hazelcast

DataJaguar, Inc.

relex.ru

Initial release

2007

2008

2015

1990

Current release

GridGain 8.5.1

5.3.6, November 2023

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL V3.0

commercial

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

C++

the server part. Clients available in other languages

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Data scheme

yes

schema-free

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

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

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

JDBC
ODBC

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

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

yes

Event Listeners, Executor Services

yes

proprietary syntax with the possibility to convert from PL/SQL

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

Multi-source replication

Source-replica replication

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

Eventual Consistency

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

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

rights management via user accounts

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks and Files

GridGain's 2023 Growth Positions Company for Strong 2024
24 January 2024, PR Newswire

GridGain Unified Real-Time Data Platform Version 8.9 Addresses Today's More Complex Real-Time Data Processing ...
12 October 2023, GlobeNewswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

provided by Google News

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast appoints Anthony Griffin as Chief Architect -
11 June 2024, Enterprise Times

Hazelcast Showcases Real-Time Data Platform at 2024 Gartner Summit
15 May 2024, Datanami

Real-Time Data Platform Hazelcast Introduces New Chief Technology Officer Adrian Soars
7 November 2023, Finovate

provided by Google News

Share this page