>>::Any advice or help would be great! Tell the architect to go back to school. Beginner class. LMAO! I needed something to wake me up this morning, thanks Thona. Hopefully no one takes offense at your style. >>1) Is OO the best approach for designing the business logic in the middle tier? I agree with Thona that OO is pretty much the best approach. The reason being that it is the simplest type of architecture to maintain and extend (assuming it is designed effectively), usually. On top of this a lot of work has gone into making it fast and with today's CPU speeds there shouldn't be a noticeable performance difference. Obviously, if you wrote in ASM it would be FASTEST, but I think we all understand why we use a high level language. >>2) Is it a necessity to use either .net remoting or web services for scalability for a large web site? I've never used remoting and haven't worked on a 30 million hits/day site, either. But, it seems to me that you would only need to use remoting in a few situations: 1) Your web servers are so overwhelmed with traffic that they CANNOT support the execution of any business logic because a large performance degradation will occur. 2) You need to share business logic "state" that is not persisted in the database/DAL. In both of these cases I see a valid need for a physically seperated middle tier - though there often might be a work around for these issues also.