DBMS > MySQL vs. openGauss vs. PostGIS vs. TempoIQ vs. TerminusDB

System Properties Comparison MySQL vs. openGauss vs. PostGIS vs. TempoIQ vs. TerminusDB

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Widely used open source RDBMS

An enterprise-class RDBMS compatible with high-performance, high-availability and high-performance originally developed by Huawei

Spatial extension of PostgreSQL

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

Relational DBMS

Document store
RDF store

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.08
Rank	#183	Overall
	#84	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.mysql.com

gitee.com/opengauss
opengauss.org

postgis.net

tempoiq.com (offline)

terminusdb.com

Technical documentation

dev.mysql.com/doc

docs.opengauss.org/en
gitee.com/opengauss/docs

postgis.net/documentation

terminusdb.github.io/terminusdb/#

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Huawei and openGauss community

TempoIQ

DataChemist Ltd.

Initial release

1995

2019

2005

2012

2018

Current release

8.4.0, April 2024

3.0, March 2022

3.4.2, February 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

commercial

Open Source

GPL V3

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.

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

Prolog, Rust

Server operating systems

FreeBSD
Linux
OS X
Solaris
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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

ANSI SQL 2011

yes

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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

C#
Java
JavaScript

Node.js
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

user defined functions

yes

Triggers

yes

Realtime Alerts

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by range, list and hash)

yes

based on PostgreSQL

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

based on PostgreSQL

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

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

in-memory journaling

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

Access rights for users, groups and roles according to SQL-standard

yes

based on PostgreSQL

simple authentication-based access control

Role-based access control

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.