Seriya: Axios Dars 106

Multiple Backend Architecture — Bir nechta backend bilan ishlash

Bir nechta backend (Core API, Auth mikroservisi, Analytics API) bilan ishlash arxitekturasi: alohida Axios instansiyalari, konfiguratsiyalar izolyatsiyasi, mustaqil interceptorlar va feature integratsiyasi.

106-dars

Multiple Backend Architecture — Bir nechta backend bilan ishlash

Real dunyodagi yirik va mikroservisli veb-ilovalarda hamma ma'lumotlar bitta yagona backend serveridan kelmaydi. Zamonaviy dasturlar ko'pincha bir nechta mustaqil serverlar bilan parallel ishlaydi:

  1. Core API (https://api.mysite.com/v1): Asosiy biznes logikasi, buyurtmalar, tovarlar va foydalanuvchilar ma'lumotlari;
  2. Auth API (https://auth.mysite.com): Alohida autentifikatsiya va OAuth 2.0 / OIDC token chiqaruvchi server;
  3. Analytics & Logging API (https://analytics.mysite.com): Foydalanuvchi harakatlarini (kliklar, ko'rishlar) qayd etuvchi telemetriya serveri;
  4. Media / S3 Service (https://upload.mysite.com): Katta hajmli fayllar, rasmlar va videolarni to'g'ridan-to'g'ri qabul qiluvchi saqlagich.

Bunday vaziyatda faqat bitta umumiy apiClient yaratish — barcha so'rovlarni bitta qolipga majburlashga, chalkash shartlarga (if (url.includes(...))) va xavfsizlik zaifliklariga olib keladi.

To'g'ri yechim — har bir backend domeni uchun alohida sozlangan va izolyatsiyalangan Axios instansiyalarini yaratishdir.


1. Papka Tuzilishi va Instansiyalarni Ajratish

Bunday arxitekturada src/shared/api/ papkasida har bir server uchun o'zining mustaqil instansiya fayli ochiladi:

src/
├── shared/
│   └── api/
│       ├── coreClient.ts      # Asosiy biznes backend uchun (JSON, Bearer token)
│       ├── authClient.ts      # Autentifikatsiya serveri uchun (Form-urlencoded, Cookies)
│       └── analyticsClient.ts # Statistika uchun (Yengil, token talab qilmaydi)
│
├── features/
│   ├── auth/api/              # authClient ishlatadi
│   ├── todos/api/             # coreClient ishlatadi
│   └── tracking/api/          # analyticsClient ishlatadi
flowchart TD
    subgraph UI["Feature Qatlami"]
        F1["AuthService"]
        F2["TodosService / OrdersService"]
        F3["TrackingService"]
    end

    subgraph Clients["Izolyatsiyalangan Axios Instansiyalari"]
        AC["authClient.ts\n(baseURL: auth.mysite.com\nwithCredentials: true)"]
        CC["coreClient.ts\n(baseURL: api.mysite.com\nBearer Interceptor)"]
        AnC["analyticsClient.ts\n(baseURL: analytics.mysite.com\nFire-and-Forget)"]
    end

    subgraph Backends["Mustaqil Serverlar"]
        B1["Auth Microservice"]
        B2["Core REST API"]
        B3["Analytics Gateway"]
    end

    F1 --> AC --> B1
    F2 --> CC --> B2
    F3 --> AnC --> B3

2. Amaliyot: TypeScript yordamida Bir Nechta Client Yaratish

A. Auth Client (src/shared/api/authClient.ts)

Autentifikatsiya serveri ko'pincha URL-encoded formatini va cookie almashinuvini talab qiladi:

import axios, { AxiosInstance } from 'axios';

export const authClient: AxiosInstance = axios.create({
  baseURL: import.meta.env.VITE_AUTH_API_URL || 'https://auth.mysite.com',
  timeout: 10000,
  headers: {
    'Content-Type': 'application/x-www-form-urlencoded',
  },
  withCredentials: true, // HttpOnly Refresh token cookie'lari uchun
});

B. Core Client (src/shared/api/coreClient.ts)

Asosiy biznes operatsiyalari uchun JSON formati, 15 soniyalik timeout va xavfsiz Bearer token interceptori kerak:

import axios, { AxiosInstance, InternalAxiosRequestConfig } from 'axios';

export const coreClient: AxiosInstance = axios.create({
  baseURL: import.meta.env.VITE_CORE_API_URL || 'https://api.mysite.com/v1',
  timeout: 15000,
  headers: {
    'Content-Type': 'application/json',
    Accept: 'application/json',
  },
});

// Faqat Core API uchun tokenni qo'shuvchi interceptor
coreClient.interceptors.request.use(
  (config: InternalAxiosRequestConfig) => {
    const token = localStorage.getItem('access_token');
    if (token && config.headers) {
      config.headers.Authorization = `Bearer ${token}`;
    }
    return config;
  },
  (error) => Promise.reject(error)
);

C. Analytics Client (src/shared/api/analyticsClient.ts)

Analitika so'rovlari past ustuvorlikka ega bo'lib, ular asosiy tizim ishiga xalaqit bermasligi, tokenni talab qilmasligi va xato bersa ham sahifani to'xtatib qo'ymasligi lozim:

import axios, { AxiosInstance } from 'axios';

export const analyticsClient: AxiosInstance = axios.create({
  baseURL: import.meta.env.VITE_ANALYTICS_API_URL || 'https://analytics.mysite.com',
  timeout: 5000, // Qisqa timeout
  headers: {
    'Content-Type': 'application/json',
  },
});

// Agar analitika serveri 500 xato bersa ham, ilovada qizil xato chiqmasin (Silent Fail)
analyticsClient.interceptors.response.use(
  (response) => response,
  (error) => {
    console.warn('[Analytics Failed]:', error.message);
    return Promise.resolve({ data: null, status: 200, statusText: 'Ignored', headers: {}, config: error.config });
  }
);

3. Feature Servislar Ichida To'g'ri Instansiyani Ishlatish

Har bir biznes feature faqat o'ziga tegishli mijozni import qiladi:

// src/features/auth/api/auth.service.ts
import { authClient } from '../../../shared/api/authClient';

export const AuthService = {
  login: async (formData: URLSearchParams) => {
    // Faqat authClient orqali yuboriladi
    const response = await authClient.post('/oauth/token', formData);
    return response.data;
  },
};
// src/features/todos/api/todos.service.ts
import { coreClient } from '../../../shared/api/coreClient';

export const TodosService = {
  getTodos: async (signal?: AbortSignal) => {
    // Faqat coreClient orqali yuboriladi (Bearer token avtomatik qo'shiladi)
    const response = await coreClient.get('/todos', { signal });
    return response.data;
  },
};
// src/features/tracking/api/tracking.service.ts
import { analyticsClient } from '../../../shared/api/analyticsClient';

export const TrackingService = {
  trackEvent: async (eventName: string, metadata: Record<string, unknown>) => {
    // Analitika serveriga xavfsiz va alohida jo'natiladi
    await analyticsClient.post('/events', { event: eventName, ...metadata, timestamp: Date.now() });
  },
};

4. Ushbu Arxitekturaning 3 Ta Kritik Afzalligi 🚀

  1. Token Sizib Chiqishining Oldini Olish (Security Isolation): Agar bitta global client bo'lsa, uning interceptori barcha so'rovlarga, shu jumladan uchinchi tomon yoki analitika serveriga ham maxfiy Authorization: Bearer <token> sarlavhasini yuborib yuborishi mumkin. Alohida instansiyalarda esa token faqat coreClient doirasida qoladi.
  2. Mustaqil Xatoliklar Boshqaruvi: Analitika serverining o'chib qolishi yoki sekin ishlashi asosiy tizimga zarracha ta'sir qilmaydi. analyticsClientdagi xatolar foydalanuvchiga hech qanday bildirishnoma chiqarmasdan fonda so'ndiriladi.
  3. Format va Protokol Moslashuvchanligi: Bir backend JSON talab qilsa, ikkinchisi XML, uchinchisi esa URLSearchParams talab qilishi mumkin. Har bir instansiya o'ziga mos transformRequest va headersga ega bo'ladi.

5. Bitta Global Client vs Ko'p Instansiyali Arxitektura

Mezon Yagona Client Bilan Hammasi Multiple Client Arxitekturasi
URL boshqaruvi apiClient.get('https://other.com/...') (Hardcoded) coreClient.get('/todos') (Toza baseURL)
Token xavfsizligi ❌ Begona serverlarga token sizib chiqish xavfi ✅ Token faqat o'z domeniga boradi
Timeout nazorati Barcha so'rovlar uchun bir xil (masalan: 15s) Core: 15s, Auth: 10s, Analytics: 5s
Interceptorlar if/else shartlariga to'lib ketadi Har bir instansiyada mustaqil va sodda
Xatolar izolatsiyasi Bitta xato barcha interceptorlarni qo'zg'atadi Har bir backend o'z xatosini o'zi hal qiladi

Xulosa

Bir nechta backend bilan ishlaydigan zamonaviy tizimlarda har bir server domeni uchun mustaqil Axios instansiyalarini (coreClient, authClient, analyticsClient) yaratish — bu xavfsizlik, barqarorlik va modulli tozalikni ta'minlovchi zaruriy arxitekturadir. Bu orqali har bir backend o'zining formati va xavfsizlik talablari bo'yicha mustaqil faoliyat yuritadi.