What Alternatives Are There to Model-View-Controller? [closed]

Answer 1

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

http://www.codeproject.com/KB/aspnet/RollingYourOwnMVCwithASP.aspx

Answer 2

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.

Answer 3

In the Lift web framework we use a View First 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.

Answer 4

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

The wikipedia article is not great http://en.m.wikipedia.org/wiki/Presentation-abstraction-control

Answer 5

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

---

You may also find this paper by Garlan & Shaw on Software Architecture a nice read.

Another noteworthy link would be the article on architectural patterns at Wikipedia.

Answer 6

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.)