Merge pull request #281335 from jcocchi/update-cache-ReadMany

[Cosmos DB] Update integrated cache docs with ReadMany guidance

Author: prmerger-automator[bot]

articles/cosmos-db/integrated-cache.md

@@ -5,7 +5,7 @@ author: seesharprun
 ms.service: cosmos-db
 ms.subservice: nosql
 ms.topic: conceptual
-ms.date: 12/27/2023
+ms.date: 7/19/2024
 ms.author: sidandrews
 ms.reviewer: jucocchi
 ---
@@ -55,6 +55,7 @@ Item cache is used for point reads (key/value look ups based on the Item ID and
 
 - New writes, updates, and deletes are automatically populated in the item cache of the node that the request is routed through
 - Items from point read requests where the item isn’t already in the cache (cache miss) of the node the request is routed through are added to the item cache
+- Read requests for multiple items, such as ReadMany, populate the query cache as a set instead of the item cache as individual items
 - Requests that are part of a [transactional batch](./nosql/transactional-batch.md) or in [bulk mode](./nosql/how-to-migrate-from-bulk-executor-library.md#enable-bulk-support) don't populate the item cache
 
 ### Item cache invalidation and eviction
@@ -73,6 +74,7 @@ The query cache is used to cache queries. The query cache transforms a query int
 
 - If the cache doesn't have a result for that query (cache miss) on the node it was routed through, the query is sent to the backend. After the query is run, the cache will store the results for that query
 - Queries with the same shape but different parameters or request options that affect the results (ex. max item count) are stored as their own key/value pair
+- Read requests for multiple items, such as ReadMany, populate the query cache. ReadMany results are stored as a set, and requests with different inputs will be stored as their own key/value pair
 
 ### Query cache eviction