DBMS > Apache Druid vs. BaseX vs. Geode vs. Realm vs. Redis

System Properties Comparison Apache Druid vs. BaseX vs. Geode vs. Realm vs. Redis

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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.

Primary database model

Relational DBMS
Time Series DBMS

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

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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	7.60
Rank	#52	Overall
	#9	Document stores

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

Website

Technical documentation

druid.apache.org/docs/latest/design

docs.basex.org

geode.apache.org/docs

realm.io/docs

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

Developer

Apache Software Foundation and contributors

BaseX GmbH

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Realm, acquired by MongoDB in May 2019

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

2007

2002

2014

2009

Current release

29.0.1, April 2024

10.7, August 2023

1.1, February 2017

7.2.5, May 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

BSD license

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

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

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

Java

Server operating systems

Linux
OS X
Unix

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Android
Backend: server-less
iOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-less columns are supported

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

XQuery supports types

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

SQL for querying

SQL-like query language (OQL)

with RediSQL module

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

Java Client API
Memcached protocol
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

.Net
All JVM based languages
C++
Groovy
Java
Scala

.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

Server-side scripts

Stored procedures

yes

user defined functions

runs within the applications so server-side scripts are unnecessary

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

Triggers

yes

via events

yes

Cache Event Listeners

yes

Change Listeners

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

Multi-source replication

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

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

Immediate 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

multiple readers, single writer

yes, on a single node

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

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Users with fine-grained authorization concept on 4 levels

Access rights per client and object definable

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.