Serverless
Scale to zero, per-request billing, cold starts and connection limits.
4 to work through
-
intermediate
A news organisation's publishing pipeline runs rarely during quiet periods and intensely around major events, performing image processing, rendering and distribution. Where does serverless fit, and where would it be a mistake?
2 min answer -
intermediate
A team is choosing between serverless functions and long-running containers for a new workload. What evidence should drive the decision, and which arguments on both sides are usually wrong?
2 min answer -
advanced
A serverless GPU platform has workloads with very expensive startup costs. How should predictive scaling, prewarming, scheduled capacity, autoscaling and queue-based smoothing be compared?
2 min answer -
advanced
A spike causes a function to fan out to 5000 concurrent executions. The database's connection limit is exhausted and everything fails. What are your options?
2 min answer
3 terms in this topic
Cold-Start Amortisation
Attacking the startup cost itself - through snapshots, lazy image pulls, local artefact caches and affinity routing - rather than choosing between sc…
conceptServerless Cold Start
The additional latency when a function invocation must allocate and initialise a new execution environment rather than reusing a warm one.
conceptServerless Compute in Practice
Compute billed per invocation with no capacity to manage — excellent for bursty low-duty-cycle work, expensive and constrained for sustained load.
Neighbouring topics
Cloud Architecture
General material on designing for cloud platforms.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Cloud Storage
Object, block and file storage, and the access patterns each suits.
Cloud Databases
Managed relational, key-value, document and analytical services.
Containers
Images, registries, immutability and the deployment model they enable.
Kubernetes
The reconciliation loop, and whether the workload needs what it provides.
Autoscaling
Signals, delays and bounds — and the maximum that caps a runaway bill.
Load Balancing
Distributing traffic, health checking, and removing failures from rotation.
Multi-Region Architecture
Surviving a region, and the data consistency price of doing so.
Availability Zones
The unit of correlated physical failure, and what zones do not protect against.
Disaster Recovery
Backup-restore, pilot light, warm standby and active-active postures.
Backup Strategies
Scope, immutability, separation, and the restore drill that makes it real.
Infrastructure as Code
Declarative infrastructure, drift, state files and rebuild-from-empty.
Landing Zones
A governed foundation of accounts, network, identity and guardrails.
Managed Services
Which operational responsibilities actually transfer, and which do not.
Cloud Migration
Per-application disposition, sequencing and the capability change underneath.
Multi-Cloud
Best-of-breed, portfolio and portable — three very different costs.
Edge Computing
Moving compute towards the user, and what cannot follow it.
Cloud Governance
Preventive policy, tagging, quotas and cost and security guardrails.