DBMS > Ehcache vs. RavenDB vs. Riak KV vs. SAP HANA

System Properties Comparison Ehcache vs. RavenDB vs. Riak KV vs. SAP HANA

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Distributed, fault tolerant key-value store

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Key-value store

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

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

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

www.ehcache.org

ravendb.net

www.sap.com/products/hana.html

Technical documentation

www.ehcache.org/documentation

ravendb.net/docs

www.tiot.jp/riak-docs/riak/kv/latest

help.sap.com/hana

Developer

Terracotta Inc, owned by Software AG

Hibernating Rhinos

OpenSource, formerly Basho Technologies

SAP

Initial release

2009

2010

2009

2010

Current release

3.10.0, March 2022

5.4, July 2022

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

AGPL version 3, commercial license available

Open Source

Apache version 2, commercial enterprise edition

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Erlang

Server operating systems

All OS with a Java VM

Linux
macOS
Raspberry Pi
Windows

Linux
OS X

Appliance or cloud-service

Data scheme

schema-free

yes

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

restricted

yes

SQL

Support of SQL

SQL-like query language (RQL)

yes

APIs and other access methods

JCache

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

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

Java

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

Erlang

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication

selectable replication factor

yes

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)

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Authorization levels configured per client per database

yes, using Riak Security

yes

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.