Design batch and streaming ETL architecture
MetaData Engineer · OnsiteLast updated
Design batch and streaming ETL architecture evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
Design an end-to-end data platform that supports both daily batch processing and near-real-time streaming for product analytics. Specify the ingestion sources and formats; schema design for raw, staging, and modeled layers; table partitioning and clustering; strategies for idempotency, deduplication, and handling late/out-of-order events; update patterns (append-only vs upsert/merge), slowly changing dimensions (SCD1/SCD 2), and backfills; orchestration, dependency management, and failure recovery; aggregation strategies for daily/hourly/rolling-window metrics; data quality checks and SLAs; and trade-offs between latency, cost, and complexity.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.