---
title: "Lambda | Skills We Assign For | Azendo"
description: "AWS Lambda for event-driven work — where serverless fits, cold starts and cost, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/lambda/"
---

[Skills](https://azendo.co/skills/) Cloud and infrastructure 

# Lambda.

AWS Lambda runs code in response to events without provisioned servers. It scales automatically, bills per millisecond of execution, and imposes limits on duration, memory and package size that shape what belongs in it.

## Where Lambda fits on a long engagement.

Lambda is excellent for spiky, event-driven, short-lived work. A function triggered by an upload, a queue message or a schedule costs nothing when idle and scales without capacity planning, which for irregular workloads is a genuinely better model than a running server.

It is a poor fit for sustained high-throughput work, where per-invocation billing exceeds what a reserved instance would cost, and for anything long-running or latency-critical where cold starts matter. The failure mode is architectural: hundreds of functions with tangled event relationships that nobody can trace end to end.

## What an assigned team does with Lambda.

Serverless moves complexity rather than removing it. There is no server to patch, but there is a large amount of configuration, permission and event wiring, and a distributed system whose control flow lives in infrastructure rather than in code.

Keeping that traceable needs deliberate observability from the start, scoped alongside the application capacity under [devops managed services](https://azendo.co/services/cloud-and-devops/).

## What we use Lambda for.

* Irregular event-driven work Uploads, webhooks and scheduled jobs where idle capacity would otherwise be paid for.
* Cost compared honestly against instances Sustained workloads measured both ways, because per-invocation billing is not always cheaper.
* Event flow that can be traced Instrumentation across function boundaries, so the control flow is followable.

## How Lambda capacity is assigned.

The cost comparison against provisioned capacity is done at scoping rather than assumed, which is part of [how an assignment runs](https://azendo.co/how-it-works/).

## Roles we assign Lambda for

* [Cloud Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/cloud-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in cloud and infrastructure

* [Terraform — skill we assign for](https://azendo.co/skills/terraform/)
* [AWS — skill we assign for](https://azendo.co/skills/aws/)
* [Azure — skill we assign for](https://azendo.co/skills/azure/)
* [GCP — skill we assign for](https://azendo.co/skills/gcp/)
* [Terraform modules — skill we assign for](https://azendo.co/skills/terraform-modules/)
* [Pulumi — skill we assign for](https://azendo.co/skills/pulumi/)
* [CloudFormation — skill we assign for](https://azendo.co/skills/cloudformation/)
* [Crossplane — skill we assign for](https://azendo.co/skills/crossplane/)

## Tell us what your roadmap needs Lambda for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)