Cluster operators want stricter consistency for ballot-status reads but looser consistency for anonymous traffic-map pings. What NoSQL concept enables that per-request-class choice?
Select an answer to reveal the explanation.
Short Explanation
Not every civic read needs the same promise. Tunable consistency lets ballot checks run strict while map pings stay loose and fast. One cluster, dialed differently per request class.
Full Explanation
Tunable consistency lets clients or operators select stronger or weaker consistency guarantees for different operations. Ballot-status reads may demand stricter agreement, while high-volume traffic-map pings may tolerate looser reads for latency. A one-size lock or random consistency would not match those varied civic needs. Awareness of tunable consistency is a standard NoSQL professional concept at syllabus depth.