Home/ Questions/Q 4344676
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T11:55:50+00:00

I’m in the process of determining an approach for design. I would like your

  • 0

I’m in the process of determining an approach for design. I would like your inputs

I have 2 types of users

  1. Corporate Internal Users
  2. Customer Users

The fundamental differences between them technically is

  1. Corporate: Don’t need to save passwords in the system but only roles (authentication against AD)
  2. Customer Users:Save password in the system and have an associated customer ID.

I have a table User which have the columns like so

User Name  
Password  
Roles  
Customer ID

If I abstract the user creation process using an abstract factory pattern, I get the 2 types of user objects.

Now when it comes to creating a repository, how do I handle it? Do I create 2 different repositories to handle individual user type objects (mapping to same table)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Can corporate users also be customers? If so, would you expect them to use the same ID? If so, you might want to look at implementing the Party-Role pattern (aka Actor-Participant).

    It would allow you a unified solution for handling both internal user roles and corporate vs. customer distinction.

    hth.

    • 0