blocks|key|3752433|text|http://martinfowler.com/eaaDev/PassiveScreen.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3752434|Supervising控制器被动视图-+http://martinfowler.com/eaaDev/SupervisingPresenter.html|unordered-list-item|3752435|
|3752436|Model-View-Presenter+-|3752437|+|ordered-list-item|3752438|3752439|3752440|3752441|我个人最喜欢的是被动视图。比我见过的其他软件更具可测试性，包括MVC。|blockquote|3752442|3752443|entityMap|0|LINK|mutability|MUTABLE|url|1|http://martinfowler.com/eaaDev/SupervisingPresenter.html^0|0|1D|0|0|K|1K|1|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|G|3|H|5|6|7|1B|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|1C|8|@]|9|@]|C|$]]|$1|K|3|L|5|M|7|1D|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]|$1|Q|3|R|5|S|7|1H|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|4]]|11|$5|X|Y|Z|C|$10|12]]]]

<ol>
<li>Passive View - <a href="http://martinfowler.com/eaaDev/PassiveScreen.html" rel="noreferrer">http://martinfowler.com/eaaDev/PassiveScreen.html</a></li>
<li>Supervising Controller - <a href="http://martinfowler.com/eaaDev/SupervisingPresenter.html" rel="noreferrer">http://martinfowler.com/eaaDev/SupervisingPresenter.html</a></li>
<li>Model-View-Presenter - <a href="http://martinfowler.com/eaaDev/ModelViewPresenter.html" rel="noreferrer">http://martinfowler.com/eaaDev/ModelViewPresenter.html</a> </li>
</ol>

<blockquote>
 My personal favorite is the Passive View. More testable than others I've seen including MVC.
</blockquote>

blocks|key|5163795|text|其他一些架构模式，包括MVC。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5163796|分层系统|offset|length|style|BOLD|5163797|TCP/IP|5163798|面向对象的组织|5163799|模型-视图-控制器，表示-抽象-控制，模型视图呈现器和模型视图ViewModel。|5163800|例如ASP.NET的MVC、Ruby+on+Rails等。|5163801|基于事件的隐式调用|5163802|浏览器环境(DOM)|5163803|管道和过滤器架构|5163804|Unix管道|5163805|存储库|5163806|表驱动解释器|5163807|5163808|你也可能会发现Garlan+&+Shaw关于软件架构的this+paper是一本不错的读物。|5163809|另一个值得注意的链接是Wikipedia上关于架构模式的文章。|5163810|entityMap|0|LINK|mutability|MUTABLE|url|http://sunner.cn/courses/SA/intro_softarch.pdf|1|http://en.wikipedia.org/wiki/Architectural_pattern_(computer_science))^0|0|0|4|0|0|0|7|0|0|0|2|7|0|0|0|8|0|0|0|3|0|0|6|0|0|R|A|0|0|B|9|1|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1K|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1L|8|@$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1O|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1P|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1T|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1U|8|@$D|1V|E|1W|F|G]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1X|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|21|8|@$D|22|E|23|F|G]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|24|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|25|8|@]|9|@$D|26|E|27|1|28]]|A|$]]|$1|14|3|15|5|6|7|29|8|@]|9|@$D|2A|E|2B|1|2C]]|A|$]]|$1|16|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]]|17|$18|$5|19|1A|1B|A|$1C|1D]]|1E|$5|19|1A|1B|A|$1C|1F]]]]

Some other architectural patterns including MVC.

Layered Systems

TCP/IP

Object-Oriented Organization

Model-View-Controller, Presentation-abstraction-control, Model View Presenter and Model View ViewModel. 

Examples would be ASP.NET's MVC, Ruby on Rails, and bunch of others.

Event Based, Implicit invocation

Browser environment (DOM)

Pipe and filter architecture

Unix pipes

Repositories

Table Driven Interpreters

<hr />

You may also find <a href="http://sunner.cn/courses/SA/intro_softarch.pdf" rel="noreferrer">this paper</a> by Garlan &amp; Shaw on Software Architecture a nice read.

