Skip to main content
Each deployment has at most one active agent key (vsa1. prefix). The key binds engine instances to the deployment at first connect; minting a new key revokes the previous one. CDC deployments are singleton because a source cursor or replication slot has one active consumer. Realtime roles can be replicated, but each realtime instance needs its own deployment and its own agent key. Operators normally target pipelines. The gateway fences concurrent CDC sessions for a deployment while allowing independently identified realtime instances.

Desired and observed state

Desired state is a complete, monotonically revisioned snapshot containing the run state and activated configuration revision. Agents persist the last trusted desired state and report observed state independently. This makes convergence auditable and prevents an older gateway message from rolling an engine backward. Lifecycle and configuration changes create durable operations. API acceptance means the operation was queued, not that an engine has completed it. Inspect or wait for the operation to reach a terminal state.