Spring for Apache Kafka – Beyond the Basics: Can Your Kafka Consumers Handle a Poison Pill?

The text discusses how to handle "poison pill" records in Apache Kafka applications, which are records that always fail to be deserialized by the consumer. The author shares lessons learned from their experience at ING and provides guidance on how to configure Spring Kafka to survive such scenarios. They explain that the problem occurs when the producer serializer and consumer deserializer are incompatible, leading to a deserialization exception. To handle this, they recommend using the `ErrorHandlingDeserializer`, which delegates to real deserializers if the delegate fails to deserialize the record content. The author also discusses how to configure the `DeadLetterPublishingRecoverer` to publish the value of the poison pill to a dead letter topic, allowing for inspection of the data. They emphasize the importance of proper monitoring and logging to prevent the consumer application from "eating" server disk space or other services becoming unhealthy due to a full disk.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.