SOA和ASP.net MVC [英] SOA and ASP.net MVC

问题描述

我们正处于基于Web的保险系统的架构设计阶段(用于报价，保单管理，理赔管理，费率制定等).该应用程序将包含不同的模块.我们计划将ASP.Net MVC和SQL Server一起使用.对于业务逻辑层，我们对于使用WCF服务分隔BLL还是仅将BLL作为模型的一部分感到困惑.非常感谢您的意见，为什么或为什么不采用SOA.

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.

推荐答案

如果您完全确定您的服务将被其他东西(SOA)消耗，但是即使遇到了麻烦，您也不需要实践亚尼通常，有人会以防万一"建立一个简单的SOA架构，而每次他们最终都会得到为productXXX提供动力的服务"，而不是SOA架构.一旦发生这种情况，开发或维护产品的人员就会开始意识到服务只是不必要的浪费，导致开发花费更长的时间.

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.

这篇关于SOA和ASP.net MVC的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！