Serverless Computing
Serverless Computing is hosted code execution. The provider starts and scales servers, while the team deploys functions or services.
Another example
An image function runs when a file arrives. It scales during bursts and sends failed jobs to a retry queue.
Main parts
- 01Originating request
- 02Resolution or processing hop
- 03Response, timing, and failure
Use it when
Use it for events or uneven traffic when automatic scaling is worth the platform limits.
Do not use it when
Servers still exist. Plan for cold starts, limits, and the cost of leaving one provider.
Name used in code
event trigger + managed runtime + autoscaling Before you ship
Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback.
Outcome: Design or review Serverless Computing for this system while keeping data correct, secure, and easy to operate. User context: An image function runs when a file arrives. It scales during bursts and sends failed jobs to a retry queue. Technical concept or control: Serverless Computing. Why it fits: Use it for events or uneven traffic when automatic scaling is worth the platform limits. Do not use it when: Servers still exist. Plan for cold starts, limits, and the cost of leaving one provider. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.
Check this request
Review the current use of Serverless Computing. Definition: Serverless Computing is hosted code execution. The provider starts and scales servers, while the team deploys functions or services. Release checks: Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.