-
Notifications
You must be signed in to change notification settings - Fork 173
Description
Image request: debezium-server
Upstream project
Debezium Server (standalone CDC runtime)
https://debezium.io/documentation/reference/stable/operations/debezium-server.html
Description / Why this image is needed
We are using Debezium Server to capture CDC events from SQL Server and
stream them directly to RabbitMQ without Kafka.
Debezium Connect is not suitable for our architecture because it requires
Kafka infrastructure.
Production usage
- Platform: Kubernetes
- Environments: UAT / Production
- Databases: SQL Server
- Sink: RabbitMQ
- Usage: Continuous CDC workloads across multiple clusters
Security motivation
We want a distroless, non-root, low-CVE image aligned with Chainguard/Wolfi
standards. The current official Debezium Server image has a larger attack
surface and does not meet our security baseline.
Why Debezium Server (not Debezium Connect)
Debezium Server supports Kafka-less CDC pipelines, which is critical for
our RabbitMQ-based event-driven architecture.
Upstream maintenance
Debezium is actively maintained with frequent releases and is widely used
in enterprise CDC pipelines.