DBMS > Amazon Redshift vs. Firebase Realtime Database vs. Geode vs. NuoDB vs. Redis

System Properties Comparison Amazon Redshift vs. Firebase Realtime Database vs. Geode vs. NuoDB vs. Redis

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

NuoDB is a webscale distributed database that supports SQL and ACID transactions

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

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	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

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

Website

aws.amazon.com/redshift

firebase.google.com/products/realtime-database

geode.apache.org

www.3ds.com/nuodb-distributed-sql-database

redis.com
redis.io

Technical documentation

docs.aws.amazon.com/redshift

firebase.google.com/docs/database

geode.apache.org/docs

doc.nuodb.com

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

Developer

Amazon (based on PostgreSQL)

Google

acquired by Google 2014

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

Dassault Systèmes

originally NuoDB, Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

2002

2013

2009

Current release

1.1, February 2017

7.2.5, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

limited edition free

Open Source

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

Cloud-based only

Only available as a cloud service

yes

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

C++

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

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

restricted

yes

with RediSearch module

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (OQL)

yes

with RediSQL module

APIs and other access methods

JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript
Objective-C

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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
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

Server-side scripts

Stored procedures

user defined functions

in Python

limited functionality with using 'rules'

user defined functions

Java, SQL

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

Triggers

Callbacks are triggered when data changes

yes

Cache Event Listeners

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

data is dynamically stored/cached on the nodes where it is read/written

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Managed transparently by NuoDB

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

if the client is offline
Immediate Consistency

if the client is online

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

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes

yes, on a single node

ACID

tunable commit protocol

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

Temporary table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

Access rights per client and object definable

Standard SQL roles/ privileges, Administrative Users

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.