Konspekt · Aloqa
Callback'lar ishonchliligi
Muammo
Tashqi tizim sizga xabar yuboradi. Xabar yo'qolmasligi, ikki marta ishlanmasligi va tizimni sekinlashtirmasligi uchun nima qilish kerak.
Nimani o'rganasiz
- Nega
200 OKfaqat saqlagandan keyin qaytariladi - Navbat va worker javobni og'ir ishdan qanday ajratadi
- Ack qachon beriladi: ishdan oldin yoki keyin
- Takroriy yetkazish va idempotentlik kaliti
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_provider>"Tashqi tizim"]
n_api["API"]
n_store[("Baza")]
n_queue[["Navbat"]]
n_worker("Worker")
n_provider -->|"chaqiruv"| n_api
n_api -->|"chaqiruv"| n_store
n_api -->|"asinxron"| n_queue
n_queue -->|"asinxron"| n_worker
n_worker -->|"chaqiruv"| n_storeMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_provider as Tashqi tizim
participant n_api as API
participant n_store as Baza
participant n_queue as Navbat
participant n_worker as Worker
Note over n_provider,n_api: Hamma ish javobdan oldin
n_provider->>n_api: POST /callbacks HTTP/1.1
n_api-->>n_provider: HTTP/1.1 200 OK
Note over n_api,n_store: Xato bo'lsa ham 200 OK
n_api-xn_store: BEGIN#59;
Note over n_api,n_store: Avval saqla, keyin javob ber
n_api->>n_store: INSERT INTO inbox (event_id, payload, received_at)
n_store-->>n_api: INSERT 0 1
Note over n_api,n_queue: Og'ir ish navbatga
n_api->>n_queue: PUBLISH callbacks.work
Note over n_queue,n_worker: Ack juda erta berildi
n_queue-xn_worker: DELIVER callbacks.work delivery_tag=7
Note over n_queue,n_worker: Ack — faqat ish tugagach
n_queue->>n_worker: DELIVER callbacks.work delivery_tag=7 redelivered=true
n_worker-->>n_queue: ACK delivery_tag=7
Note over n_provider,n_api: Bitta xabar, ikki natija
n_provider->>n_api: POST /callbacks HTTP/1.1
Note over n_worker,n_store: Idempotentlik kaliti
n_worker->>n_store: INSERT INTO processed (event_id, result)
n_store-->>n_worker: INSERT 0 0D2
direction: right
n_provider: "Tashqi tizim" {
shape: cloud
}
n_api: "API" {
shape: rectangle
}
n_store: "Baza" {
shape: cylinder
}
n_queue: "Navbat" {
shape: queue
}
n_worker: "Worker" {
shape: rectangle
style.multiple: true
}
n_provider -> n_api: "chaqiruv"
n_api -> n_store: "chaqiruv"
n_api -> n_queue: "asinxron"
n_queue -> n_worker: "asinxron"
n_worker -> n_store: "chaqiruv"PlantUML: so'rovlar ketma-ketligi
@startuml
boundary "Tashqi tizim" as n_provider
participant "API" as n_api
database "Baza" as n_store
queue "Navbat" as n_queue
participant "Worker" as n_worker
note over n_provider, n_api : Hamma ish javobdan oldin
n_provider -> n_api : POST /callbacks HTTP/1.1
n_api --> n_provider : HTTP/1.1 200 OK
note over n_api, n_store : Xato bo'lsa ham 200 OK
n_api ->x n_store : [yo'qoldi] BEGIN;
note over n_api, n_store : Avval saqla, keyin javob ber
n_api -> n_store : INSERT INTO inbox (event_id, payload, received_at)
n_store --> n_api : INSERT 0 1
note over n_api, n_queue : Og'ir ish navbatga
n_api ->> n_queue : PUBLISH callbacks.work
note over n_queue, n_worker : Ack juda erta berildi
n_queue ->x n_worker : [yo'qoldi] DELIVER callbacks.work delivery_tag=7
note over n_queue, n_worker : Ack — faqat ish tugagach
n_queue ->> n_worker : [qayta urinish] DELIVER callbacks.work delivery_tag=7 redelivered=true
n_worker -->> n_queue : ACK delivery_tag=7
note over n_provider, n_api : Bitta xabar, ikki natija
n_provider -> n_api : [dublikat] POST /callbacks HTTP/1.1
note over n_worker, n_store : Idempotentlik kaliti
n_worker -> n_store : INSERT INTO processed (event_id, result)
n_store --> n_worker : INSERT 0 0
@endumlPlantUML: komponentlar
@startuml
left to right direction
cloud "Tashqi tizim" as n_provider
component "API" as n_api
database "Baza" as n_store
queue "Navbat" as n_queue
collections "Worker" as n_worker
n_provider --> n_api : chaqiruv
n_api --> n_store : chaqiruv
n_api --> n_queue : asinxron
n_queue --> n_worker : asinxron
n_worker --> n_store : chaqiruv
@endumlXulosa
Ishonchli callback uchun to'rt qoida.
1) 200 faqat xabar saqlangandan keyin. 2) Og'ir ish navbat va worker'da. 3) Ack — ish tugagach. 4) Har ish idempotent: takror kelsa ham natija bitta.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Kiruvchi | 40/s | 40/s |
| Javob p95 | 3 800 ms | 30 ms |
| Yo'qolgan | 0% | 0% |
| Ikki marta | 0/daq | 0/daq |
Qadamlar
- Muammo Hamma ish javobdan oldin
Tashqi tizim callback yuboradi.
- Muammo Xato bo'lsa ham
200 OKBazaga yozish yarim yo'lda yiqildi.
- Yechim Avval saqla, keyin javob ber
API endi bitta ish qiladi: kelgan xabarni o'zgartirmasdan bazadagi inbox jadvaliga yozadi va darhol
200qaytaradi. - Yechim Og'ir ish navbatga
Xabar saqlangach, API navbatga qisqa topshiriq qo'yadi.
- Muammo Ack juda erta berildi
Worker xabarni olishi bilan navbatga «qabul qildim» (
ack) deydi va keyin ishlay boshlaydi. - Yechim Ack — faqat ish tugagach
Worker ack'ni natija bazaga yozilgandan keyin beradi.
- Holat Bitta xabar, ikki natija
Takror ikki joydan keladi: tashqi tizim timeout'dan keyin qayta yuboradi, navbat esa worker yiqilgach qayta yetkazadi.
- Yechim Idempotentlik kaliti
Har xabarning barqaror kaliti bor, masalan hujjat ID va holat.
- Xulosa Xulosa
Ishonchli callback uchun to'rt qoida.
Atamalar
- Idempotentlik
- Amalni bir marta yoki bir necha marta bajarish bir xil natija beradi. Xabarlar qayta yetkazilishi mumkin, shuning uchun har handler idempotent bo'lishi kerak.