Konspekt · Biznes jarayonlar
Xabarnomalarni yetkazish
Muammo
Biznes ilova kirish kodlari, "hisob-faktura keldi" xabarlari va to'lov kvitansiyalarini yuboradi. Ularni so'rov ichida yuborish ilovani sekin provayderga bog'lab qo'yadi. Outbox, navbat va yuboruvchi worker provayderni so'rovdan chiqaradi; keyin rate limit, yetkazish kvitansiyalari, muddatli zaxira kanallar zanjiri, takrorlarni olib tashlash, foydalanuvchi sozlamalari, narx va ikkinchi provayder keladi.
Nimani o'rganasiz
- Nega xabar biznes hodisa bilan birga outbox'ga yoziladi va uni so'rov emas, worker yuboradi
- Har provayder uchun token bucket bilan rate limit,
429vaRetry-After, kirish kodlari uchun alohida yo'lak - Qabul qilindi degani yetkazildi degani emas: yetkazish kvitansiyalari, push, SMS, email zanjiri va muddati o'tgan kodni to'xtatadigan muddat
- Bitta hodisa, har kanalga bitta xabar: idempotency kalitlari, sokin soatlar, sozlamalar, har xabar narxi va provayderni almashtirish
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_api["Biznes API"]
n_sms>"SMS provayder A"]
n_db[("Outbox bazasi")]
n_queue[["Navbat"]]
n_worker("Yuboruvchi worker")
n_limiter{{"Rate limiter"}}
n_sms2>"SMS provayder B"]
n_api --> n_db
n_db --> n_queue
n_queue --> n_worker
n_worker --x|"yo'qoldi"| n_sms
n_worker --> n_limiter
n_sms -.-> n_api
n_worker --> n_db
n_worker --> n_sms2
classDef down fill:#fde2e2,stroke:#c62828,color:#4a0d0d,stroke-dasharray:4 3
class n_sms downMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_api as Biznes API
participant n_sms as SMS provayder A
participant n_db as Outbox bazasi
participant n_queue as Navbat
participant n_worker as Yuboruvchi worker
participant n_limiter as Rate limiter
participant n_push as Push servis
participant n_sms2 as SMS provayder B
Note over n_api,n_sms: API SMS'ni so'rov ichida yuboradi
n_api->>n_sms: POST /v1/messages HTTP/1.1
n_sms-->>n_api: HTTP/1.1 200 OK
Note over n_api,n_sms: Sekin provayder kirishni ham, qolgan hammasini ham to'xtatadi
n_api->>n_sms: 09:00:02 POST /auth/otp u_42: calling SMS provider
Note over n_api,n_db: Xabarni o'sha tranzaksiyada outbox'ga yozish
n_api->>n_db: BEGIN#59;
n_db-->>n_api: COMMIT 12 ms
Note over n_queue,n_worker: Navbat va yuboruvchi worker yuboradi
n_queue->>n_worker: notifications.sms partition 3 offset 88120
Note over n_worker,n_sms: Oy oxiri: provayder 429 qaytaradi
n_worker->>n_sms: POST /v1/messages HTTP/1.1
n_sms-->>n_worker: HTTP/1.1 429 Too Many Requests
Note over n_worker,n_limiter: Har provayderga token bucket, kodlarga alohida yo'lak
n_worker->>n_limiter: EVAL token_bucket 1 bucket:sms_a rate=50 burst=50 take=1
n_limiter-->>n_worker: (integer) 0
Note over n_sms,n_api: Qabul qilindi degani yetkazildi emas: yetkazish kvitansiyalari
n_sms->>n_api: POST /webhooks/sms-dlr HTTP/1.1
n_api-->>n_sms: HTTP/1.1 200 OK
Note over n_worker,n_push: Har turdagi xabar uchun muddatli zaxira zanjiri
n_worker->>n_push: ob_7730 invoice.received chain: push -#62; sms -#62; email
Note over n_worker,n_db: Bitta hodisa, har kanalga bitta xabar
n_worker->>n_db: INSERT INTO deliveries (event_id, channel, provider_ref)
n_db-->>n_worker: INSERT 0 0
Note over n_worker,n_db: Foydalanuvchi sozlamalari va sokin soatlar
n_worker->>n_db: SELECT channels, quiet_hours, tz FROM prefs WHERE user_id = 'u_77'
n_db-->>n_worker: decision ob_7731 payment.receipt at 23:40 local
Note over n_worker,n_sms2: Har xabar narxi va ikkinchi provayder
n_worker->>n_sms2: cost ob_5590 otp_login provider=sms_bD2
direction: right
n_api: "Biznes API" {
shape: rectangle
}
n_sms: "SMS provayder A" {
shape: cloud
style.fill: "#fde2e2"
style.stroke: "#c62828"
style.stroke-dash: 3
}
n_db: "Outbox bazasi" {
shape: cylinder
}
n_queue: "Navbat" {
shape: queue
}
n_worker: "Yuboruvchi worker" {
shape: rectangle
style.multiple: true
}
n_limiter: "Rate limiter" {
shape: hexagon
}
n_sms2: "SMS provayder B" {
shape: cloud
}
n_api -> n_db
n_db -> n_queue
n_queue -> n_worker
n_worker -> n_sms: "yo'qoldi" {
target-arrowhead.shape: cross
}
n_worker -> n_limiter
n_sms -> n_api {
style.stroke-dash: 3
}
n_worker -> n_db
n_worker -> n_sms2PlantUML: so'rovlar ketma-ketligi
@startuml
participant "Biznes API" as n_api
boundary "SMS provayder A" as n_sms
database "Outbox bazasi" as n_db
queue "Navbat" as n_queue
participant "Yuboruvchi worker" as n_worker
collections "Rate limiter" as n_limiter
boundary "Push servis" as n_push
boundary "SMS provayder B" as n_sms2
note over n_api, n_sms : API SMS'ni so'rov ichida yuboradi
n_api -> n_sms : POST /v1/messages HTTP/1.1
n_sms --> n_api : HTTP/1.1 200 OK
note over n_api, n_sms : Sekin provayder kirishni ham, qolgan hammasini ham to'xtatadi
n_api -> n_sms : 09:00:02 POST /auth/otp u_42: calling SMS provider
note over n_api, n_db : Xabarni o'sha tranzaksiyada outbox'ga yozish
n_api -> n_db : BEGIN;
n_db --> n_api : COMMIT 12 ms
note over n_queue, n_worker : Navbat va yuboruvchi worker yuboradi
n_queue -> n_worker : notifications.sms partition 3 offset 88120
note over n_worker, n_sms : Oy oxiri: provayder 429 qaytaradi
n_worker -> n_sms : POST /v1/messages HTTP/1.1
n_sms --> n_worker : HTTP/1.1 429 Too Many Requests
note over n_worker, n_limiter : Har provayderga token bucket, kodlarga alohida yo'lak
n_worker -> n_limiter : EVAL token_bucket 1 bucket:sms_a rate=50 burst=50 take=1
n_limiter --> n_worker : (integer) 0
note over n_sms, n_api : Qabul qilindi degani yetkazildi emas: yetkazish kvitansiyalari
n_sms -> n_api : POST /webhooks/sms-dlr HTTP/1.1
n_api --> n_sms : HTTP/1.1 200 OK
note over n_worker, n_push : Har turdagi xabar uchun muddatli zaxira zanjiri
n_worker -> n_push : ob_7730 invoice.received chain: push -> sms -> email
note over n_worker, n_db : Bitta hodisa, har kanalga bitta xabar
n_worker -> n_db : INSERT INTO deliveries (event_id, channel, provider_ref)
n_db --> n_worker : INSERT 0 0
note over n_worker, n_db : Foydalanuvchi sozlamalari va sokin soatlar
n_worker -> n_db : SELECT channels, quiet_hours, tz FROM prefs WHERE user_id = 'u_77'
n_db --> n_worker : decision ob_7731 payment.receipt at 23:40 local
note over n_worker, n_sms2 : Har xabar narxi va ikkinchi provayder
n_worker -> n_sms2 : cost ob_5590 otp_login provider=sms_b
@endumlPlantUML: komponentlar
@startuml
left to right direction
component "Biznes API" as n_api
cloud "SMS provayder A" as n_sms #fde2e2;line:c62828;line.dashed
database "Outbox bazasi" as n_db
queue "Navbat" as n_queue
collections "Yuboruvchi worker" as n_worker
stack "Rate limiter" as n_limiter
cloud "SMS provayder B" as n_sms2
n_api --> n_db
n_db --> n_queue
n_queue --> n_worker
n_worker -[#c62828,dashed]-> n_sms : yo'qoldi
n_worker --> n_limiter
n_sms ..> n_api
n_worker --> n_db
n_worker --> n_sms2
@endumlXulosa
Xabar yetkazishning olti qoidasi.
1) Provayderni hech qachon foydalanuvchi so'rovi ichida chaqirmang: xabarni hodisa bilan bitta tranzaksiyada outbox'ga yozing, worker uni navbatdan yuborsin. 2) Yuborishni har provayder uchun token bucket bilan cheklang, 429 va Retry-After'ga amal qiling, kirish kodlariga alohida yo'lak bering. 3) Qabul qilindi yetkazildi emas: kvitansiyalarni kuzating, kvitansiya yo'qligini noma'lum deb hisoblang. 4) Har turdagi xabar uchun muddatli zaxira zanjiri ishlating, shunda muddati o'tgan kod yuborilmaydi. 5) Hodisa va kanal bo'yicha takrorni olib tashlang, sozlamalar va sokin soatlarni hurmat qiling. 6) Har xabar narxini yozing va ikkinchi provayderni circuit breaker ortida tayyor saqlang.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| API p95 kechikishi | 320 ms | 140 ms |
| Yetkazilgan | 97% | 98% |
| Takror xabarlar | 0/kun | 0/kun |
| Kunlik xabar xarajati | 410 $ | 345 $ |
Qadamlar
- Holat API SMS'ni so'rov ichida yuboradi
Foydalanuvchi tizimga kiradi.
- Muammo Sekin provayder kirishni ham, qolgan hammasini ham to'xtatadi
09:00 da provayder 0.3 s o'rniga 10 s da javob beradi.
- Yechim Xabarni o'sha tranzaksiyada outbox'ga yozish
Kirish so'rovi endi kodni va bitta
outboxqatorini bitta tranzaksiyada saqlaydi: qaysi hodisa, qaysi kanal, qaysi shablon va qachongacha yetishi kerak. - Yechim Navbat va yuboruvchi worker yuboradi
Relay yangi outbox qatorlarini o'qiydi va ularni navbatga chiqaradi, har kanalga alohida topic.
- Muammo Oy oxiri: provayder 429 qaytaradi
Oyning oxirgi kuni soat 18:00 da navbatga 40 000 ta hisob-faktura xabari tushadi.
- Yechim Har provayderga token bucket, kodlarga alohida yo'lak
Har yuborishdan oldin worker umumiy rate limiter'dan token oladi: har provayderga bitta bucket, soniyasiga 50 token, hamma worker'lar uchun umumiy.
- Holat Qabul qilindi degani yetkazildi emas: yetkazish kvitansiyalari
Provayderning
200javobi faqat u xabarni olganini bildiradi. - Yechim Har turdagi xabar uchun muddatli zaxira zanjiri
Har turdagi xabarning zanjiri bor.
- Yechim Bitta hodisa, har kanalga bitta xabar
Navbat xabarni kamida bir marta yetkazadi.
- Yechim Foydalanuvchi sozlamalari va sokin soatlar
Yuborishdan oldin worker foydalanuvchi sozlamalarini o'qiydi: har turdagi xabar uchun kanallar, sokin soatlar va vaqt mintaqasi.
- Yechim Har xabar narxi va ikkinchi provayder
Har yuborish narx qatorini yozadi: provayder, bo'laklar, kodlash, narx.
- Xulosa Xulosa
Xabar yetkazishning olti qoidasi.
Atamalar
- Yetkazish kvitansiyasi (DLR)
- SMS yoki push provayderining xabar telefonga yetdimi yoki yo'qligini keyinroq bildiradigan callback'i. Qabul qilindi degani yetkazildi degani emas.
- Kanallar zaxira zanjiri
- Xabar turi uchun ketma-ket sinaladigan kanallar (push, SMS, email). Birinchi tasdiqlangan yetkazishda yoki xabar muddati tugaganda to'xtaydi.
- Sokin soatlar
- Foydalanuvchining mahalliy vaqtidagi oraliq: shoshilinch bo'lmagan xabarlar ertalabgacha ushlab turiladi. Kodlar va xavfsizlik ogohlantirishlari bundan mustasno.