Konspekt · Masshtablash
Yukni taqsimlash
Muammo
Bitta balancer, uchta app server. Balancer har bir so'rovni qayerga yuborishni qanday tanlaydi, noto'g'ri tanlov nega bitta serverni yondirib, qolganlarini bo'sh qoldiradi, o'lik serverni qanday payqaydi va sticky sessiyalar aslida qanchaga tushadi.
Nimani o'rganasiz
- L4 va L7: ulanishlarni taqsimlash va so'rovlarni taqsimlash
- Round robin, least connections va og'irliklar, har biri qachon pand beradi
- Health check: o'lik server pool'dan qanday chiqadi
- Sticky sessiyalar yukni nega buzadi va stateless muqobil
Diagramma kod sifatida
Darsdagi yakuniy sxemani matn ko'rinishida oling va Jira, GitLab, GitHub, Notion yoki hujjatga qo'ying: Mermaid u yerlarda o'zi chiziladi. D2 va PlantUML (Confluence, IntelliJ) uchun alohida variantlar bor.
Mermaid: sxema
flowchart LR
n_clients(["Klientlar"])
n_lb{"Load balancer"}
n_a["Server A"]
n_b["Server B"]
n_c["Server C"]
n_db[("Baza")]
n_sessions{{"Sessiyalar ombori"}}
n_clients --> n_lb
n_lb --> n_a
n_lb --> n_b
n_lb --> n_c
n_a --> n_db
n_b --> n_db
n_c --> n_db
n_a --> n_sessions
n_b --> n_sessions
n_c --> n_sessionsMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_lb as Load balancer
participant n_b as Server B
participant n_a as Server A
participant n_clients as Klientlar
participant n_c as Server C
participant n_sessions as Sessiyalar ombori
Note over n_lb,n_b: L4 balancer ulanishlarni taqsimlaydi
n_lb->>n_b: TCP 198.51.100.7:52114 -#62; 192.0.2.12:8443
Note over n_lb,n_a: Bitta band ulanish, bitta yonayotgan server
n_lb->>n_a: balancer connection table
Note over n_lb,n_a: L7 balancer so'rovlarni taqsimlaydi
n_lb->>n_a: GET /api/orders?page=2 HTTP/1.1
Note over n_clients,n_lb: Round robin: navbat bilan
n_clients->>n_lb: balancer access log
Note over n_lb,n_c: Soni bir xil, ishi juda har xil
n_lb->>n_c: GET /api/reports/export?year=2026 HTTP/1.1
n_c-->>n_lb: HTTP/1.1 200 OK
Note over n_lb,n_b: Least connections: kim bo'shligini so'rash
n_lb->>n_b: pick upstream for req_5e11
Note over n_lb,n_b: B o'ldi, balancer yuborishda davom etadi
n_lb-xn_b: GET /api/orders HTTP/1.1
Note over n_lb,n_b: Health check o'lik serverni chiqaradi
n_lb->>n_b: GET /healthz HTTP/1.1
n_b-->>n_lb: timeout after 1000 ms
Note over n_clients,n_lb: Sticky sessiyalar foydalanuvchini serverga bog'laydi
n_clients->>n_lb: POST /api/cart/items HTTP/1.1
n_lb-->>n_clients: HTTP/1.1 200 OK
Note over n_b,n_sessions: Umumiy sessiyalar ombori, sticky'siz
n_b->>n_sessions: HGETALL session:9c1e7a
n_sessions-->>n_b: 3 fieldsD2
direction: right
n_clients: "Klientlar" {
shape: rectangle
}
n_lb: "Load balancer" {
shape: diamond
}
n_a: "Server A" {
shape: rectangle
}
n_b: "Server B" {
shape: rectangle
}
n_c: "Server C" {
shape: rectangle
}
n_db: "Baza" {
shape: cylinder
}
n_sessions: "Sessiyalar ombori" {
shape: hexagon
}
n_clients -> n_lb
n_lb -> n_a
n_lb -> n_b
n_lb -> n_c
n_a -> n_db
n_b -> n_db
n_c -> n_db
n_a -> n_sessions
n_b -> n_sessions
n_c -> n_sessionsPlantUML: so'rovlar ketma-ketligi
@startuml
participant "Load balancer" as n_lb
participant "Server B" as n_b
participant "Server A" as n_a
participant "Klientlar" as n_clients
participant "Server C" as n_c
collections "Sessiyalar ombori" as n_sessions
note over n_lb, n_b : L4 balancer ulanishlarni taqsimlaydi
n_lb -> n_b : TCP 198.51.100.7:52114 -> 192.0.2.12:8443
note over n_lb, n_a : Bitta band ulanish, bitta yonayotgan server
n_lb -> n_a : balancer connection table
note over n_lb, n_a : L7 balancer so'rovlarni taqsimlaydi
n_lb -> n_a : GET /api/orders?page=2 HTTP/1.1
note over n_clients, n_lb : Round robin: navbat bilan
n_clients -> n_lb : balancer access log
note over n_lb, n_c : Soni bir xil, ishi juda har xil
n_lb -> n_c : GET /api/reports/export?year=2026 HTTP/1.1
n_c --> n_lb : HTTP/1.1 200 OK
note over n_lb, n_b : Least connections: kim bo'shligini so'rash
n_lb -> n_b : pick upstream for req_5e11
note over n_lb, n_b : B o'ldi, balancer yuborishda davom etadi
n_lb ->x n_b : [yo'qoldi] GET /api/orders HTTP/1.1
note over n_lb, n_b : Health check o'lik serverni chiqaradi
n_lb -> n_b : GET /healthz HTTP/1.1
n_b --> n_lb : timeout after 1000 ms
note over n_clients, n_lb : Sticky sessiyalar foydalanuvchini serverga bog'laydi
n_clients -> n_lb : POST /api/cart/items HTTP/1.1
n_lb --> n_clients : HTTP/1.1 200 OK
note over n_b, n_sessions : Umumiy sessiyalar ombori, sticky'siz
n_b -> n_sessions : HGETALL session:9c1e7a
n_sessions --> n_b : 3 fields
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Klientlar" as n_clients
node "Load balancer" as n_lb
component "Server A" as n_a
component "Server B" as n_b
component "Server C" as n_c
database "Baza" as n_db
stack "Sessiyalar ombori" as n_sessions
n_clients --> n_lb
n_lb --> n_a
n_lb --> n_b
n_lb --> n_c
n_a --> n_db
n_b --> n_db
n_c --> n_db
n_a --> n_sessions
n_b --> n_sessions
n_c --> n_sessions
@endumlXulosa
Balancer tanlovi qanchalik to'g'ri bo'lsa, shunchalik foydali.
1) L4 ulanishlarni, L7 so'rovlarni taqsimlaydi: uzoq yashaydigan ulanishlarga L7 kerak. 2) Teng ish uchun round robin, notekis ish uchun least connections, teng bo'lmagan serverlar uchun og'irliklar. 3) Health check o'lik serverlarni soniyalar ichida chiqaradi. 4) Sticky sessiyalar qulaylik uchun muvozanat va chidamlilikni qurbon qiladi, umumiy holat — yaxshiroq yechim.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| So'rovlar | 900/s | 1 300/s |
| Kechikish p99 | 140 ms | 160 ms |
| Xatolar | 0% | 0,3% |
| Eng band server | 35% | 55% |
Qadamlar
- Holat L4 balancer ulanishlarni taqsimlaydi
Balancer transport qatlamida (L4) ishlaydi.
- Muammo Bitta band ulanish, bitta yonayotgan server
Hamkor integratsiyasi bitta keep-alive ulanish ochadi va u orqali soniyasiga 400 so'rov yuboradi.
- Yechim L7 balancer so'rovlarni taqsimlaydi
Balancer endi TLS'ni o'zida yechadi va HTTP tilida gaplashadi (L7).
- Holat Round robin: navbat bilan
Eng oddiy algoritm: A, B, C, A, B, C… Har bir server bir xil sonda so'rov oladi.
- Muammo Soni bir xil, ishi juda har xil
Yangi hisobot eksporti har so'rovga 4 soniya oladi, oddiy so'rov esa 13 ms.
- Yechim Least connections: kim bo'shligini so'rash
Balancer endi har bir server ayni damda nechta so'rov ustida ishlayotganini kuzatadi va keyingisini eng kam ishi bor serverga yuboradi.
- Holat Teng bo'lmagan serverlar uchun og'irlik
C ikki baravar katta mashinaga almashtiriladi.
- Muammo B o'ldi, balancer yuborishda davom etadi
B serverning xotirasi tugaydi va u yiqiladi.
- Yechim Health check o'lik serverni chiqaradi
Har 2 soniyada balancer har bir serverning
/healthzmanzilini chaqiradi. - Muammo Sticky sessiyalar foydalanuvchini serverga bog'laydi
Savat har bir serverning xotirasida yashaydi, shuning uchun jamoa sticky sessiyalarni yoqadi: balancer cookie qo'yadi va har bir foydalanuvchini doim bitta serverga yuboradi.
- Yechim Umumiy sessiyalar ombori, sticky'siz
Savat va sessiyalar barcha serverlar o'qiydigan umumiy omborga ko'chadi.
- Xulosa Xulosa
Balancer tanlovi qanchalik to'g'ri bo'lsa, shunchalik foydali.
Atamalar
- Load balancer
- Kiruvchi trafikni bir nechta server orasida taqsimlaydigan qism. L4 ulanishlarni, L7 alohida so'rovlarni taqsimlaydi; round robin, least connections yoki og'irliklar bilan tanlaydi.
- Health check
- Balancer serverni muntazam tekshirib turadi va javob bermaganini bir necha soniyada pool'dan chiqaradi. Server tuzalgach u yana qaytariladi.