Kafka - Multi-Datacenter and Replication
Why does MirrorMaker 2 use Kafka Connect framework instead of just Kafka Producer and Consumer APIs?
Why does MirrorMaker 2 use Kafka Connect framework instead of just Kafka Producer and Consumer APIs?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand Kafka Connect advantages
Kafka Connect offers scalable, fault-tolerant connectors that simplify replication management.Step 2: Evaluate limitations of Producer and Consumer APIs
Producer and Consumer APIs can connect to clusters but lack built-in fault tolerance and scalability for replication tasks.Step 3: Eliminate incorrect reasons
Compression and topic creation are not main reasons for using Kafka Connect.Final Answer:
Kafka Connect provides scalable, fault-tolerant connectors for replication -> Option AQuick Check:
Kafka Connect = scalable, fault-tolerant replication [OK]
Quick Trick: Kafka Connect enables scalable, fault-tolerant replication [OK]
Common Mistakes:
MISTAKES- Thinking Producer/Consumer APIs can't connect to clusters
- Assuming Kafka Connect compresses data
- Believing Producer/Consumer APIs handle topic creation
Master "Multi-Datacenter and Replication" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes