A design pattern is an industry-proven model for creating a custom solution to a recurring software architecture problem. It is a model, not a ready-made solution: adapt it to the application’s requirements. section 1.1 section 8.0
Use design patterns to:
- Address common architecture problems while managing change and complexity. section 1.4.5 section 1.7
- Build more flexible, reliable, maintainable, and scalable software. section 1.10 section 1.3
- Support iterative design by revising poor decisions as requirements evolve. section 1.0 section 1.7
Publisher–subscriber architecture
A publisher produces data while subscribers consume it. The Observer Design Pattern supplies a model for separating these roles into a custom solution. Similar pattern-based evolution appears when interchangeable sports strategies are selected at runtime. section 1.4.5 section 8.0
Apply a pattern after understanding requirements, then compare a straightforward implementation with a refactored design. Good design balances flexibility against added complexity rather than anticipating every possible change. section 1.2 section 1.7
