In this post, the author explores different methods of retrying requests in web development. They emphasize the importance of handling failed requests to prevent user-facing errors. The post visualizes the process of sending requests, load balancing, and server responses. The author highlights the dangers of retrying in a tight loop and explains that it can increase overall server load. They also discuss the drawbacks of adding a delay between retries, as it can lead to a poor user experience. The best practice recommended is to use exponential backoff with jitter, which balances user experience and recovery time. The author provides example code in Go for implementing this retry strategy.
https://encore.dev/blog/retries