mufassall

Konspekt · Arxitektura

Mikroservislar

13 daq · O'rta · mufassall.dtwin.uz/uz/l/microservices/

← Darsni ochish

Muammo

Onlayn kitob do'koni bitta ilova va bitta bazadan boshlanadi. Servislarga bo'lish qachon yordam beradi, har bo'linish nimaga tushadi va API gateway qayerda turadi.

Nimani o'rganasiz

  • Nega monolitdan boshlash kerak va bo'lish vaqti kelganini qaysi belgilar aytadi
  • Bo'linish nima beradi: mustaqil deploy, jamoalar va masshtablash
  • Narxi: tarmoq chaqiruvlari, qisman yiqilish, ma'lumotga egalik, taqsimlangan debugging
  • API gateway kirishda nima qiladi
Yakuniy sahna
40%35%50%30%

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"])
  n_app["Do'kon ilovasi"]
  n_db[("Do'kon bazasi")]
  n_gw{"API gateway"}
  n_search["Qidiruv servisi"]
  n_pay["To'lov servisi"]
  n_paydb[("To'lov bazasi")]
  n_queue[["Hodisalar jurnali"]]
  n_app --> n_db
  n_client --> n_gw
  n_gw --> n_app
  n_gw --> n_search
  n_pay --> n_paydb
  n_app --> n_queue
  n_queue --> n_pay

Mermaid: so'rovlar ketma-ketligi

sequenceDiagram
  participant n_app as Do'kon ilovasi
  participant n_db as Do'kon bazasi
  participant n_client as Xaridor
  participant n_gw as API gateway
  participant n_search as Qidiruv servisi
  participant n_pay as To'lov servisi
  participant n_queue as Hodisalar jurnali
  Note over n_app,n_db: Bitta ilova, bitta baza
  n_app->>n_db: BEGIN#59;
  Note over n_client,n_app: Bir jamoaning muammosi hammaning muammosi
  n_client->>n_app: GET /v1/search?q=dune HTTP/1.1
  n_app-->>n_client: HTTP/1.1 200 OK
  Note over n_gw,n_search: Og'riyotgan qismni ajratamiz
  n_gw->>n_search: GET /v1/search?q=dune HTTP/1.1
  n_search-->>n_gw: HTTP/1.1 200 OK
  Note over n_client,n_gw: API gateway: bitta kirish eshigi
  n_client->>n_gw: GET /api/search?q=dune HTTP/1.1
  n_gw-->>n_client: HTTP/1.1 200 OK
  Note over n_app,n_pay: To'lovning o'z servisi va bazasi
  n_app->>n_pay: POST /internal/payments HTTP/1.1
  n_pay-->>n_app: HTTP/1.1 201 Created
  Note over n_app,n_pay: Qisman yiqilish
  n_app-xn_pay: POST /internal/payments HTTP/1.1
  Note over n_pay,n_db: Boshqa servisning jadvalini o'qish
  n_pay->>n_db: SELECT total FROM orders WHERE id = 9001#59;
  n_db-->>n_pay: ERROR: column #34;total#34; does not exist
  Note over n_app,n_queue: Har servis o'z ma'lumotiga ega, hodisa e'lon qiladi
  n_app->>n_queue: produce topic=orders.events key=9001
  Note over n_queue,n_pay: Narxi: bir necha servis bo'ylab debugging
  n_queue->>n_pay: consume orders.events partition=2 offset=48211

D2

direction: right

n_client: "Xaridor" {
  shape: rectangle
}
n_app: "Do'kon ilovasi" {
  shape: rectangle
}
n_db: "Do'kon bazasi" {
  shape: cylinder
}
n_gw: "API gateway" {
  shape: diamond
}
n_search: "Qidiruv servisi" {
  shape: rectangle
}
n_pay: "To'lov servisi" {
  shape: rectangle
}
n_paydb: "To'lov bazasi" {
  shape: cylinder
}
n_queue: "Hodisalar jurnali" {
  shape: queue
}

n_app -> n_db
n_client -> n_gw
n_gw -> n_app
n_gw -> n_search
n_pay -> n_paydb
n_app -> n_queue
n_queue -> n_pay

PlantUML: so'rovlar ketma-ketligi

