Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
45 results across 1 active filter
Page 2 of 2
Explains how to reprocess event streams safely for new projections, bug fixes, and data repair.
Designs saved filters, scheduled matching, alert delivery, and freshness trade-offs for search-driven product workflows.
Designs plan entitlements, provider webhooks, idempotent billing updates, access checks, grace periods, and support overrides.
Designs an invitation workflow with token security, expiry, membership creation, email delivery, and replay-safe onboarding.
Explains command messages versus event messages and how ownership changes their design.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Keeps long-running queue work safe when message ownership expires, renewal fails, settlement is uncertain, or another worker receives the same job.
Explains when to store large payloads outside the broker and pass references through messages.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Explains when backend work belongs in a queue instead of slow or unreliable inline request handling.
Preserves order only within the business key that requires it, while handling hot keys, gaps, stale events, replay, and poison messages explicitly.
Explains correlation IDs across request logs, dependency calls, queues, workers, and support investigations.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Explains how multiple worker instances share queue work and what limits safe scaling.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Explains how to investigate queue age, backlog, worker health, poison messages, dependency failures, and safe catch-up.
Explains saturation signals and how systems shed, queue, throttle, or degrade before cascading failure.
Explains delayed delivery, scheduled work, reminders, retry timing, cancellation, and clock-related trade-offs.
Makes consumer-side deduplication atomic with the business change while supporting concurrent delivery, retention, replay, and failed processing.
Explains event schema evolution, backward compatibility, additive changes, consumer rollout, and contract ownership.