是ASP.NET MVC的大型企业项目一个坏的选择？ [英] Is ASP.NET MVC a bad choice for a large enterprise project?

问题描述

我们即将踏上大型企业应用程序。我很认真地考虑使用ASP.NET MVC，因为：

1. 我们需要使用微软的技术（BIZ逻辑是所有C＃）


2. 性能是至关重要


3. ，我想尽可能多的测试尽可能

我的团队只用了PHP的Web开发，但很有经验的.NET的WinForms（所以不管怎样，我们有一个学习曲线）。我担心的是，有些人对ASP.NET MVC的可扩展性，以大型应用前pressed担忧。但是，从我读的WebForms有自己的问题也是如此。

我应该重新考虑web表单，或坚持我的直觉和使用ASP.NET MVC？

相关：

  

<一个href=\"http://stackoverflow.com/questions/247115/should-i-build-my-next-web-app-in-asp-net-mvc\">http://stackoverflow.com/questions/247115/should-i-build-my-next-web-app-in-asp-net-mvc
  <一href=\"http://stackoverflow.com/questions/521388/from-webforms-to-asp-net-mvc\">http://stackoverflow.com/questions/521388/from-webforms-to-asp-net-mvc

解决方案

ASP.NET的WebForms非常像WinForms和允许RAD（快速应用开发）。这是非常快速获得在任何时间的东西。这个问题正在测试可以是一个重大的痛苦，如果用于任何面向公众的可能意味着ViewState的一些重大问题。的WebForms可以保持状态就像一个向导一件轻而易举的使用使事情。

ASP.NET MVC，另一方面可以需要一点时间与开发，并要求开发者了解如何HTTP的工作原理。这是一个无状态的架构意味着每个请求是它自己的小世界里，通常没有previous要求的知识。该框架还允许高的可测试性。

至于性能也越高，他们很可能相同，因为ASP.NET MVC仅仅是建立在现有的ASP.NET架构之上的框架。虽然对客户端的经验，我会说MVC是快了些。

至于可扩展性，我会说他们是差不多的，只要技术去。至于如何使用API​​和集成其MVC很可能会更容易一点。

您现在正在使用要问这个问题，版本网站是建立在ASP.NET MVC，他们有2个Web服务器和仡数据库服务器。

We are about to embark on a large enterprise application. I am seriously considering using ASP.NET MVC because:

1. We need to use Microsoft technology (biz logic is all C#)
2. Performance is critical
3. I'd like to test as much as possible

My team has only used PHP for web development, but are very experienced with .NET winforms (so either way we have a learning curve). My concern is that some people have expressed concerns about ASP.NET MVC's scalability to large apps. But from what I read webforms have their own problems as well.

Should I be reconsidering webforms, or stick with my gut and use ASP.NET MVC?

Related:

http://stackoverflow.com/questions/247115/should-i-build-my-next-web-app-in-asp-net-mvc http://stackoverflow.com/questions/521388/from-webforms-to-asp-net-mvc

解决方案

ASP.NET WebForms is very much like Winforms and allows for RAD (rapid application development). It's very fast to get something in no-time. Problem with this is testing can be a major pain and if used for anything public facing can mean some major issues with ViewState. WebForms can hold state making things like a wizard a breeze to use.

ASP.NET MVC on the other hand can take a little longer to develop with and requires that devs understand how HTTP works. It's a stateless architecture meaning each request is it's own little world and usually has no knowledge of previous requests. The framework also allows for high testability.

As far as performance goes they're probably the same because ASP.NET MVC is just a framework built on top of the existing ASP.NET architecture. Though for client-side experience I'd say MVC is a bit faster.

As far as scalability I would say they're about the same as far as technical goes. How as for using the API and integrating it MVC would probably be a bit easier.

The website you're using right now to ask this version question is built on ASP.NET MVC and they have 2 web servers and a beefy db server.

这篇关于是ASP.NET MVC的大型企业项目一个坏的选择？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！