Another noteworthy link would be the article on architectural patterns at <a href="http://en.wikipedia.org/wiki/Architectural_pattern_(computer_science)" rel="noreferrer">Wikipedia</a>.

blocks|key|5163468|text|我偶尔会看到没有C的MVC，视图监听模型数据的更改并相应地更改呈现，模型中的方法被绑定到视图的事件处理程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5163469|对于视图必须与数据紧密耦合的项目(例如，当存在与模型或模型属性直接相关的可视组件时)，这可能相当有用，因为它省去了“中间人”。|5163470|我想许多人会争辩说，这仍然是MVC，只是一个混合版本，视图和模型之间建立的绑定是控制器逻辑。|5163471|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I've occasionally seen MVC without the C, where the view listens for changes in the model's data and alters rendering accordingly, and where the methods in the model are bound to event handlers for the view.

For projects where the view is by necessity tightly couple with the data (such as when there are visual components that directly relate to the model or attributes of the model), this can be rather useful, as it cuts out the "middle man."

I think many would argue, though, that this is still MVC, just a hybridized version, and that the bindings established between the view and model are controller logic.

blocks|key|5163513|text|当然，有Model-View-Presenter，但是我想你会发现MVC最常见的“替代方案”就是缺乏适当的分离。作为一个极端的例子，考虑一下典型的ASP页面，其中HTML、VBScript和SQL并排出现在同一个文件中。(这不是一大堆ASP+--你会在其他语言中找到很多这样的例子。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5163514|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Well, there's Model-View-Presenter, but I think you'll find that the most common "alternative" to MVC is really a lack of proper separation. As an extreme example, consider classic ASP pages where HTML, VBScript and SQL are found side-by-side in the same file. (That's not a bash of ASP — you'll find plenty of such examples in other languages.)

blocks|key|5163571|text|虽然上面的答案是正确的，但我认为更重要的是要注意到，90%25的软件开发人员完全不知道“设计模式”这个词。他们只是开始写代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5163572|挑战不是选择最好的设计方法，而是让别人相信设计是有价值的。|5163573|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Although the above answers are quite correct, I think it's much more important to note that the words "design pattern" are completely unknown to 90% of all people who create software. They just start writing code. 

The challenge is not selecting the best design approach, it's convincing others that design has value.

blocks|key|5163869|text|嗯，它现在已经很旧了。我想再提一个(为了了解更多的信息)是PresenterFirst+patrern|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5163870|以下是关于同一主题的更多信息：|5163871|http://en.wikipedia.org/wiki/Presenter_First|5163872|http://www.atomicobject.com/pages/Presenter%2BFirst|5163873|HTH|5163874|entityMap|0|LINK|mutability|MUTABLE|url|1|http://www.atomicobject.com/pages/Presenter%2BFirst^0|T|M|0|0|0|18|0|0|0|1D|1|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|J|3|K|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|L|3|M|5|6|7|18|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|I]]|U|$5|Q|R|S|E|$T|V]]]]

Well it is quite old now. I would like to mention one more (in the interest of info for additional knowledge) is PresenterFirst patrern

Here is more information on the same:

<a href="http://en.wikipedia.org/wiki/Presenter_First" rel="nofollow">http://en.wikipedia.org/wiki/Presenter_First</a>

<a href="http://www.atomicobject.com/pages/Presenter+First" rel="nofollow">http://www.atomicobject.com/pages/Presenter+First</a>

HTH

blocks|key|706877|text|表示-抽象-控制(+Presentation-Abstraction-Control，PAC)模式系列，其中接口/交互由代理层次结构处理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|706878|维基百科上的那篇文章不是很棒的http://en.m.wikipedia.org/wiki/Presentation-abstraction-control|offset|length|706879|entityMap|0|LINK|mutability|MUTABLE|url|http://en.m.wikipedia.org/wiki/Presentation-abstraction-control^0|0|F|1R|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

The Presentation-Abstraction-Control (PAC) family of patterns, where interface/interaction is handled by a hierarchy of agents.

The wikipedia article is not great
<a href="http://en.m.wikipedia.org/wiki/Presentation-abstraction-control" rel="nofollow noreferrer">http://en.m.wikipedia.org/wiki/Presentation-abstraction-control</a>

blocks|key|3752823|text|在Lift+web框架中，我们使用View+First方法。基本上，一个视图由一个或多个代码片段(有点类似于控制器)组成，并且代码片段可以嵌套。这与HTML和Scala内置的XML处理功能配合使用非常好。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3752824|entityMap|0|LINK|mutability|MUTABLE|url|http://liftweb.net/|1|https://www.assembla.com/wiki/show/liftweb/View_First^0|1|4|0|H|A|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

In the <a href="http://liftweb.net" rel="nofollow noreferrer">Lift</a> web framework we use a <a href="https://www.assembla.com/wiki/show/liftweb/View_First" rel="nofollow noreferrer">View First</a> approach. Basically a view is composed of one or more snippets (somewhat similar to controllers) and snippets can be nested. This works very well with HTML and Scala's built-in XML processing capabilities.

blocks|key|2908302|text|您可以使用当前的ASP.NET框架滚动自己的MVC，并且仍然保留回发模型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2908303|http://www.codeproject.com/KB/aspnet/RollingYourOwnMVCwithASP.aspx|offset|length|2908304|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1U|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

You can roll your own MVC with the current ASP.NET framework and still keep the postback model.

<a href="http://www.codeproject.com/KB/aspnet/RollingYourOwnMVCwithASP.aspx" rel="nofollow noreferrer">http://www.codeproject.com/KB/aspnet/RollingYourOwnMVCwithASP.aspx</a>

blocks|key|707029|text|那么Observer模式呢？如果我没记错的话，MVC是在Smalltalk中引入的，此后出现了几种发布/订阅模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|707030|观察者模式(发布/订阅模式的子集)是一种软件设计模式，在该模式中，称为主题的对象维护其依赖项的列表，称为观察者，并自动通知它们任何状态更改，通常通过调用它们的方法之一。它主要用于实现分布式事件处理系统。|707031|例如:只有当有数据要保存时，保存按钮才会在编辑者中启用。观察者模式的另一个示例是MFC中的文档视图体系结构，其中视图中的内容会随着文档的更改而更新。|707032|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Observer_pattern^0|2|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

What about the <a href="http://en.wikipedia.org/wiki/Observer_pattern" rel="nofollow">Observer</a> pattern. If I am not mistaken , MVC was introduced in Smalltalk and thereafter several publish/ subscribe patterns have come into picture. 

The observer pattern (a subset of the publish/subscribe pattern) is a software design pattern in which an object, called the subject, maintains a list of its dependents, called observers, and notifies them automatically of any state changes, usually by calling one of their methods. It is mainly used to implement distributed event handling systems.

Ex : The Save button gets enabled in an editior, only when there is data to be saved. Another example of the observer pattern is Document View architecture in MFC, where in the view gets updated when the document changes .

While going through university and from following the development of SO, I've heard a lot about the Model-View-Controller architectural design pattern. I inadvertently used the MVC pattern even before I knew what it was, and still use it in my everyday job. From what I've seen, it's probably the most popular pattern used today. What I haven't heard much about though, are the alternative patterns you can use instead of MVC. What options are there, and for what reasons would you decide to use them over MVC? I'm also interested in knowing the types of systems they are typical of being used for. Finally, what are the pros and cons that come along with using them?

What Alternatives Are There to Model-View-Controller?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在大学期间，通过跟踪SO的发展，我听说了很多关于Model-View-Controller架构设计模式的事情。甚至在我知道MVC模式是什么之前，我就无意中使用了MVC模式，并且仍然在我的日常工作中使用它。据我所知，这可能是当今使用的最流行的模式。然而，我没有听说太多的是你可以用来代替MVC的替代模式。有哪些选项，出于什么原因，您会决定使用它们而不是MVC？我也有兴趣了解它们通常用于的系统类型。最后

问模型-视图-控制器有哪些替代方案？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问模型-视图-控制器有哪些替代方案？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问模型-视图-控制器有哪些替代方案？
EN