Loading
Pick a focused question that fits your time, stack, and interview goal.
94 results across 1 active filter
Page 3 of 4
Stores an idempotency key, request hash, and response in the same transaction as the created resource.
Implements descending keyset pagination in LINQ using a compound timestamp-and-id cursor.
Explains stable EF Core pagination using cursor predicates, deterministic ordering, and index-aligned queries.
Processes a large import in chunks with fresh DbContexts, idempotent keys, cancellation, and bounded tracker growth.
Explains `Include` versus `Select` in EF Core with practical .NET data-access examples and production trade-offs.
Verifies the exact request bytes, rejects stale signatures, deduplicates event ids, and queues processing durably.
Explains how to inspect EF Core generated SQL and connect LINQ shape to database execution behavior.
Investigates a growing-data EF Core slowdown through one correlated request, generated SQL, representative parameters, execution plan, waits, query shape, measured repair, and guarded rollout.
Explains `IQueryable` versus `IEnumerable` in EF Core with practical .NET data-access examples and production trade-offs.
Compares rollback, reset, schema, database, and tenant isolation without hiding transaction or parallelism limits.
Explains transaction isolation levels with practical .NET data-access examples and production trade-offs.
Explains when LINQ is enough, when raw SQL is clearer, and how to keep raw SQL safe and maintainable.
Explains LINQ translation boundaries with practical .NET data-access examples and production trade-offs.
Uses `AsSplitQuery` deliberately for a tracked aggregate with multiple collections and explains its consistency boundary.
Relies on a database unique constraint and translates only the expected provider error into a domain conflict.
Explains multi-tenant data filtering with practical .NET data-access examples and production trade-offs.
Explains offset versus cursor pagination with practical .NET data-access examples and production trade-offs.
Designs an EF Core optimistic-concurrency contract around tokens, conflict policy, HTTP semantics, merge behavior, and real relational tests.
Uses a transactional outbox to make a local state change durably publishable while accepting at-least-once delivery and operating the backlog safely.
Chooses between EF Core complex types, owned entities, and regular entities from value semantics, identity, ownership, querying, and storage needs.
Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.
Builds a read-only EF Core projection with aggregates, stable ordering, and bounded results instead of loading an entity graph.
Explain why request cancellation should flow into EF Core queries and where it does or does not help.
Carries the ASP.NET Core request token into a bounded EF Core query while keeping cancellation separate from business rollback guarantees.