How do you guarantee online-offline feature consistency?
hardAnswer
- (1) Single source of truth for feature definition (code + config).
- (2) Compute both paths from same definition: batch compute (offline) + streaming compute (online) share transformation logic.
- (3) Automated parity checks: sample production requests, recompute offline, compare.
- (4) Alert on divergence.
- (5) Feast / Tecton implement this via 'feature views'.
- (6) Ideal: same code runs in both contexts (Python function transpiled to SQL + streaming).
- Anti-pattern: hand-write both paths → drift.
Check yourself — multiple choice
- Random
- Single source of truth for feature def; compute both paths from same def + automated parity checks (sample + recompute + compare) + alert on divergence; Feast/Tecton feature views
- Impossible
- Just monitor
Online-offline consistency: single def + parity checks + alerting.
#features#data-quality
Practise MLOps & Data Quality
215 interview questions in this topic.
Related questions
- How do you handle missing values in a production pipeline?
- What is point-in-time correctness in feature stores?
- How do you prove there is no training-serving skew?
- What is point-in-time correctness, and how does violating it look in practice?
- What is data drift and how do you detect it?
- How is concept drift different from data drift?