While intuitively UserIdentity::getActorId() seems useful to have, there is no way to know at which point an ID will be assigned to an actor. Any code calling the getter would have to implement a fallback for the case no actor ID is present yet. And any code creating a UserIdentity value object would have to check if an ID has been assigned yet.
For this reason, the actor ID should be treated as an optimization/normalization internal to the storage layer, and not modeled on the level of domain entities (the "user"). Application logic should not know or care about actor IDs. Storage level code should rely on the ActorNormalization service to obtain actor IDs when needed for database operations.
- soft-deprecate getActorId()
- remove known callers of getActorId()
- hard-deprecate getActorId()
- wait for at least one release branch and three months per the stable interface policy
- remove getActorId()