mufassall

Konspekt · Arxitektura

Servislarni topish (service discovery)

11 daq · O'rta · mufassall.dtwin.uz/uz/l/service-discovery/

← Darsni ochish

Muammo

Buyurtmalar servisi ombor nusxalarini chaqiradi, ular esa ishga tushadi, to'xtaydi va ko'chadi. Heartbeat'li registry qo'lda yozilgan IP'larni qanday almashtiradi va uni so'rashning uch yo'li: client'dan, DNS orqali yoki load balancer orqali.

Nimani o'rganasiz

  • Nega qo'lda yozilgan manzillar nusxalar ko'chishi bilan buziladi
  • Nusxalar qanday ro'yxatdan o'tadi va heartbeat o'liklarini qanday olib tashlaydi
  • Client-side va server-side discovery
  • DNS orqali topish va uning TTL'i nimaga tushadi
Yakuniy sahna
30%30%40%40%

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_orders["Buyurtmalar servisi"]
  n_inv_a["Ombor A"]
  n_inv_c["Ombor C"]
  n_registry[("Servislar registry'si")]
  n_inv_d["Ombor D"]
  n_lb{"Load balancer"}
  n_inv_c -.-> n_registry
  n_inv_d -.-> n_registry
  n_orders --> n_lb
  n_lb --> n_inv_c
  n_lb --> n_inv_d
  n_registry -.-> n_lb
  classDef down fill:#fde2e2,stroke:#c62828,color:#4a0d0d,stroke-dasharray:4 3
  class n_inv_a down

Mermaid: so'rovlar ketma-ketligi

sequenceDiagram
  participant n_orders as Buyurtmalar servisi
  participant n_inv_a as Ombor A
  participant n_inv_b as Ombor B
  participant n_inv_c as Ombor C
  participant n_registry as Servislar registry'si
  participant n_lb as Load balancer
  Note over n_orders,n_inv_a: Config'da ikkita IP
  n_orders->>n_inv_a: GET /v1/stock/sku_19 HTTP/1.1
  n_inv_a-->>n_orders: HTTP/1.1 200 OK
  Note over n_orders,n_inv_b: Nusxa ko'chdi, config esa yo'q
  n_orders-xn_inv_b: GET /v1/stock/sku_19 HTTP/1.1
  Note over n_inv_c,n_registry: Nusxalar o'zini o'zi ro'yxatdan o'tkazadi
  n_inv_c->>n_registry: PUT /v1/agent/service/register HTTP/1.1
  n_registry-->>n_inv_c: HTTP/1.1 200 OK
  Note over n_orders,n_registry: Client tomonida topish
  n_orders->>n_registry: GET /v1/health/service/inventory?passing=true HTTP/1.1
  n_registry-->>n_orders: HTTP/1.1 200 OK
  Note over n_orders,n_inv_a: Yiqilgan nusxa ro'yxatda qoldi
  n_orders-xn_inv_a: GET /v1/stock/sku_19 HTTP/1.1
  Note over n_inv_c,n_registry: Heartbeat va health check
  n_inv_c->>n_registry: PUT /v1/agent/check/pass/service:inv-c HTTP/1.1
  n_registry-->>n_inv_c: HTTP/1.1 200 OK
  Note over n_orders,n_registry: DNS orqali topish
  n_orders->>n_registry: dig @registry.internal -p 8600 inventory.service.internal A
  n_registry-->>n_orders: #59;#59; ANSWER SECTION:
  Note over n_orders,n_lb: Server tomonida topish: load balancer so'raydi
  n_orders->>n_lb: GET /v1/stock/sku_19 HTTP/1.1
  n_lb-->>n_orders: HTTP/1.1 200 OK

D2

direction: right

n_orders: "Buyurtmalar servisi" {
  shape: rectangle
}
n_inv_a: "Ombor A" {
  shape: rectangle
  style.fill: "#fde2e2"
  style.stroke: "#c62828"
  style.stroke-dash: 3
}
n_inv_c: "Ombor C" {
  shape: rectangle
}
n_registry: "Servislar registry'si" {
  shape: cylinder
}
n_inv_d: "Ombor D" {
  shape: rectangle
}
n_lb: "Load balancer" {
  shape: diamond
}

n_inv_c -> n_registry {
  style.stroke-dash: 3
}
n_inv_d -> n_registry {
  style.stroke-dash: 3
}
n_orders -> n_lb
n_lb -> n_inv_c
n_lb -> n_inv_d
n_registry -> n_lb {
  style.stroke-dash: 3
}

PlantUML: so'rovlar ketma-ketligi

