Softwr

Cloud · head to head

Lambda (AWS Serverless) vs Trino

Lambda (AWS Serverless) logo

Lambda (AWS Serverless)

Cloud

Run code without thinking about servers

From
Free
Free plan
Yes
Trino logo

Trino

Databases

A distributed SQL engine that queries data where it already lives, across object storage, warehouses and operational databases.

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Lambda (AWS Serverless) lists multiple languages; only Trino lists federated querying.
  • Where Lambda (AWS Serverless) falls short: provisioned concurrency, used to avoid cold starts, is charged separately at $0.0000041667 per GB-second whether or not the function runs.
  • Prices and features on this page were last checked on 13 November 2026.

How do Lambda (AWS Serverless) and Trino differ?

Lambda (AWS Serverless) and Trino differ on pricing model (Usage-based against Open-source), platforms (Web, API against Web) and category (Cloud against Databases). Only the attributes on which Lambda (AWS Serverless) and Trino actually diverge.

Attributes where Lambda (AWS Serverless) and Trino differ
AttributeLambda (AWS Serverless)Trino
Pricing modelUsage-basedOpen-source
PlatformsWeb, APIWeb
CategoryCloudDatabases

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Trino.

Which features does each one have?

They share no listed features; 20 appear only for Lambda (AWS Serverless) and 8 only for Trino. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Lambda (AWS Serverless)

  • Function-as-a-Service
  • Event-driven execution
  • Auto-scaling
  • Pay-per-use
  • Multiple languages
  • Concurrency limits
  • Dead Letter Queues
  • Environment variables

Only in Trino

  • Federated querying
  • Connector architecture
  • Predicate and aggregation pushdown
  • Massively parallel execution
  • Fault-tolerant execution
  • Resource groups
  • Iceberg and Delta table support
  • Standard client protocols

What is each one used for?

Lambda (AWS Serverless) is most often brought in for event-driven functions without managing servers. The jobs each tool is most often brought in to do.

Lambda (AWS Serverless)

  • Event-driven functions without managing serversnot Trino
  • API backends behind API Gatewaynot Trino
  • Processing S3, DynamoDB, SQS and Kinesis eventsnot Trino
  • Scheduled jobs without a always-on instancenot Trino
  • Edge compute through Lambda@Edgenot Trino

Trino

  • Ad hoc analysis that spans a data lake and one or more operational databases, without building an ingestion pipeline firstnot Lambda (AWS Serverless)
  • Serving a BI tool a single SQL endpoint over an estate that is actually several separate storage systemsnot Lambda (AWS Serverless)
  • Querying Iceberg or Delta tables on object storage interactively, as the compute layer of a lakehousenot Lambda (AWS Serverless)
  • Investigating whether a dataset is worth ingesting, by querying it in place before committing to a pipeline for itnot Lambda (AWS Serverless)

Where do Lambda (AWS Serverless) and Trino fall short?

Lambda (AWS Serverless)'s most cited limit: ephemeral storage beyond the included 512 MB is metered. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Lambda (AWS Serverless)

  • Billed on two axes at once, $0.20 per million requests plus $0.0000166667 per GB-second of duration, so memory settings change the bill as much as traffic does
  • Provisioned concurrency, used to avoid cold starts, is charged separately at $0.0000041667 per GB-second whether or not the function runs
  • Ephemeral storage beyond the included 512 MB is metered
  • Lambda@Edge costs $0.60 per million requests, three times the standard request rate
  • VPC use and cross-region data transfer carry EC2 charges on top

Trino

  • Trino stores nothing and computes no statistics of its own, so the plan it produces is only as good as the partitioning, file sizes and table statistics on the source; a Hive table of thousands of small files or a lake with no stats produces a slow query the engine cannot improve
  • Federated queries pull data out of the systems they touch, so a join between a lake table and a production Postgres can put a full table scan onto an OLTP database that other applications depend on, and the person who wrote the query will not see the incident it causes
  • Releases come roughly every one to two weeks with no community long-term support line, and deprecations arrive quickly, so you either dedicate someone to keeping current or you buy Starburst Enterprise for a supported long-term version
  • It is memory-based and disk spilling was deprecated in favour of fault-tolerant execution, so a query exceeding cluster memory fails outright rather than degrading; enabling fault-tolerant execution requires an external exchange store on object storage and makes queries measurably slower
  • It is a query engine and not a warehouse: there is no built-in job scheduling, no incremental materialised view maintenance and no transformation framework, so producing curated tables still needs dbt or an equivalent layer that somebody has to own
  • The 2020 fork split the ecosystem, so documentation, connectors, Stack Overflow answers and vendor material written before then describe PrestoDB, which is now a different project with different behaviour, and following the wrong one wastes real time

