DBMS > Google Cloud Datastore vs. Trino vs. XTDB

System Properties Comparison Google Cloud Datastore vs. Trino vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store

Relational DBMS

Document store

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	3.62
Rank	#71	Overall
	#12	Document stores

Score	5.34
Rank	#60	Overall
	#34	Relational DBMS

Score	0.20
Rank	#314	Overall
	#46	Document stores

Website

cloud.google.com/datastore

trino.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

cloud.google.com/datastore/docs

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

www.xtdb.com/docs

Developer

Google

Trino Software Foundation

Juxt Ltd.

Initial release

2008

2012

2020 rebranded from PrestoSQL

2019

Current release

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

MIT License

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

Clojure

Server operating systems

hosted

Linux
macOS

for devlopment

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

yes, extensible-data-notation format

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.

Secondary indexes

yes

depending on connected data-source

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
RESTful HTTP API
Trino CLI

HTTP REST
JDBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Clojure
Java

Server-side scripts

Stored procedures

using Google App Engine

yes, depending on connected data-source

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on connected data-source

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

depending on connected data-source

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

depending on connected data-source

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

depending on connected data-source

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

depending on connected data-source

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

SQL standard access control

More information provided by the system vendor

News

73: Wrapping Trino packages with a bow
9 April 2025

Core Principles and Design Practices of OLAP Engines
27 March 2025

72: Keeping the lake clean
17 March 2025

Twenty four
3 March 2025

71: Fake it real good
27 February 2025

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Best cloud storage of 2025: tested, reviewed and rated by experts
9 May 2025, TechRadar

Storage news ticker – April 11
11 April 2025, Blocks and Files

Best Cloud Storage Options for All Your Data in 2025
16 April 2025, CNET

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
5 April 2025, Cloudwards.net

Enabling Security for Hadoop Data Lake on Google Cloud Storage
30 July 2024, Uber

provided by Google News

A look at Presto, Trino SQL query engines
9 August 2022, TechTarget

How to Deploy MinIO and Trino with Kubernetes
23 May 2024, HackerNoon

The Perfect AI Storage: Trino From Facebook And Iceberg From Netflix?
30 April 2024, The Next Platform

Query big data with resilience using Trino in Amazon EMR with Amazon EC2 Spot Instances for less cost
4 October 2023, Amazon Web Services

Trino turns 10: Starburst celebrates a decade of its open source query engine
11 August 2022, VentureBeat

provided by Google News

Share this page