DBMS > Realm vs. Redis vs. Sadas Engine vs. Sphinx

System Properties Comparison Realm vs. Redis vs. Sadas Engine vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store

Key-value store

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

Relational DBMS

Search engine

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	7.71
Rank	#52	Overall
	#9	Document stores

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

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

Technical documentation

realm.io/docs

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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

sphinxsearch.com/docs

Developer

Realm, acquired by MongoDB in May 2019

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SADAS s.r.l.

Sphinx Technologies Inc.

Initial release

2014

2009

2006

2001

Current release

7.2.4, January 2024

8.0

3.5.1, February 2023

License

Commercial or Open Source

Open Source

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

commercial

free trial version available

Open Source

GPL version 2, commercial licence available

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.

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

Implementation language

C++

Server operating systems

Android
Backend: server-less
iOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

AIX
Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
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

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

full-text index on all search fields

SQL

Support of SQL

with RediSQL module

yes

SQL-like query language (SphinxQL)

APIs and other access methods

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC
Proprietary protocol

Proprietary protocol

Supported programming languages

.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

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

runs within the applications so server-side scripts are unnecessary

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

Triggers

yes

Change Listeners

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

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

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

Atomic execution of command blocks and scripts and optimistic locking

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

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

In-Memory realm

yes

managed by 'Learn by Usage'

User concepts

Access control

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

Access rights for users, groups and roles according to SQL-standard

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.