Konspekt · Masshtablash
CDN va edge keshlar
Muammo
Do'kon serveri bir qit'ada, xaridorlari boshqasida. Rasm va skriptlar foydalanuvchilarga yaqin edge (chekka server) keshlarga ko'chadi: so'rov edge'ga qanday yetadi, qachon origin'ga qaytadi, faylni qanday almashtirish va nimani hech qachon keshlab bo'lmaydi.
Nimani o'rganasiz
- Edge kesh foydalanuvchi va origin orasida qanday turadi, miss va hit qanchaga tushadi
- Nima va qancha keshlanishini
Cache-Controlhal qiladi - Faylni almashtirish: purge yoki versiyali URL
- Origin shield va nega shaxsiy javoblar hech qachon keshlanmaydi
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_client(["Xaridor, A hudud"])
n_origin["Origin server"]
n_bucket[("Fayl ombori")]
n_edge[/"Edge kesh A"\]
n_client2(["Xaridor, B hudud"])
n_edge2[/"Edge kesh B"\]
n_shield[/"Origin shield"\]
n_origin --> n_bucket
n_client --> n_edge
n_client2 --> n_edge2
n_edge --> n_shield
n_edge2 --> n_shield
n_shield --> n_originMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_client as Xaridor, A hudud
participant n_origin as Origin server
participant n_edge as Edge kesh A
actor n_ops as Muhandis
participant n_edge2 as Edge kesh B
participant n_shield as Origin shield
participant n_client2 as Xaridor, B hudud
Note over n_client,n_origin: Har rasm sayyoraning yarmini kesib o'tadi
n_client->>n_origin: GET /img/sofa-1042.jpg HTTP/1.1
n_origin-->>n_client: HTTP/1.1 200 OK
Note over n_client,n_edge: Xaridorlar yonida kesh
n_client->>n_edge: dig static.example.com
n_edge-->>n_client: static.example.com. 300 IN CNAME edge.cdn.example.net.
Note over n_edge,n_origin: Miss: edge origin'dan bir marta so'raydi
n_edge->>n_origin: GET /img/sofa-1042.jpg HTTP/1.1
n_origin-->>n_edge: HTTP/1.1 200 OK
Note over n_client,n_edge: Hit: origin ishtirok etmaydi
n_client->>n_edge: GET /img/sofa-1042.jpg HTTP/1.1
n_edge-->>n_client: HTTP/1.1 200 OK
Note over n_client,n_edge: Rasm o'zgardi, edge'da esa eskisi
n_client->>n_edge: GET /img/sofa-1042.jpg HTTP/1.1
n_edge-->>n_client: HTTP/1.1 200 OK
Note over n_ops,n_edge: Purge: har edge'ga faylni tashlashni ayt
n_ops->>n_edge: POST /v1/purge HTTP/1.1
n_edge-->>n_ops: HTTP/1.1 202 Accepted
Note over n_client,n_edge: Versiyali URL: yangi faylga yangi nom
n_client->>n_edge: GET /img/sofa-1042.3f9a2c.jpg HTTP/1.1
n_edge-->>n_client: HTTP/1.1 200 OK
Note over n_edge2,n_origin: Har edge origin'dan o'zi so'raydi
n_edge2->>n_origin: GET /app.9c1d.js edge=edge-a MISS
Note over n_shield,n_origin: O'rtada origin shield
n_shield->>n_origin: GET /app.9c1d.js HTTP/1.1
n_origin-->>n_shield: HTTP/1.1 200 OK
Note over n_client2,n_edge2: Shaxsiy javob keshlandi
n_client2->>n_edge2: GET /api/cart HTTP/1.1
n_edge2-->>n_client2: HTTP/1.1 200 OK
Note over n_client2,n_edge2: Shaxsiy javoblar: private, no-store
n_client2->>n_edge2: GET /api/cart HTTP/1.1
n_edge2-->>n_client2: HTTP/1.1 200 OKD2
direction: right
n_client: "Xaridor, A hudud" {
shape: rectangle
}
n_origin: "Origin server" {
shape: rectangle
}
n_bucket: "Fayl ombori" {
shape: stored_data
}
n_edge: "Edge kesh A" {
shape: oval
}
n_client2: "Xaridor, B hudud" {
shape: rectangle
}
n_edge2: "Edge kesh B" {
shape: oval
}
n_shield: "Origin shield" {
shape: oval
}
n_origin -> n_bucket
n_client -> n_edge
n_client2 -> n_edge2
n_edge -> n_shield
n_edge2 -> n_shield
n_shield -> n_originPlantUML: so'rovlar ketma-ketligi
@startuml
participant "Xaridor, A hudud" as n_client
participant "Origin server" as n_origin
participant "Edge kesh A" as n_edge
actor "Muhandis" as n_ops
participant "Edge kesh B" as n_edge2
participant "Origin shield" as n_shield
participant "Xaridor, B hudud" as n_client2
note over n_client, n_origin : Har rasm sayyoraning yarmini kesib o'tadi
n_client -> n_origin : GET /img/sofa-1042.jpg HTTP/1.1
n_origin --> n_client : HTTP/1.1 200 OK
note over n_client, n_edge : Xaridorlar yonida kesh
n_client -> n_edge : dig static.example.com
n_edge --> n_client : static.example.com. 300 IN CNAME edge.cdn.example.net.
note over n_edge, n_origin : Miss: edge origin'dan bir marta so'raydi
n_edge -> n_origin : GET /img/sofa-1042.jpg HTTP/1.1
n_origin --> n_edge : HTTP/1.1 200 OK
note over n_client, n_edge : Hit: origin ishtirok etmaydi
n_client -> n_edge : GET /img/sofa-1042.jpg HTTP/1.1
n_edge --> n_client : HTTP/1.1 200 OK
note over n_client, n_edge : Rasm o'zgardi, edge'da esa eskisi
n_client -> n_edge : GET /img/sofa-1042.jpg HTTP/1.1
n_edge --> n_client : HTTP/1.1 200 OK
note over n_ops, n_edge : Purge: har edge'ga faylni tashlashni ayt
n_ops -> n_edge : POST /v1/purge HTTP/1.1
n_edge --> n_ops : HTTP/1.1 202 Accepted
note over n_client, n_edge : Versiyali URL: yangi faylga yangi nom
n_client -> n_edge : GET /img/sofa-1042.3f9a2c.jpg HTTP/1.1
n_edge --> n_client : HTTP/1.1 200 OK
note over n_edge2, n_origin : Har edge origin'dan o'zi so'raydi
n_edge2 -> n_origin : GET /app.9c1d.js edge=edge-a MISS
note over n_shield, n_origin : O'rtada origin shield
n_shield -> n_origin : GET /app.9c1d.js HTTP/1.1
n_origin --> n_shield : HTTP/1.1 200 OK
note over n_client2, n_edge2 : Shaxsiy javob keshlandi
n_client2 -> n_edge2 : GET /api/cart HTTP/1.1
n_edge2 --> n_client2 : HTTP/1.1 200 OK
note over n_client2, n_edge2 : Shaxsiy javoblar: private, no-store
n_client2 -> n_edge2 : GET /api/cart HTTP/1.1
n_edge2 --> n_client2 : HTTP/1.1 200 OK
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Xaridor, A hudud" as n_client
component "Origin server" as n_origin
storage "Fayl ombori" as n_bucket
frame "Edge kesh A" as n_edge
agent "Xaridor, B hudud" as n_client2
frame "Edge kesh B" as n_edge2
frame "Origin shield" as n_shield
n_origin --> n_bucket
n_client --> n_edge
n_client2 --> n_edge2
n_edge --> n_shield
n_edge2 --> n_shield
n_shield --> n_origin
@endumlXulosa
CDN uchun besh qoida.
1) Statik fayllar foydalanuvchiga yaqin edge'dan beriladi; origin faqat miss'larni to'ldiradi. 2) Origin har javobda Cache-Control ni aniq qo'yadi. 3) Fayllar versiyali URL bilan almashtiriladi; purge favqulodda holat uchun. 4) Origin shield ko'p edge miss'ini bittaga aylantiradi. 5) Shaxsiy javoblar doim private, no-store.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Sahifa yuklanishi p95 | 1 900 ms | 120 ms |
| Edge'da hit ulushi | 0% | 93% |
| Origin'ga so'rovlar | 1 200/s | 120/s |
| Noto'g'ri kontent | 0% | 0% |
Qadamlar
- Muammo Har rasm sayyoraning yarmini kesib o'tadi
Do'kon serveri bitta data markazda.
- Yechim Xaridorlar yonida kesh
CDN ko'p shaharlarda kesh serverlarini ushlab turadi.
- Holat Miss: edge origin'dan bir marta so'raydi
Edge'da rasm hali yo'q.
- Holat Hit: origin ishtirok etmaydi
Shu hududdagi keyingi har xaridor rasmni to'g'ridan-to'g'ri edge'dan oladi.
- Muammo Rasm o'zgardi, edge'da esa eskisi
Do'kon o'sha fayl nomi bilan yaxshiroq rasm yuklaydi.
- Yechim Purge: har edge'ga faylni tashlashni ayt
Muhandis CDN'ning purge API'sini chaqiradi.
- Yechim Versiyali URL: yangi faylga yangi nom
Build har fayl nomiga uning tarkibidan olingan qisqa hash qo'shadi.
- Muammo Har edge origin'dan o'zi so'raydi
Ikkinchi hududdagi xaridorlarga o'z edge'i beriladi.
- Yechim O'rtada origin shield
Edge'lar endi origin o'rniga bitta o'rta keshdan, origin shield'dan so'raydi.
- Muammo Shaxsiy javob keshlandi
Savat endpoint'i xato bilan
publicdeb javob berdi. - Yechim Shaxsiy javoblar: private, no-store
Shaxsiy API javoblari endi
private, no-storebilan keladi. - Xulosa Xulosa
CDN uchun besh qoida.
Atamalar
- CDN va edge
- Statik fayllarni foydalanuvchiga yaqin edge serverlardagi keshdan beradigan tarmoq. Origin faqat miss'larni to'ldiradi, nima va qancha keshlanishini Cache-Control hal qiladi.
- Origin shield
- Edge'lar va origin orasidagi oraliq kesh qatlami. Har edge alohida so'rash o'rniga ko'p edge miss'i origin'ga bitta so'rov bo'lib boradi.