Cloud · head to head
Lambda (AWS Serverless) vs etcd

Lambda (AWS Serverless)
Cloud
Run code without thinking about servers
- From
- Free
- Free plan
- Yes

etcd
Databases
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No
The short version
- Lambda (AWS Serverless) is free; etcd prices on request.
- Only Lambda (AWS Serverless) lists event-driven execution; only etcd lists raft consensus.
- 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 etcd differ?
Lambda (AWS Serverless) and etcd differ on starting price (Free against On request), pricing model (Usage-based against Open-source) and free tier (Yes against No). Only the attributes on which Lambda (AWS Serverless) and etcd actually diverge.
| Attribute | Lambda (AWS Serverless) | etcd |
|---|---|---|
| Starting price | Free | On request |
| Pricing model | Usage-based | Open-source |
| Free tier | Yes | No |
| Platforms | Web, API | Web |
| Category | Cloud | Databases |
Not yet recorded: founded for etcd.
Which features does each one have?
They share no listed features; 20 appear only for Lambda (AWS Serverless) and 8 only for etcd. 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 etcd
- Raft consensus
- Linearizable reads
- Transactions
- Leases
- Watches
- MVCC revision history
- Role-based access control
- Snapshot backup and restore
What is each one used for?
Lambda (AWS Serverless) is most often brought in for event-driven functions without managing servers; etcd for coordinating failover in a clustered database, as Patroni does for PostgreSQL. The jobs each tool is most often brought in to do.
Lambda (AWS Serverless)
- Event-driven functions without managing serversnot etcd
- API backends behind API Gatewaynot etcd
- Processing S3, DynamoDB, SQS and Kinesis eventsnot etcd
- Scheduled jobs without a always-on instancenot etcd
- Edge compute through Lambda@Edgenot etcd
etcd
- Storing Kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doingnot Lambda (AWS Serverless)
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Lambda (AWS Serverless)
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Lambda (AWS Serverless)
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Lambda (AWS Serverless)
Where do Lambda (AWS Serverless) and etcd 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
etcd
- It is sized for coordination data, not application data: the default backend quota is 2 GB and 8 GB is the documented recommended maximum, and exceeding it puts the cluster into a NOSPACE alarm where it accepts no writes until an operator compacts, defragments and clears the alarm by hand
- Every write is replicated and fsynced before acknowledgement, so cluster performance is bounded by the slowest disk in it; a member on network-attached storage with high fsync latency causes leader elections and cluster-wide latency spikes that look like network problems and are not
- Adding members increases availability but reduces write throughput, because each write must reach a larger quorum; you run three or five members for fault tolerance, and increasing capacity means faster hardware rather than more nodes
- There is no sharding and no multi-tenancy, so isolating workloads means running separate clusters, each with its own quorum, certificates, backup schedule and upgrade path, and that operational multiplication is often unexpected
- Running it yourself is a real job: periodic compaction and defragmentation, snapshot backups you have actually rehearsed restoring, and rotation of both peer and client TLS certificates, none of which happens automatically outside a managed Kubernetes service
- Losing quorum is not self-healing; recovering a cluster that has lost a majority means restoring from a snapshot and accepting that everything written since that snapshot is gone, which makes backup frequency a data-loss budget decision rather than a routine setting
How much do Lambda (AWS Serverless) and etcd cost?
Lambda (AWS Serverless) 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
etcd
On requestNo published plan breakdown. See the etcd 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.
Questions people ask
- Is Lambda (AWS Serverless) or etcd better?
- Neither clearly leads. Lambda (AWS Serverless) starts at Free and etcd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Lambda (AWS Serverless) or etcd?
- Lambda (AWS Serverless) has a free tier; the other does not. Paid plans start at Free for Lambda (AWS Serverless) and On request for etcd.
- Does Lambda (AWS Serverless) or etcd run on more platforms?
- Lambda (AWS Serverless) runs on Web, API. etcd runs on Web.
- Can I use Lambda (AWS Serverless) for free?
- Yes. Lambda (AWS Serverless) has a free tier, so you can try it without paying. etcd starts at On request.
- 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 etcd is typically brought in for.
- What can Lambda (AWS Serverless) do that etcd cannot?
- Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. etcd covers Raft consensus, Linearizable reads, Transactions, Leases.
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.
Sourceetcd: Can I use etcd as an application database?
No. It is designed for metadata and coordination, with a recommended maximum store size of around 8 GB, no sharding and a write path deliberately optimised for durability rather than throughput. Application data belongs in a database built for it.
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.
Sourceetcd: How many members should a cluster have?
Three for most cases, five where you need to survive two simultaneous failures. Always an odd number, because an even-sized cluster gains no additional fault tolerance while making quorum harder to reach.
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).
Sourceetcd: What happens when the store fills up?
The cluster raises a NOSPACE alarm and stops accepting writes, becoming effectively read-only. Recovery requires compacting old revisions, defragmenting each member and then explicitly disarming the alarm, all done by an operator.
etcd: Why is my etcd cluster slow or unstable?
Almost always disk latency. Because every write is fsynced before acknowledgement, slow or shared storage causes heartbeat timeouts, leader elections and cascading latency. Local SSDs with low fsync latency are effectively a requirement.
etcd: How does it compare with Consul or ZooKeeper?
All three provide consensus-backed coordination. etcd has the simplest data model and the Kubernetes ecosystem behind it; Consul bundles service discovery, health checking and a service mesh; ZooKeeper is older, JVM-based and still common under Kafka and Hadoop-era systems.
Related pages
More on Lambda (AWS Serverless)
Other head to heads
- Lambda (AWS Serverless) vs Deno Deploy
- Lambda (AWS Serverless) vs Cerebrium
- Lambda (AWS Serverless) vs Serverless Framework
- Lambda (AWS Serverless) vs Neon
- Lambda (AWS Serverless) vs Beam Cloud
- Lambda (AWS Serverless) vs Upstash
- Lambda (AWS Serverless) vs Koyeb
- Lambda (AWS Serverless) vs Azure Functions
- Lambda (AWS Serverless) vs Lambda
- Lambda (AWS Serverless) vs Porter
- Lambda (AWS Serverless) vs Terragrunt
- Lambda (AWS Serverless) vs Heroku
- Lambda (AWS Serverless) vs HAProxy
- Lambda (AWS Serverless) vs K3s
- Lambda (AWS Serverless) vs Proxmox VE
- Lambda (AWS Serverless) vs Buildah
- Lambda (AWS Serverless) vs CloudAMQP
- Lambda (AWS Serverless) vs Rancher
- Lambda (AWS Serverless) vs DynamoDB
- Lambda (AWS Serverless) vs Timeplus
- Lambda (AWS Serverless) vs Firebase Realtime Database
- Lambda (AWS Serverless) vs Knack
- Lambda (AWS Serverless) vs Turso
- Lambda (AWS Serverless) vs BigQuery
- Lambda (AWS Serverless) vs TiDB
- Lambda (AWS Serverless) vs Dgraph
- Lambda (AWS Serverless) vs turbopuffer
- Lambda (AWS Serverless) vs Apache Kafka
- Lambda (AWS Serverless) vs Redis
- Lambda (AWS Serverless) vs Postgres
- Lambda (AWS Serverless) vs Presto
- Lambda (AWS Serverless) vs Privacera
- Lambda (AWS Serverless) vs RavenDB
- Lambda (AWS Serverless) vs Readyset
- Lambda (AWS Serverless) vs Redpanda
- Lambda (AWS Serverless) vs Apache Airflow
- etcd vs Deno Deploy
- etcd vs Cerebrium
- etcd vs Serverless Framework
- etcd vs Neon
- etcd vs Beam Cloud
- etcd vs Upstash
- etcd vs Koyeb
- etcd vs Azure Functions
- etcd vs Lambda
- etcd vs Porter
- etcd vs Terragrunt
- etcd vs Heroku
- etcd vs HAProxy
- etcd vs K3s
- etcd vs Proxmox VE
- etcd vs Buildah
- etcd vs CloudAMQP
- etcd vs Rancher
- etcd vs DynamoDB
- etcd vs Timeplus
- etcd vs Firebase Realtime Database
- etcd vs Knack
- etcd vs Turso
- etcd vs BigQuery
- etcd vs TiDB
- etcd vs Dgraph
- etcd vs turbopuffer
- etcd vs Apache Kafka
- etcd vs Redis
- etcd vs Postgres
- etcd vs Presto
- etcd vs Privacera
- etcd vs RavenDB
- etcd vs Readyset
- etcd vs Redpanda
- etcd vs Apache Airflow
