Перейти к содержимому
Сервисы

Сервисы

Services

Service boundaries and source locations.

Эта страница ещё не переведена, поэтому показана английская версия.

ItsBagelBot separates receiving events, deciding what to do, executing external effects, and owning durable data. Most service code is Go; Twitch ingress and the controls gateway are Elixir. NATS carries events and request/reply calls. The data services own their schemas; callers use RPC and projections instead of reading another owner’s database.

flowchart LR
  Twitch[Twitch] --> TI[Twitch ingress]
  TI --> Sesame
  Sesame --> TO[Twitch outgress]
  TO --> Twitch
  Owners[Data owners] --> Projector
  Projector --> Sesame
  Sesame --> Gossip
  Dashboard --> Owners

The diagram shows the main paths, not every event or RPC. For message types and retry behavior, follow the linked source and shared contracts under internal/domain/ and pkg/bus/.

Service registry

Area Service Source
Twitch Ingress, Sesame, AutoMod, Outgress app/twitch/
Data Users, Commands, Modules, Loyalty, Notifications, Transactions app/db/
Shared runtime Projector, Gossip, WARP image app/projector/, app/gossip/, app/warp/
Desktop Controls gateway, Desktop app app/controls/gateway/, app/desktop/
Web Dashboard, Admin, Marketing web/

The repository also contains the desktop app (app/desktop/), release tooling (app/release/) and cluster operations (app/clusterops/). app/plain/ is an unfinished scaffold and app/yt-ingress/ is a placeholder. See CONTEXT-MAP.md for the full source map.