skip to content

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 pageshow

questions

page 2 of 2

Before 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?

level: seniorimportance: should knowfreq 45%

basics

~20 s

Replay 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.

open as a page

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?

level: seniorimportance: should knowfreq 58%

basics

~20 s

Each 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.

open as a page

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?

level: seniorimportance: should knowfreq 50%

basics

~20 s

Count 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.

open as a page

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?

level: seniorimportance: should knowfreq 48%

basics

~20 s

A 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.

open as a page

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?

level: seniorimportance: should knowfreq 35%

basics

~20 s

Executions 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.

open as a page

As a platform lead, how would you choose the function platform your organisation standardises on, and when would you allow a second one?

level: principalimportance: should knowfreq 24%

basics

~20 s

Standardise 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.

open as a page

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?

level: principalimportance: should knowfreq 32%

basics

~20 s

Weigh 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.

open as a page

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?

level: principalimportance: should knowfreq 45%

basics

~20 s

Move 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.

open as a page

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?

level: principalimportance: should knowfreq 32%

basics

~20 s

Mandate 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.

open as a page

Should a platform team standardise multi-step function jobs on a hosted workflow engine or keep coordination in application code, and what decides it?

level: principalimportance: should knowfreq 30%

basics

~20 s

Standardise 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.

open as a page

A platform team must run customers' untrusted code as functions; how do you choose between microVMs, isolates and hardened containers as the sandbox?

level: principalimportance: nice to knowfreq 25%

basics

~20 s

Choose 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.

open as a page

showing 31–41 of 41