Konspekt · Arxitektura
Event sourcing
Muammo
Onlayn do'kon har buyurtmaga bitta qator saqlaydi va uni joyida yangilaydi. Nizolarga javob berib bo'lmaydi, bir vaqtdagi ikki tahrir esa bir-birini jimgina ustidan yozadi. Event sourcing har o'zgarishni versiyali stream'dagi o'zgarmas hodisa (event) sifatida saqlaydi, holat va read model'larni hodisalardan quradi, keyin esa uzun stream'lar, eski hodisa formatlari, o'qish kechikishi va unutilish huquqi bilan ishlashga to'g'ri keladi.
Nimani o'rganasiz
- Nega joyida yangilanadigan qator tarixni yo'qotadi va versiyali, faqat qo'shiladigan stream uni qanday saqlaydi
expected_versionbilan optimistic concurrency va yozuvchiga nima o'zgarganini aytadigan 409- Checkpoint'li projection'lar, qayta qurish, uzun stream'lar uchun snapshot va eski hodisalarni upcast qilish
- UI'dagi CQRS o'qish kechikishi va o'zgarmas hodisalarda GDPR o'chirish: crypto-shredding
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_app(["Do'kon ilovasi"])
n_support(("Support xodimi"))
n_api["Buyurtma servisi"]
n_store[("Event store")]
n_projector("Projector")
n_views[("Read model")]
n_vault>"Kalit ombori"]
n_app --> n_api
n_support --> n_api
n_api --> n_store
n_projector --> n_store
n_projector --> n_views
n_api --> n_views
n_api --> n_vaultMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_api as Buyurtma servisi
participant n_orders as Buyurtmalar jadvali
participant n_store as Event store
actor n_support as Support xodimi
participant n_projector as Projector
participant n_views as Read model
participant n_app as Do'kon ilovasi
participant n_vault as Kalit ombori
Note over n_api,n_orders: Buyurtma doim o'zgarib turadigan qator
n_api->>n_orders: UPDATE orders
n_orders-->>n_api: UPDATE 1
Note over n_api,n_orders: Support mijozning tahririni ustidan yozadi, hech kim bilmaydi
n_api->>n_orders: 10:02:11 app SET address = '12 Elm St'
Note over n_api,n_store: Hodisani qo'sh, hech qachon yangilama
n_api->>n_store: INSERT INTO events (stream_id, version, type, data)
n_store-->>n_api: INSERT 0 1
Note over n_support,n_api: Kutilgan versiya: eskirgan yozuv rad etiladi
n_support->>n_api: POST /v1/streams/order-ord_77/events HTTP/1.1
n_api-->>n_support: HTTP/1.1 409 Conflict
Note over n_projector,n_views: Read model'lar hodisalardan quriladi
n_projector->>n_views: projector order_list checkpoint 1204880
Note over n_api,n_store: 120 000 hodisali stream
n_api->>n_store: SELECT type, data FROM events
n_store-->>n_api: 120037 rows 2.6 s
Note over n_api,n_store: Snapshot: saqlangan holatdan boshlash
n_api->>n_store: snapshot account-b_12
n_store-->>n_api: then: events WHERE version #62; 120000
Note over n_projector,n_store: Yangi kod 2024 yilgi hodisaga duch keladi
n_projector->>n_store: projector order_list v2 started
Note over n_projector,n_store: Upcasting: eski hodisa o'qishda o'giriladi
n_projector->>n_store: stored in 2024 (never rewritten)
n_store-->>n_projector: after upcast v1 -#62; v2 (in memory)
Note over n_app,n_api: Foydalanuvchi saqlaydi va eski qiymatni ko'radi
n_app->>n_api: GET /v1/orders/ord_77?min_version=7 HTTP/1.1
n_api-->>n_app: HTTP/1.1 200 OK
Note over n_api,n_vault: Hodisalarni tahrirlamasdan mijozni unutish
n_api->>n_vault: DELETE /v1/keys/subject/c_501 HTTP/1.1
n_vault-->>n_api: HTTP/1.1 200 OKD2
direction: right
n_app: "Do'kon ilovasi" {
shape: rectangle
}
n_support: "Support xodimi" {
shape: person
}
n_api: "Buyurtma servisi" {
shape: rectangle
}
n_store: "Event store" {
shape: cylinder
}
n_projector: "Projector" {
shape: rectangle
style.multiple: true
}
n_views: "Read model" {
shape: cylinder
}
n_vault: "Kalit ombori" {
shape: cloud
}
n_app -> n_api
n_support -> n_api
n_api -> n_store
n_projector -> n_store
n_projector -> n_views
n_api -> n_views
n_api -> n_vaultPlantUML: so'rovlar ketma-ketligi
@startuml
participant "Buyurtma servisi" as n_api
database "Buyurtmalar jadvali" as n_orders
database "Event store" as n_store
actor "Support xodimi" as n_support
participant "Projector" as n_projector
database "Read model" as n_views
participant "Do'kon ilovasi" as n_app
boundary "Kalit ombori" as n_vault
note over n_api, n_orders : Buyurtma doim o'zgarib turadigan qator
n_api -> n_orders : UPDATE orders
n_orders --> n_api : UPDATE 1
note over n_api, n_orders : Support mijozning tahririni ustidan yozadi, hech kim bilmaydi
n_api -> n_orders : [dublikat] 10:02:11 app SET address = '12 Elm St'
note over n_api, n_store : Hodisani qo'sh, hech qachon yangilama
n_api -> n_store : INSERT INTO events (stream_id, version, type, data)
n_store --> n_api : INSERT 0 1
note over n_support, n_api : Kutilgan versiya: eskirgan yozuv rad etiladi
n_support -> n_api : POST /v1/streams/order-ord_77/events HTTP/1.1
n_api --> n_support : HTTP/1.1 409 Conflict
note over n_projector, n_views : Read model'lar hodisalardan quriladi
n_projector -> n_views : projector order_list checkpoint 1204880
note over n_api, n_store : 120 000 hodisali stream
n_api -> n_store : SELECT type, data FROM events
n_store --> n_api : 120037 rows 2.6 s
note over n_api, n_store : Snapshot: saqlangan holatdan boshlash
n_api -> n_store : snapshot account-b_12
n_store --> n_api : then: events WHERE version > 120000
note over n_projector, n_store : Yangi kod 2024 yilgi hodisaga duch keladi
n_projector -> n_store : projector order_list v2 started
note over n_projector, n_store : Upcasting: eski hodisa o'qishda o'giriladi
n_projector -> n_store : stored in 2024 (never rewritten)
n_store --> n_projector : after upcast v1 -> v2 (in memory)
note over n_app, n_api : Foydalanuvchi saqlaydi va eski qiymatni ko'radi
n_app -> n_api : GET /v1/orders/ord_77?min_version=7 HTTP/1.1
n_api --> n_app : HTTP/1.1 200 OK
note over n_api, n_vault : Hodisalarni tahrirlamasdan mijozni unutish
n_api -> n_vault : DELETE /v1/keys/subject/c_501 HTTP/1.1
n_vault --> n_api : HTTP/1.1 200 OK
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Do'kon ilovasi" as n_app
actor "Support xodimi" as n_support
component "Buyurtma servisi" as n_api
database "Event store" as n_store
collections "Projector" as n_projector
database "Read model" as n_views
cloud "Kalit ombori" as n_vault
n_app --> n_api
n_support --> n_api
n_api --> n_store
n_projector --> n_store
n_projector --> n_views
n_api --> n_views
n_api --> n_vault
@endumlXulosa
Event sourcing uchun olti qoida.
1) O'zgarishlarni versiyali stream'larda o'tgan zamondagi o'zgarmas hodisalar sifatida saqlang; holat fold natijasi. 2) expected_version bilan qo'shing; 409 yozuvchiga nimani o'tkazib yuborganini aytadi. 3) Read model'lar checkpoint'i bitta tranzaksiyada saqlanadigan, tashlab yuboriladigan projection'lar; ularni qayta o'ynab quring. 4) Faqat uzun stream'larga snapshot qiling va snapshot'ni kesh deb biling. 5) Hodisalar abadiy: ularni versiyalang va eskilarini o'qishda upcast qiling. 6) UI'da o'qish kechikishini rejalang, shaxsiy ma'lumotni har subyektga alohida shifrlang, shunda o'chirish kalitni o'chirishga aylanadi.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Javobsiz nizolar | 0/kun | 0/kun |
| Ustidan yozilgan tahrir | 0/kun | 0/kun |
| Read model kechikishi | 0 ms | 340 ms |
| Bitta stream'ni yuklash | 3 ms | 30 ms |
Qadamlar
- Holat Buyurtma doim o'zgarib turadigan qator
Buyurtma servisi har buyurtmaga bitta qator saqlaydi.
- Muammo Support mijozning tahririni ustidan yozadi, hech kim bilmaydi
10:02 da mijoz ilovada yetkazish manzilini o'zgartiradi.
- Yechim Hodisani qo'sh, hech qachon yangilama
Har o'zgarish hodisa (event) bo'ladi:
OrderPlaced,ItemAdded,AddressChanged,OrderShipped. - Yechim Kutilgan versiya: eskirgan yozuv rad etiladi
Har qo'shish yozuvchi oxirgi marta qaysi versiyani ko'rganini aytadi.
- Yechim Read model'lar hodisalardan quriladi
Stream'ni fold qilish bitta buyurtma uchun yaxshi, "shu shahardagi hamma ochiq buyurtmalar" uchun emas.
- Muammo 120 000 hodisali stream
Ulgurji xaridorlarning account stream'i bor: 2021 dan beri har buyurtma qatori, to'lov va kredit o'zgarishi.
- Yechim Snapshot: saqlangan holatdan boshlash
Har 500 hodisada servis snapshot saqlaydi: stream'ning ma'lum versiyadagi fold qilingan holati.
- Muammo Yangi kod 2024 yilgi hodisaga duch keladi
Jamoa manzilni ko'cha, shahar va indeksga ajratadi.
- Yechim Upcasting: eski hodisa o'qishda o'giriladi
Har hodisa sxema versiyasini olib yuradi.
- Yechim Foydalanuvchi saqlaydi va eski qiymatni ko'radi
Mijoz manzilni o'zgartiradi, ilova buyurtma sahifasini ochadi.
- Yechim Hodisalarni tahrirlamasdan mijozni unutish
Mijoz o'z ma'lumotlarini o'chirishni so'raydi.
- Xulosa Xulosa
Event sourcing uchun olti qoida.
Atamalar
- Event sourcing
- Har o'zgarishni versiyali stream'da o'zgarmas hodisa sifatida saqlash va joriy holatni shu hodisalarni qayta o'ynab hisoblash.
- CQRS
- Yozuv modelini so'rovlar uchun qurilgan va odatda biroz kechikadigan read model'lardan ajratish.
- Crypto-shredding
- O'chirib bo'lmaydigan ma'lumotni, masalan hodisa yoki zaxirani, u shifrlangan har subyekt kalitini yo'q qilib o'chirish.