iconsulting/packages/services/conversation-service
hailin e1bcd0145e refactor(evolution): use API instead of shared database tables
Breaking change: evolution-service no longer directly accesses
conversations and messages tables.

Changes:
- Add internal API endpoints to conversation-service for service-to-service calls
- Create ConversationClient in evolution-service to call conversation-service API
- Remove ConversationORM and MessageORM from evolution-service
- Update evolution.service to use ConversationClient

This follows microservices best practices:
- Each service owns its data
- Services communicate via API, not shared tables

TODO: Apply same pattern to system_experiences (knowledge-service)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-24 19:48:09 -08:00
..
src refactor(evolution): use API instead of shared database tables 2026-01-24 19:48:09 -08:00
Dockerfile fix: 使用jq正确处理package.json移除workspace依赖 2026-01-09 08:49:41 -08:00
nest-cli.json Initial commit: iConsulting 香港移民咨询智能客服系统 2026-01-09 00:01:12 -08:00
package.json fix(migration): add production migration support for Docker 2026-01-24 08:05:14 -08:00
tsconfig.json Initial commit: iConsulting 香港移民咨询智能客服系统 2026-01-09 00:01:12 -08:00