DBMS > Ehcache vs. GeoMesa vs. Heroic vs. Ingres vs. OrigoDB

System Properties Comparison Ehcache vs. GeoMesa vs. Heroic vs. Ingres vs. OrigoDB

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.

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

Well established RDBMS

A fully ACID in-memory object graph database

Primary database model

Document store
Object oriented DBMS

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

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

www.ehcache.org

www.geomesa.org

github.com/spotify/heroic

www.actian.com/databases/ingres

origodb.com

Technical documentation

www.ehcache.org/documentation

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

spotify.github.io/heroic

docs.actian.com/ingres

origodb.com/docs

Developer

Terracotta Inc, owned by Software AG

CCRi and others

Spotify

Actian Corporation

Robert Friberg et al

Initial release

2009

2014

1974

originally developed at University Berkely in early 1970s

2009

under the name LiveDB

Current release

3.10.0, March 2022

4.0.5, February 2024

11.2, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Open Source

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

Server operating systems

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

but tools for importing/exporting data from/to XML-files available

can be achieved using .NET

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

JCache

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

.NET Client API
HTTP API
LINQ

Supported programming languages

Java

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

Cache Event Listeners

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

depending on storage layer

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

depending on storage layer

yes

Ingres Replicator

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

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

MVCC

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

Write ahead log

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

fine grained access rights according to SQL-standard

Role based authorization

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

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.com

provided by Google News

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

provided by Google News

Share this page