Softwr

Cloud · head to head

Lambda (AWS Serverless) vs Vitess

Lambda (AWS Serverless) logo

Lambda (AWS Serverless)

Cloud

Run code without thinking about servers

From
Free
Free plan
Yes
Vitess logo

Vitess

Databases

Scalable database clustering system for horizontal scaling of MySQL

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Lambda (AWS Serverless) lists event-driven execution; only Vitess lists horizontal Sharding.
  • 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.
  • Where Vitess falls short: VTGate scatter queries without sharding key incur significant performance penalties.
  • Prices and features on this page were last checked on 13 November 2026.

How do Lambda (AWS Serverless) and Vitess differ?

Lambda (AWS Serverless) and Vitess differ on platforms, category (Cloud against Databases) and year founded (2014 against 2010). Only the attributes on which Lambda (AWS Serverless) and Vitess actually diverge.

Attributes where Lambda (AWS Serverless) and Vitess differ
AttributeLambda (AWS Serverless)Vitess
PlatformsWeb, APILinux, macOS, Self-hosted
CategoryCloudDatabases
Founded20142010

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

Not yet recorded: pricing model for Vitess.

Which features does each one have?

They share no listed features; 20 appear only for Lambda (AWS Serverless) and 15 only for Vitess. 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 Vitess

  • Horizontal Sharding
  • Connection Pooling
  • Query Routing
  • Online Schema Changes
  • Shard Management
  • Replication Management
  • Automated Failover
  • MySQL

What is each one used for?

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

Lambda (AWS Serverless)

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

Vitess

  • Transaction processingnot Lambda (AWS Serverless)
  • Data storagenot Lambda (AWS Serverless)
  • Application backendnot Lambda (AWS Serverless)
  • Reportingnot Lambda (AWS Serverless)
  • Data analyticsnot Lambda (AWS Serverless)

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

Lambda (AWS Serverless)'s most cited limit: ephemeral storage beyond the included 512 MB is metered. Vitess's: VTGate scatter queries without sharding key incur significant performance penalties. 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

Vitess

  • VTGate scatter queries without sharding key incur significant performance penalties
  • Foreign key constraints not enforced across shards, requiring application-level integrity handling
  • Single primary per keyspace limits multi-region write capabilities
  • Distributed transactions without proper sharding key routing suffer performance degradation

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

Lambda (AWS Serverless) is free to use; Vitess 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

Vitess

Free

No published plan breakdown. See the Vitess 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 Vitess if

  • You need horizontal sharding.
  • You want to start without paying.
  • You work on Linux, macOS, Self-hosted.
  • You also want connection pooling.

Questions people ask

Is Lambda (AWS Serverless) or Vitess better?
Neither clearly leads. Lambda (AWS Serverless) starts at Free and Vitess at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Lambda (AWS Serverless) or Vitess?
Lambda (AWS Serverless) starts at Free and Vitess at Free.
Does Lambda (AWS Serverless) or Vitess run on more platforms?
Lambda (AWS Serverless) runs on Web, API. Vitess runs on Linux, macOS, Self-hosted.
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 Vitess is typically brought in for.
What can Lambda (AWS Serverless) do that Vitess cannot?
Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes.

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
Vitess: Is Vitess free to use?

Yes. Vitess is completely free and open source under the Apache 2.0 license. It is a graduated CNCF project with no licensing costs or pricing tiers.

Source
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
Vitess: What databases does Vitess support?

Vitess supports MySQL and MariaDB as backend databases. It acts as a middleware layer that adds sharding and orchestration capabilities on top of these databases.

Source
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
Vitess: Does Vitess require Kubernetes to run?

No. Vitess can run on Kubernetes using the Vitess Operator, but it can also be deployed on traditional infrastructure. Kubernetes integration is optional and provides additional automation benefits.

Source
Vitess: How does Vitess handle cross-shard transactions?

Vitess supports distributed transactions across shards, but they require queries to be routed through the sharding key. Transactions without a proper sharding key can result in slower performance.

Source
Vitess: Does Vitess enforce foreign key constraints?

Vitess does not enforce foreign key constraints across shards by default. Referential integrity must be managed at the application layer, though per-database support can be enabled with limitations.

Source
Share

Related pages

Other head to heads