mufassall

Konspekt · Masshtablash

Vertikal va gorizontal masshtablash

11 daq · Boshlang'ich · mufassall.dtwin.uz/uz/l/vertical-horizontal/

← Darsni ochish

Muammo

Lenta API o'z serveriga sig'may qoladi. Avval kattaroq serverga ko'chadi — kattarog'i qolmaguncha va o'sha bitta server yiqilguncha. Keyin bir nechta kichik serverlarga tarqaladi va buning uchun nega load balancer hamda hech narsani eslab qolmaydigan app kerakligini o'rganadi.

Nimani o'rganasiz

  • Vertikal masshtablash: nega oson va qayerda to'xtaydi
  • Nega bitta server, qanchalik katta bo'lmasin, yagona nosozlik nuqtasi
  • Gorizontal masshtablashga nima kerak: load balancer va stateless app serverlar
  • Nega bitta server hajmida zaxira saqlanadi (N+1)
Yakuniy sahna
92%92%70%

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_users(["Foydalanuvchilar"])
  n_app["App server 1"]
  n_db[("Baza")]
  n_lb{"Load balancer"}
  n_app2["App server 2"]
  n_app3["App server 3"]
  n_sessions{{"Sessiyalar ombori"}}
  n_app --> n_db
  n_users --> n_lb
  n_lb -.-> n_users
  n_lb --> n_app
  n_lb --x|"yo'qoldi"| n_app2
  n_lb --> n_app3
  n_app2 --> n_db
  n_app3 --> n_db
  n_app --> n_sessions
  n_app2 --> n_sessions
  n_app3 --> n_sessions
  classDef down fill:#fde2e2,stroke:#c62828,color:#4a0d0d,stroke-dasharray:4 3
  class n_app2 down

Mermaid: so'rovlar ketma-ketligi

sequenceDiagram
  participant n_users as Foydalanuvchilar
  participant n_app as App server 1
  participant n_lb as Load balancer
  participant n_app2 as App server 2
  participant n_sessions as Sessiyalar ombori
  Note over n_users,n_app: Hammasini bitta server qiladi
  n_users->>n_app: GET /feed HTTP/1.1
  n_app-->>n_users: HTTP/1.1 200 OK
  Note over n_users,n_app: Trafik ikki baravar, server to'ldi
  n_users->>n_app: GET /feed HTTP/1.1
  n_app-->>n_users: HTTP/1.1 503 Service Unavailable
  Note over n_users,n_app: Bitta server — bitta nosozlik
  n_users-xn_app: curl https://api.example.com/feed
  Note over n_lb,n_app2: Gorizontal masshtablash: ko'proq server
  n_lb->>n_app2: GET /feed HTTP/1.1
  n_app2-->>n_lb: HTTP/1.1 200 OK
  Note over n_lb,n_app2: Foydalanuvchilar tizimdan chiqib ketaveradi
  n_lb->>n_app2: GET /cart HTTP/1.1
  n_app2-->>n_lb: HTTP/1.1 302 Found
  Note over n_app2,n_sessions: App serverlarni stateless qilish
  n_app2->>n_sessions: GET session:9c1e7a
  n_sessions-->>n_app2: (bulk string)
  Note over n_lb,n_app2: Bitta server o'ldi, foydalanuvchilar deyarli sezmadi
  n_lb-xn_app2: GET /healthz HTTP/1.1

D2

direction: right

n_users: "Foydalanuvchilar" {
  shape: rectangle
}
n_app: "App server 1" {
  shape: rectangle
}
n_db: "Baza" {
  shape: cylinder
}
n_lb: "Load balancer" {
  shape: diamond
}
n_app2: "App server 2" {
  shape: rectangle
  style.fill: "#fde2e2"
  style.stroke: "#c62828"
  style.stroke-dash: 3
}
n_app3: "App server 3" {
  shape: rectangle
}
n_sessions: "Sessiyalar ombori" {
  shape: hexagon
}

n_app -> n_db
n_users -> n_lb
n_lb -> n_users {
  style.stroke-dash: 3
}
n_lb -> n_app
n_lb -> n_app2: "yo'qoldi" {
  target-arrowhead.shape: cross
}
n_lb -> n_app3
n_app2 -> n_db
n_app3 -> n_db
n_app -> n_sessions
n_app2 -> n_sessions
n_app3 -> n_sessions

PlantUML: so'rovlar ketma-ketligi

