DBMS > Bangdb vs. Ehcache vs. GeoMesa vs. Heroic

System Properties Comparison Bangdb vs. Ehcache vs. GeoMesa vs. Heroic

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

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

Primary database model

Document store
Graph DBMS
Time Series DBMS

Key-value store

Spatial DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

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

Website

bangdb.com

www.ehcache.org

www.geomesa.org

github.com/spotify/heroic

Technical documentation

docs.bangdb.com

www.ehcache.org/documentation

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

spotify.github.io/heroic

Developer

Sachin Sinha, BangDB

Terracotta Inc, owned by Software AG

CCRi and others

Spotify

Initial release

2012

2009

2014

Current release

BangDB 2.0, October 2021

3.10.0, March 2022

4.0.5, February 2024

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

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

C, C++

Java

Scala

Java

Server operating systems

Linux

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

via Elasticsearch

SQL

Support of SQL

SQL like support with command line tool

APIs and other access methods

Proprietary protocol
RESTful HTTP API

JCache

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

Supported programming languages

C
C#
C++
Java
Python

Java

Server-side scripts

Stored procedures

Triggers

yes, Notifications (with Streaming only)

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

by using Terracotta Server

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

yes

by using Terracotta Server

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes

supports JTA and can work as an XA resource

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

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, run db with in-memory only mode

yes

depending on storage layer

User concepts

Access control

yes (enterprise version only)

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

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

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

provided by Google News

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

provided by Google News

Share this page