DBMS > Datomic vs. Ehcache vs. IBM Cloudant vs. Redis vs. STSdb

System Properties Comparison Datomic vs. Ehcache vs. IBM Cloudant vs. Redis vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A widely adopted Java cache with tiered storage options

Database as a Service offering based on Apache CouchDB

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Key-value store

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.datomic.com

www.ehcache.org

www.ibm.com/products/cloudant

redis.com
redis.io

github.com/STSSoft/STSdb4

Technical documentation

docs.datomic.com

www.ehcache.org/documentation

cloud.ibm.com/docs/Cloudant

docs.redis.com/latest/index.html
redis.io/docs

Developer

Cognitect

Terracotta Inc, owned by Software AG

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

STS Soft SC

Initial release

2012

2009

2010

2009

2011

Current release

1.0.6735, June 2023

3.10.0, March 2022

7.2.4, January 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

Open Source

GPLv2, commercial license available

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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java, Clojure

Java

Erlang

Server operating systems

All OS with a Java VM

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

yes

primitive types and user defined types (classes)

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

with RediSearch module

SQL

Support of SQL

with RediSQL module

APIs and other access methods

RESTful HTTP API

JCache

RESTful HTTP/JSON API

proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API

Supported programming languages

Clojure
Java

Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C#
Java

Server-side scripts

Stored procedures

yes

Transaction Functions

View functions (Map-Reduce) in JavaScript

Lua; Redis Functions coming in Redis 7 (slides and Github)

Triggers

By using transaction functions

yes

Cache Event Listeners

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

by using Terracotta Server

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

by using Terracotta Server

Multi-source replication
Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes

supports JTA and can work as an XA resource

atomic operations within a document possible

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

using a tiered cache-storage approach

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users can be defined per database

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

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.