Serverless

System composed of managed, event-triggered functions instead of long-running services — see Compute/Serverless for the execution-model angle.

Why we need this / what value this brings

Zero idle cost and no server management — you pay only for actual invocations, ideal for bursty or infrequent workloads.

When to use this

For event-triggered, stateless, short-lived work — not for long-running processes or workloads needing persistent in-memory state.

How to use or implement this

Identify natural event triggers (file upload, scheduled time, incoming webhook) and implement each as an independent function rather than a monolithic handler.

Research questions

• Which Localz workflows are naturally serverless-shaped (image resize on upload, scheduled reminder emails)?

---

Empty folder — drop notes, links, and findings here as you research.