DBMS > Ehcache vs. HarperDB vs. Heroic vs. OpenSearch

System Properties Comparison Ehcache vs. HarperDB vs. Heroic vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Secondary database models

Vector 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.55
Rank	#248	Overall
	#38	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

www.ehcache.org

www.harperdb.io

github.com/spotify/heroic

github.com/opensearch-project
opensearch.org

Technical documentation

www.ehcache.org/documentation

docs.harperdb.io/docs

spotify.github.io/heroic

opensearch.org/docs/latest

Developer

Terracotta Inc, owned by Software AG

HarperDB

Spotify

Amazon Web Services

Initial release

2009

2017

2014

2021

Current release

3.10.0, March 2022

3.1, August 2021

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

free community edition available

Open Source

Apache 2.0

Open Source

Apache Version 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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

Node.js

Java

Server operating systems

All OS with a Java VM

Linux
OS X

All OS with a Java VM

Data scheme

schema-free

dynamic schema

schema-free

Flexible type definitions. Once a type is defined, it is persistent

Typing

predefined data types such as float or date

yes

JSON data types

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

All search fields are automatically indexed

SQL

Support of SQL

SQL-like data manipulation statements

SQL-like query language

APIs and other access methods

JCache

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

Java API
RESTful HTTP/JSON API

Supported programming languages

Java

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

yes

Triggers

yes

Cache Event Listeners

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

the nodes on which a table resides can be defined

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes, using LMDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.