DBMS > Ehcache vs. GeoMesa

System Properties Comparison Ehcache vs. GeoMesa

Please select another system to include it in the comparison.

Our visitors often compare Ehcache and GeoMesa with PostgreSQL, MongoDB and Elasticsearch.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

Primary database model

Key-value store

Spatial DBMS

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

Score	4.26
Rank	#69	Overall
	#8	Key-value stores

Score	0.80
Rank	#208	Overall
	#4	Spatial DBMS

Website

www.ehcache.org

www.geomesa.org

Technical documentation

www.ehcache.org/documentation

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

Developer

Terracotta Inc, owned by Software AG

CCRi and others

Initial release

2009

2014

Current release

3.10.0, March 2022

5.0.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 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

Server operating systems

All OS with a Java VM

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

JCache

Supported programming languages

Java

Server-side scripts

Stored procedures

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

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

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

yes

depending on the DBMS used for storage

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

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

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

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

provided by Google News

Share this page