A city is designing a new mobile 311 API. Engineers are debating services before agreeing how success will be measured. What methodology should lead the design?
Select an answer to reveal the explanation.
Short Explanation
Don’t buy tools before you know what ‘fast enough’ means. Nail p99 latency and friends first, then pick AWS services that can hit those marks for 311.
Full Explanation
A sound selection methodology defines measurable KPIs and business tasks before choosing services. Leading with popularity, skipping NFRs, or copying architectures without local metrics produces misfit designs. Establishing p99 latency and related objectives first guides purpose-built service choices for the mobile 311 API.