Serverless computing describes a cloud execution model where applications run in provider-managed runtime environments and developers do not manage server infrastructure. It emphasizes event-driven functions, automatic scaling and pay-per-use billing, reduces operational burden and alters architectural and development decisions across teams and organizations…
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 computing is a cloud execution model in which the provider operates, provisions, and scales the computing environment and charges according to use.
The term describes cloud computing moving toward more abstract execution services. CNCF presents serverless as a model in which users run code or containers without provisioning or continuously operating server capacity themselves.
Separate the execution model from the architecture: serverless computing describes how compute is consumed; serverless architecture describes how components and data flows are structured. Functions, containers, events, and managed services may all participate. Assess limits, startup latency, runtime, sustained-load cost, and portability.
Provisioning, patching, and capacity adjustment of underlying servers are handled by the cloud provider.
Compute instances start and scale in response to events or requests.
Usage-based pricing can suit sporadic load but is not automatically cheaper for sustained high utilization.
Serverless computing shifts operational responsibility and cost structure. A sound decision considers runtime limits, data handling, security, observability, and provider dependence.
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.