Imagine publishing a message to Kafka topic A. Suddenly, your consumer crashes. It hit a deserialization error. Because the client never successfully processes the record, it never commits the offset. Upon restarting, it reads the exact same record again, failing repeatedly in an infinite loop. This bad record is called a poison pill...
When integrating Kafka consumers with reactive OAuth2 for securing outbound HTTP calls, a common pitfall arises: Kafka processing typically operates in a background, non-HTTP context. This means there's no `ServerWebExchange` available, which is a core component of the reactive web stack that exposes the current HTTP request/response and request-scoped attributes...