Control plane
guru-master serves the operator API, the worker API, the AMQP derivation hook and a cron
sweep — one binary, four modes.
Proxy Guru
Operators design a topology on a canvas, the control plane derives one config per server from
it, and data-plane workers pick up every new revision automatically.
Two planes, one model
Section titled “Two planes, one model”Data plane
guru-worker terminates listeners and forwards traffic, either from a local TOML file or by
streaming configs from the master.
Convergent rollout
Every server keeps desired, in_flight and applied snapshots, so no revision drops
traffic mid-rollout.
Everything is a Processor
State plus an async function. Each query, operation and consumer is an input struct with one
Processor impl.
Where to go next
Section titled “Where to go next”Guides
Reference