Public works receives occasional Object Storage uploads of inspection photos and needs a short, stateless transform with scale-to-zero between jobs. Which runtime choice best fits?
Select an answer to reveal the explanation.
Short Explanation
When the job is a brief, triggered chore—like stamping a form when a photo lands—Functions shine: scale to zero and pay per invoke. Continuous listeners and heavy always-on processes belong elsewhere.
Full Explanation
Choose Oracle Functions when the unit of work is short, stateless, and event-triggered, and you do not want to operate replicas. Scale-to-zero and pay-per-invoke are the design point. Workloads that must listen all day, hold large in-memory models, or exceed Functions payload and time ceilings are a poor fit.