Emergency outage maps must refresh within minutes, while annual grant audits tolerate day-old extracts. What should architecture do with that difference?
Select an answer to reveal the explanation.
Short Explanation
A fire-truck GPS ping and a yearly filing cabinet aren’t the same rush order. Match pipelines and patterns to the latency class—near-real-time for outage maps, batch-friendly for annual audits—instead of one speed for everything.
Full Explanation
Non-functional latency and freshness requirements drive architecture choices for ingestion, processing, and serving layers. Emergency situational awareness often needs near-real-time movement, whereas periodic audits may be well served by scheduled extracts. Differentiating by SLA class avoids both over-engineering calm workloads and under-serving urgent ones.