DBMS > Ehcache vs. GeoMesa vs. Heroic vs. SiteWhere vs. YDB

System Properties Comparison Ehcache vs. GeoMesa vs. Heroic vs. SiteWhere vs. YDB

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

M2M integration platform for persisting/querying time series data

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Key-value store

Spatial DBMS

Time Series DBMS

Document store
Relational 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	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

www.ehcache.org

www.geomesa.org

github.com/spotify/heroic

github.com/sitewhere/sitewhere

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

www.ehcache.org/documentation

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

spotify.github.io/heroic

sitewhere1.sitewhere.io/index.html

ydb.tech/en/docs

Developer

Terracotta Inc, owned by Software AG

CCRi and others

Spotify

SiteWhere

Yandex

Initial release

2009

2014

2010

2019

Current release

3.10.0, March 2022

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.0

Open Source

Apache 2.0; commercial license available

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

Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

schema-free

predefined scheme

Flexible Schema (defined schema, partial schema, 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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language (YQL)

APIs and other access methods

JCache

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

HTTP REST

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

Java

Go
Java
JavaScript (Node.js)
PHP
Python

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

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

depending on storage layer

yes

selectable replication factor

based on HBase

Active-passive shard 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

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

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

Users with fine-grained authorization concept

Access rights defined for Yandex Cloud users

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

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Personal Data Protection Service Initiates Probe into Yandex.Go App’s Data Processing
10 August 2023, Civil Georgia

Russian Court Sues Yandex CEO For LGBT Propaganda Case
3 January 2024, VOI.ID

Data leak from Russian delivery app shows dining habits of the secret police
3 April 2022, The Verge

Yandex code leak: Why hack of ‘Russian Google’s’ ranking factors has spooked the SEO industry
1 February 2023, The Indian Express

Yandex Food's Data Gets Leaked, Russian Secret Service Habits Are Revealed, Including Putin's Lover's House
4 April 2022, VOI English

provided by Google News

Share this page