@startuml
participant "Buyurtmalar servisi" as n_orders
participant "Ombor A" as n_inv_a
participant "Ombor B" as n_inv_b
participant "Ombor C" as n_inv_c
database "Servislar registry'si" as n_registry
participant "Load balancer" as n_lb
note over n_orders, n_inv_a : Config'da ikkita IP
n_orders -> n_inv_a : GET /v1/stock/sku_19 HTTP/1.1
n_inv_a --> n_orders : HTTP/1.1 200 OK
note over n_orders, n_inv_b : Nusxa ko'chdi, config esa yo'q
n_orders ->x n_inv_b : [yo'qoldi] GET /v1/stock/sku_19 HTTP/1.1
note over n_inv_c, n_registry : Nusxalar o'zini o'zi ro'yxatdan o'tkazadi
n_inv_c -> n_registry : PUT /v1/agent/service/register HTTP/1.1
n_registry --> n_inv_c : HTTP/1.1 200 OK
note over n_orders, n_registry : Client tomonida topish
n_orders -> n_registry : GET /v1/health/service/inventory?passing=true HTTP/1.1
n_registry --> n_orders : HTTP/1.1 200 OK
note over n_orders, n_inv_a : Yiqilgan nusxa ro'yxatda qoldi
n_orders ->x n_inv_a : [yo'qoldi] GET /v1/stock/sku_19 HTTP/1.1
note over n_inv_c, n_registry : Heartbeat va health check
n_inv_c -> n_registry : PUT /v1/agent/check/pass/service:inv-c HTTP/1.1
n_registry --> n_inv_c : HTTP/1.1 200 OK
note over n_orders, n_registry : DNS orqali topish
n_orders -> n_registry : dig @registry.internal -p 8600 inventory.service.internal A
n_registry --> n_orders : ;; ANSWER SECTION:
note over n_orders, n_lb : Server tomonida topish: load balancer so'raydi
n_orders -> n_lb : GET /v1/stock/sku_19 HTTP/1.1
n_lb --> n_orders : HTTP/1.1 200 OK
@enduml

PlantUML: komponentlar

@startuml
left to right direction
component "Buyurtmalar servisi" as n_orders
component "Ombor A" as n_inv_a #fde2e2;line:c62828;line.dashed
component "Ombor C" as n_inv_c
database "Servislar registry'si" as n_registry
component "Ombor D" as n_inv_d
node "Load balancer" as n_lb
n_inv_c ..> n_registry
n_inv_d ..> n_registry
n_orders --> n_lb
n_lb --> n_inv_c
n_lb --> n_inv_d
n_registry ..> n_lb
@enduml

Xulosa

Nusxa manzillarini hech qachon qo'lda yozmang.

1) Ishga tushganda nusxalar nomi va manzilini registry'ga yozadi. 2) TTL'li heartbeat va faol health check o'lik nusxalarni avtomatik olib tashlaydi. 3) Client-side: chaqiruvchi registry'dan o'zi so'raydi va balanslaydi, ortiqcha qadam yo'q. 4) Server-side: load balancer siz uchun so'raydi, chaqiruvchilar soddaroq, lekin bitta qadam ko'p. 5) DNS hamma joyda ishlaydi, lekin TTL va keshlashga e'tibor bering.

Ko'rsatkichlar: boshida va oxirida

Ko'rsatkichBoshidaOxirida
Yiqilgan ombor so'rovlari0,1%0,3%
O'lik nusxani chaqirishni to'xtatish vaqti1 800 s15 s
Tirik ombor nusxalari22

Qadamlar

  1. Holat Config'da ikkita IP

    Har buyurtmadan oldin buyurtmalar servisi qoldiqni tekshiradi.

  2. Muammo Nusxa ko'chdi, config esa yo'q

    Host yiqilgandan keyin platforma B nusxasini almashtirdi.

  3. Yechim Nusxalar o'zini o'zi ro'yxatdan o'tkazadi

    Servislar registry'si kichik, yuqori darajada ishonchli baza: kim qayerda ishlayapti.

  4. Yechim Client tomonida topish

    Buyurtmalar registry'dan sog' inventory nusxalarini so'raydi, ro'yxatni bir necha soniya keshda saqlaydi va har chaqiruvga nusxani o'zi navbat bilan tanlaydi.

  5. Muammo Yiqilgan nusxa ro'yxatda qoldi

    A nusxasining host'ida elektr o'chdi.

  6. Yechim Heartbeat va health check

    Endi har nusxa har 5 soniyada «men tirikman» deydi, TTL 15 soniya.

  7. Holat DNS orqali topish

    Registry DNS orqali ham javob bera oladi.

  8. Yechim Server tomonida topish: load balancer so'raydi

    Endi buyurtmalar bitta barqaror nomni chaqiradi, inventory.internal.

  9. Xulosa Xulosa

    Nusxa manzillarini hech qachon qo'lda yozmang.

Atamalar

Service discovery
Nusxalar ishga tushganda nomi va manzilini registry'ga yozadi, heartbeat to'xtasa o'chiriladi. Chaqiruvchi manzilni qo'lda emas, registry'dan oladi: o'zi (client-side), load balancer orqali (server-side) yoki DNS orqali.