DBContext for Identity and application models, to separate or not?

I can’t find a concrete answer on best practices(in fact some blog posts say there is no definite right way to do this), so I was curious what other developers usually do. Do you guys have separate dbcontexts for your Identity models and your application models? The upsides seem to be its easier to separate logic and components in the future if you need to, and the downsides can include having to perform joins in application memory vs in the database (this seems significant to me). Are there other things I should be taking into consideration? I’m using .NET core 2.1, if that makes a difference.

submitted by /u/Chatterfoam
[link] [comments]

Leave a Reply