Change Data Capture configurations
CDC modes, managed and direct delivery options, and the current destination validation rules.
Parix models CDC explicitly in the control plane.
Modes available today
The current CDC configuration supports three modes:
disableddirect_amqpmanaged_amqp
Direct AMQP
Direct AMQP mirrors TigerBeetle-native CDC settings. The current UI collects:
- host
- port
- username
- password
- virtual host
- exchange
- routing key
- TLS enabled
- publish confirms
On first save, a password is required. Later edits can keep the stored password by leaving the field empty.
Managed AMQP
Managed AMQP is a platform-managed delivery path. The current UI models:
- managed provider selection
- one or more webhook destinations
- destination authentication mode
- destination secret handling
- active versus inactive destinations
Current validation rules include:
- at least one active destination is required for managed delivery
- destination URLs must use HTTPS
- authenticated destinations require a secret on first save
- static-header auth also requires a header name
Current support boundary
The schema includes provider-managed delivery paths. The current platform-managed support includes:
- Fly-backed clusters
- AWS-backed clusters that use the shared RabbitMQ broker path
For AWS, the managed AMQP host remains a literal private IP because the TigerBeetle AMQP integration does not accept DNS names for that field.
Operational model
CDC changes are queued through workflows and surfaced later through durable control-plane state. They are not applied synchronously in the browser.