If someone is now asking me the most stupid thing to do in WebService, I will definitely say that "the business layer and the data access layer did not do peeling". At the beginning of the project, I think this project is small, and the intermediate layer chose WebService, so I think about the efficiency and complexity, I decided that every WebService added a data access (written by yourself) I haven't had any problems in the beginning of the stage, but as the development is in-depth, the problem has occurred. Due to the increase in the original access class, I have to make the code in each Webservice once again, and I have to update each WebService. Each WebService starts a database connection, so that 5 WebService have established 5 joints, and the impact of performance begins. Although the project is still delivered smoothly, the result of this makes it makes the subsequent code unable to use it. When I pick up a new list, I have to create it again, it is difficult to reduce efficiency and improve quality. . It seems that after completing the sweeping work, you must set up your own general data access WebService.
