创建页面,内容为“ = Services and responsibilities == Auth / Identity (Keycloak) == Responsibility: Authentication, user identity, SSO, OIDC tokens. Data owned: Keycloak user record (sub), basic profile attributes. Notes: Other services store keycloak_id as foreign reference only. == Customer Service (customer profile / account)== Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId…” |
小无编辑摘要 |
||
第2行: | 第2行: | ||
= Services and responsibilities | = Services and responsibilities | ||
== Auth / Identity (Keycloak) == | == Auth / Identity (Keycloak) == | ||
Responsibility: Authentication, user identity, SSO, OIDC tokens. | * Responsibility: Authentication, user identity, SSO, OIDC tokens. | ||
Data owned: Keycloak user record (sub), basic profile attributes. | * Data owned: Keycloak user record (sub), basic profile attributes. | ||
Notes: Other services store keycloak_id as foreign reference only. | * Notes: Other services store keycloak_id as foreign reference only. | ||
== Customer Service (customer profile / account)== | == Customer Service (customer profile / account)== | ||
Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId), invoice delivery preferences, links to internal user records. | * Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId), invoice delivery preferences, links to internal user records. | ||
Data owned: customer table (customer_id, keycloak_id, contact info, provider customer id, metadata). | * Data owned: customer table (customer_id, keycloak_id, contact info, provider customer id, metadata). | ||
API examples: GET/PUT customer, attach payment method token, list customer’s subscriptions/orders. | * API examples: GET/PUT customer, attach payment method token, list customer’s subscriptions/orders. | ||
When to call: read-heavy for CRM and billing, write when profile changes. | * When to call: read-heavy for CRM and billing, write when profile changes. | ||
[[Category:Ystack]] | [[Category:Ystack]] | ||
[[Category:DDD]] | [[Category:DDD]] | ||
[[Category:Distributed]] | [[Category:Distributed]] |
2025年8月17日 (日) 13:41的版本
= Services and responsibilities
Auth / Identity (Keycloak)
- Responsibility: Authentication, user identity, SSO, OIDC tokens.
- Data owned: Keycloak user record (sub), basic profile attributes.
- Notes: Other services store keycloak_id as foreign reference only.
Customer Service (customer profile / account)
- Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId), invoice delivery preferences, links to internal user records.
- Data owned: customer table (customer_id, keycloak_id, contact info, provider customer id, metadata).
- API examples: GET/PUT customer, attach payment method token, list customer’s subscriptions/orders.
- When to call: read-heavy for CRM and billing, write when profile changes.