Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
23 results for “Dead Letter Handling”
Dead Letter Queue
A separate queue that receives messages which could not be processed after a set number of attempts, so they neither block the consumer nor disappear.
Poison Message
A record that a consumer cannot process and cannot skip, which halts its partition entirely until someone intervenes.
Enterprise Integration Patterns
A catalogue of named, composable messaging patterns — router, translator, aggregator, splitter, filter, dead letter channel — that gives integration work a shared vocabulary.
Ambiguity Tolerance
The capacity to make progress on a problem before it is fully specified, which is the normal condition of architectural work.
Disagree and Commit
A convention in which a participant states their objection, accepts the decision once made, and supports its execution fully.
Fan-Out Delivery
Delivering one published message to many independent subscribers, each with its own copy, position and failure handling.
Geo-Blocking Accuracy
The reliability of determining a user's jurisdiction from network signals, which is imperfect in both directions and therefore needs a designed handling of errors.
Model Routing
Directing each request to the cheapest model capable of handling it, rather than sending all traffic to the most capable one.
OAuth 2.0
An authorisation framework that lets an application obtain scoped, delegated access to a resource without handling the user's credentials.
Page and Ticket Routing
Deciding for each monitored condition whether it warrants immediate human interruption or asynchronous handling, and enforcing the distinction.
Problem Details
A standard JSON structure for HTTP error responses, giving machine-readable type, human-readable detail, and room for extensions.
Retryable Error
An error whose cause may resolve on its own, which a client may safely attempt again — as distinct from one that will fail identically.
Slowly Changing Dimension
A strategy for handling attributes that change over time, deciding whether history is preserved and how facts attach to the correct version.
Design a URL shortener handling 100 million new links per month and 10 billion redirects. Where is the real difficulty?
What the interviewer is testing The classic warm up. What is being assessed is not whether you can shorten a URL — it is whether you do capacity arithmetic befo
Design the audit logging for a system handling financial transactions. What is logged, where does it go, and what makes it hold up?
What is logged Significant actions only , defined explicitly rather than logging everything — an audit trail nobody can search is not usable evidence: Authentic
An executive says "we need an AI strategy" and asks you to come back in two weeks. How do you handle the ambiguity?
Do not go away and produce a strategy document A document answering a question nobody has articulated will be received politely and shelved. The brief is ambigu
Dead Letter Handling
The poison message that blocks a partition, and the queue nobody reads.
Integration Patterns
Routers, translators, splitters, aggregators and dead letter channels.
API Error Handling
Error shapes, retryability signals and machine-readable causes.
Handling Ambiguity
Making progress when the requirements are not yet knowable.
Handling Disagreement
Arguing from consequences, and escalating in the room.
Healthcare Data Protection
PHI handling, minimum necessary access, and audit expectations in clinical systems.
Waste Elimination
Idle environments, orphaned volumes, forgotten instances, dead data.