DBMS > Ehcache vs. Heroic vs. RavenDB vs. RDF4J

System Properties Comparison Ehcache vs. Heroic vs. RavenDB vs. RDF4J

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

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	0.72
Rank	#222	Overall
	#9	RDF stores

Website

www.ehcache.org

github.com/spotify/heroic

ravendb.net

rdf4j.org

Technical documentation

www.ehcache.org/documentation

spotify.github.io/heroic

ravendb.net/docs

rdf4j.org/documentation

Developer

Terracotta Inc, owned by Software AG

Spotify

Hibernating Rhinos

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2009

2014

2010

2004

Current release

3.10.0, March 2022

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.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

Server operating systems

All OS with a Java VM

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

RDF Schemas

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 (RQL)

APIs and other access methods

JCache

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Java

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

Multi-source replication

none

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)

Eventual Consistency
Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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, Cluster-wide transaction available

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

in-memory storage is supported as well

In-memory capabilities

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

yes

User concepts

Access control

Authorization levels configured per client per database

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

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

How to partition Sonatype Nexus Repository: Targets, privileges, and roles
9 February 2010, Sonatype Blog

Implementing fallback with cached data
8 October 2018, O'Reilly Media

provided by Google News

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and Accelerate Growth
13 June 2023, PR Newswire

Get To Know: Oren Eini, CEO, RavenDB
22 October 2019, Intelligent CIO

RavenDB Adds Graph Queries
15 May 2019, Datanami

provided by Google News

Share this page