I'm designing an MVC application.
I'm considering using webservices so that multiple deployments of the MVC front end can work off a central database accessed via webservices hosted on a seperate server from the MVC application e.g.
- MVC application on one server
- Webservices implementing business logic and calling database on another server
- A database server
If I go down this route then
- The controllers in the MVC app will call the webservices, rather than the database directly
However I'm concerned that under this setup the models in the MVC project will just be placeholder objects with validation attributes in them and I will be missing out on other benefits/cabilitiues of the model.
Are there ways of aligning MVC applications with WCF so that using WCF dosn't mean you lose any of the benefits of MVC