Sep 17, 2010 05:33 PM|HeartattacK|LINK
You don't design an app to match patterns - you find patterns that match your scenario and use whichever one seems appropriate. A lot of the times, you may need to be flexible in the implementations of those patterns so that they better server your needs.
Your needs don't serve patterns - the patterns serve you. As such, there's no pattern suited for all scenarios. WebForms is geared to Smart UI, MVC is used in ASP.NET MVC to separate concerns, MVVM is used in XAML based apps, MVP is used to make some codebehind
in WebForms or other Smart UI based presentation engines more testable, the Repository can help in simplifying data access, Specification may help in querying, Stategy and Visitor in simplifying complex business logic, Singletons can be used in thread safety
scenarios, Adapter, Bridge and Facade can be used to connect mismatching sections of a project or to the outside world, Infinite Data can make pagination seem instant, Unit of Work can help in change tracking and transaction management - the list goes on and