DevOps & Cloud

AWS Lambda

AWS Lambda runs code in response to events without provisioning servers, billing per millisecond of execution. It integrates natively with the broader AWS ecosystem for triggers and permissions.

Pros

  • True pay-per-use. Idle functions cost nothing; billing is per-millisecond of execution. 0
  • Automatic scaling. Thousands of concurrent executions spin up without capacity planning. 0
  • Deep AWS integration. S3, SQS, and API Gateway trigger functions natively. 0
  • No server patching. AWS manages the runtime, OS, and security updates. 0

Cons

  • Cold start latency. Idle functions add hundreds of milliseconds on first invocation. 0
  • 15-minute ceiling. Long-running work must be split or moved elsewhere. 0
  • Vendor lock-in. Event formats and IAM wiring are AWS-specific. 0
  • Local testing friction. Faithfully emulating triggers and permissions locally is hard. 0
  • Cost cliffs at scale. Constant high traffic often costs more than containers. 0

Compare AWS Lambda against