A city’s overnight pipelines occasionally stall silently, ship broken schemas, or spike in volume without alerts. What should architecture include among non-functionals?
Select an answer to reveal the explanation.
Short Explanation
If the night truck never arrives and nobody’s pager buzzes, leadership still drives with yesterday’s map. Architect for freshness, schema-break, and volume alarms—not just server CPU smileys.
Full Explanation
Data observability covers whether pipelines meet freshness SLOs, whether schemas change unexpectedly, and whether volumes deviate from norms that may signal upstream failure or abuse. Architecture that omits these signals discovers incidents through wrong decisions rather than controlled alerts. Non-functional requirements should fund monitors, ownership, and response playbooks alongside storage and compute.