DBMS > Ehcache vs. Heroic vs. JanusGraph vs. TerarkDB vs. XTDB

System Properties Comparison Ehcache vs. Heroic vs. JanusGraph vs. TerarkDB vs. XTDB

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.ehcache.org

github.com/spotify/heroic

janusgraph.org

github.com/bytedance/terarkdb

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.ehcache.org/documentation

spotify.github.io/heroic

docs.janusgraph.org

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.xtdb.com/docs

Developer

Terracotta Inc, owned by Software AG

Spotify

Linux Foundation; originally developed as Titan by Aurelius

ByteDance, originally Terark

Juxt Ltd.

Initial release

2009

2014

2017

2016

2019

Current release

3.10.0, March 2022

1.0.0, October 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

restricted open source version available

Open Source

MIT License

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

C++

Clojure

Server operating systems

All OS with a Java VM

Linux
OS X
Unix
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

JCache

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

C++ API
Java API

HTTP REST
JDBC

Supported programming languages

Java

Clojure
Java
Python

C++
Java

Clojure
Java

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

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

User authentification and security via Rexster Graph Server

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

Simple Deployment of a Graph Database: JanusGraph
12 October 2020, Towards Data Science

Database Deep Dives: JanusGraph
8 August 2019, IBM

JanusGraph Picks Up Where TitanDB Left Off
13 January 2017, Datanami

Nordstrom Builds Flexible Backend Ops with Kubernetes, Spark and JanusGraph
3 October 2019, The New Stack

From graph db to graph embedding. In 7 simple steps. | by Andy Greatorex
30 July 2020, Towards Data Science

provided by Google News

Share this page