c# - Business Logic Classes Naming -
I have a business layer in which some business items / POCOs / institutions / whatever I have got some repositories Also till this point, I am reaching the repository directly from my UI layer. I am at a point where I really want some more classes which are not directly CRUD, so I'm going to create some business logic classes which will argue, and the CRUD will be used, and the repository will not be used anymore (from the beginning Should have been done only)
What should I say to these classes? The only thing I can think of are service classes, but I have real WCF services in this application, so that it will be confused. WCF services are also using these sections, so using a service service is strange and confusing.
I also use the "service" naming convention, it is true that "service" The overloaded period has become, but it is most understandable. Developers reviewing the code should be able to determine the difference between an application / domain service with WCF service, and while calling the WCF service, another service class may be confusing, I think you believe that this is not. The idea of a service is that this is the code that functions, and is available for use by other codes, it can be an internal service, or it may be a service that is external to http or whatever, but the code What does the same idea do?
Comments
Post a Comment