DBMS > Ehcache vs. EJDB vs. JaguarDB vs. Titan

System Properties Comparison Ehcache vs. EJDB vs. JaguarDB vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

A widely adopted Java cache with tiered storage options

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Performant, highly scalable DBMS for AI and IoT applications

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Key-value store

Document store

Key-value store
Vector DBMS

Graph 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	#331	Overall
	#46	Document stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Website

www.ehcache.org

github.com/Softmotions/ejdb

www.jaguardb.com

github.com/thinkaurelius/titan

Technical documentation

www.ehcache.org/documentation

github.com/Softmotions/ejdb/blob/master/README.md

www.jaguardb.com/support.html

github.com/thinkaurelius/titan/wiki

Developer

Terracotta Inc, owned by Software AG

Softmotions

DataJaguar, Inc.

Aurelius, owned by DataStax

Initial release

2009

2012

2015

2012

Current release

3.10.0, March 2022

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPLv2

Open Source

GPL V3.0

Open Source

Apache license, 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.

Implementation language

Java

C++

the server part. Clients available in other languages

Java

Server operating systems

All OS with a Java VM

server-less

Linux

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JCache

in-process shared library

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

Java

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Clojure
Java
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

none

Sharding

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

Multi-source replication

yes

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Relationships in graph

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

Read/Write Locking

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

In-memory capabilities

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

yes

User concepts

Access control

rights management via user accounts

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

DB-Engines blog posts

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, 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

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

Amazon DynamoDB Storage Backend for Titan: Distributed Graph Database
24 August 2015, AWS Blog

DSE Graph review: Graph database does double duty
14 November 2019, InfoWorld

Beyond Titan: The Evolution of DataStax’s New Graph Database
21 June 2016, Datanami

Database Deep Dives: JanusGraph
8 August 2019, IBM

TigerGraph, a graph database born to roar
19 September 2017, ZDNet

provided by Google News

Share this page