DBMS > MySQL vs. PostGIS vs. Sequoiadb vs. TimescaleDB vs. TinkerGraph

System Properties Comparison MySQL vs. PostGIS vs. Sequoiadb vs. TimescaleDB vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Spatial extension of PostgreSQL

NewSQL database with distributed OLTP and SQL

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store
Relational DBMS

Time Series DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

dev.mysql.com/doc

postgis.net/documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.timescale.com

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Sequoiadb Ltd.

Timescale

Initial release

1995

2005

2013

2017

2009

Current release

8.4.0, April 2024

3.4.2, February 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache 2.0

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.

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

Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

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

TinkerPop 3

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Groovy
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

JavaScript

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

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

Source-replica replication with hot standby and reads on replicas

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Document is locked during a transaction

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

optional

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

simple password-based access control

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.