@startuml
participant "Do'kon ilovasi" as n_app
database "Do'kon bazasi" as n_db
participant "Xaridor" as n_client
participant "API gateway" as n_gw
participant "Qidiruv servisi" as n_search
participant "To'lov servisi" as n_pay
queue "Hodisalar jurnali" as n_queue
note over n_app, n_db : Bitta ilova, bitta baza
n_app -> n_db : BEGIN;
note over n_client, n_app : Bir jamoaning muammosi hammaning muammosi
n_client -> n_app : GET /v1/search?q=dune HTTP/1.1
n_app --> n_client : HTTP/1.1 200 OK
note over n_gw, n_search : Og'riyotgan qismni ajratamiz
n_gw -> n_search : GET /v1/search?q=dune HTTP/1.1
n_search --> n_gw : HTTP/1.1 200 OK
note over n_client, n_gw : API gateway: bitta kirish eshigi
n_client -> n_gw : GET /api/search?q=dune HTTP/1.1
n_gw --> n_client : HTTP/1.1 200 OK
note over n_app, n_pay : To'lovning o'z servisi va bazasi
n_app -> n_pay : POST /internal/payments HTTP/1.1
n_pay --> n_app : HTTP/1.1 201 Created
note over n_app, n_pay : Qisman yiqilish
n_app ->x n_pay : [yo'qoldi] POST /internal/payments HTTP/1.1
note over n_pay, n_db : Boshqa servisning jadvalini o'qish
n_pay -> n_db : SELECT total FROM orders WHERE id = 9001;
n_db --> n_pay : ERROR: column "total" does not exist
note over n_app, n_queue : Har servis o'z ma'lumotiga ega, hodisa e'lon qiladi
n_app -> n_queue : produce topic=orders.events key=9001
note over n_queue, n_pay : Narxi: bir necha servis bo'ylab debugging
n_queue -> n_pay : consume orders.events partition=2 offset=48211
@enduml

PlantUML: komponentlar

@startuml
left to right direction
agent "Xaridor" as n_client
component "Do'kon ilovasi" as n_app
database "Do'kon bazasi" as n_db
node "API gateway" as n_gw
component "Qidiruv servisi" as n_search
component "To'lov servisi" as n_pay
database "To'lov bazasi" as n_paydb
queue "Hodisalar jurnali" as n_queue
n_app --> n_db
n_client --> n_gw
n_gw --> n_app
n_gw --> n_search
n_pay --> n_paydb
n_app --> n_queue
n_queue --> n_pay
@enduml

Xulosa

Toza modulli monolitdan boshlang. Faqat nomlay oladigan sabab bilan bo'ling.

1) Yaxshi sabablar: jamoalar bir-birini to'sadi, bir qismning yuki butunlay boshqacha, qismga o'z reliz sur'ati yoki izolyatsiya kerak. 2) Har bo'linish funksiya chaqiruvini tarmoq chaqiruviga aylantiradi: timeout, qisman yiqilish, umumiy tranzaksiya yo'q. 3) Har servis o'z ma'lumotiga ega; boshqalar API yoki hodisa orqali. 4) Kirishda autentifikatsiya, limit va yo'naltirish uchun gateway. 5) Tracing va markaziy log'ni bo'lishdan oldin rejalashtiring, keyin emas.

Ko'rsatkichlar: boshida va oxirida

Ko'rsatkichBoshidaOxirida
Deploylar0,1/kun6/kun
So'rov p95140 ms280 ms
Buyurtmadagi servislar14
Yiqilgan so'rovlar0,3%0,4%

Qadamlar

  1. Holat Bitta ilova, bitta baza

    Do'kon bitta ilova va bitta bazadan iborat.

  2. Muammo Bir jamoaning muammosi hammaning muammosi

    Ikki yildan keyin: beshta jamoada 40 dasturchi, bitta kod bazasi.

  3. Yechim Og'riyotgan qismni ajratamiz

    Qidiruv o'z indeksi bilan alohida servisga aylanadi, egasi bitta jamoa.

  4. Holat API gateway: bitta kirish eshigi

    Mijozlar bitta host'ni ko'radi.

  5. Yechim To'lovning o'z servisi va bazasi

    To'lov jamoasi har kuni deploy qilishni va karta ma'lumotlarini qolgan hamma narsadan uzoq tutishni xohlaydi.

  6. Muammo Qisman yiqilish

    To'lov servisi yiqildi.

  7. Muammo Boshqa servisning jadvalini o'qish

    Buyurtma summasini ko'rsatish uchun to'lov jamoasi do'kon bazasini to'g'ridan o'qiydi.

  8. Yechim Har servis o'z ma'lumotiga ega, hodisa e'lon qiladi

    Begona o'qish ham, to'g'ridan chaqiruv ham olib tashlandi.

  9. Holat Narxi: bir necha servis bo'ylab debugging

    Bitta buyurtma endi gateway, ilova, hodisalar jurnali va to'lovdan o'tadi.

  10. Xulosa Xulosa

    Toza modulli monolitdan boshlang.

Atamalar

Mikroservis
Alohida deploy qilinadigan va o'z ma'lumotiga ega bo'lgan kichik servis; boshqalar unga faqat API yoki hodisa orqali murojaat qiladi. Narxi: tarmoq chaqiruvlari, qisman yiqilish va umumiy tranzaksiyaning yo'qligi, shuning uchun toza monolitdan boshlanadi.
API gateway
Barcha servislar oldidagi bitta kirish eshigi: tokenni tekshiradi, rate limit qo'llaydi, request id qo'shadi va yo'l bo'yicha yo'naltiradi. Ichki tuzilmani klientlardan yashiradi.