DBMS > Ehcache vs. Prometheus vs. Snowflake vs. TerarkDB vs. Titan

System Properties Comparison Ehcache vs. Prometheus vs. Snowflake vs. TerarkDB vs. Titan

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

Open-source Time Series DBMS and monitoring system

Cloud-based data warehousing service for structured and semi-structured data

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

www.ehcache.org

prometheus.io

www.snowflake.com

github.com/bytedance/terarkdb

github.com/thinkaurelius/titan

Technical documentation

www.ehcache.org/documentation

prometheus.io/docs

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

github.com/thinkaurelius/titan/wiki

Developer

Terracotta Inc, owned by Software AG

Snowflake Computing Inc.

ByteDance, originally Terark

Aurelius, owned by DataStax

Initial release

2009

2015

2014

2016

2012

Current release

3.10.0, March 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

restricted open source version available

Open Source

Apache license, version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Java

Server operating systems

All OS with a Java VM

Linux
Windows

hosted

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JCache

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

C++ API
Java API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

JavaScript (Node.js)
Python

C++
Java

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

yes

none

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

by Federation

yes

none

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)

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.