Each month the city mashes multi-agency open-data dumps for a retrospective equity report. Where should that heavy batch mashup run?
Select an answer to reveal the explanation.
Short Explanation
Month-end mashups are warehouse work, not cashier-window work. A Hadoop batch cluster is built for hauling big historical open-data piles; the live tax OLTP box is not. Keep the mashup off the payment servers.
Full Explanation
Large monthly open-data mashups are batch analytical workloads. Hadoop clusters are appropriate for scanning and joining large historical sets without burdening OLTP systems that serve citizen transactions. Running those mashups on property-tax or CAD databases risks contention and does not match Hadoop’s batch analytics role.