The citizen portal is served from NoSQL, but planners need heavy multi-year group-by analytics across all districts. Where should those analytical aggregations typically run?
Select an answer to reveal the explanation.
Short Explanation
The portal needs snappy NoSQL reads; the big group-bys belong on the analytical track. Hadoop or Spark can crunch years of districts without choking the serving tier. Keep serving and heavy analytics in their own lanes.
Full Explanation
NoSQL serving tiers optimize for operational reads and writes at interactive latency. Heavy analytical group-bys over multi-year civic datasets usually belong on batch or analytical engines such as Hadoop or Spark. Mixing those workloads into the serving path risks latency and capacity problems for the portal. Separating analytical processing from NoSQL serving is a standard Big Data architecture practice.