DBMS > Graph Engine vs. MySQL vs. PostGIS vs. TempoIQ vs. Teradata

System Properties Comparison Graph Engine vs. MySQL vs. PostGIS vs. TempoIQ vs. Teradata

Editorial information provided by DB-Engines

Name

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

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Widely used open source RDBMS

Spatial extension of PostgreSQL

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

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

www.graphengine.io

www.mysql.com

postgis.net

tempoiq.com (offline)

www.teradata.com

Technical documentation

www.graphengine.io/docs/manual

dev.mysql.com/doc

postgis.net/documentation

docs.teradata.com

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

TempoIQ

Teradata

Initial release

2010

1995

2005

2012

1984

Current release

8.4.0, April 2024

3.4.2, February 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

commercial

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

.NET and C

C and C++

Server operating systems

.NET

FreeBSD
Linux
OS X
Solaris
Windows

hosted
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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL 2016 + extensions

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C#
C++
F#
Visual Basic

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
JavaScript

Node.js
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Realtime Alerts

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication
Source-replica replication

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

simple authentication-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.