Action–domain–responder: Difference between revisions
Content deleted Content added
Martin Bean (talk | contribs) mNo edit summary |
Martin Bean (talk | contribs) Add external links |
||
| Line 8: | Line 8: | ||
== ADR versus MVC == |
== ADR versus MVC == |
||
ADR should not be mistaken for a renaming of MVC. |
ADR should not be mistaken for a renaming of MVC. |
||
== References == |
|||
{{Reflist}} |
|||
==External links== |
|||
* Paul M Jones' original proposal of ADR: http://paul-m-jones.com/archives/5970 |
|||
* [http://martinbean.co.uk/blog/2016/10/20/implementing-adr-in-laravel/ Implementing ADR in Laravel], an implementation of the pattern in the [[Laravel]] [[PHP]] [[Web framework|framework]], by Martin Bean |
|||
Revision as of 09:22, 14 June 2017
Action–domain–responder (ADR) is an adaptation of Model–view–controller (MVC), a software architectural pattern that was proposed by Paul M Jones[1] to be better suited for web applications. Similar to MVC, the application is divided into three parts.
Components
- The action part can closely match http requests (URLs and their methods).
- The domain part relates to the subjects of the application.
- The responder part relates to providing the output from the application.
ADR versus MVC
ADR should not be mistaken for a renaming of MVC.
References
External links
- Paul M Jones' original proposal of ADR: http://paul-m-jones.com/archives/5970
- Implementing ADR in Laravel, an implementation of the pattern in the Laravel PHP framework, by Martin Bean