User opens app → feature store fetched in < 5ms from Redis → ranking model scores 100 candidates → top 10 shown.
Justification
Slightly stale recommendations are acceptable. Showing old rankings is better than showing an error. Always available.
ML System
Display
Key Insight
Most ML systems choose AP over CP. Stale recommendations beat error pages. Only fraud detection and feature stores need CP - where wrong data is worse than no data.
CAP Theorem Applied to ML Systems - Interactive Visualization
CAP theorem states distributed systems can guarantee at most two of: Consistency, Availability, Partition Tolerance. In ML systems, most real-time serving systems choose AP - stale recommendations are better than error pages. Fraud detection systems choose CP - using outdated transaction history could approve fraudulent transactions. Feature stores choose CP - training-serving skew from inconsistent features is one of the most costly ML production bugs. Understanding these choices is essential for senior ML engineering roles.
AP systems (recommendation, batch ML): availability over consistency - stale data is tolerated
CP systems (fraud detection, feature store): consistency over availability - wrong data is worse than no data
During partition: CP systems block writes, AP systems serve from cache or replica
Feature store consistency is especially critical - training-serving skew is a silent killer of model quality
Part of the EngineersOfAI Interactive 3D - free interactive visualizations covering every major concept in machine learning and AI engineering. Hover any element for a plain-English explanation. No code required.