Konspekt · Arxitektura
Multi-tenancy: ko'p mijozli tizim
Muammo
B2B invoys servisi 1 200 mijoz kompaniyani bitta bazada saqlaydi. Bitta unutilgan `WHERE tenant_id` invoyslarni oqizadi, bitta katta mijozning eksporti hammani sekinlashtiradi, bitta migratsiya hammani birdan sindirishi mumkin. Yechimlar: izolyatsiyani bazaning o'zi ta'minlaydi, tenant faqat token'dan olinadi, har tenant'ga kvota, katta tenant'ga marshrutlash katalogi orqali alohida silo, har tenant'ga o'z kaliti va to'lqinma-to'lqin migratsiya.
Nimani o'rganasiz
- Nega ilova kodidagi
tenant_idfiltri oqib chiqadi va row-level security hamda har tranzaksiyadagi tenant konteksti buni qanday to'xtatadi - Tenant qayerdan olinishi kerak: imzolangan token'dan, mijoz o'zgartira oladigan header yoki URL'dan hech qachon
- Shovqinli qo'shni: har tenant'ga kvota, limit header'lari bilan 429, og'ir ish navbatda
- Pool, silo va bridge, tenant marshrutlash, har tenant'ga kalit va to'lqinlab migratsiya
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_ta(["Kichik tenant"])
n_tb(["Katta tenant"])
n_api["Invoys API"]
n_db[("Umumiy baza")]
n_exporter("Eksport worker")
n_catalog[("Tenant katalogi")]
n_db900[("Silo baza")]
n_kms>"Kalit servisi"]
n_migrator("Migratsiya runner")
n_ta --> n_api
n_tb --> n_api
n_api --> n_db
n_api -->|"asinxron"| n_exporter
n_exporter --> n_db
n_api --> n_catalog
n_api --> n_db900
n_api --> n_kms
n_migrator --> n_db
n_migrator --> n_db900Mermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_api as Invoys API
participant n_db as Umumiy baza
participant n_tb as Katta tenant
participant n_catalog as Tenant katalogi
participant n_kms as Kalit servisi
participant n_migrator as Migratsiya runner
Note over n_api,n_db: 1 200 kompaniya, bitta baza
n_api->>n_db: SELECT id, total FROM invoices
n_db-->>n_api: 3 rows
Note over n_api,n_db: Bitta unutilgan filtr, bitta CSV'da 37 kompaniya
n_api->>n_db: SELECT id, tenant_id, total FROM invoices
n_db-->>n_api: 1840 rows
Note over n_api,n_db: Row-level security: filtrni baza qo'yadi
n_api->>n_db: ALTER TABLE invoices ENABLE ROW LEVEL SECURITY#59;
n_db-->>n_api: 312 rows (t_900 only)
Note over n_tb,n_api: Tenant foydalanuvchi boshqaradigan header'dan kelgan
n_tb->>n_api: GET /v1/invoices?status=open HTTP/1.1
n_api-->>n_tb: HTTP/1.1 200 OK
Note over n_tb,n_api: Tenant faqat imzolangan token'dan
n_tb->>n_api: Bearer token, decoded claims
n_api-->>n_tb: tenant context = t_900 (from the token)
Note over n_api,n_db: Bitta tenant eksporti hammani sekinlashtiradi
n_api->>n_db: top tenants by DB time, last 5 min
Note over n_tb,n_api: Har tenant'ga kvota va eksport navbati
n_tb->>n_api: POST /v1/exports HTTP/1.1
n_api-->>n_tb: HTTP/1.1 429 Too Many Requests
Note over n_api,n_catalog: Eng katta tenant o'z bazasini oladi
n_api->>n_catalog: SELECT cell, db_host, state FROM tenant_routes
n_catalog-->>n_api: cell #124; db_host #124; state
Note over n_api,n_kms: Har tenant'ga bitta shifrlash kaliti
n_api->>n_kms: POST /v1/keys/decrypt HTTP/1.1
n_kms-->>n_api: HTTP/1.1 200 OK
Note over n_migrator,n_db: Migratsiya birdan emas, to'lqinlab
n_migrator->>n_db: migrate 0042_invoice_currencyD2
direction: right
n_ta: "Kichik tenant" {
shape: rectangle
}
n_tb: "Katta tenant" {
shape: rectangle
}
n_api: "Invoys API" {
shape: rectangle
}
n_db: "Umumiy baza" {
shape: cylinder
}
n_exporter: "Eksport worker" {
shape: rectangle
style.multiple: true
}
n_catalog: "Tenant katalogi" {
shape: cylinder
}
n_db900: "Silo baza" {
shape: cylinder
}
n_kms: "Kalit servisi" {
shape: cloud
}
n_migrator: "Migratsiya runner" {
shape: rectangle
style.multiple: true
}
n_ta -> n_api
n_tb -> n_api
n_api -> n_db
n_api -> n_exporter: "asinxron"
n_exporter -> n_db
n_api -> n_catalog
n_api -> n_db900
n_api -> n_kms
n_migrator -> n_db
n_migrator -> n_db900PlantUML: so'rovlar ketma-ketligi
@startuml
participant "Invoys API" as n_api
database "Umumiy baza" as n_db
participant "Katta tenant" as n_tb
database "Tenant katalogi" as n_catalog
boundary "Kalit servisi" as n_kms
participant "Migratsiya runner" as n_migrator
note over n_api, n_db : 1 200 kompaniya, bitta baza
n_api -> n_db : SELECT id, total FROM invoices
n_db --> n_api : 3 rows
note over n_api, n_db : Bitta unutilgan filtr, bitta CSV'da 37 kompaniya
n_api -> n_db : SELECT id, tenant_id, total FROM invoices
n_db --> n_api : 1840 rows
note over n_api, n_db : Row-level security: filtrni baza qo'yadi
n_api -> n_db : ALTER TABLE invoices ENABLE ROW LEVEL SECURITY;
n_db --> n_api : 312 rows (t_900 only)
note over n_tb, n_api : Tenant foydalanuvchi boshqaradigan header'dan kelgan
n_tb -> n_api : GET /v1/invoices?status=open HTTP/1.1
n_api --> n_tb : HTTP/1.1 200 OK
note over n_tb, n_api : Tenant faqat imzolangan token'dan
n_tb -> n_api : Bearer token, decoded claims
n_api --> n_tb : tenant context = t_900 (from the token)
note over n_api, n_db : Bitta tenant eksporti hammani sekinlashtiradi
n_api -> n_db : top tenants by DB time, last 5 min
note over n_tb, n_api : Har tenant'ga kvota va eksport navbati
n_tb -> n_api : POST /v1/exports HTTP/1.1
n_api --> n_tb : HTTP/1.1 429 Too Many Requests
note over n_api, n_catalog : Eng katta tenant o'z bazasini oladi
n_api -> n_catalog : SELECT cell, db_host, state FROM tenant_routes
n_catalog --> n_api : cell | db_host | state
note over n_api, n_kms : Har tenant'ga bitta shifrlash kaliti
n_api -> n_kms : POST /v1/keys/decrypt HTTP/1.1
n_kms --> n_api : HTTP/1.1 200 OK
note over n_migrator, n_db : Migratsiya birdan emas, to'lqinlab
n_migrator -> n_db : migrate 0042_invoice_currency
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Kichik tenant" as n_ta
agent "Katta tenant" as n_tb
component "Invoys API" as n_api
database "Umumiy baza" as n_db
collections "Eksport worker" as n_exporter
database "Tenant katalogi" as n_catalog
database "Silo baza" as n_db900
cloud "Kalit servisi" as n_kms
collections "Migratsiya runner" as n_migrator
n_ta --> n_api
n_tb --> n_api
n_api --> n_db
n_api --> n_exporter : asinxron
n_exporter --> n_db
n_api --> n_catalog
n_api --> n_db900
n_api --> n_kms
n_migrator --> n_db
n_migrator --> n_db900
@endumlXulosa
Bitta tizimda ko'p mijoz uchun olti qoida.
1) Har so'rov tenant_id ni eslashiga ishonmang: uni bazada row-level security va har tranzaksiyada SET LOCAL bilan majburlang. 2) Tenant faqat imzolangan token'dan keladi; boshqa har manba ishonish uchun emas, tekshirish uchun kiritma. 3) Har tenant'ga kvota va navbat bitta mijozning hammasini olib qo'yishiga yo'l qo'ymaydi. 4) Odatda pool, kerak bo'lgan yoki to'laganlarga silo, har tenant'ni yo'naltiradigan katalog. 5) Har tenant'ga bitta kalit: oqish kichik qoladi, ketish kalitni o'chirish bilan tugaydi. 6) Canary va har tenant'ga versiya bilan to'lqinlab migratsiya qiling.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Oqqan qatorlar | 0 | 0 |
| API p99 | 120 ms | 140 ms |
| Bitta o'zgarish ta'siri | 100% | 1% |
Qadamlar
- Holat 1 200 kompaniya, bitta baza
Invoys SaaS kompaniyalarga sotiladi.
- Muammo Bitta unutilgan filtr, bitta CSV'da 37 kompaniya
Dasturchi t_900 uchun "muddati o'tgan invoyslar" hisobotini qo'shadi.
- Yechim Row-level security: filtrni baza qo'yadi
Jadvaldagi policy har so'rovga, uni unutgan so'rovga ham,
tenant_id = joriy tenantshartini qo'shadi. - Muammo Tenant foydalanuvchi boshqaradigan header'dan kelgan
API tenant'ni veb-ilova yuborgan
X-Tenant-Idheader'idan olgan. - Yechim Tenant faqat imzolangan token'dan
Login paytida identity servisi tenant'ni access token'ga yozadi va imzolaydi.
- Muammo Bitta tenant eksporti hammani sekinlashtiradi
Eng katta mijoz t_900 yetti yillik invoyslar eksportini boshlaydi, sekin tuyulgani uchun yana bir marta boshlaydi.
- Yechim Har tenant'ga kvota va eksport navbati
API so'rovlar va ishlayotgan eksportlarni har tenant bo'yicha sanaydi.
- Yechim Eng katta tenant o'z bazasini oladi
t_900 butun ma'lumotning 30% i va alohida muhit uchun to'laydi.
- Yechim Har tenant'ga bitta shifrlash kaliti
Har tenant o'z data key'ini oladi, u kalit servisidagi master key bilan o'ralgan.
- Yechim Migratsiya birdan emas, to'lqinlab
O'tgan chorakda bitta
ALTER TABLEumumiy jadvalni hamma tenant uchun 40 daqiqaga qulflab qo'ydi. - Xulosa Xulosa
Bitta tizimda ko'p mijoz uchun olti qoida.
Atamalar
- Row-level security
- Jadvaldagi har so'rovga joriy tenant kabi shart qo'shadigan baza policy'si: so'rov filtrni unutsa ham boshqa tenant qatorlari ko'rinmaydi.
- Shovqinli qo'shni
- Umumiy tizimdagi bitta tenant CPU, disk yoki ulanishlarni shunchalik ko'p ishlatadiki, qolgan hamma tenant sekinlashadi.
- Pool, silo va bridge
- Tenant izolyatsiyasi modellari: hamma resursni bo'lishadi (pool), tenant o'zinikini oladi (silo) yoki kod umumiy, ma'lumot alohida aralashma (bridge).