DBMS > Amazon Redshift vs. Dragonfly vs. Oracle NoSQL

System Properties Comparison Amazon Redshift vs. Dragonfly vs. Oracle NoSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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

Primary database model

Relational DBMS

Key-value store

Document store
Key-value store
Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	15.07
Rank	#38	Overall
	#23	Relational DBMS

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	2.93
Rank	#94	Overall
	#17	Document stores
	#14	Key-value stores
	#50	Relational DBMS

Website

aws.amazon.com/redshift

github.com/dragonflydb/dragonfly
www.dragonflydb.io

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

Technical documentation

docs.aws.amazon.com/redshift

www.dragonflydb.io/docs

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

Developer

Amazon (based on PostgreSQL)

DragonflyDB team and community contributors

Oracle

Initial release

2012

2023

2011

Current release

1.0, March 2023

24.1, May 2024

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

Open Source

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

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.

Implementation language

C++

Java

Server operating systems

hosted

Linux

Linux
Solaris SPARC/x86

Data scheme

yes

scheme-free

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

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

optional

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

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

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

Triggers

publish/subscribe channels provide some trigger functionality

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

off heap cache

User concepts

Access control

fine grained access rights according to SQL-standard

Password-based authentication

Access rights for users and roles

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.