Serverless & FaaS
How functions run and are operated across cloud providers and edge runtimes: sandboxes, cold starts, scaling limits, event delivery, workflows, deployment and the bill.
on this pageshowhide
explore
- Function Sandbox Lifecycle6 questions
- Cold-Start Measurement & Tuning5 questions
- Scaling Limits & Throttling5 questions
- Event Delivery & Retries6 questions
- Function Workflow Orchestration5 questions
- Function Platforms Compared5 questions
- Function Deployment & Operations5 questions
- Function Cost & Trade-offs4 questions
questions
page 2 of 2Before a ticket sale expected to send fifty times normal traffic within a minute, how would you load-test a function-backed API to expose its scaling limits?
basics
~20 sReplay the ramp, not just the peak: climb from normal to fifty times inside a minute, starting cold, in an environment with production's quotas but not its shared pool, and watch throttles, cold-start share, latency and every downstream.
A function that writes its result into the same storage bucket that triggers it ran up a large bill overnight; what happened, and what stops it recurring?
basics
~20 sEach result written to the bucket fired the trigger again, so the function looped and scaled out until a limit or a person stopped it. Write output elsewhere, cap concurrency and alarm on invocation rate; billing alerts lag by hours.
After a weekend downstream outage failed thousands of asynchronous order-event invocations, how do you find every failed event and redrive it safely once the fix ships?
basics
~20 sCount three groups: events in the failure destination, events dropped before reaching it, and half-applied ones. Reconcile against the order store, test one replay, then redrive through the normal path at a controlled rate, parking superseded events.
Why might a queue-triggered function process some messages twice with no invocation failing, and how do the function timeout and the queue's visibility timeout explain it?
basics
~20 sA received message is hidden for the queue's visibility timeout and deleted only after success. If processing outlasts that timeout and nothing renews it, the message reappears and a second invocation runs it while the first is still working.
Why do in-flight executions of a days-long hosted workflow fail after you deploy a new version, and how do you ship workflow changes safely?
basics
~20 sExecutions started before the deploy resume against changed code: replayed workflow code requests different steps than their history recorded, or steps call the newest function version with old-shaped input. Gate changes by version, pin step targets, and drain old executions.
As a platform lead, how would you choose the function platform your organisation standardises on, and when would you allow a second one?
basics
~20 sStandardise on the regional function platform of the cloud already holding your data, identity and network, with a paved road around it. Allow a second platform, such as an edge runtime, only for a workload class the default cannot serve, with an owner.
For a ticket sale that will send fifty times normal traffic to a function-backed API, how do you decide between raising quotas, pre-starting capacity and metering users in?
basics
~20 sWeigh what a throttled launch costs against what idle capacity and a waiting room cost. A quota raise lifts the ceiling, pre-started capacity skips the ramp but bills while idle, and metering protects every downstream at the price of user waits.
A steady, always-busy API has run on functions for years and its bill keeps growing; what evidence would make you move it to containers, and would you move all of it?
basics
~20 sMove when the evidence shows a steady concurrency floor, pre-provisioned capacity covering it, and full-bill cost per request above a realistic container estimate including operations work. Usually move only the steady hot path and keep event-shaped work on functions.
What event-delivery defaults should a platform team enforce for every asynchronously triggered function in an organisation, and what does each default cost the teams?
basics
~20 sMandate a failure destination with an owned alarm, enough retention and timeout ordering checks on every asynchronous function; derive retries and event age from declared side effects and freshness. The costs are alarm noise, storage, pipeline friction and exceptions.
Should a platform team standardise multi-step function jobs on a hosted workflow engine or keep coordination in application code, and what decides it?
basics
~20 sStandardise on a hosted engine for long, branching, waiting or fan-out workflows where per-execution history and built-in retries pay off; keep short, high-volume chains in code. Weigh per-step cost, definition-language lock-in and team discipline, not features alone.
A platform team must run customers' untrusted code as functions; how do you choose between microVMs, isolates and hardened containers as the sandbox?
basics
~20 sChoose by the code you accept and the risk you can carry: arbitrary binaries need a microVM per tenant, single-language scripts can share isolate processes, containers need an extra kernel layer. Whatever you pick, never reuse a sandbox across tenants.
showing 31–41 of 41