Integration for Apache Kafkas
Kafka integration with Kafka Connect is a framework for moving data between Kafka and external systems without writing custom code. Source connectors pull data from databases or files into topics, and sink connectors push topic data into stores such as databases or search indexes, with configuration, transforms and scalable workers.
Stage: Design and Data · Part of the Apache Kafka roadmap · Last reviewed 19 November 2026
What to learn in Integration
- Explain the difference between a source and a sink connector
- Deploy a connector using the Connect REST API
- Apply a single message transform to rename or mask a field
- Describe how change data capture streams database changes into Kafka
- Monitor connector and task status and restart a failed task
Integration interview questions
What is Kafka Connect and why use it instead of writing a consumer?
Kafka Connect is a runtime for configurable connectors that copy data in and out of Kafka. It handles offset tracking, parallel tasks, restarts, converters and scaling for you. A hand-written consumer needs all of that code, so Connect is better for standard integrations.
What is change data capture?
Change data capture reads a database's transaction log and emits each insert, update and delete as an event, so downstream systems see changes in near real time without polling tables. Tools such as Debezium run as Kafka Connect source connectors to publish these changes into topics.
Where Integration fits in the Apache Kafka roadmap
Integration belongs to the Design and Data stage (intermediate level). Build pipelines.
Other units in this stage
Back to the full Apache Kafka roadmap