DBMS > Amazon Redshift vs. PlanetScale vs. TerminusDB vs. Tibero

System Properties Comparison Amazon Redshift vs. PlanetScale vs. TerminusDB vs. Tibero

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

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

aws.amazon.com/redshift

planetscale.com

terminusdb.com

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/redshift

planetscale.com/docs

terminusdb.github.io/terminusdb/#

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon (based on PostgreSQL)

PlanetScale

DataChemist Ltd.

TmaxSoft

Initial release

2012

2020

2018

2003

Current release

11.0.0, January 2023

6, April 2015

License

Commercial or Open Source

commercial

Open Source

GPL V3

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

Prolog, Rust

C and Assembler

Server operating systems

hosted

Docker
Linux
macOS

Linux

AIX
HP-UX
Linux
Solaris
Windows

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

SQL-like query language (WOQL)

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

All languages supporting JDBC/ODBC

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

JavaScript
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

yes

proprietary syntax

yes

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Graph Partitioning

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Journaling Streams

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

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

ACID

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 journaling

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

planned for next version

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.