How do you implement retry logic with exponential backoff for failed microservice calls in NestJS?

Q: How do you implement retry logic with exponential backoff for failed microservice calls in NestJS?

import { retry, timer } from 'rxjs'; @Injectable() export class ResilientOrdersService { constructor( @Inject('INVENTORY_SERVICE') private inventoryClient: ClientProxy, ) {} async reserveItems(orderId: string, items: OrderItem[]): Promise { await firstValueFrom( this.inventoryClient .send ({ cmd: 'reserve_items' }, { orderId, items }) .pipe( retry({ count: 3, delay: (error, retryCount) => { // Exponential backoff: 1s, 2s, 4s + jitter const base = Math.pow(2, retryCount - 1) * 1000; const jitter = Math.random() * 500; const delayMs = base + jitter; console.warn(`Retry ${retryCount} after ${Math.round(delayMs)}ms`); return timer(delayMs); }, }), catchError(err => { // All retries exhausted — dead-letter for manual review this.inventoryClient .emit('reservation_failed', { orderId, error: err.message }) .subscribe(); throw new ServiceUnavailableException('Inventory service unavailable'); }), ), ); } } Add random jitter to the delay — prevents thundering herd when many clients retry simultaneously. Exponential backoff: delay = 2^(retryCount - 1) * baseMs — doubles the wait on each attempt. After all retries are exhausted, emit to a dead-letter topic rather than silently discarding. Pair retries with a circuit breaker — retries without a circuit breaker amplify load on a failing service. Only retry on transient errors (timeouts, connection refused) — do not retry on 400 Bad Request.

Difficulty: 5/10

exponential backoff, NestJS interceptors, retry configuration

Use the RxJS retry operator with a delay function for exponential backoff. The delay function receives the error and the retry count — return a timer Observable with increasing delay. After all retries are exhausted, publish the failure to a dead-letter topic for manual review rather than silently dropping it.

Exponential backoff retry with RxJS and dead-letter fallback

Retry strategy design rules:

1
Add random jitter to the delay — prevents thundering herd when many clients retry simultaneously.
2

How do you implement retry logic with exponential backoff for failed microservice calls in NestJS?

Difficulty: 5/10

exponential backoff, NestJS interceptors, retry configuration

Use the RxJS retry operator with a delay function for exponential backoff. The delay function receives the error and the retry count — return a timer Observable with increasing delay. After all retries are exhausted, publish the failure to a dead-letter topic for manual review rather than silently dropping it.

Exponential backoff retry with RxJS and dead-letter fallback

Retry strategy design rules:

1
Add random jitter to the delay — prevents thundering herd when many clients retry simultaneously.
2

How do you implement retry logic with exponential backoff for failed microservice calls in NestJS?

How do you implement retry logic with exponential backoff for failed microservice calls in NestJS?

Scenario Questions

Follow-up Questions