Open-data crunch weeks spike compute once a month, then demand drops. Which cost-aware architecture choice fits better than always-on oversized clusters?
Select an answer to reveal the explanation.
Short Explanation
Paying for a stadium that is full one weekend a month is rough on the budget. Burst when the open-data crunch hits, then shrink back down.
Full Explanation
Cost-aware Big Data architecture treats elasticity as a first-class driver. Spiky municipal workloads—such as monthly open-data publication crunches—often favor burst or autoscaled capacity over permanently provisioned peak clusters. Always-on oversizing wastes budget; undersized single machines fail SLAs. Match provisioning model to demand shape.