Question

A team runs an image-processing function that is triggered only when users occasionally upload photos. Between uploads, there can be hours of no activity, and the team wants to avoid paying for idle compute while still handling sudden bursts of uploads automatically. Which cloud native architectural approach best fits these requirements?

Accepted Answer

A serverless (Function-as-a-Service) model that scales to zero when idle and scales out automatically on incoming events

Answer

A monolithic application deployed on a fixed-size cluster of always-on virtual machines

Answer

A StatefulSet with a fixed replica count sized for peak upload volume

Answer

A DaemonSet running one processing pod on every node in the cluster at all times