Architecture
Architecture
Data and state
Ownership and movement of application state.
On this page
Scope and flow
Each service under app/db/ owns its schema and exposes operations over NATS. Other services use those operations or consume events; they do not query another owner’s tables. app/projector maintains derived state in Valkey for frequent reads.
flowchart LR
Client -->|RPC| Owner["Data service"]
Owner --> DB[("Owned MySQL schema")]
Owner -->|change event| NATS
NATS --> Projector
Projector --> Valkey[("Valkey projection")]
Reader --> Valkey
Projector -->|snapshot RPC| Owner
Ownership
| Owner | Main state |
|---|---|
app/db/users |
Accounts, lifecycle, grants and tokens |
app/db/commands |
Commands, aliases and custom fetches |
app/db/modules |
Module settings and module-owned data |
app/db/loyalty |
Balances, watchtime and counters |
app/db/transactions |
Billing, giveaways and awards |
app/db/notifications |
Notifications |
See database, caching and write-behind, code design and projection. Event definitions are in internal/domain/event/data; stream configuration is in pkg/bus/streams.go. A durable consumer can resume only while its messages remain retained; the stream is not an indefinite event log.