DBMS > Amazon Redshift vs. RavenDB vs. RDF4J vs. ToroDB

System Properties Comparison Amazon Redshift vs. RavenDB vs. RDF4J vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Open Source Operational and Transactional Enterprise NoSQL Document Database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

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.92
Rank	#101	Overall
	#18	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

aws.amazon.com/redshift

ravendb.net

rdf4j.org

github.com/torodb/server

Technical documentation

docs.aws.amazon.com/redshift

ravendb.net/docs

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

Hibernating Rhinos

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

8Kdata

Initial release

2012

2010

2004

2016

Current release

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

AGPL-V3

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
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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 query language (RQL)

APIs and other access methods

JDBC
ODBC

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

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

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

Eventual Consistency
Immediate Consistency

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

ACID, Cluster-wide transaction available

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.