DBMS > Amazon Redshift vs. MonetDB vs. Oracle Berkeley DB vs. PlanetScale vs. RavenDB

System Properties Comparison Amazon Redshift vs. MonetDB vs. Oracle Berkeley DB vs. PlanetScale vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A relational database management system that stores data in columns

Widely used in-process key-value store

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS

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	1.72
Rank	#141	Overall
	#64	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

www.monetdb.org

www.oracle.com/database/technologies/related/berkeleydb.html

planetscale.com

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

www.monetdb.org/Documentation

docs.oracle.com/cd/E17076_05/html/index.html

planetscale.com/docs

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

MonetDB BV

Oracle

originally developed by Sleepycat, which was acquired by Oracle

PlanetScale

Hibernating Rhinos

Initial release

2012

2004

1994

2020

2010

Current release

Dec2023 (11.49), December 2023

18.1.40, May 2020

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Mozilla Public License 2.0

Open Source

commercial license available

commercial

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

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Docker
Linux
macOS

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

yes

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL 2003 with some extensions

yes

SQL interfaced based on SQLite is available

yes

with proprietary extensions

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

ADO.NET
JDBC
MySQL protocol
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

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes, in SQL, C, R

yes

proprietary syntax

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication available in experimental status

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

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

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.