**Section 1 — The Context (The 'Why')**
Kafka as event backbone: producers (apps, CDC), consumers (stream, batch). Same event to both—Lambda. Schema Registry for evolution. Kafka for simple batch ETL overkill.
**Section 2 — The Diagram**
```
[Apps | CDC] --> [Kafka]
|
v
[Stream] + [Batch]
Fan-out
|
v
[Delta] Single table
```
**Section 3 — Component Logic**
**Kafka** event backbone. **Fan-out**: stream + batch consumers. **Single table** Delta: both write via idempotent merge....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Meesho. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.