정리중
This commit is contained in:
@@ -11,6 +11,11 @@ monorepo plan is prepared alongside it.
|
||||
- Legacy frontend: Vue/TypeScript under `legacy/hwe/ts/`
|
||||
- Rewrite (planned): pnpm workspace monorepo under `packages/` and `app/`
|
||||
|
||||
## Legacy Data Migration Policy
|
||||
|
||||
- Data under `legacy/` is migration-only and not used by the rewrite at runtime.
|
||||
- After DB migration completes, legacy data is no longer required.
|
||||
|
||||
## Data and State
|
||||
|
||||
- PHP engine owns authoritative gameplay state today
|
||||
|
||||
@@ -23,6 +23,11 @@ Vue 3 frontends.
|
||||
- Data: PostgreSQL, Redis sessions
|
||||
- Testing: Vitest
|
||||
|
||||
## Legacy Data Migration
|
||||
|
||||
- Legacy data is for migration only; the rewrite runtime does not depend on it.
|
||||
- Once DB migration is complete, legacy data can be retired.
|
||||
|
||||
## Profiles (Planned)
|
||||
|
||||
- `che`, `kwe`, `pwe`, `twe`, `nya`, `pya`
|
||||
|
||||
@@ -20,6 +20,8 @@ deployments predictable.
|
||||
- Turn daemon responsibilities: scheduling, turn resolution, state persistence
|
||||
- API server responsibilities: query/command intake, validation, response shaping
|
||||
- Concurrency model between daemon and API server
|
||||
- Communication channel: Redis Stream or Redis pub/sub
|
||||
- Client updates: SSE between API server and frontend where appropriate
|
||||
|
||||
## Engine Runtime Flow (Draft)
|
||||
|
||||
@@ -38,13 +40,16 @@ deployments predictable.
|
||||
|
||||
### API Server Flow
|
||||
|
||||
- The API server validates queries/commands and writes them to Redis Streams.
|
||||
- The API server validates queries/commands and writes them to Redis Streams
|
||||
or Redis pub/sub.
|
||||
- After a request is processed, the API server returns the result to clients.
|
||||
- Read-only queries may access the DBMS directly.
|
||||
- The API server may use SSE to stream live updates to the frontend.
|
||||
|
||||
### Queue and Rate Limits
|
||||
|
||||
- API server requests are delivered to the daemon via Redis Streams.
|
||||
- API server requests are delivered to the daemon via Redis Streams or
|
||||
Redis pub/sub.
|
||||
- Redis Stream mutation requests are rate-limited per user.
|
||||
- Each user can have up to 30 pending mutation requests.
|
||||
- Additional requests are rejected once the limit is exceeded.
|
||||
|
||||
Reference in New Issue
Block a user