DBMS > MySQL vs. Newts vs. PostGIS vs. Prometheus vs. TinkerGraph

System Properties Comparison MySQL vs. Newts vs. PostGIS vs. Prometheus vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Time Series DBMS based on Cassandra

Spatial extension of PostgreSQL

Open-source Time Series DBMS and monitoring system

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

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	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

www.mysql.com

opennms.github.io/newts

postgis.net

prometheus.io

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

Technical documentation

dev.mysql.com/doc

github.com/OpenNMS/newts/wiki

postgis.net/documentation

prometheus.io/docs

Developer

Oracle

since 2010, originally MySQL AB, then Sun

OpenNMS Group

Initial release

1995

2014

2005

2015

2009

Current release

8.4.0, April 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

GPL v2.0

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

Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
Java API

RESTful HTTP/JSON API

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

Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Groovy
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on Cassandra

yes

based on PostgreSQL

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

yes

by Federation

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

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

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.