Source: Wikipedia. Pages: 146. Chapters: Design pattern, Abstract factory pattern, Design Patterns, Facade pattern, Adapter pattern, Bridge pattern, Singleton pattern, Visitor pattern, Flyweight pattern, Memento pattern, Lazy initialization, Builder pattern, Proxy pattern, Hierarchical visitor pattern, Delegation pattern, Strategy pattern, Mediator pattern, Interpreter pattern, Command pattern, Factory method pattern, Prototype pattern, Scheduler pattern, State pattern, Iterator pattern, Guarded suspension, Composite pattern, Balking pattern, Observer pattern, Template method pattern, Double-checked locking, Decorator pattern, Identity map, Data, Context and Interaction, Model¿view¿controller, Dependency injection, Model View ViewModel, Fluent interface, Mock object, Naked objects, Null Object pattern, Interaction design pattern, Pipeline, Chain-of-responsibility pattern, Extensibility pattern, Multiton pattern, Workflow patterns, Design pattern Servant, Active record pattern, Double dispatch, Inversion of control, Model 2, Asynchronous method invocation, Presentation-abstraction-control, Specification pattern, Model-view-presenter, Object pool pattern, Separation of presentation and content, Hollywood Principle, Curiously recurring template pattern, Architectural pattern, Data access object, MVC4WPF, Private class data pattern, Model¿view¿adapter, Barton¿Nackman trick, Thread pool pattern, Single-serving visitor pattern, Dependency inversion principle, Reactor pattern, Archetype pattern, Message broker, Initialization on demand holder idiom, Double-chance function, Canonical Model, Marker interface pattern, Hash consing, Circuit breaker design pattern, Front Controller pattern, Lazy loading, Behavioral pattern, Interceptor pattern, Portland Pattern Repository, Differentiated service, Dispose pattern, Enterprise Integration Patterns, Aggregate pattern, Lazy inheritance, Model 1, Data transfer object, Structural pattern, Type Tunnel pattern, Creational pattern, Exception chaining, Multiuse Model View, Proactor pattern, Utility pattern, Provider model, Active object, ActiveJDBC, Point of Delivery, Concurrency pattern, Mangler Pattern, Fundamental pattern, Process patterns, Debugging patterns, Service locator pattern, Head-Body Pattern, Distributed design patterns, Scheduled-task pattern, Table Data Gateway, Row Data Gateway, Amelioration patterns, Nianio. Excerpt: In software engineering, a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved. Many patterns imply object-orientation or more generally mutable state, and so may not be as applicable in functional programming languages, in which data is immutable or treated as such. Design patterns reside in the domain of modules and interconnections. At a higher level there are architectural patterns that are larger in scope, usually describing an overall pattern followed by an entire system. There are many types of design patterns, like Patterns originated as an architectural concept by Christopher Alexander (1977/79). In 1987, Kent Beck and Ward Cunningham bega...