DBMS > Cachelot.io vs. Redis vs. SWC-DB vs. Titan vs. Yanza

System Properties Comparison Cachelot.io vs. Redis vs. SWC-DB vs. Titan vs. Yanza

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.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

In-memory caching system

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.

A high performance, scalable Wide Column DBMS

Titan is a Graph DBMS optimized for distributed clusters.

Time Series DBMS for IoT Applications

Primary database model

Key-value store

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

Wide column store

Graph DBMS

Time Series DBMS

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

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

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

cachelot.io

redis.com
redis.io

github.com/kashirin-alex/swc-db
www.swcdb.org

github.com/thinkaurelius/titan

yanza.com

Technical documentation

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

github.com/thinkaurelius/titan/wiki

Developer

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Alex Kashirin

Aurelius, owned by DataStax

Yanza

Initial release

2015

2009

2020

2012

2015

Current release

7.2.4, January 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

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

Open Source

GPL V3

Open Source

Apache license, version 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

C++

Java

Server operating systems

FreeBSD
Linux
OS X

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Linux
OS X
Unix
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

partial

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

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

with RediSearch module

yes

SQL

Support of SQL

with RediSQL module

SQL-like query language

APIs and other access methods

Memcached protocol

proprietary protocol

RESP - REdis Serialization Protocol

Proprietary protocol
Thrift

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
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++

Clojure
Java
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

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

yes

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

yes

via pluggable storage backends

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

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

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

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

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.