Implications of using /id for the partition key in CosmosDb
I am from the Cosmos DB engineering team.
You don't have to worry about the number of logical partition keys that are created on a Cosmos DB collection/container. As long as the partition key is an appropriate choice for your writes (subject to a per-logical partition key cap of 10GB) and queries, you should be good.
- best cardinality
easy&fast&cheap document reads
no transactions as transaction scope is partition key
- queries by anything other than
idwill be cross-partition
I can hardly imagine the case for not needing anything but by
id reads/queries. except maybe for document caching (combined with TTL).