DBMS > Greenplum vs. Snowflake vs. Trino

System Properties Comparison Greenplum vs. Snowflake vs. Trino

Please select another system to include it in the comparison.

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.

Cloud-based data warehousing service for structured and semi-structured data

Fast distributed SQL query engine for big data analytics. Forked from Presto and originally named PrestoSQL

Primary database model

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Key-value store
Spatial DBMS
Search engine
Time Series DBMS
Wide column store

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

Score	7.39
Rank	#47	Overall
	#29	Relational DBMS

Score	140.60
Rank	#7	Overall
	#5	Relational DBMS

Score	5.47
Rank	#62	Overall
	#35	Relational DBMS

Website

greenplum.org

www.snowflake.com

trino.io

Technical documentation

docs.greenplum.org

docs.snowflake.net/manuals/index.html

trino.io/broadcast
trino.io/docs/current

Developer

Pivotal Software Inc.

Snowflake Computing Inc.

Trino Software Foundation

Initial release

2005

2014

2012

2020 rebranded from PrestoSQL

Current release

7.0.0, September 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

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.

Implementation language

Java

Server operating systems

Linux

hosted

Linux
macOS

for devlopment

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

since Version 4.2

yes

Secondary indexes

yes

depending on connected data-source

SQL

Support of SQL

yes

APIs and other access methods

JDBC
ODBC

CLI Client
JDBC
ODBC

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

C
Java
Perl
Python
R

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes, depending on connected data-source

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on connected data-source

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

depending on connected data-source

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on connected data-source

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

depending on connected data-source

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

depending on connected data-source

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

SQL standard access control

More information provided by the system vendor

News

A glimpse at the summit
17 October 2024

A Kubernetes operator for Trino?
10 October 2024

SQL basecamps before Trino Summit
7 October 2024

23 is a go, keeping pace with Java
17 September 2024

66: Chat with Trino and Wren AI
12 September 2024

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.