0

I saw a lot of examples of decoupling domain models from Identity models. For my knowledge, currently IIdentity is included in standard .NET library, so is this actual now and should I follow this approach? Thanks in advance!

asked Dec 11, 2020 at 13:44

1 Answer 1

2

This has little to do with Identity being part of the basic framework.

Identity is a security and user management API, while your domain model does business logic.

Architecturally speaking, Identity is a cross-cutting concern, while domain models represent your core functionality. So it makes sense to separate them from each other.

Furthermore, Identity is not the only way to manage users, so, looking at it as a component, it can absolutely be switched out, if required. Which is going to be much more difficult, if you tie it to your domain model.

answered Dec 12, 2020 at 6:26
1
  • Thank you for explanation. Could you advise articles about best approaches in asp.net? Commented Dec 12, 2020 at 10:23

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.