DBMS > PostgreSQL vs. ScyllaDB vs. TiDB

System Properties Comparison PostgreSQL vs. ScyllaDB vs. TiDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Cassandra and DynamoDB compatible wide column store

TiDB is an open source distributed SQL database that supports Hybrid Transactional/Analytical Processing (HTAP) workloads. It is MySQL compatible and features horizontal scalability, strong consistency, and high availability.

Primary database model

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Wide column store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Key-value store

Document store

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

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Score	3.70
Rank	#69	Overall
	#5	Wide column stores

Score	3.58
Rank	#73	Overall
	#38	Relational DBMS

Website

www.postgresql.org

www.scylladb.com

pingcap.com

Technical documentation

www.postgresql.org/docs

docs.scylladb.com

docs.pingcap.com/tidb/stable

Developer

PostgreSQL Global Development Group

www.postgresql.org/developer

ScyllaDB

PingCAP, Inc.

Initial release

1989

1989: Postgres, 1996: PostgreSQL

2015

2016

Current release

16.4, August 2024

ScyllaDB Open Source 6.2.0, October 2024

8.2.0, July 2024

License

Commercial or Open Source

Open Source

BSD

Open Source

Open Source (AGPL), commercial license available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

C++

Go, Rust

Server operating systems

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Linux

Data scheme

yes

schema-free

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

cluster global secondary indices

yes

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like DML and DDL statements (CQL)

yes

APIs and other access methods

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

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

GORM
JDBC
ODBC
Proprietary protocol
SQLAlchemy

Supported programming languages

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

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

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes, Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

partitioning by range, list and (since PostgreSQL 11) by hash

Sharding

horizontal partitioning (by key range)

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

selectable replication factor

Representation of geographical distribution of servers is possible

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with TiSpark Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Immediate Consistency

Foreign keys

Referential integrity

yes

full support since version 6.6

Transaction concepts

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

ACID

yes

Atomicity and isolation are supported for single operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

in-memory tables

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

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.