intermediateConsumer Errors, Retry & Recovery
What's the standard pattern for handling a message that fails processing repeatedly, without blocking the whole partition?
Route it to a dead-letter topic (DLT) after a bounded number of retries — the consumer publishes the failing message (plus error context) to a separate topic for later inspection/manual reprocessing, then commits its offset and moves on, so one bad message doesn't stall the healthy ones behind it.
This is a Pro chapter
Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.
What's the standard pattern for handling a message that fails processing repeatedly, without blocking the whole partition?