DBMS > Drizzle vs. RDF4J vs. Realm vs. Redis vs. SwayDB

System Properties Comparison Drizzle vs. RDF4J vs. Realm vs. Redis vs. SwayDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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.

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

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	0.72
Rank	#222	Overall
	#9	RDF stores

Score	7.18
Rank	#52	Overall
	#8	Document stores

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

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

Website

Technical documentation

rdf4j.org/documentation

realm.io/docs

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

Developer

Drizzle project, originally started by Brian Aker

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Realm, acquired by MongoDB in May 2019

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Simer Plaha

Initial release

2008

2004

2014

2009

2018

Current release

7.2.4, September 2012

7.2.5, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

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

Open Source

GNU Affero GPL V3.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

C++

Java

Scala

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Unix
Windows

Android
Backend: server-less
iOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

RDF Schemas

yes

schema-free

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

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

yes

with proprietary extensions

with RediSQL module

APIs and other access methods

JDBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C
C++
Java
PHP

Java
PHP
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

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

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

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

Triggers

hooks for callbacks inside the server can be used.

yes

Change Listeners

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Atomic execution of command blocks and scripts and optimistic locking

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

In-Memory realm

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

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.