问题
We are in architecture design phase of a web based Insurance System (for quoting, policy management, claims management, rate-making etc). This application would be comprises of different modules. We are planing to go with ASP.Net MVC and SQL Server. For business logic layer, we are bit confused whether to seperate our BLL using WCF services or just make BLL part of our Model. I would really appreciate your input why or why not go with SOA in our situation.
回答1:
If you absolutely sure that your services are going to be consumed by something else, SOA, but if there is even a hit that you won't need it practice YAGNI. All too often someone will build out a simple SOA arch "just in case" and each and every time they end up with "the services that power productXXX" and not a SOA arch. Once that happens the people that are developing or maintaining the product start to realize that the services are just an unnecessary waste that is causing development to take longer.
回答2:
In an MVC app most of your business logic would be in the Model, while some may be in the controllers. WCF could be used to make data services layer to support your Model/business domain. If you think the Insurance System and it's data will be consumed by anything other than the MVC app, then you should definitely go with a design that supports service-orientation (ie; WCF services).
来源：https://stackoverflow.com/questions/7879085/soa-and-asp-net-mvc