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

Lambda (AWS Serverless)
Cloud
Run code without thinking about servers
- From
- Free
- Free plan
- Yes
Memcached
Databases
Distributed memory object caching system
- From
- Free
- Free plan
- Yes
The short version
- Both are free.
- Only Lambda (AWS Serverless) lists event-driven execution; only Memcached lists in-memory key-value cache.
- 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 Memcached falls short: no persistence at all: restart a node and its cache is gone, which every design must assume.
- Prices and features on this page were last checked on 13 November 2026.
How do Lambda (AWS Serverless) and Memcached differ?
Lambda (AWS Serverless) and Memcached differ on pricing model, platforms and category (Cloud against Databases). Only the attributes on which Lambda (AWS Serverless) and Memcached actually diverge.
| Attribute | Lambda (AWS Serverless) | Memcached |
|---|---|---|
| Pricing model | Usage-based | Open source, no licence fee; managed cloud billed separately |
| Platforms | Web, API | Linux, macOS, Windows, Self-hosted |
| Category | Cloud | Databases |
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for Memcached.
Which features does each one have?
They share no listed features; 20 appear only for Lambda (AWS Serverless) and 4 only for Memcached. 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 Memcached
- In-memory key-value cache
- Multithreaded
- Client-side sharding
- Predictable memory use
What is each one used for?
Lambda (AWS Serverless) is most often brought in for event-driven functions without managing servers; Memcached for caching expensive database query results to cut load. The jobs each tool is most often brought in to do.
Lambda (AWS Serverless)
- Event-driven functions without managing serversnot Memcached
- API backends behind API Gatewaynot Memcached
- Processing S3, DynamoDB, SQS and Kinesis eventsnot Memcached
- Scheduled jobs without a always-on instancenot Memcached
- Edge compute through Lambda@Edgenot Memcached
Memcached
- Caching expensive database query results to cut loadnot Lambda (AWS Serverless)
- Session storage where losing sessions on restart is acceptablenot Lambda (AWS Serverless)
- Fronting an API whose responses are costly and change slowlynot Lambda (AWS Serverless)
Where do Lambda (AWS Serverless) and Memcached fall short?
Lambda (AWS Serverless)'s most cited limit: ephemeral storage beyond the included 512 MB is metered. Memcached's: no persistence at all: restart a node and its cache is gone, which every design must assume. 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
Memcached
- No persistence at all: restart a node and its cache is gone, which every design must assume
- No replication or failover, so losing a node loses that share of the cache
- Only simple key-value, with none of the lists, sorted sets or streams Redis offers
- Values are capped at 1MB by default, which surprises teams caching large documents
How much do Lambda (AWS Serverless) and Memcached cost?
Lambda (AWS Serverless) is free to use; Memcached 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
Memcached
Free- MemcachedFree
- Full functionality
- Self-hosted
- No usage limits
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 Memcached if
- You need in-memory key-value cache.
- You want to start without paying.
- You work on Linux, macOS, Windows, Self-hosted.
- You also want multithreaded.
Questions people ask
- Is Lambda (AWS Serverless) or Memcached better?
- Neither clearly leads. Lambda (AWS Serverless) starts at Free and Memcached at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Lambda (AWS Serverless) or Memcached?
- Lambda (AWS Serverless) starts at Free and Memcached at Free.
- Does Lambda (AWS Serverless) or Memcached run on more platforms?
- Lambda (AWS Serverless) runs on Web, API. Memcached runs on Linux, macOS, Windows, 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 Memcached is typically brought in for.
- What can Lambda (AWS Serverless) do that Memcached cannot?
- Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use.
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.
SourceMemcached: Is Memcached free?
Yes, open source with no licence fee.
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.
SourceMemcached: Memcached or Redis?
Memcached is a pure cache: simpler, multithreaded and very predictable. Redis adds persistence, replication and rich data structures, which is why it is the default choice unless you specifically want a cache and nothing more.
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).
SourceMemcached: Does Memcached persist data?
No. Everything is in memory and lost on restart, by design.
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 Redis
- Lambda (AWS Serverless) vs Dragonfly
- Lambda (AWS Serverless) vs Valkey
- Lambda (AWS Serverless) vs Readyset
- Lambda (AWS Serverless) vs PostgreSQL
- Lambda (AWS Serverless) vs DuckDB
- Lambda (AWS Serverless) vs DynamoDB
- Lambda (AWS Serverless) vs NATS
- Lambda (AWS Serverless) vs Apache Pulsar
- Lambda (AWS Serverless) vs Presto
- Lambda (AWS Serverless) vs Timeplus
- Lambda (AWS Serverless) vs DataGrip
- Lambda (AWS Serverless) vs Firebolt
- Lambda (AWS Serverless) vs Google Cloud SQL
- Lambda (AWS Serverless) vs QuestDB
- Lambda (AWS Serverless) vs Apache Kafka
- Lambda (AWS Serverless) vs Cassandra
- Lambda (AWS Serverless) vs CouchDB
- Memcached vs Deno Deploy
- Memcached vs Cerebrium
- Memcached vs Serverless Framework
- Memcached vs Neon
- Memcached vs Beam Cloud
- Memcached vs Upstash
- Memcached vs Koyeb
- Memcached vs Azure Functions
- Memcached vs Lambda
- Memcached vs Porter
- Memcached vs Terragrunt
- Memcached vs Heroku
- Memcached vs HAProxy
- Memcached vs K3s
- Memcached vs Proxmox VE
- Memcached vs Buildah
- Memcached vs CloudAMQP
- Memcached vs Rancher
- Memcached vs Redis
- Memcached vs Dragonfly
- Memcached vs Valkey
- Memcached vs Readyset
- Memcached vs PostgreSQL
- Memcached vs DuckDB
- Memcached vs DynamoDB
- Memcached vs NATS
- Memcached vs Apache Pulsar
- Memcached vs Presto
- Memcached vs Timeplus
- Memcached vs DataGrip
- Memcached vs Firebolt
- Memcached vs Google Cloud SQL
- Memcached vs QuestDB
- Memcached vs Apache Kafka
- Memcached vs Cassandra
- Memcached vs CouchDB
