Concept map: Batch vs online serving and deployment
Prerequisites (two levels) and direct dependents of Batch vs online serving and deployment. Show everything
- 2prerequisites shown
- 4direct dependents
- 3lessons use it
Insights 29
- Compare candidate and incumbent per slice before shipping an aggregate improvement
- Use feature hashing when the vocabulary keeps growing, and accept what it gives up
- Plan model API capacity in tokens per minute, and count what your provider counts
- Shadow a candidate on mirrored production requests before it serves any user
- Generate load at a fixed arrival rate when load-testing a scoring service, not one request after another
- Treat a pickled model file as executable code and control who can write the artifact path
- Keep unbounded identifiers out of metric labels and log them as events instead
- Design a degraded mode for when upstream features are late or missing
Projects 12
- Passenger no-show probabilities for overbooking and reconfirmation decisions
- Card-fraud alerts under a fixed review budget: ranking on day 1, tested on day 2
- Structured extraction from disruption notices: JSON-schema validation, safe repair and injected-instruction detection
- Tool-calling agent vs deterministic workflow for rebooking proposals after a cancellation
- Golden-set regression suite that gates prompt changes for a claims-intake triage assistant
- Cost and latency routing study: small model, large model, router and cascade on checkable answers
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