DBMS > Amazon Redshift vs. IBM Db2 vs. Linter vs. PlanetScale

System Properties Comparison Amazon Redshift vs. IBM Db2 vs. Linter 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

Common in IBM host environments, 2 different versions for host and Windows/Linux

RDBMS for high security requirements

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

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

aws.amazon.com/redshift

www.ibm.com/products/db2

linter.ru

planetscale.com

Technical documentation

docs.aws.amazon.com/redshift

www.ibm.com/docs/en/db2

planetscale.com/docs

Developer

Amazon (based on PostgreSQL)

IBM

relex.ru

PlanetScale

Initial release

2012

1983

host version

1990

2020

Current release

12.1, October 2016

License

Commercial or Open Source

commercial

free version is available

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

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
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

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Source-replica replication

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

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

User concepts

Access control

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.