Leaders want interactive queries over huge municipal log stores, similar to web-scale query systems. Which architecture pattern should the team emphasize?
Select an answer to reveal the explanation.
Short Explanation
Huge logs with snappy answers need a serving pattern built for questions, not a paper newsletter. Think indexed, cached, query-ready stores — not empty folders or offline tape treasure hunts.
Full Explanation
Reference architectures for large-scale interactive query separate durable storage from low-latency serving paths. Municipal log analytics borrows that pattern: persist at scale, then serve interactive requests with appropriate indexes and engines. Print-only digests, wiping history, or forcing offline full scans defeat the interactive goal. Pattern awareness matters more than copying any single vendor’s private stack.