Debezium
Change data capturedebezium
Open-source log-based change data capture connectors, usually deployed on Kafka Connect.
- Provider
- default
- Category
- Messaging
- Official docs
- https://debezium.io/documentation/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| deployment | enum | kafka-connect | server | embedded | no | kafka-connect | inherited |
| managed | boolean | — | no | false | inherited |
| mode | enum | log-based | trigger | polling | no | log-based | ▸ log-based |
| ordered | boolean | — | no | true | ▸ true |
| schemaEvolution | boolean | — | no | false | ▸ true |
| snapshotOnStart | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
No rule reads this kind yet. That is a gap, not a guarantee.
nodes:
- { id: "debezium", component: "debezium" }Data Transmission Servicealibaba-dtsAWS DMSaws-dmsAmazon DynamoDB Streamsaws-dynamodb-streamsBrooklinbrooklinAlibaba CanalcanalGeneric change data capturechange-data-captureEstuary FlowestuaryApache Kafka Connectkafka-connectMaxwellmaxwellStriimstriimDatabase Migration Servicegoogle-database-migration-serviceDatastreamgoogle-datastreamIBM Data Replicationibm-data-replicationOCI GoldenGateoci-goldengate
# yaml-language-server: $schema=../../schema/component.schema.json # Debezium: log-based CDC connectors (Postgres, MySQL, Mongo, SQL Server) usually run on Kafka Connect; # takes an initial snapshot and records schema history so schema changes are handled. schemaVersion: "1" type: "component" id: "debezium" kind: "change-data-capture" provider: "default" docs: "https://debezium.io/documentation/" defaults: mode: "log-based" ordered: true schemaEvolution: true properties: deployment: type: "enum" values: ["kafka-connect", "server", "embedded"] default: "kafka-connect" snapshotOnStart: type: "boolean" default: true