Each night the city enriches parcel records with mobility indices before morning planning views refresh. Where should that enrichment job live in a layered Big Data architecture?
Select an answer to reveal the explanation.
Short Explanation
Nightly parcel enrichment is kitchen prep, not table service. Keep the heavy batch work in processing and let serving just dish up the ready results.
Full Explanation
Layered architectures place heavy, scheduled transformations in the processing layer. Enriching parcels with mobility indices overnight is a classic batch job that should complete before serving layers expose planning views. Embedding that work in interactive UIs or ad-hoc documents couples latency-sensitive interfaces to long-running compute and blurs operational ownership.