Editors need live page-view counters while analysts keep multi-year history. How should NoSQL and the lake share duties?
Select an answer to reveal the explanation.
Short Explanation
Live counters want a sprinter's shoes; history wants a warehouse. Stick hot tallies in a KV or wide-column store and park the long tale in the lake. Chapter 6 NoSQL skills show up right inside the chapter 10 analyzer.
Full Explanation
Hybrid serving often pairs NoSQL stores for low-latency page-view counters with a data lake for historical clickstream and aggregates. That chapter 6 pattern inside chapter 10 matches access patterns: frequent tiny increments versus deep analytic scans. One technology rarely optimizes both live counters and long-term history equally.