DBMS > MySQL vs. PostGIS vs. PouchDB vs. Transbase

System Properties Comparison MySQL vs. PostGIS vs. PouchDB vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Spatial extension of PostgreSQL

JavaScript DBMS with an API inspired by CouchDB

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.35
Rank	#116	Overall
	#22	Document stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

www.mysql.com

postgis.net

pouchdb.com

www.transaction.de/en/products/transbase.html

Technical documentation

dev.mysql.com/doc

postgis.net/documentation

pouchdb.com/guides

www.transaction.de/en/products/transbase/features.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Transaction Software GmbH

Initial release

1995

2005

2012

1987

Current release

8.3.0, January 2024

3.4.2, February 2024

7.1.1, June 2019

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Open Source

commercial

free development license

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

JavaScript

C and C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
macOS
Solaris
Windows

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

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

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

JavaScript

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

not for MyISAM storage engine

ACID

yes

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 using IndexedDB, WebSQL or LevelDB as backend

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

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.