1. MVC+ xml web service using MS MVC.

The project is made with MS ASP.net front end and business logic, and the logic contains does coded with some complicated logics to interact with the front end layer , then it calls a xml web service to handle some other business logic, and at the end it interact with the SQL server by stored procedure.

The cons of that implementation is that when things go wrong, it's hard to step in the web service to trace what is going wrong inside, after the execution run through multiple layers. nd worse of all. there are no logging at all.

I think what goes wrong is that the previous project lead does not instruct the junior programmers to avoid putting logic in the front end asp.net layer, and concentrate engineer the logic behind the web service.

Also the MS-IIS is a beast to configure. people have to dig in the application pool and apply some tricks like, threads, setting some strange user to the OS and apply security on them.