Review EF Core migrations as database changes
Review generated EF Core operations, inspect the deployment SQL, and check application compatibility before applying schema changes.
Reliability
Treat the model finish reason as a control signal
Check why generation stopped before accepting model output, and give incomplete responses an explicit application outcome.
Persist ingestion checkpoints at source boundaries
Track progress per consumer and source ordering boundary, and advance each checkpoint only after the corresponding ingestion work succeeds.
Treat provider throttling as a shared capacity signal
Let one throttling response reduce pressure from every caller sharing the affected capacity pool.
`await foreach` does not automatically use your cancellation token
A CancellationToken in scope does nothing unless the async enumeration receives and observes it.
Run production evaluations outside the user response path
Hand production samples to a separate evaluation worker instead of making users wait for an evaluator model.
AI Systems Need Runtime Budgets
How to bound time, tokens, retries, tool calls, and estimated cost across a complete AI execution instead of limiting each call in isolation.
Return Retry-After when a client should back off
Tell API clients when another attempt may succeed instead of leaving them to guess a retry delay.
Choose histogram boundaries from the service objective
Put the latency objective into the histogram boundaries so compliance can be calculated without interpolating between buckets.
Use concurrency tokens to detect lost updates
Make stale writes fail explicitly instead of silently overwriting newer database state.