Agreed.<p>Usually it&#x27;s always the &quot;user&quot; object which cuts across services. Was wondering if there is some common pattern for handling this.<p>For the scenario I outlined here some kind of &quot;third service&quot; &#x2F; aggregated view of the data could also be a solution. Ie. store the data needed for queries in some queryable datastore (nosql, sql; pull the info from the needed services and refresh the view when needed)