mufassall

Konspekt · Ma'lumot va saqlash

Unikal ID'lar

12 daq · O'rta · mufassall.dtwin.uz/uz/l/unique-ids/

← Darsni ochish

Muammo

Buyurtmalar servisi ID'ni baza hisoblagichidan oladi. Keyin ma'lumot ikkita bazaga bo'linadi va hisoblagichlar bir xil raqamlarni bera boshlaydi. Hamma joyda unikal, indeksda yaxshi tartiblanadigan va soat orqaga sakrasa ham buzilmaydigan ID qanday yasaladi.

Nimani o'rganasiz

  • Nega shard'lashdan keyin auto-increment unikal bo'lmay qoladi
  • Nega tasodifiy UUIDv4 kalitlar B-tree indeksga zarar qiladi va UUIDv7 buni qanday tuzatadi
  • 64 bitli ID vaqt, mashina va ketma-ketlikdan qanday yig'iladi
  • Soat orqaga ketsa nima qilish kerak
Yakuniy sahna
20%32%20%31%

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(["Ilova"])
  n_api["Buyurtmalar API"]
  n_db_1[("Shard 1")]
  n_db_2[("Shard 2")]
  n_api_2["Buyurtmalar API #35;2"]
  n_ntp>"Vaqt serveri"]
  n_client --> n_api
  n_api --> n_db_1
  n_api --> n_db_2
  n_client --> n_api_2
  n_api_2 --> n_db_2
  n_ntp --> n_api_2

Mermaid: so'rovlar ketma-ketligi

sequenceDiagram
  participant n_api as Buyurtmalar API
  participant n_db_1 as Shard 1
  participant n_db_2 as Shard 2
  participant n_client as Ilova
  participant n_api_2 as Buyurtmalar API #35;2
  participant n_ntp as Vaqt serveri
  Note over n_api,n_db_1: Bitta baza, bitta hisoblagich
  n_api->>n_db_1: INSERT INTO orders (user_id, total)
  n_db_1-->>n_api: id = 48213
  Note over n_api,n_db_2: Ikki shard, ikki hisoblagich, bir xil raqamlar
  n_api->>n_db_2: INSERT INTO orders (user_id, total)
  n_db_2-->>n_api: id = 48214
  Note over n_api,n_db_2: Yamoq: bir shard'da toq, ikkinchisida juft ID
  n_api->>n_db_2: ALTER SEQUENCE orders_id_seq
  n_db_2-->>n_api: ALTER SEQUENCE
  Note over n_client,n_api: ID'ni servis yasasin: tasodifiy UUID
  n_client->>n_api: POST /orders HTTP/1.1
  n_api-->>n_client: HTTP/1.1 201 Created
  Note over n_api,n_db_1: Tasodifiy kalitlar indeksni titib tashlaydi
  n_api->>n_db_1: SELECT avg_leaf_density, leaf_fragmentation
  n_db_1-->>n_api: 61.2 #124; 48.7
  Note over n_client,n_api: UUIDv7: avval vaqt, keyin tasodif
  n_client->>n_api: POST /orders HTTP/1.1
  n_api-->>n_client: HTTP/1.1 201 Created
  Note over n_api_2,n_db_2: Yanada kichik: 64 bitda vaqt + mashina + ketma-ketlik
  n_api_2->>n_db_2: DEBUG new id 250413553075367937
  Note over n_ntp,n_api_2: Soat orqaga ketdi va ID takrorlandi
  n_ntp->>n_api_2: INFO clock step: -40 ms (offset from server 0.040 s)
  Note over n_api_2,n_db_2: Hech qachon oxirgi vaqt belgisidan pastga tushma
  n_api_2->>n_db_2: WARN clock behind last id by 40 ms, waiting

D2

direction: right

n_client: "Ilova" {
  shape: rectangle
}
n_api: "Buyurtmalar API" {
  shape: rectangle
}
n_db_1: "Shard 1" {
  shape: cylinder
}
n_db_2: "Shard 2" {
  shape: cylinder
}
n_api_2: "Buyurtmalar API #2" {
  shape: rectangle
}
n_ntp: "Vaqt serveri" {
  shape: cloud
}

n_client -> n_api
n_api -> n_db_1
n_api -> n_db_2
n_client -> n_api_2
n_api_2 -> n_db_2
n_ntp -> n_api_2

PlantUML: so'rovlar ketma-ketligi

