More constructive / conceptual question.
At work, it was decided to call our level of data access through web services. Therefore, our website will call web services for any / all data to and from the database. Both the website and the web services will reside on the same computer (so don't drive through the wire), but the database is on a separate machine (so this will require disconnecting by cable independently). This is all inside the company, the website, the web service and the database are in the same company (AFAIK, the web services will not be reused by the other party).
As far as I know, the website will open a port for web services, and web services, in turn, will open another port and go through the wire to the database server to receive / send data. A trip through the wire cannot be avoided, but I am concerned that web services are in the middle.
I agree that there should be different levels between functionality (such as a business level, data access level, etc.), but for me it is too complicated. I also feel that there will be problems with line performance.
I think it would be better to have (DAL) assemblies that link directly to the solution, thereby denying the first port to connect to the port.
Any thoughts (or links) for or against this idea will be appreciated.
PS We are a .NET store (transition from vb to C # 3.5)
Edit/Update
, ( , , , , ), . .