I am responsible for the solution architecture of an ASP .NET MVC 3 web application and want to ensure that I follow the best practices. I have worked with MVC 3 once before, but using a solution someone else put together.
My main concern is that the Web application will make use of a WCF service to retrieve and update data. I don’t think that calling the WCF service directly from my controller methods would be best practice, but I am not sure what a good alternative would be (perhaps a Repository pattern, would this be unusual to use in conjunction with WCF?). I just would like to know if there is a standard pattern/practice I could use.
Additionally, the WCF service is a wrapper for many other webservices and so it has it’s own classes for business objects. I am not sure if I should be creating another level of abstraction between the the WCF service classes and my model classes in the MVC application. So for example the WCF service has a Reservation class, do I need to create the same class in my Models for the Web Application?
Any assistance would be much appreciated.
Thanks!
My 2 cents
No, don’t do a yet another abstraction. Use your services directly, inject a proxy instance into your controller and just call WCF methods directly from there. If you wish you may create a wrapper class to handle some WCF faults or errors.
Will your application allow an easy switch between WCF and say a database (as a data source) in the nearest future? If not stay away from the Repository pattern – keep it simple, stupid!
Do not write a copy-paste code, because it is hard to maintain it. If you need to change one type in one of your services, you must do the same mirror change in other services.
Instead separate all you common business objects into a separate project (a core library) and reuse this library in any other solutions.