DBMS > Redis vs. Spark SQL vs. Sphinx vs. XTDB

System Properties Comparison Redis vs. Spark SQL vs. Sphinx vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Document 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	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

redis.com
redis.io

spark.apache.org/sql

sphinxsearch.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

spark.apache.org/docs/latest/sql-programming-guide.html

sphinxsearch.com/docs

www.xtdb.com/docs

Developer

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Apache Software Foundation

Sphinx Technologies Inc.

Juxt Ltd.

Initial release

2009

2014

2001

2019

Current release

7.2.4, January 2024

3.5.0 ( 2.13), September 2023

3.5.1, February 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

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

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

Open Source

MIT License

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

Scala

C++

Clojure

Server operating systems

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

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

yes, extensible-data-notation format

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

yes

SQL

Support of SQL

with RediSQL module

SQL-like DML and DDL statements

SQL-like query language (SphinxQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC

Proprietary protocol

HTTP REST
JDBC

Supported programming languages

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
Python
R
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Clojure
Java

Server-side scripts

Stored procedures

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

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes, utilizing Spark Core

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.