DBMS > Amazon Redshift vs. OrientDB vs. RavenDB vs. Tkrzw

System Properties Comparison Amazon Redshift vs. OrientDB vs. RavenDB vs. Tkrzw

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

Multi-model DBMS (Document, Graph, Key/Value)

Open Source Operational and Transactional Enterprise NoSQL Document Database

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store

Document store

Key-value store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

aws.amazon.com/redshift

orientdb.org

ravendb.net

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

www.orientdb.com/docs/last/index.html

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

OrientDB LTD; CallidusCloud; SAP

Hibernating Rhinos

Mikio Hirabayashi

Initial release

2012

2010

2020

Current release

3.2.29, March 2024

5.4, July 2022

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

AGPL version 3, commercial license available

Open Source

Apache Version 2.0

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

C++

Server operating systems

hosted

All OS with a Java JDK (>= JDK 6)

Linux
macOS
Raspberry Pi
Windows

Linux
macOS

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

Typing

predefined data types such as float or date

yes

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, no joins

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON 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#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Java, Javascript

yes

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

relationship in graphs

Transaction concepts

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

ACID

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

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

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.