Of all the design patterns and code methodologies we will cover in this book, perhaps the most pervasive of these is the Model-View-Presenter pattern. Model-View-Presenter, or MVP, represents the latest evolution of front-end orchestration code. It is lightweight, allowing for its application within a large number of varying platforms and programming models. It is loosely coupled, enabling enterprise developers to quickly create unit tests and deploy them easily. Most importantly, it separates code in a predictable manner, ultimately facilitating the development of a more flexible code base. Once developers become accustomed to the MVP pattern, most find that jumping in and out of other MVP projects is quite simple.
In this chapter, we will:
Review a brief overview of the MVP pattern and what it's like today
Discuss the application of MVP in different platforms
Build an MVP example in ASP.NET using the previously developed mortgage calculator code
Refactor the mortgage calculator example into a thick client application
OK, so back to this whole front-end orchestration thing. By this point, we hope the benefits of using an orchestration pattern within your front end is evident to you, but we would be remiss not to quickly review the core benefits these patterns offer. To begin with, a good front-end orchestration pattern should facilitate the separation of concerns. This is a really important concept when handling this conceptual ...