[Why commercial easycrm sample doesn't follow the domain driven design best practices? #2609](https://support.abp.io/QA/Questions/2609/Why-commercial-easycrm-sample-doesn%27t-follow-the-domain-driven-design-best-practices)
How can I get the new EasyCrm?
I would like to know is there a clear time/plan to complete this feature? Now ABP is tightly coupled with IdentityServer and it's not as simple to switch to other providers. We would suggest it's completely redesigned so ABP supports different Oauth providers. Our business users always concerning about the identity server future and want to switch to they own idp. Now I see the the task #7221 in 5.3-preview milestone. Is this feature determined to be completed at Milestone 5.3-preview this time? Won't it move to another milestones at the last minute? Because I'll arrange our schedue according this feature. Can you help to comfim? Best regards.
I have queries about the commercial easycrm sample.
Take ProductGroup and Product for example, there are both aggregate root.
As saied in book <<Implementing_Domain_Driven_Design>>:
But as you can see in EasyCrm sample, ProductGroup have a collection of the Products, and Product have a navigation property for the ProductGroup.
Above is just one sample doesn't follow the book. Actully, there are many places. I would like to know why not follow the best practices? Do you have any good reasons? if not, can you refactor these code? And this sample always upgrade delayed. Now still in v5.0.0.
