DBMS > PlanetScale vs. PostGIS vs. TimescaleDB vs. XTDB

System Properties Comparison PlanetScale vs. PostGIS vs. TimescaleDB vs. XTDB

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

Spatial extension of PostgreSQL

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

A general purpose database with bitemporal SQL and Datalog and graph queries

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	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

planetscale.com

postgis.net

www.timescale.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

planetscale.com/docs

postgis.net/documentation

docs.timescale.com

www.xtdb.com/docs

Developer

PlanetScale

Timescale

Juxt Ltd.

Initial release

2020

2005

2017

2019

Current release

3.4.2, February 2024

2.13.0, November 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

Apache 2.0

Open Source

MIT License

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

Clojure

Server operating systems

Docker
Linux
macOS

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

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, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
MySQL protocol
ODBC

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

HTTP REST
JDBC

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

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

based on PostgreSQL

Source-replica replication with hot standby and reads on replicas

yes, each node contains all data

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

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

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

yes

based on PostgreSQL

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Ranked Number 188 Fastest-Growing Company in North America on the 2023 Deloitte Technology Fast ...
8 November 2023, businesswire.com

PlanetScale Ranked Number 188 Fastest-Growing Company in North America on the 2023 Deloitte Technology Fast ...
8 November 2023, Yahoo Finance

PlanetScale Insights Anomalies introduces smart query monitoring
29 November 2023, SDTimes.com

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

TimescaleDB for Azure Database for PostgreSQL to power IoT and time-series workloads | Azure updates
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

Visualizing IoT Data at Scale With Hopara and TimescaleDB
16 May 2023, Embedded Computing Design

provided by Google News

Share this page