A recreation registration API keeps shopping-cart selections only in server memory on one instance; scaling out drops carts mid-checkout. What change best aligns with a stateless compute pattern?
Select an answer to reveal the explanation.
Short Explanation
Leaving the cart only in one server's head is like keeping a sticky note on one clerk's monitor — hire a second clerk and the note is gone. Park the cart in a shared store or cache so any instance can pick it up. That is what "stateless compute" really means here.
Full Explanation
Stateless application tiers externalize session or cart state so compute instances can scale horizontally without losing user progress. Sticky sessions and larger RAM still couple users to a single failure domain. Copying in-memory maps without a shared source of truth creates inconsistent carts. DynamoDB or ElastiCache are common in-scope choices for shared ephemeral or durable session state.