DBMS > Amazon Redshift vs. Citus vs. Oracle NoSQL vs. RavenDB

System Properties Comparison Amazon Redshift vs. Citus vs. Oracle NoSQL vs. RavenDB

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Document store

Secondary database models

Document store

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

www.citusdata.com

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

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

docs.citusdata.com

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

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Oracle

Hibernating Rhinos

Initial release

2012

2010

2011

2010

Current release

8.1, December 2018

23.3, December 2023

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

Open Source

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

Open Source

AGPL version 3, commercial license available

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

Java

Server operating systems

hosted

Linux

Linux
Solaris SPARC/x86

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

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

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

standard, with numerous extensions

SQL-like DML and DDL statements

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Triggers

yes

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

other methods possible by using 3rd party extensions

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

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

configurable

ACID within a storage node (=shard)

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

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

Access rights for users and roles

Authorization levels configured per client per database

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.