Follow-up · depth 9
How do you make Eager vs Explicit Loading safer under partial failure?
How do you make Eager vs Explicit Loading safer under partial failure?
Answers use simple, clear English.
Quick interview answer
Harden Eager vs Explicit Loading with timeouts, retries with jitter, isolation, and graceful degradation. Mitigate first, then root-cause. Check symptoms against: Lazy loading enabled globally causing hidden N+1 in foreach..
Detailed answer
Resilience for Eager vs Explicit Loading under partial failure: • Timeouts + budgets on every dependency call • Retries only when idempotent, with jitter/backoff • Isolation: bulkheads/queues so one failure does not cascade • Degradation: serve stale/cached/limited mode when needed Practices: Prefer Select projection DTOs; AsSplitQuery for multiple collections. Parent context: Mitigate first, then root-cause. Check symptoms against: Lazy loading enabled globally causing hidden N+1 in foreach..
Full explanation
Partial failure is the default in distributed systems — show how Eager vs Explicit Loading stays useful anyway. Include/ThenInclude eager-loads related data in one query. Explicit loading: reference/load after query. Avoid lazy loading in web apps (N+1 in loops).
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — Eager vs Explicit Loading
Mitigate first, then root-cause. Check symptoms against: Lazy loading enabled globally causing hidden N+1 in foreach..
View full parent question →