DBMS > Amazon Aurora vs. FatDB vs. InfluxDB vs. Oracle NoSQL vs. Redis

System Properties Comparison Amazon Aurora vs. FatDB vs. InfluxDB vs. Oracle NoSQL vs. Redis

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

MySQL and PostgreSQL compatible cloud service by Amazon

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

DBMS for storing time series, events and metrics

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Document store
Key-value store

Time Series DBMS

Document store
Key-value store
Relational DBMS

Key-value store

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

Secondary database models

Document store

Spatial DBMS

with GEO package

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.91
Rank	#50	Overall
	#32	Relational DBMS

Score	25.83
Rank	#28	Overall
	#1	Time Series DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

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

Website

aws.amazon.com/rds/aurora

www.influxdata.com/products/influxdb-overview

www.oracle.com/database/nosql/technologies/nosql

redis.com
redis.io

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.influxdata.com/influxdb

docs.oracle.com/en/database/other-databases/nosql-database/index.html

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

Developer

Amazon

FatCloud

Oracle

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2015

2012

2013

2011

2009

Current release

2.7.6, April 2024

23.3, December 2023

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

MIT-License; commercial enterprise version available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Server operating systems

hosted

Windows

Linux
OS X

through Homebrew

Linux
Solaris SPARC/x86

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

Numeric data and Strings

optional

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.

yes

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes

Via inetgration in SQL Server

SQL-like query language

SQL-like DML and DDL statements

with RediSQL module

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP API
JSON over UDP

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C#
Go
Java
JavaScript (Node.js)
Python

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

via applications

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

Triggers

yes

via applications

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

in enterprise version only

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

in enterprise version only

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

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

Depending on used storage engine

yes

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

simple rights management via user accounts

Access rights for users and roles

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

Specific characteristics

InfluxData is the creator of InfluxDB , the open source time series database. It...
» more

Competitive advantages

Time to Value InfluxDB is available in all the popular languages and frameworks,...
» more

Typical application scenarios

IoT & Sensor Monitoring Developers are witnessing the instrumentation of every available...
» more

Key customers

InfluxData has more than 1,900 paying customers, including customers include MuleSoft,...
» more

Market metrics

Fastest-growing database to drive 27,500 GitHub stars Over 750,000 daily active instances
» more

Licensing and pricing models

Open source core with closed source clustering available either on-premise or on...
» more

News

An Introductory Guide to Grafana Alerts
16 May 2024

What to Expect When You’re Expecting InfluxDB: A Guide
14 May 2024

Introduction to Apache Iceberg
9 May 2024

Converting Timestamp to Date in Java
7 May 2024

A Detailed Guide to C# TimeSpan
2 May 2024

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.