Konspekt · Aloqa
Real-time yangilanishlar
Muammo
Chat yangi xabarni yuborilgan zahoti ko'rsatishi kerak. Polling, long polling, Server-Sent Events va WebSocket, hamda ko'p ochiq ulanishni ushlab turish uchun nima kerak.
Nimani o'rganasiz
- Polling, long polling, SSE va WebSocket serverga qanchaga tushadi
- Nega uzoq yashaydigan ulanishlarga alohida gateway qatlami kerak
- Pub/sub boshqa gateway'dagi foydalanuvchiga xabarni qanday yetkazadi
- Klient xabar yo'qotmasdan qanday qayta ulanadi
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_alice(["Alisa"])
n_bob(["Bobur"])
n_db[("Baza")]
n_lb{"Load balancer"}
n_gw1["Gateway 1"]
n_gw2["Gateway 2"]
n_chat["Chat servisi"]
n_bus{{"Pub/sub"}}
n_alice --> n_lb
n_bob -.->|"qayta urinish"| n_lb
n_lb --> n_gw1
n_lb --> n_gw2
n_gw1 --> n_chat
n_chat --> n_db
n_gw1 -.-> n_alice
n_gw2 -.-> n_bob
n_chat --> n_bus
n_bus -.-> n_gw1
n_bus -.-> n_gw2
n_gw2 --> n_chatMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_bob as Bobur
participant n_api as Chat server
participant n_alice as Alisa
participant n_lb as Load balancer
participant n_gw1 as Gateway 1
participant n_chat as Chat servisi
participant n_bus as Pub/sub
participant n_gw2 as Gateway 2
Note over n_bob,n_api: Har ikki soniyada so'rash
n_bob->>n_api: GET /rooms/r_17/updates?since=m_730 HTTP/1.1
n_api-->>n_bob: HTTP/1.1 200 OK
Note over n_bob,n_api: Long polling: server so'rovni ushlab turadi
n_bob->>n_api: GET /rooms/r_17/updates?since=m_730#38;wait=25 HTTP/1.1
n_api-->>n_bob: HTTP/1.1 200 OK
Note over n_api,n_bob: Server-Sent Events: pastga bitta oqim
n_api->>n_bob: GET /rooms/r_17/stream HTTP/1.1
n_bob-->>n_api: HTTP/1.1 200 OK
Note over n_alice,n_api: WebSocket: bitta ulanish, ikki tomonga
n_alice->>n_api: GET /ws HTTP/1.1
n_api-->>n_alice: HTTP/1.1 101 Switching Protocols
Note over n_bob,n_api: Bitta server, 65 000 socket
n_bob-xn_api: chat-1: accept() failed: EMFILE (too many open files)
Note over n_bob,n_lb: Ulanishlarni gateway qatlami ushlaydi
n_bob->>n_lb: GET /ws?room=r_17 HTTP/1.1
n_lb-->>n_bob: HTTP/1.1 101 Switching Protocols
Note over n_gw1,n_alice: Xabar noto'g'ri gateway'da qolib ketadi
n_gw1->>n_alice: gw1: deliver m_740 to room r_17
Note over n_chat,n_bus: Gateway'lar orasida pub/sub
n_chat->>n_bus: PUBLISH room:r_17
n_bus-->>n_chat: (integer) 2
Note over n_gw2,n_bob: Telefon tunnelga kirdi
n_gw2-xn_bob: gw2: socket u_77 closed, code 1006
Note over n_bob,n_lb: Qayta ulanib, oxirgi ID'dan yetib olish
n_bob->>n_lb: WS frame (after reconnect)
n_lb-->>n_bob: WS frameD2
direction: right
n_alice: "Alisa" {
shape: rectangle
}
n_bob: "Bobur" {
shape: rectangle
}
n_db: "Baza" {
shape: cylinder
}
n_lb: "Load balancer" {
shape: diamond
}
n_gw1: "Gateway 1" {
shape: rectangle
}
n_gw2: "Gateway 2" {
shape: rectangle
}
n_chat: "Chat servisi" {
shape: rectangle
}
n_bus: "Pub/sub" {
shape: hexagon
}
n_alice -> n_lb
n_bob -> n_lb: "qayta urinish" {
style.stroke-dash: 3
}
n_lb -> n_gw1
n_lb -> n_gw2
n_gw1 -> n_chat
n_chat -> n_db
n_gw1 -> n_alice {
style.stroke-dash: 3
}
n_gw2 -> n_bob {
style.stroke-dash: 3
}
n_chat -> n_bus
n_bus -> n_gw1 {
style.stroke-dash: 3
}
n_bus -> n_gw2 {
style.stroke-dash: 3
}
n_gw2 -> n_chatPlantUML: so'rovlar ketma-ketligi
@startuml
participant "Bobur" as n_bob
participant "Chat server" as n_api
participant "Alisa" as n_alice
participant "Load balancer" as n_lb
participant "Gateway 1" as n_gw1
participant "Chat servisi" as n_chat
collections "Pub/sub" as n_bus
participant "Gateway 2" as n_gw2
note over n_bob, n_api : Har ikki soniyada so'rash
n_bob -> n_api : GET /rooms/r_17/updates?since=m_730 HTTP/1.1
n_api --> n_bob : HTTP/1.1 200 OK
note over n_bob, n_api : Long polling: server so'rovni ushlab turadi
n_bob -> n_api : GET /rooms/r_17/updates?since=m_730&wait=25 HTTP/1.1
n_api --> n_bob : HTTP/1.1 200 OK
note over n_api, n_bob : Server-Sent Events: pastga bitta oqim
n_api -> n_bob : GET /rooms/r_17/stream HTTP/1.1
n_bob --> n_api : HTTP/1.1 200 OK
note over n_alice, n_api : WebSocket: bitta ulanish, ikki tomonga
n_alice -> n_api : GET /ws HTTP/1.1
n_api --> n_alice : HTTP/1.1 101 Switching Protocols
note over n_bob, n_api : Bitta server, 65 000 socket
n_bob ->x n_api : [yo'qoldi] chat-1: accept() failed: EMFILE (too many open files)
note over n_bob, n_lb : Ulanishlarni gateway qatlami ushlaydi
n_bob -> n_lb : GET /ws?room=r_17 HTTP/1.1
n_lb --> n_bob : HTTP/1.1 101 Switching Protocols
note over n_gw1, n_alice : Xabar noto'g'ri gateway'da qolib ketadi
n_gw1 -> n_alice : gw1: deliver m_740 to room r_17
note over n_chat, n_bus : Gateway'lar orasida pub/sub
n_chat -> n_bus : PUBLISH room:r_17
n_bus --> n_chat : (integer) 2
note over n_gw2, n_bob : Telefon tunnelga kirdi
n_gw2 ->x n_bob : [yo'qoldi] gw2: socket u_77 closed, code 1006
note over n_bob, n_lb : Qayta ulanib, oxirgi ID'dan yetib olish
n_bob -> n_lb : [qayta urinish] WS frame (after reconnect)
n_lb --> n_bob : WS frame
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Alisa" as n_alice
agent "Bobur" as n_bob
database "Baza" as n_db
node "Load balancer" as n_lb
component "Gateway 1" as n_gw1
component "Gateway 2" as n_gw2
component "Chat servisi" as n_chat
stack "Pub/sub" as n_bus
n_alice --> n_lb
n_bob ..> n_lb : qayta urinish
n_lb --> n_gw1
n_lb --> n_gw2
n_gw1 --> n_chat
n_chat --> n_db
n_gw1 ..> n_alice
n_gw2 ..> n_bob
n_chat --> n_bus
n_bus ..> n_gw1
n_bus ..> n_gw2
n_gw2 --> n_chat
@endumlXulosa
Mos keladigan eng arzon kanalni tanlang: kam yangilanishga polling, serverdan klientga oqimga SSE, ikki tomonlama chatga WebSocket.
1) Uzoq yashaydigan ulanishlar alohida gateway qatlamida. 2) Gateway'lar xabardan pub/sub orqali xabar topadi. 3) Jonli yetkazish o'tkazib yuborishi mumkin; haqiqat bazada. 4) Klient backoff va jitter bilan qayta ulanadi va oxirgi ID'dan davom etadi.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| So'rovlar | 50 000/s | 300/s |
| Yetkazish kechikishi | 1 000 ms | 45 ms |
| Yetib bormagan | 0/daq | 0/daq |
Qadamlar
- Muammo Har ikki soniyada so'rash
Har bir ochiq chat serverdan ikki soniyada bir marta «
m_730dan keyin yangi narsa bormi?» deb so'raydi. - Yechim Long polling: server so'rovni ushlab turadi
Klient o'sha so'rovni yuboradi, lekin server darhol javob bermaydi.
- Yechim Server-Sent Events: pastga bitta oqim
Klient bitta HTTP so'rov ochadi, server esa javobni hech qachon tugatmaydi.
- Yechim WebSocket: bitta ulanish, ikki tomonga
Klient HTTP so'rov bilan boshlaydi va uni upgrade qilishni so'raydi.
- Muammo Bitta server, 65 000 socket
Har foydalanuvchi socket'ni kun bo'yi ochiq ushlaydi.
- Yechim Ulanishlarni gateway qatlami ushlaydi
Ulanishlar gateway'lar qatlamiga ko'chadi.
- Muammo Xabar noto'g'ri gateway'da qolib ketadi
Alisa xabar yuboradi.
- Yechim Gateway'lar orasida pub/sub
Xabarni saqlagach, chat servisi uni xona kanaliga publish qiladi.
- Muammo Telefon tunnelga kirdi
Boburning ulanishi xayrlashmasdan uziladi.
- Yechim Qayta ulanib, oxirgi ID'dan yetib olish
Boburning ilovasi tobora uzayadigan pauza va tasodifiy jitter bilan qayta ulanadi, shunda minglab telefon bitta soniyada yopirilib kelmaydi.
- Xulosa Xulosa
Mos keladigan eng arzon kanalni tanlang: kam yangilanishga polling, serverdan klientga oqimga SSE, ikki tomonlama chatga WebSocket.
Atamalar
- Long polling
- Klient so'rov yuboradi, server esa yangi narsa paydo bo'lguncha yoki vaqt tugaguncha uni ushlab turadi. Har ikki soniyada so'rashdan arzonroq, lekin har javobdan keyin yangi so'rov kerak.
- WebSocket
- Klient va server orasidagi bitta doimiy ulanish, ikkala tomon ham istalgan vaqtda xabar yuboradi. Ko'p ochiq ulanishlar alohida gateway qatlamida ushlanadi.
- Server-Sent Events (SSE)
- Server bitta ochiq HTTP javob orqali mijozga hodisalarni ketma-ket yuborib turadi. Faqat bir tomonlama (serverdan mijozga), lekin oddiy HTTP ustida ishlaydi va uzilsa o'zi qayta ulanadi.