DBMS > atoti vs. Ehcache vs. GeoMesa vs. GridGain vs. Heroic

System Properties Comparison atoti vs. Ehcache vs. GeoMesa vs. GridGain vs. Heroic

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

A widely adopted Java cache with tiered storage options

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Primary database model

Object oriented DBMS

Key-value store

Spatial DBMS

Key-value store
Relational DBMS

Time Series DBMS

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

Score	0.56
Rank	#245	Overall
	#10	Object oriented DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

github.com/spotify/heroic

Technical documentation

docs.atoti.io

www.ehcache.org/documentation

www.geomesa.org/documentation/stable/user/index.html

www.gridgain.com/docs/index.html

spotify.github.io/heroic

Developer

ActiveViam

Terracotta Inc, owned by Software AG

CCRi and others

GridGain Systems, Inc.

Spotify

Initial release

2009

2014

2007

2014

Current release

3.10.0, March 2022

4.0.5, February 2024

GridGain 8.5.1

License

Commercial or Open Source

commercial

free versions available

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

commercial

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

Scala

Java, C++, .Net

Java

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

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

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

Multidimensional Expressions (MDX)

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

APIs and other access methods

JCache

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

Java

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Python

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

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

Sharding

by using Terracotta Server

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

depending on storage layer

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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, multi-version concurrency control (MVCC)

yes

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Best use of cloud: ActiveViam
28 November 2023, Risk.net

FRTB product of the year: ActiveViam
28 November 2023, Risk.net

provided by Google News

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

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

provided by Google News

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

GridGain to Sponsor and Speak at Three Key Industry Events in May 2024
6 May 2024, Martechcube

GridGain's 2023 Growth Positions Company for Strong 2024
25 January 2024, Datanami

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

GridGain Named in the 2023 Gartner® Market Guide for Event Stream Processing
22 August 2023, GlobeNewswire

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page