How much do Lambda (AWS Serverless) and Trino cost?

Lambda (AWS Serverless) is free to use; Trino is free to use. Plan by plan below, from each vendor's own pricing page.

Lambda (AWS Serverless)

Free
  • Free TierFree
    • 1M free requests/month
    • 400,000 GB-seconds/month
    • Always free

Trino

Free

No published plan breakdown. See the Trino review.

Which should you pick?

Choose Lambda (AWS Serverless) if

  • You need function-as-a-service.
  • You want to start without paying.
  • You work on Web, API.
  • You also want event-driven execution.

Choose Trino if

  • You need federated querying.
  • You want to start without paying.
  • You also want connector architecture.

Questions people ask

Is Lambda (AWS Serverless) or Trino better?
Neither clearly leads. Lambda (AWS Serverless) starts at Free and Trino at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Lambda (AWS Serverless) or Trino?
Lambda (AWS Serverless) starts at Free and Trino at Free.
Does Lambda (AWS Serverless) or Trino run on more platforms?
Lambda (AWS Serverless) runs on Web, API. Trino runs on Web.
Can I use Lambda (AWS Serverless) for free?
Both have a free tier, so you can try either at no cost before committing.
What is Lambda (AWS Serverless) best used for?
Lambda (AWS Serverless) is most often used for event-driven functions without managing servers, api backends behind api gateway, processing s3, dynamodb, sqs and kinesis events, scheduled jobs without a always-on instance. Of those, event-driven functions without managing servers and api backends behind api gateway are not what Trino is typically brought in for.
What can Lambda (AWS Serverless) do that Trino cannot?
Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. Trino covers Federated querying, Connector architecture, Predicate and aggregation pushdown, Massively parallel execution.

Answered from the vendors’ own pages

Lambda (AWS Serverless): Is there a free tier for AWS Lambda?

Yes. AWS Lambda offers a free tier including 1 million requests per month, 400,000 GB-seconds per month, and 100 GB monthly response streaming.

Source
Trino: What is the difference between Trino and Presto?

They share an origin. The original creators left Meta and renamed their fork from PrestoSQL to Trino in December 2020; PrestoDB continues separately under the Linux Foundation. They have diverged in features, connectors and SQL behaviour, so material written for one may not apply to the other.

Lambda (AWS Serverless): How is AWS Lambda charged?

Lambda charges $0.20 per million requests. Duration charges are $0.0000166667 per GB-second for x86 (up to 6 billion GB-seconds/month in US East Ohio with tiered pricing). Ephemeral storage over the included 512 MB costs $0.0000000309 per GB-second. Provisioned Concurrency costs $0.0000041667 per GB-second with a 5-minute minimum.

Source
Trino: Does Trino replace my data warehouse?

Not on its own. It is compute without storage, scheduling or transformation. Paired with Iceberg or Delta on object storage and something like dbt for modelling it can serve as a lakehouse; used alone it is a query layer over what you already have.

Lambda (AWS Serverless): What are Lambda Durable Functions pricing?

Lambda Durable Functions include operations at $8.00 per million (start execution, steps, waits). Data written costs $0.25 per GB. Data retention is $0.15 per GB-month with configurable 1-90 day retention (default 14 days).

Source
Trino: Why is my federated query slow?

Usually because a connector could not push a filter or aggregation down, so Trino is pulling whole tables across the network to join them itself. The fix is usually better source-side partitioning or statistics, or ingesting that source rather than federating it.

Trino: What happens when a query runs out of memory?

It fails. Disk spilling was deprecated in favour of fault-tolerant execution, which checkpoints to an external exchange store such as S3 and lets long queries survive memory pressure and worker loss, at the cost of noticeably slower execution.

Trino: Is there commercial support?

Yes, from Starburst, which offers Starburst Enterprise with long-term supported releases and Starburst Galaxy as a managed service. The open source project itself has no long-term support line.

Share

Related pages

Other head to heads