A civic inventory table with thousands of rows issues one REST call per row to a Cisco platform API, and the page feels slow even though each call is fast. What latency design change should be preferred?
Select an answer to reveal the explanation.
Short Explanation
Asking for each library book one whisper at a time loses even if every whisper is quick. Prefer a bulk or filtered list the platform already offers. Chunky beats chatty for multi-thousand-row tables.
Full Explanation
One REST call per row of a multi-thousand-row table loses on latency even when each call is fast. Prefer a list or bulk endpoint or a server-side filter the Cisco platform already offers. This is chatty versus chunky API conversation as a latency design choice, not pagination-token construction detail.