Loading content
Serverless architecture is a cloud-native paradigm where applications run on fully managed services and event-driven functions without managing server infrastructure. It reduces operational overhead and enables elastic scaling, but introduces design trade-offs around cold starts, dependency management, cost model and potential vendor lock-in. Compared to tra…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Serverless architecture combines application code with managed cloud services and event-driven execution units while the provider operates servers and capacity.
The approach grew from separating infrastructure operations from application logic. AWS Lambda documents a typical form: events invoke functions, the platform provides runtime and scaling, and execution is billed according to use.
Treat serverless as a distribution of responsibilities, not as an absence of servers. The design comprises event sources, short-lived functions, managed stores, and explicit interfaces. Evaluate cold starts, runtime limits, idempotency, observability, and provider dependency before choosing it for a service.
The cloud provider operates the operating system, execution environment, and capacity provisioning.
Events invoke individual execution units coupled through APIs or messages.
Cold starts, runtime and resource limits, cost behavior, and lock-in shape suitability.
The approach can reduce operational work and idle cost, but requires deliberate designs for state, errors, retries, and tracing. Serverless architecture describes the overall structure; individual executions and billing are related but distinct concerns.
Where this building block is located in the topic model.
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.