DBMS > Greenplum vs. MySQL vs. Tarantool vs. TDSQL for MySQL vs. Teradata

System Properties Comparison Greenplum vs. MySQL vs. Tarantool vs. TDSQL for MySQL vs. Teradata

Editorial information provided by DB-Engines

Name

Description

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Widely used open source RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.85
Rank	#207	Overall
	#97	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

greenplum.org

www.mysql.com

www.tarantool.io

www.tencentcloud.com/products/dcdb

www.teradata.com

Technical documentation

docs.greenplum.org

dev.mysql.com/doc

www.tarantool.io/en/doc

www.tencentcloud.com/document/product/1042

docs.teradata.com

Developer

Pivotal Software Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Tencent

Teradata

Initial release

2005

1995

2008

2013

1984

Current release

7.0.0, September 2023

8.4.0, April 2024

2.10.0, May 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

C and C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
macOS

hosted

hosted
Linux

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

since Version 4.2

yes

Secondary indexes

yes

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

SQL

Support of SQL

yes

with proprietary extensions

Full-featured ANSI SQL support

yes

SQL 2016 + extensions

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Open binary protocol

JDBC
ODBC

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

Supported programming languages

C
Java
Perl
Python
R

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C
C#
C++
Java
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

proprietary syntax

Lua, C and SQL stored procedures

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Automatic sharding

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

Users with fine-grained authorization concept

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.