Loading
Pick a focused question that fits your time, stack, and interview goal.
45 results across 1 active filter
Page 1 of 2
Explains partition key selection for ordering, load distribution, hot keys, and consumer scalability.
Compares point-to-point queues with publish-subscribe topics and explains when each model fits.
Compares Redis pub/sub with durable queues when broadcasting cache invalidation or refresh events.
Diagnose a growing queue backlog in an Azure-based background processing system.
Traces duplicate side effects across message delivery, lock ownership, settlement, durable job state, and external idempotency, then repairs affected users safely.
Diagnose missing trace continuity when an API enqueues work processed by an Azure worker.
Investigate messages that repeatedly fail and move to a poison queue or dead-letter queue.
Designs an async export flow for large reports without blocking API requests or exhausting database and memory resources.
Designs explicit workflow states, allowed transitions, guard rules, audit history, idempotency, and operational repair paths.
Explains useful message metadata for tracing, idempotency, ownership, versioning, and support diagnostics.
Explains how EF Core SaveChanges, transactions, and an outbox keep database changes and messages consistent.
Designs a checkout or order creation flow that survives client retries without duplicate orders, payments, or messages.
Designs email, in-app, and push-style notification delivery with preferences, retries, and idempotent side effects.
Designs synchronization with an external system using cursors, retries, idempotency, rate limits, and reconciliation.
Designs a multi-service business workflow using local transactions, durable progress, idempotency, retries, and domain-specific compensation.
Designs authenticated, replay-resistant webhook intake with durable acknowledgement, idempotent asynchronous processing, ordering policy, and reconciliation.
Designs a safe admin import flow with upload staging, validation, preview, confirmation, idempotency, and rollback strategy.
Designs comments with permissions, threading, mentions, notifications, editing history, and moderation concerns.
Designs deletion, retention, soft delete, hard delete, backups, audit records, and asynchronous cleanup across related data.
Explains why message handlers must tolerate duplicate delivery and how idempotency protects side effects.
Explains how systems behave when the broker is down or slow and how backpressure protects callers and dependencies.
Designs user preferences, channel rules, unsubscribe behavior, digest generation, and delivery suppression.
Designs scheduled jobs with locking, idempotency, observability, retries, and safe operations across multiple instances.
Explains retry strategy for transient failures and poison-message handling for permanent failures.