@startuml
participant "Buyurtmalar API" as n_api
database "Shard 1" as n_db_1
database "Shard 2" as n_db_2
participant "Ilova" as n_client
participant "Buyurtmalar API #2" as n_api_2
boundary "Vaqt serveri" as n_ntp
note over n_api, n_db_1 : Bitta baza, bitta hisoblagich
n_api -> n_db_1 : INSERT INTO orders (user_id, total)
n_db_1 --> n_api : id = 48213
note over n_api, n_db_2 : Ikki shard, ikki hisoblagich, bir xil raqamlar
n_api -> n_db_2 : [dublikat] INSERT INTO orders (user_id, total)
n_db_2 --> n_api : id = 48214
note over n_api, n_db_2 : Yamoq: bir shard'da toq, ikkinchisida juft ID
n_api -> n_db_2 : ALTER SEQUENCE orders_id_seq
n_db_2 --> n_api : ALTER SEQUENCE
note over n_client, n_api : ID'ni servis yasasin: tasodifiy UUID
n_client -> n_api : POST /orders HTTP/1.1
n_api --> n_client : HTTP/1.1 201 Created
note over n_api, n_db_1 : Tasodifiy kalitlar indeksni titib tashlaydi
n_api -> n_db_1 : SELECT avg_leaf_density, leaf_fragmentation
n_db_1 --> n_api : 61.2 | 48.7
note over n_client, n_api : UUIDv7: avval vaqt, keyin tasodif
n_client -> n_api : POST /orders HTTP/1.1
n_api --> n_client : HTTP/1.1 201 Created
note over n_api_2, n_db_2 : Yanada kichik: 64 bitda vaqt + mashina + ketma-ketlik
n_api_2 -> n_db_2 : DEBUG new id 250413553075367937
note over n_ntp, n_api_2 : Soat orqaga ketdi va ID takrorlandi
n_ntp -> n_api_2 : INFO clock step: -40 ms (offset from server 0.040 s)
note over n_api_2, n_db_2 : Hech qachon oxirgi vaqt belgisidan pastga tushma
n_api_2 -> n_db_2 : WARN clock behind last id by 40 ms, waiting
@enduml

PlantUML: komponentlar

@startuml
left to right direction
agent "Ilova" as n_client
component "Buyurtmalar API" as n_api
database "Shard 1" as n_db_1
database "Shard 2" as n_db_2
component "Buyurtmalar API #2" as n_api_2
cloud "Vaqt serveri" as n_ntp
n_client --> n_api
n_api --> n_db_1
n_api --> n_db_2
n_client --> n_api_2
n_api_2 --> n_db_2
n_ntp --> n_api_2
@enduml

Xulosa

Baza hisoblagichi baza bittadan ko'p bo'lmaguncha a'lo ishlaydi.

1) ID'ni har bir shard'da emas, servisda yarating. 2) Tasodifiy ID'dan ko'ra vaqt bo'yicha tartiblanganini tanlang (UUIDv7, ULID, vaqt + mashina + ketma-ketlik): indeks ixcham qoladi. 3) Har bir generatorga unikal mashina raqami bering. 4) Oxirgisidan kichik vaqt belgili ID'ni hech qachon bermang: kuting yoki rad eting.

Ko'rsatkichlar: boshida va oxirida

Ko'rsatkichBoshidaOxirida
Yozish p954 ms6 ms
Takroriy ID'lar0/kun0/kun
Indeks sahifa bo'linishi2/s3/s

Qadamlar

  1. Holat Bitta baza, bitta hisoblagich

    Har bir yangi buyurtma ID'ni bazadan oladi: faqat o'sib boradigan sequence (ketma-ketlik).

  2. Muammo Ikki shard, ikki hisoblagich, bir xil raqamlar

    Buyurtmalar foydalanuvchi bo'yicha ikkita bazaga bo'lindi.

  3. Yechim Yamoq: bir shard'da toq, ikkinchisida juft ID

    Endi ikkala hisoblagich 2 qadam bilan yuradi va har xil joydan boshlaydi: shard 1 toq, shard 2 juft raqam beradi.

  4. Yechim ID'ni servis yasasin: tasodifiy UUID

    Endi API ID'ni yozishdan oldin o'zi yaratadi: UUIDv4, 122 ta tasodifiy bit.

  5. Muammo Tasodifiy kalitlar indeksni titib tashlaydi

    Primary key indeksi kalit tartibida saqlanadigan B-tree.

  6. Yechim UUIDv7: avval vaqt, keyin tasodif

    UUIDv7 o'sha 128 bitli formatni saqlaydi, lekin uning birinchi 48 biti — millisekunddagi joriy vaqt.

  7. Holat Yanada kichik: 64 bitda vaqt + mashina + ketma-ketlik

    Ikkinchi API server qo'shildi.

  8. Muammo Soat orqaga ketdi va ID takrorlandi

    Vaqt serveri API #2 ga uning soati 40 ms oldinda ekanini aytadi.

  9. Yechim Hech qachon oxirgi vaqt belgisidan pastga tushma

    Generator oxirgi ID vaqtini eslab qoladi.

  10. Xulosa Xulosa

    Baza hisoblagichi baza bittadan ko'p bo'lmaguncha a'lo ishlaydi.

Atamalar

UUIDv7
Birinchi 48 biti millisekunddagi vaqt, qolgani tasodifiy bo'lgan 128 bitli ID. Yangi ID'lar indeks oxiriga tushadi, shuning uchun tasodifiy UUIDv4 kabi B-tree'ni titib tashlamaydi.
Snowflake ID (vaqt + mashina + ketma-ketlik)
64 bitli ID: tanlangan davrdan beri o'tgan millisekundlar, mashina raqami va shu millisekund ichidagi hisoblagich. Har server ID'ni o'zi yaratadi, soat orqaga ketsa kutadi yoki rad etadi.