DBMS > Amazon Redshift vs. Apache Doris vs. PlanetScale vs. RRDtool

System Properties Comparison Amazon Redshift vs. Apache Doris vs. PlanetScale vs. RRDtool

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

An MPP-based analytics DBMS embracing the MySQL protocol

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

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.61
Rank	#235	Overall
	#110	Relational DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	1.70
Rank	#136	Overall
	#11	Time Series DBMS

Website

aws.amazon.com/redshift

doris.apache.org
github.com/apache/doris

planetscale.com

oss.oetiker.ch/rrdtool

Technical documentation

docs.aws.amazon.com/redshift

github.com/apache/doris/wiki

planetscale.com/docs

oss.oetiker.ch/rrdtool/doc

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation, originally contributed from Baidu

PlanetScale

Tobias Oetiker

Initial release

2012

2017

2020

1999

Current release

1.2.2, February 2023

1.8.0, 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

GPL V2 and FLOSS

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

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

hosted

Linux

Docker
Linux
macOS

HP-UX
Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

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

JDBC
MySQL client

ADO.NET
JDBC
MySQL protocol
ODBC

in-process shared library
Pipes

Supported programming languages

All languages supporting JDBC/ODBC

Java

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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

none

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

none

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

yes

by using the rrdcached daemon

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.