Feature Request: Add Hedge Request Support Alongside Retry Logic

[korECM]

Hello Resty team,
First of all, thank you for the excellent HTTP client library! The built-in retry mechanism is very useful for improving request reliability.

However, I noticed that Resty currently supports only retry logic, and I believe adding hedge requests support would be a a valuable enhancement. Hedge requests involve sending multiple parallel requests to reduce tail latency and improve overall responsiveness, which is especially beneficial in high-latency or unreliable network environments.

A great example of this approach can be found in the Failsafe Go library, which provides hedge request capabilities alongside retries. It would be fantastic if Resty could offer native support for hedging as well, allowing users to configure how many parallel requests to send and how to handle their responses.

This feature would complement the existing retry logic and provide developers with more robust options for handling transient failures and latency spikes.

Thank you for considering this feature request. I would be happy to discuss further or contribute to the implementation if needed!

[jeevatkm]

@korECM Thanks for creating a discussion. I just wanted to let you know that I have looked at your reference. I will consider your suggestion for the Hedge feature with Retry. However, I'm focusing my effort on getting the v3 first release, so I will focus on this later.

FYI, the upcoming Resty v3 comes with the following features-

• Failure handling: Retry (existing feature in v2, enhanced in v3)
• Load limiting: Circuit Breaker new in v3, Rate Limiter - v3 handles OOTB rate limit headers
• Time limiting: Timeout

[liuzengh]

I have added sliding window implementation for the current Circuit Breaker #1020 after browsing "Failsafe Go library" document