Freshness Is a Consumer Clock
Design a freshness check around consumer need, snapshot frequency, and failure behavior.
The move: freshness is a promise to the consumer, not a badge on the job. Pick the timestamp that carries truth Use the event or load timestamp that represents source recency. A warehouse ingestion timestamp may tell you when the file landed, while an event timestamp may tell you when the business action happened. Choose deliberately and document the difference. Match check frequency to risk A freshness SLA needs a snapshot cadence that can catch problems in time. A one-hour freshness promise cannot be checked once per day. The check should run often enough that someone can still mitigate before…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in