@startuml
participant "Foydalanuvchilar" as n_users
participant "App server 1" as n_app
participant "Load balancer" as n_lb
participant "App server 2" as n_app2
collections "Sessiyalar ombori" as n_sessions
note over n_users, n_app : Hammasini bitta server qiladi
n_users -> n_app : GET /feed HTTP/1.1
n_app --> n_users : HTTP/1.1 200 OK
note over n_users, n_app : Trafik ikki baravar, server to'ldi
n_users -> n_app : GET /feed HTTP/1.1
n_app --> n_users : HTTP/1.1 503 Service Unavailable
note over n_users, n_app : Bitta server — bitta nosozlik
n_users ->x n_app : [yo'qoldi] curl https://api.example.com/feed
note over n_lb, n_app2 : Gorizontal masshtablash: ko'proq server
n_lb -> n_app2 : GET /feed HTTP/1.1
n_app2 --> n_lb : HTTP/1.1 200 OK
note over n_lb, n_app2 : Foydalanuvchilar tizimdan chiqib ketaveradi
n_lb -> n_app2 : GET /cart HTTP/1.1
n_app2 --> n_lb : HTTP/1.1 302 Found
note over n_app2, n_sessions : App serverlarni stateless qilish
n_app2 -> n_sessions : GET session:9c1e7a
n_sessions --> n_app2 : (bulk string)
note over n_lb, n_app2 : Bitta server o'ldi, foydalanuvchilar deyarli sezmadi
n_lb ->x n_app2 : [yo'qoldi] GET /healthz HTTP/1.1
@enduml

PlantUML: komponentlar

@startuml
left to right direction
agent "Foydalanuvchilar" as n_users
component "App server 1" as n_app
database "Baza" as n_db
node "Load balancer" as n_lb
component "App server 2" as n_app2 #fde2e2;line:c62828;line.dashed
component "App server 3" as n_app3
stack "Sessiyalar ombori" as n_sessions
n_app --> n_db
n_users --> n_lb
n_lb ..> n_users
n_lb --> n_app
n_lb -[#c62828,dashed]-> n_app2 : yo'qoldi
n_lb --> n_app3
n_app2 --> n_db
n_app3 --> n_db
n_app --> n_sessions
n_app2 --> n_sessions
n_app3 --> n_sessions
@enduml

Xulosa

Avval kattalashtiring: bu oddiy. Server juda qimmat, juda katta yoki yagona bo'lishi juda xavfli bo'lib qolganda — kengaytiring.

1) Bitta server, qanchalik katta bo'lmasin, yagona nosozlik nuqtasi. 2) Ko'p serverlar oldida load balancer kerak. 3) App serverlar stateless bo'lishi shart: sessiya va fayllar umumiy omborlarga. 4) N+1 saqlang. 5) Baza hali ham bitta server: keyingi masshtablanadigan narsa shu.

Ko'rsatkichlar: boshida va oxirida

Ko'rsatkichBoshidaOxirida
Xizmat ko'rsatildi300/s2 400/s
Kechikish p9580 ms240 ms
Xatolar0%0,5%
Oylik narx160 $1 040 $

Qadamlar

  1. Holat Hammasini bitta server qiladi

    Kichik lenta API 4 vCPU li bitta serverda ishlaydi.

  2. Muammo Trafik ikki baravar, server to'ldi

    Reklama kampaniyasidan keyin foydalanuvchilar soniyasiga 700 so'rov yubormoqchi.

  3. Yechim Vertikal masshtablash: kattaroq server

    Eng oson yechim: 16 vCPU li serverga o'tish.

  4. Muammo Bundan kattasi yo'q

    Bir yildan keyin: soniyasiga 2 400 so'rov.

  5. Muammo Bitta server — bitta nosozlik

    Ishdan chiqqan disk serverni to'xtatadi.

  6. Yechim Gorizontal masshtablash: ko'proq server

    Bitta 64 vCPU li gigant o'rniga uchta 8 vCPU li server.

  7. Muammo Foydalanuvchilar tizimdan chiqib ketaveradi

    Sessiyalar foydalanuvchi kirgan serverning xotirasida saqlangan edi.

  8. Yechim App serverlarni stateless qilish

    Sessiyalar umumiy, tez sessiyalar omboriga ko'chadi.

  9. Holat Bitta server o'ldi, foydalanuvchilar deyarli sezmadi

    app-2 yiqiladi.

  10. Xulosa Xulosa

    Avval kattalashtiring: bu oddiy.

Atamalar

Vertikal masshtablash
Serverni kattaroq va kuchliroq serverga almashtirish. Oddiy, lekin bir kun undan kattasi qolmaydi va u baribir yagona nosozlik nuqtasi.
Gorizontal masshtablash
Bitta katta server o'rniga ko'p serverlar qo'yish. Buning uchun oldida load balancer va stateless app serverlar kerak.