مصطفی جعفرزاده
مصطفی جعفرزاده
خواندن ۴ دقیقه·۲ ماه پیش

Exponential Backoff and Retry Mechanism in Nest.js and Complex Systems


In complex systems that rely on external services or distributed databases, temporary errors such as network failures or server overloads often occur. These issues can lead to request failures and negatively impact user experience. One of the best approaches to managing these errors is through Retry Mechanism and Exponential Backoff. In this article, we will explain these mechanisms and implement them in Nest.js as well as discuss real-world examples from systems like PayPal and AWS S3.

Note: This article was created with the assistance of AI.

What is Retry Mechanism?

A Retry Mechanism enables the system to automatically retry a failed request. This is particularly effective in systems sensitive to connectivity issues or traffic congestion.

When your request fails due to temporary issues (e.g., network disruptions or overloaded servers), the Retry Mechanism allows you to retry the request multiple times, increasing the likelihood of success.

What is Exponential Backoff?

Exponential Backoff is a technique that increases the time between retry attempts exponentially after each failure. Instead of continuously sending requests immediately (which can overload servers), the system gradually increases the delay between retries.

For example:

- After the first failure, the system waits 1 second before retrying.

- If the second attempt fails, the delay increases to 2 seconds.

- Then 4 seconds, 8 seconds, and so on, until either the request succeeds or the retry limit is reached.

Implementation in Nest.js

Suppose you want to send a request to an external API, and in case of failure, the system will retry with Exponential Backoff. In Nest.js, we can implement this mechanism using Axios and RxJS libraries.

Installing Required Libraries

First, install Axios and RxJS:

npm install axios rxjs

Implementing Retry Service in Nest.js

In this example, we will implement a service that sends an HTTP request to an external API. If an error occurs, the system retries the request, and with each failure, the time between retries increases exponentially.

import { Injectable, HttpService, InternalServerErrorException } from '@nestjs/common';
import { AxiosError } from 'axios';
import { catchError, retryWhen, delay, take, scan } from 'rxjs/operators';
import { throwError } from 'rxjs';
@Injectable()
export class RetryService {
constructor(private readonly httpService: HttpService) {}
private maxRetries = 5; // Maximum number of retries
private delayMs = 1000; // Initial delay in milliseconds
async fetchData(url: string) {
return this.httpService.get(url).pipe(
retryWhen(errors =>
errors.pipe(
scan((retryCount, error) => {
if (retryCount >= this.maxRetries) {
throw error; // If retry limit is reached, throw error
}
retryCount++;
const backoffDelay = this.delayMs * Math.pow(2, retryCount); // Exponential Backoff
console.log(`Retrying... Attempt #${retryCount} after ${backoffDelay} ms`);
return retryCount;
}, 0),
delay(this.delayMs), // Apply delay between retries
take(this.maxRetries), // Limit the number of retries
),
),
catchError((error: AxiosError) => {
console.error(`Failed after ${this.maxRetries} retries`);
return throwError(() => new InternalServerErrorException('Request failed'));
}),
).toPromise();
}
}

Key Points:

1. retryWhen and delay: These RxJS operators manage retry attempts and delays between each retry. `retryWhen` allows controlling the number of retries and the time between them.

2. Exponential Backoff: The delay between retries increases exponentially (1 second, 2 seconds, 4 seconds, etc.).

3. Error Handling: After a specified number of retries, if the issue persists, the system returns a final error and stops further attempts.

Using the Service in a Controller

You can now use this service within a controller:

import { Controller, Get } from '@nestjs/common';
import { RetryService } from './retry.service';
@Controller('retry')
export class RetryController {
constructor(private readonly retryService: RetryService) {}
@Get()
async handleRequest() {
const url = 'https://example.com/api';
try {
const response = await this.retryService.fetchData(url);
return response.data;
} catch (error) {
throw error;
}
}
}

Real-World Examples

1. PayPal and International Payment System

In financial systems like PayPal, temporary network failures between servers and banks can disrupt transactions. PayPal uses Exponential Backoff to handle these problems. If a transaction fails due to network issues, the system automatically retries, increasing the delay between retries to prevent overloading the bank’s servers.

2. AWS S3 and File Upload Management

In AWS S3, when users upload large files, the process may fail temporarily due to network issues or server overload. AWS S3 uses Retry Mechanism with Exponential Backoff to handle these cases, ensuring files are uploaded correctly even with temporary network disruptions.

3. Google Cloud and API Requests

Google Cloud also uses Exponential Backoff to manage its API requests. When requests fail due to network congestion or server overload, Google Cloud retries with increasing delays between attempts, ensuring that the servers are not overwhelmed.

Pros and Cons

Pros:

1. Reduced server load: By gradually increasing the delay between retries, servers are less likely to be overwhelmed.

2. Increased success rate: Temporary network issues often resolve with time, and Retry Mechanism with Exponential Backoff increases the chances of request success.

3. Improved user experience: Users don't need to retry failed requests manually; the system automatically manages retry attempts.

Cons:

1. Response delays: If the Backoff intervals are too long, the response delay can lead to a poor user experience.

2. Resource consumption: Each retry consumes system resources, and if not configured correctly, it may lead to wasted resources.

3. Implementation complexity: Correctly implementing this mechanism in distributed systems requires complex configurations and coordination between components.

Conclusion

The Retry and Exponential Backoff mechanisms are effective strategies for managing temporary errors and preventing server overload in complex, distributed systems. Implementing them in Nest.js, using appropriate tools like Axios and RxJS, helps developers build reliable and fault-tolerant systems.

nestjs
برنامه نویس علاقه مند به طراحی الگوریتم
شاید از این پست‌ها خوشتان بیاید