Search before asking

• I had searched in the issues and found no similar issues.

Enhancement Request

Currently, EventMesh supports two retry strategies for the case of message consumption failure: a retry strategy using HashedWheelTimer in memory (default) and a retry strategy based on external storage RocketMQ. There are still retry strategies based on other message brokers waiting to be implemented.

对于消息消费失败的情况，目前EventMesh支持在内存中使用HashedWheelTimer的重试策略（默认）和基于外部存储RocketMQ的重试策略。还有基于其他消息中间件的重试策略等待实现。

Describe the solution you'd like

task list

• Implement a retry strategy based on Kafka
• Implement a retry strategy based on RabbitMQ
• Implement a retry strategy based on Pulsar
• Implement a retry strategy based on Redis

Welcome to claim the task you are interested in and create corresponding sub issue.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct *