问题描述
我们计划升级我们的网站，并使用N层设计。我读过了
这在我看来是相当不错的。结果
我的问题是：结果
1）是该架构仍然有效设计应用程序？结果
2）我们应该用其他建筑，如洋葱，3层，DDD等？结果
3）服务层的文章表明，我们把数据信息和命令，是最好的实现是建立两个服务一个用于数据，一个用于指令？结果
谢谢
we are planning to upgrade our web site and use the N-TIER design. i have readthis article which is quite good in my opinion.
My questions are:
1) is this architecture still valid for designing an application ?
2) should we use other architecture like the onion , 3 layer , ddd and so on?
3) in the Service Layers the article suggest that we divide the data messages and the commands, is the best implementation is to create two services one for data and one for commands ?
Thanks
推荐答案
该架构取决于你需要创建，项目和业务逻辑，可扩展性，可维护性，应该在实施项目任何方式的复杂性，什么样的项目方式，你可以很容易地改变你的code和层级和类别应该有更
解耦你应该使用ASP.NET MVC应用层，我建议使用的IoC，contaners依赖注入，你可以用3层架构开始
资料库数据访问层，服务类的商业逻辑层，ASP.NET MVC应用层
而另一件事你应该使用ORM像NHibernate的或实体框架
如果你有一个复杂的领域，你应该看看DDD
The architecture depends on what kind of project you need to create, complexity of project and business logic, scalability, maintainability, any way you should implement your project in the way that you can easily change your code and the tiers and classes should be much moredecoupled you should use ASP.NET MVC for application layer, and I suggest to use IoC-contaners for dependency injection, you can start with 3 layer architecture withRepositories data access layer, Services classes business logic layer, ASP.NET MVC application layerand another thing you should use ORM like Nhibernate or Entity FrameworkIf you have a complex domain you should look at the DDD
这篇关于Web应用程序/程序设计架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！