DBMS > BigObject vs. Ehcache vs. GeoMesa vs. HEAVY.AI vs. Heroic

System Properties Comparison BigObject vs. Ehcache vs. GeoMesa vs. HEAVY.AI vs. Heroic

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A widely adopted Java cache with tiered storage options

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Secondary database models

Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

bigobject.io

www.ehcache.org

www.geomesa.org

github.com/heavyai/heavydb
www.heavy.ai

github.com/spotify/heroic

Technical documentation

docs.bigobject.io

www.ehcache.org/documentation

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

docs.heavy.ai

spotify.github.io/heroic

Developer

BigObject, Inc.

Terracotta Inc, owned by Software AG

CCRi and others

HEAVY.AI, Inc.

Spotify

Initial release

2015

2009

2014

2016

2014

Current release

3.10.0, March 2022

4.0.5, February 2024

5.10, January 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

Open Source

Apache Version 2; enterprise edition available

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

C++ and CUDA

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

Linux

Data scheme

yes

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.

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JCache

JDBC
ODBC
Thrift
Vega

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

Supported programming languages

Java

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

Lua

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

depending on storage layer

Sharding

Round robin

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

depending on storage layer

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

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

fine grained access rights according to SQL-standard

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

Big Data Analytics: A Game Changer for Infrastructure
13 July 2023, Spiceworks News and Insights

HEAVY.AI Launches HEAVY 7.0, Introducing Real-Time Machine Learning Capabilities
19 April 2023, Business Wire

Making the most of geospatial intelligence
14 April 2023, InfoWorld

OmniSci Gets HEAVY New Name and New CEO
1 March 2022, Datanami

The insideBIGDATA IMPACT 50 List for Q4 2023
11 October 2023, insideBIGDATA

provided by Google News

Share this page