DBMS > Databricks vs. Google BigQuery vs. Trino

System Properties Comparison Databricks vs. Google BigQuery vs. Trino

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Large scale data warehouse service with append-only tables

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

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	87.68
Rank	#13	Overall
	#2	Document stores
	#9	Relational DBMS

Score	52.29
Rank	#19	Overall
	#13	Relational DBMS

Score	5.38
Rank	#60	Overall
	#35	Relational DBMS

Website

www.databricks.com

cloud.google.com/bigquery

trino.io

Technical documentation

docs.databricks.com

cloud.google.com/bigquery/docs

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

Developer

Databricks

Google

Trino Software Foundation

Initial release

2013

2010

2012

2020 rebranded from PrestoSQL

License

Commercial or Open Source

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

hosted

Linux
macOS

for devlopment

Data scheme

Flexible Schema (defined schema, partial schema, 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

depending on connected data-source

SQL

Support of SQL

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

Python
R
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

in JavaScript

yes, depending on connected data-source

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on connected data-source

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on connected data-source

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on connected data-source

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

SQL standard access control

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

News

The long journey to Apache Ranger
2 December 2024

The glorious lineup for Trino Summit 2024
22 November 2024

View the SQL basecamps before Trino Summit
21 November 2024

Trino and Javascript?! YES!
18 November 2024

67: Extra speed with Exasol and Trino
30 October 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.