zheng020
3ee35601e2
Per user feedback, the relationships of the 4 new services to the existing backend are different than previously described: - admin: SHARES database with current system (direct DB connection, not API). Access control via DB account/RBAC. - review: CALLED BY current backend (gateway/assetservice invokes its API for submission; result returns via callback/message/shared table) - ai-image-gen: CALLED BY current backend (gateway originally called MiniMax directly, now calls ai-image-gen's API) - ai-chat: CALLED BY current backend/frontend (extracted from aichatservice) Section 1.3 rewritten to make this distinction explicit. Section 11.4.3 expanded to describe the different cross-namespace patterns: - admin: no API calls, connects to same RDS via ExternalName - review: needs cross-ns Dubbo to read content from each group - ai-image-gen / ai-chat: receive calls, may indirectly call userservice via short DNS This also has implications for the data-layer multi-tenancy in §11.4.4 — admin still needs group_id to filter across groups when reading the shared DB. |
||
|---|---|---|
| .agents/skills | ||
| backend | ||
| docker | ||
| docs | ||
| frontend | ||
| mock | ||
| scripts | ||
| supabase/migrations | ||
| .gitignore | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| README.md | ||