AspNetCore.Identity.DocumentDb
AspNetCore.Identity.DocumentDb copied to clipboard
Figure out a way to support Partitioning
In Identity, sometimes all we have is a UserId
or UserName
only, but querying for as User with those already requires to know the according PartitionKey
. A generic, fast and convenient way to get a PartitionKey
from either a UserId
or a UserName
, when the PartitionKey
can really be anything, needs to be figured out (just for example: when creating a user with a PartitionKey
, store a UserId
-UserName
-PartitionKey
mapping in DocumentDb).
Ideas on how support for automatic partitioning could be implemented in an as flexible and unopinionated way as possible, please chime in.
Hi, I'm not remotely thinking that I am a specialist in Identity, or CosmosDB, but I am certainly an interested party, but there could certainly be some big holes in my suggestion.
My understanding of partitions is that Cosmos automatically assigns the partitions in the background, keeping track of what partition keys are in what partition. Everything with the same partition key is guaranteed to be on the same partition.
I think the easiest way to do this is to have 3 documents. The main user document which will have the userId (or some guid/random string) as the partition key, and in general any other documents for that known user would have the same partition key, keeping all their documents on the same partition.
The other 2 documents are very small and are used to find the partition key for the main document. One would be for finding the user by the user name, and would have a partition key that is the user name. All this document really contains is the partition key for the main user document that work can then be performed from. The other one would basically be the same, but with the user id (or whatever other info is used to search for the user) instead of the user name.
Does that make sense? I appreciate that it will mean there are always 2 files to read when someone logs in, but don't think this would be too much overhead would it??
Do you have any progress on this? We would like to use this repository in our project with partitioned Cosmos DB, but with the current implementation we can't.
@daveh101 I think your idea is good because by querying by partitionkey is almost free in cosmosdb so you can get the partitionkey for almost free and then query for the user also for free.
Hi Folks,
Is there any update on this topic? I see the thread is quite long out there so just wanted to ping if there`s any update on it...