❔ Naming Conventions N-Tier architecture, conflicts?
Hey!
Would like to hear additional feedbacks regarding this naming approach and a suggestion to solve conflicts.
The general naming idea is explained in details here -
https://softwareengineering.stackexchange.com/a/259840/429884
The summarize example would be (Taking User entity as example) -
*If the logic class gets too big we break it down to CQRS classes.
Following the convention above how would you avoid explicitly writing namespaces between the Model layer and the Business layer?
For example, you have this namespace in your Model layer -
And this namespace in your Logic layer -
You can't use
What do you think?
thx!
Would like to hear additional feedbacks regarding this naming approach and a suggestion to solve conflicts.
The general naming idea is explained in details here -
https://softwareengineering.stackexchange.com/a/259840/429884
The summarize example would be (Taking User entity as example) -
*If the logic class gets too big we break it down to CQRS classes.
Following the convention above how would you avoid explicitly writing namespaces between the Model layer and the Business layer?
For example, you have this namespace in your Model layer -
ProjectName.Models.UserUser.csAnd this namespace in your Logic layer -
ProjectName.Logic.UserUserLogic.csYou can't use
User.csUserLogic.csWhat do you think?
thx!
