DBMS > Ehcache vs. EJDB vs. GridGain vs. Lovefield

System Properties Comparison Ehcache vs. EJDB vs. GridGain vs. Lovefield

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Key-value store

Document store

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

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

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Website

www.ehcache.org

github.com/Softmotions/ejdb

www.gridgain.com

google.github.io/lovefield

Technical documentation

www.ehcache.org/documentation

github.com/Softmotions/ejdb/blob/master/README.md

www.gridgain.com/docs/index.html

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Terracotta Inc, owned by Software AG

Softmotions

GridGain Systems, Inc.

Google

Initial release

2009

2012

2007

2014

Current release

3.10.0, March 2022

GridGain 8.5.1

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPLv2

commercial, open source

Open Source

Apache 2.0

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

Java, C++, .Net, Python, REST, SQL

JavaScript

Server operating systems

All OS with a Java VM

server-less

Linux
OS X
Solaris
Windows
z/OS

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

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

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JCache

in-process shared library

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

Supported programming languages

Java

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

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

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

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.

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

Jira Data Center user? Here's a critical Ehcache vulnerability to spoil your day
22 July 2021, The Register

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

How to partition Sonatype Nexus Repository: Targets, privileges, and roles
9 February 2010, Sonatype Blog

Implementing fallback with cached data
8 October 2018, O'Reilly Media

provided by Google News

GridGain Advances Its Unified Real-Time Data Platform to Help Enterprises Accelerate AI-Driven Data Processing
10 July 2024, insideBIGDATA

GridGain Sponsoring Strategic AI and Kafka Conferences This Month
4 September 2024, Datanami

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

Data Management News for the Week of July 12; Updates from Cloudera, HerculesAI, Oracle & More
12 July 2024, Solutions Review

Lalit Ahuja
13 August 2024, Forbes

provided by Google News

Share this page