Retry Strategies — Exponential backoff va delay strategiyalari
API so'rovlarida qayta urinish strategiyalari: Fixed Delay, Exponential Backoff, Jitter, Thundering Herd muammosi, Retry-After header'i va axios-retry integratsiyasi.
71-dars
Retry Strategies — Exponential backoff va delay strategiyalari
Har doim ham muayyan bir xil vaqt oralig'ida (masalan, har 1 soniyada) qayta urinish (Fixed Delay) to'g'ri strategiya hisoblanmaydi. Agar server millionlab foydalanuvchilarning so'rovlari ostida qotib qolgan bo'lsa va barcha mijozlar bir xil soniyada qaytadan so'rov yo'llayversa, bu serverni butunlay qulatishi mumkin (Thundering Herd Problem — Olomon effekti).
Buning oldini olish uchun professional arxitekturada ikkita asosiy strategiya qo'llaniladi: Exponential Backoff va Jitter.
1. Delay strategiyalarining turlari
flowchart TD
A["Muvaffaqiyatsiz so'rov"] --> B{"Qayta urinish strategiyasi"}
B -->|Fixed Delay| C["1s -> 1s -> 1s\n(Serverga uzluksiz zarba)"]
B -->|Exponential Backoff| D["1s -> 2s -> 4s -> 8s\n(Serverga tiklanish vaqti beriladi)"]
B -->|Backoff + Jitter| E["1.2s -> 2.4s -> 4.1s\n(So'rovlar vaqt bo'yicha sochib yuboriladi)"]
A. Fixed Delay (Doimiy kechikish)
- Qanday ishlaydi: Har bir urinish orasida bir xil qat'iy vaqt kutiladi (masalan: 1s, 1s, 1s).
- Kamchiligi: Server hali o'ziga kelib ulgurmagan bo'lsa ham, mijozlar tinimsiz bir xil maromda so'rov yuboraveradi.
B. Exponential Backoff (Eksponensial o'suvchi kechikish — 🥇 Oltin standart)
- Qanday ishlaydi: Har bir muvaffaqiyatsiz urinishdan keyin kutish vaqti eksponensial ravishda (geometrik progressiya bo'yicha) ortib boradi:
- 1-urinishdan keyin: 1 soniya kutish ($2^0$)
- 2-urinishdan keyin: 2 soniya kutish ($2^1$)
- 3-urinishdan keyin: 4 soniya kutish ($2^2$)
- 4-urinishdan keyin: 8 soniya kutish ($2^3$)
- Afzalligi: Serverga nafas olish va o'zini tiklash uchun tobora kengroq vaqt oralig'i taqdim etiladi.
C. Jitter (Tasodifiy kechikish qo'shish)
- Qanday ishlaydi: Eksponensial vaqt ustiga biroz tasodifiy (random) millisekundlar qo'shiladi.
- Nima uchun kerak? Tasavvur qiling, tarmoqdagi nosozlik sabab bir vaqtning o'zida 10,000 ta mijozning so'rovi tushib qoldi. Agar ularning barchasi bir xil eksponensial vaqtda (masalan, aniq 2-soniyada) qayta so'rov yuborsa, server yana bir lahzada qulab tushadi. Jitter ularning so'rovlarini turli millisekundlarga taqsimlab yuboradi (biri 2.1s, ikkinchisi 2.4s, uchinchisi 2.7s).
2. Amaliyot: axios-retry bilan Exponential Backoff va Jitter sozlash
axios-retry kutubxonasida eksponensial kechikish, serverning Retry-After sarlavhasi va Jitter'ni birlashtirish:
// src/api/client.ts
import axios from 'axios';
import axiosRetry from 'axios-retry';
export const apiClient = axios.create({
baseURL: 'https://api.mysite.com/v1',
timeout: 10000,
});
axiosRetry(apiClient, {
retries: 4, // Ko'pi bilan 4 marta urinib ko'ramiz
// Eksponensial Backoff, Retry-After va Jitter kombinatsiyasi:
retryDelay: (retryCount, error) => {
// 1. Agar backend server "Retry-After" sarlavhasini yuborgan bo'lsa, unga bo'ysunamiz
const serverRetryAfter = error.response?.headers['retry-after'];
if (serverRetryAfter) {
return parseInt(serverRetryAfter, 10) * 1000;
}
// 2. Asosiy eksponensial vaqtni hisoblaymiz: 2 ^ retryCount * 1000ms
const exponentialDelay = Math.pow(2, retryCount) * 1000; // 2s, 4s, 8s, 16s...
// 3. Jitter qo'shamiz (0 dan 1000ms gacha tasodifiy vaqt)
const jitter = Math.random() * 1000;
return exponentialDelay + jitter;
},
retryCondition: (error) => {
// Faqat tarmoq, timeout va 5xx server xatolarida ishlaydi
const isNetworkOrTimeout = !error.response || error.code === 'ECONNABORTED';
const isServerError = error.response ? error.response.status >= 500 : false;
return isNetworkOrTimeout || isServerError;
},
onRetry: (retryCount, error, requestConfig) => {
console.warn(
`[Smart Retry]: Urinish #${retryCount}. Xato: ${error.message} -> ${requestConfig.url}`
);
},
});
3. Qo'lda (Custom Interceptor ichida) Exponential Backoff yozish
Tashqi kutubxonalarsiz, sof Axios Response Interceptor yordamida eksponensial kechikishni amalga oshirish:
import { apiClient } from './client';
declare module 'axios' {
export interface AxiosRequestConfig {
_retryCount?: number;
}
}
apiClient.interceptors.response.use(
(response) => response,
async (error) => {
const config = error.config;
// Faqat 5xx xatoliklar va tarmoq uzilishlarida qayta urinamiz
const isServerError = error.response && error.response.status >= 500;
const isNetworkError = !error.response;
if (!config || (!isServerError && !isNetworkError)) {
return Promise.reject(error);
}
config._retryCount = config._retryCount || 0;
const MAX_RETRIES = 3;
if (config._retryCount < MAX_RETRIES) {
config._retryCount += 1;
// Eksponensial kechikish + Jitter: 2^count * 1000ms + random(500ms)
const delay = Math.pow(2, config._retryCount) * 1000 + Math.random() * 500;
console.log(
`[Backoff]: ${Math.round(delay)}ms kutib, qayta urinilmoqda (${config._retryCount}/${MAX_RETRIES})...`
);
await new Promise((resolve) => setTimeout(resolve, delay));
return apiClient(config);
}
return Promise.reject(error);
}
);
4. Delay strategiyalari taqqoslash jadvali
| Strategiya | Formula | Serverga ta'siri | Tavsiya etilgan holat |
|---|---|---|---|
| Fixed Delay | const delay = 1000; |
Yuqori yuklama davrida serverni qulatishi mumkin | Kichik lokal ilovalar, test muhiti |
| Exponential Backoff | 2^n * 1000ms |
Serverga nafas olish imkonini beradi | Barcha production API mijozlari |
| Full Jitter | (2^n * 1000) + random() |
Eng xavfsiz, olomon effektini yo'q qiladi | Katta miqyosli, millionlab mijozli tizimlar |
| Retry-After Header | headers['retry-after'] |
Serverning o'zi belgilagan aniq vaqtga bo'ysunadi | Rate limiting (429) yoki 503 texnik ishlar |
Xulosa
- Fixed Delay — sodda, ammo yuqori yuklamalarda xavfli.
- Exponential Backoff — har bir qadamda vaqt oralig'ini kengaytirib borish orqali serverni himoya qiladi.
- Jitter — barcha mijozlarning qayta urinishlarini vaqt o'qi bo'ylab sochib yuborish orqali Olomon effektini (Thundering Herd) bartaraf etadi.