Splitting a Website

Question

User-146938715 posted

Hello,
I would like to build a website that has several almost independent areas. For example: customers, clients and employees. Each of the areas uses some of the other's elements, all of which I provide through a shared DLL. They should all use their own databases, with one exception. The user administration. Because every customer can also be a client or an employee at the same time.
The customer area will probably only rarely receive updates later, while the employee area will receive updates almost daily. Therefore I would like to separate this so that the customers are not affected by the updates.
Now I wonder how I build a program, specifically the Entity Framework, which always creates the user administration.

Answer 1

User475983607 posted

Now I wonder how I build a program, specifically the Entity Framework, which always creates the user administration.

Identity is modular user account API.

https://docs.microsoft.com/en-us/aspnet/core/security/authentication/identity?view=aspnetcore-2.2

You can go a step further and implement centralized authentication using IdentityServer4 which will be included in ASP.NET Core 3.0 templates.

http://docs.identityserver.io/en/latest/

 

Answer 2

User379720387 posted

You can more easily create the separation at code level through User Roles, than at db level.

Because every customer can also be a client or an employee at the same time

Identity is handled at db level.  Were you to have one user have multiple log ins that would complicate things enormously. You would end up with unnecessary complexity.

In a single db you assign user roles and you design functionality for the various roles.