A single VM that polls Meraki sites and transforms JSON for a water…

Question

A single VM that polls Meraki sites and transforms JSON for a water-utility dashboard is CPU-saturated. The workers are designed to be identical and stateless behind a load balancer. Which scaling direction matches that constraint?

Accepted Answer

Scale out by adding more identical, load-balanced workers instead of only enlarging one VM — When one kitchen is slammed, hiring more cooks who share the same recipe beats buying one giant stove that still has one pair of hands. Stateless Cisco-API workers scale horizontally behind the balancer. A bigger single VM hits a ceiling.

Answer

Replace the fleet with one oversized bare-metal host that never load-balances

Answer

Move the poller into the clerk’s browser so each user absorbs transform cost

Answer

Pin all polling to a single thread and raise that one process’s memory ceiling only

A single VM that polls Meraki sites and transforms JSON for a water-utility dashboard is CPU-saturated. The workers are designed to be identical and stateless behind a load balancer. Which scaling direction matches that constraint?

Short Explanation

Full Explanation