**Latency**: Batch hours; stream seconds. **Throughput**: Batch higher per dollar; stream lower. **Complexity**: Batch simpler; stream more ops. **Cost**: Batch cheaper per GB; stream always-on.
**When Batch**: Analytics, ML training, reporting. Latency acceptable (hours).
**When Stream**: Alerts, fraud, real-time dashboards. SLA = seconds/minutes.
**Hybrid**: Lambda (stream + batch) or incremental batch (hourly micro-batch).
**Scalability Trade-offs**: Batch scales with partition count....
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 McKinsey. 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.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
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.