Devon4Js Kafka module provides a retry implementation which leverages additional retry queues to offer a non blocking retry.
In the meantime Spring Kafkas library provides a very similar implementation.
I suggest dropping our own implementation and recommend using the "native" Spring implementation.
New projects should use this even if is currently in an experimental state (expected API changes, but considered "robust" and "feature complete").
So we should:
[x] Deprecate our own retry implementation
[ ] Upgrade Spring Kafka to a newer version (> 2.7.0 which introduced this feature)
[ ] Check carefully if other features (e.g. span injection, logging, ...) are still necessary in Devon4J-Kafka module or also have been superseeded by Spring
Devon4Js Kafka module provides a retry implementation which leverages additional retry queues to offer a non blocking retry. In the meantime Spring Kafkas library provides a very similar implementation. I suggest dropping our own implementation and recommend using the "native" Spring implementation. New projects should use this even if is currently in an experimental state (expected API changes, but considered "robust" and "feature complete").
So we should: