DBMS > Amazon Redshift vs. Kinetica vs. MonetDB vs. PlanetScale

System Properties Comparison Amazon Redshift vs. Kinetica vs. MonetDB vs. PlanetScale

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

Fully vectorized database across both GPUs and CPUs

A relational database management system that stores data in columns

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

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.42
Rank	#261	Overall
	#120	Relational DBMS

Score	1.72
Rank	#135	Overall
	#62	Relational DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Website

aws.amazon.com/redshift

www.kinetica.com

www.monetdb.org

planetscale.com

Technical documentation

docs.aws.amazon.com/redshift

docs.kinetica.com

www.monetdb.org/Documentation

planetscale.com/docs

Developer

Amazon (based on PostgreSQL)

Kinetica

MonetDB BV

PlanetScale

Initial release

2012

2004

2020

Current release

7.1, August 2021

Dec2023 (11.49), December 2023

License

Commercial or Open Source

commercial

Open Source

Mozilla Public License 2.0

commercial

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, C++

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

yes

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 DML and DDL statements

yes

SQL 2003 with some extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
JavaScript (Node.js)
Python

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

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes, in SQL, C, R

yes

proprietary syntax

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding via remote tables

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

Source-replica replication available in experimental status

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

GPU vRAM or System RAM

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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