Concept map: ML system design
Prerequisites (two levels) and direct dependents of ML system design. Show everything
- 4prerequisites shown
- 0direct dependents
- 2lessons use it
Insights 16
- Unit-test monotone constraints with paired counterfactual rows instead of trusting the parameter
- Publish a score contract that says whether the number is a probability, a rank or a margin, and how it was calibrated
- Generate load at a fixed arrival rate when load-testing a scoring service, not one request after another
- Design a degraded mode for when upstream features are late or missing
- Scale governance effort to the risk tier of each model
- Compare managed and self-hosted ML platforms on total cost including people
- Use batch scoring when decisions are made on a schedule
- Look for hidden feedback loops when a model influences its own future training data
Projects 4
- Data validation, drift monitoring and a retrain decision for a booking forecast with delayed labels
- Weekly batch forecasting platform for tens of thousands of item-store series
- Real-time call-prioritisation scoring: serving contract, training-serving skew and safe rollout
- LLM question-answering service: versioned golden set, regression gate and request observability
List view151 concepts
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 11
Day 12
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Day 19
Day 21
Day 22
Day 23
Day 24
Day 25
Day 26
Day 27
Day 28
Day 29
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
Day 49
Day 51
Day 52
Day 53
Day 54
Day 55
Day 58
Day 59
Day 60