Pick a focused question that fits your time, stack, and interview goal.
19 results across 1 active filter
Page 1 of 1
Explains how tenant query filters help, where they can be bypassed, and what extra safeguards protect tenant isolation.
Explains batching, tracking control, idempotency, validation, and operational safety for large EF Core imports.
Explains how EF Core SaveChanges, transactions, and an outbox keep database changes and messages consistent.
Maps an HTTP ETag precondition to EF Core rowversion and returns 412 when the representation is stale.
Performs a set-based bulk update without loading session entities into the change tracker.
Uses the client's original rowversion to detect a lost update and return a deliberate conflict response.
Makes EF Core transient retries safe across transactions, uncertain commits, generated keys, and external side effects.
Explains optimistic concurrency with EF Core rowversion tokens, API conflict responses, and safe retry boundaries.
Explains why application-level duplicate checks are not enough and how EF Core APIs map database constraints to friendly errors.
Validates a bounded command set completely before applying all updates in one SaveChanges transaction.
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Processes a large import in chunks with fresh DbContexts, idempotent keys, cancellation, and bounded tracker growth.
Relies on a database unique constraint and translates only the expected provider error into a domain conflict.
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Attaches a key-only stub and marks one property modified for a narrow update while naming the rules this pattern bypasses.
Explains when set-based EF Core updates are better than loading entities and where lifecycle behavior can differ.