DBMS > MySQL vs. PostGIS vs. Quasardb vs. Trafodion vs. Yanza

System Properties Comparison MySQL vs. PostGIS vs. Quasardb vs. Trafodion vs. Yanza

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used open source RDBMS

Spatial extension of PostgreSQL

Distributed, high-performance timeseries database

Transactional SQL-on-Hadoop DBMS

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

yanza.com

Technical documentation

dev.mysql.com/doc

postgis.net/documentation

doc.quasar.ai/master

trafodion.apache.org/documentation.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

quasardb

Apache Software Foundation, originally developed by HP

Yanza

Initial release

1995

2005

2009

2014

2015

Current release

8.4.0, April 2024

3.4.2, February 2024

3.14.1, January 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

C++

C++, Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

Linux

Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

ADO.NET
JDBC
ODBC

HTTP 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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

All languages supporting JDBC/ODBC/ADO.Net

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Java Stored Procedures

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

consistent hashing

Sharding

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 selectable replication factor

yes, via HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

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

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 LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

Cryptographically strong user authentication and audit trail

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.