DBMS > PlanetScale vs. RocksDB vs. TimescaleDB vs. TimesTen

System Properties Comparison PlanetScale vs. RocksDB vs. TimescaleDB vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

In-Memory RDBMS compatible to Oracle

Primary database model

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

planetscale.com

rocksdb.org

www.timescale.com

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

Technical documentation

planetscale.com/docs

github.com/facebook/rocksdb/wiki

docs.timescale.com

docs.oracle.com/database/timesten-18.1

Developer

PlanetScale

Facebook, Inc.

Timescale

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2020

2013

2017

1998

Current release

8.11.4, April 2024

2.13.0, November 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

Apache 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++

Server operating systems

Docker
Linux
macOS

Linux

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

full PostgreSQL SQL syntax

yes

APIs and other access methods

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication with hot standby and reads on replicas

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

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

yes

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

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.