Konspekt · Butun tizimlar
Talablardan dizayngacha
Muammo
Dizayn vazifasiga darhol quti chizmasdan qanday yondashish kerak. Bitta kichik tizim, shahar avtobuslari kelish taxtasi, talablar, taxminiy hisob, yuqori darajadagi rasm va bitta qismning batafsil dizaynidan o'tadi, trade-off'lar esa yozib qo'yiladi.
Nimani o'rganasiz
- Funksional va nofunksional talablar, va nega aynan ikkinchisi dizaynni belgilaydi
- Taxminiy hisob: bir nechta ma'lum sondan o'qish, yozish va hajm
- High-level dizayn: qutilar, strelkalar va tizimning ikki yo'li
- Bitta komponentning low-level dizayni: API, ma'lumot joylashuvi, sxema va yozilgan trade-off
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_rider(["Yo'lovchi ilovasi"])
n_bus(["Avtobus GPS qurilmasi"])
n_api["Kelish API"]
n_db[("Baza")]
n_ingest["Qabul servisi"]
n_queue[["Pozitsiyalar oqimi"]]
n_worker("ETA worker'lar")
n_cache{{"ETA kesh"}}
n_bus --> n_ingest
n_rider --> n_api
n_ingest --> n_queue
n_queue --> n_worker
n_worker --> n_cache
n_worker --> n_db
n_api --x n_cache
n_api --> n_db
classDef down fill:#fde2e2,stroke:#c62828,color:#4a0d0d,stroke-dasharray:4 3
class n_cache downMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_bus as Avtobus GPS qurilmasi
participant n_api as Kelish API
participant n_rider as Yo'lovchi ilovasi
participant n_ingest as Qabul servisi
participant n_queue as Pozitsiyalar oqimi
participant n_worker as ETA worker'lar
participant n_cache as ETA kesh
participant n_db as Baza
Note over n_bus,n_api: «Avtobus kelish taxtasini qiling»
n_bus->>n_api: POST /positions HTTP/1.1
n_api-->>n_bus: HTTP/1.1 204 No Content
Note over n_rider,n_api: Talablar: nima qiladi va qanchalik yaxshi
n_rider->>n_api: GET /stops/s_204/arrivals HTTP/1.1
n_api-->>n_rider: HTTP/1.1 200 OK
Note over n_ingest,n_queue: High-level dizayn: ikki yo'l
n_ingest->>n_queue: topic bus-positions, key b_17, partition 3
Note over n_queue,n_worker: Worker ortda qolmoqda
n_queue->>n_worker: consumer group eta-workers
Note over n_rider,n_api: Low-level dizayn: kelish API'si
n_rider->>n_api: GET /v1/stops/s_204/arrivals HTTP/1.1
n_api-->>n_rider: HTTP/1.1 200 OK
Note over n_worker,n_cache: Low-level dizayn: har bekatga bitta kalit
n_worker->>n_cache: HSET arrivals:s_204 R11 240 R3 610 updated_at 1795421720
n_cache-->>n_worker: (integer) 3
Note over n_worker,n_db: Low-level dizayn: tarix jadvali
n_worker->>n_db: INSERT INTO positions (bus_id, route, ts, lat, lon)
n_db-->>n_worker: INSERT 0 1
Note over n_rider,n_api: Trade-off: eskiroq, lekin mavjud
n_rider->>n_api: GET /v1/stops/s_204/arrivals HTTP/1.1
n_api-->>n_rider: HTTP/1.1 200 OKD2
direction: right
n_rider: "Yo'lovchi ilovasi" {
shape: rectangle
}
n_bus: "Avtobus GPS qurilmasi" {
shape: rectangle
}
n_api: "Kelish API" {
shape: rectangle
}
n_db: "Baza" {
shape: cylinder
}
n_ingest: "Qabul servisi" {
shape: rectangle
}
n_queue: "Pozitsiyalar oqimi" {
shape: queue
}
n_worker: "ETA worker'lar" {
shape: rectangle
style.multiple: true
}
n_cache: "ETA kesh" {
shape: hexagon
style.fill: "#fde2e2"
style.stroke: "#c62828"
style.stroke-dash: 3
}
n_bus -> n_ingest
n_rider -> n_api
n_ingest -> n_queue
n_queue -> n_worker
n_worker -> n_cache
n_worker -> n_db
n_api -> n_cache {
target-arrowhead.shape: cross
}
n_api -> n_dbPlantUML: so'rovlar ketma-ketligi
@startuml
participant "Avtobus GPS qurilmasi" as n_bus
participant "Kelish API" as n_api
participant "Yo'lovchi ilovasi" as n_rider
participant "Qabul servisi" as n_ingest
queue "Pozitsiyalar oqimi" as n_queue
participant "ETA worker'lar" as n_worker
collections "ETA kesh" as n_cache
database "Baza" as n_db
note over n_bus, n_api : «Avtobus kelish taxtasini qiling»
n_bus -> n_api : POST /positions HTTP/1.1
n_api --> n_bus : HTTP/1.1 204 No Content
note over n_rider, n_api : Talablar: nima qiladi va qanchalik yaxshi
n_rider -> n_api : GET /stops/s_204/arrivals HTTP/1.1
n_api --> n_rider : HTTP/1.1 200 OK
note over n_ingest, n_queue : High-level dizayn: ikki yo'l
n_ingest -> n_queue : topic bus-positions, key b_17, partition 3
note over n_queue, n_worker : Worker ortda qolmoqda
n_queue -> n_worker : [qayta urinish] consumer group eta-workers
note over n_rider, n_api : Low-level dizayn: kelish API'si
n_rider -> n_api : GET /v1/stops/s_204/arrivals HTTP/1.1
n_api --> n_rider : HTTP/1.1 200 OK
note over n_worker, n_cache : Low-level dizayn: har bekatga bitta kalit
n_worker -> n_cache : HSET arrivals:s_204 R11 240 R3 610 updated_at 1795421720
n_cache --> n_worker : (integer) 3
note over n_worker, n_db : Low-level dizayn: tarix jadvali
n_worker -> n_db : INSERT INTO positions (bus_id, route, ts, lat, lon)
n_db --> n_worker : INSERT 0 1
note over n_rider, n_api : Trade-off: eskiroq, lekin mavjud
n_rider -> n_api : GET /v1/stops/s_204/arrivals HTTP/1.1
n_api --> n_rider : HTTP/1.1 200 OK
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Yo'lovchi ilovasi" as n_rider
agent "Avtobus GPS qurilmasi" as n_bus
component "Kelish API" as n_api
database "Baza" as n_db
component "Qabul servisi" as n_ingest
queue "Pozitsiyalar oqimi" as n_queue
collections "ETA worker'lar" as n_worker
stack "ETA kesh" as n_cache #fde2e2;line:c62828;line.dashed
n_bus --> n_ingest
n_rider --> n_api
n_ingest --> n_queue
n_queue --> n_worker
n_worker --> n_cache
n_worker --> n_db
n_api -[#c62828]-> n_cache
n_api --> n_db
@endumlXulosa
Dizayn — har biri raqamga bog'langan qarorlar zanjiri.
1) Avval funksional va nofunksional talablarni yozing: dizaynni ikkinchisi hal qiladi. 2) Og'ir qismni topish uchun o'qish, yozish va hajmni taxmin qiling. 3) High-level: qutilar va strelkalar, har xil yukka alohida yo'l. 4) Low-level bir vaqtda bitta komponent uchun: API, ma'lumot joylashuvi, sxema. 5) Har trade-off'ni va uning ortidagi talabni yozib qo'ying.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Kelayotgan pozitsiyalar | 80/s | 80/s |
| Yo'lovchi so'rovlari | 3 000/s | 3 000/s |
| Javob p95 | 900 ms | 180 ms |
| ETA yoshi | 12 s | 60 s |
Qadamlar
- Muammo «Avtobus kelish taxtasini qiling»
Vazifa bitta gap.
- Yechim Talablar: nima qiladi va qanchalik yaxshi
Funksional: avtobus har 10 soniyada pozitsiyasini yuboradi; yo'lovchi bekatni ochadi va keyingi avtobuslarni kelishigacha qolgan daqiqalar bilan ko'radi.
- Holat Qutilardan oldin taxminiy raqamlar
800 avtobus, har 10 soniyada bitta pozitsiya: soniyasiga 80 yozish.
- Yechim High-level dizayn: ikki yo'l
Rasmda endi ikkita alohida yo'l bor.
- Muammo Worker ortda qolmoqda
Tig'iz soatda bitta worker har pozitsiya uchun kelish vaqtini hisoblaydi.
- Yechim Ko'proq worker, har biriga partition'lar
Worker guruhi to'rtta nusxaga o'sadi, 12 partition ular orasida bo'linadi.
- Yechim Low-level dizayn: kelish API'si
Endi bitta komponent batafsil.
- Yechim Low-level dizayn: har bekatga bitta kalit
Keshda har bekatga bitta hash: yo'nalish va kelishgacha soniyalar, ustiga hisoblangan vaqt.
- Yechim Low-level dizayn: tarix jadvali
Tarix faqat qo'shiladi: har pozitsiyaga bitta qator, hech qachon yangilanmaydi.
- Holat Trade-off: eskiroq, lekin mavjud
Kesh yiqiladi.
- Xulosa Xulosa
Dizayn — har biri raqamga bog'langan qarorlar zanjiri.