Loading content
AWS Lambda is a serverless compute service that runs code in response to events and automatically manages the underlying compute resources in the AWS cloud. It enables developers to build event-driven applications without provisioning servers, scales automatically with demand, and integrates with many AWS services for production workloads.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
AWS Lambda is a serverless compute service in AWS that runs code in response to events and takes over operation, scaling, and maintenance of the underlying runtime environment.
AWS Lambda was introduced by Amazon as part of AWS and released on 13 November 2014. It emerged from the goal of running code without provisioning or managing servers: events should invoke functions while AWS handles runtime, capacity, scaling, and infrastructure maintenance. That shifted attention from server operations to application logic and service integration.
Think of Lambda as a reaction chain: an event arrives, a trigger invokes the function, AWS provides an isolated execution environment, and the handler runs. After the call, the environment may be reused or discarded. When traffic increases, AWS creates additional parallel environments; individual invocations remain independent and do not share persistent state.
Operation and scaling are handled by the cloud provider; the application defines only the logic to execute.
An event from an AWS service or API starts the function automatically.
The handler is the entry point where the business logic of one invocation runs.
Each invocation runs in an isolated runtime environment provisioned and managed by AWS.
More demand leads to more parallel executions instead of manual server sizing.
AWS Lambda is a good fit for event workloads, API backends, automation, and integrations where you want to avoid server management. Its value grows with irregular traffic and many short requests. Important limits still apply: invocations are independent, execution time is bounded, and tight coupling to AWS can reduce portability. For long-running or state-heavy processes, other services are often a better fit.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.