Is having user-type per micro-service good approach?
Users in identity management context can have one of predefined user_types:
affiliate_user b2b_user accomodation_owner agent admin
But looking from the perspective of support bounded context, it cares only about agents (people who are answering tickets), and end_users (people who are asking questions).
If newly created user inside identity BC is accommodation_owner, he will be replicated to supporting bc as end_user, cause he can only ask for help.
Is this good or bad design practice? What if i need to list all agents, so I can assign a ticket.
Should I query identity microservice for users with certain user_type, or should i query supporting microservice to list me all users with type agent (