A GIS desktop tool keeps long-lived local state, while a related web API should scale behind a load balancer. Which design principle should guide the web tier?
Select an answer to reveal the explanation.
Short Explanation
The web API should travel light—no stuffed suitcase under the seat—so ALB can hand requests to any healthy instance. The chunky GIS desktop can stay stateful; don’t pretend it scales like a stateless API.
Full Explanation
Horizontally scaled tiers should be stateless behind a load balancer, externalizing session or shared state as needed. Stateful desktop GIS workloads often cannot scale the same way and should not dictate sticky single-host designs for the API. Collapsing both onto one instance recreates a SPOF.