5.5 Patterns with Common Characteristics
Each pattern in this book is distinct and unique and is considered an equal member of the overall pattern catalog. However, it is worth highlighting certain groups of similar patterns to better understand how they were named and why they share common characteristics.
Canonical design patterns propose that the best solution for a particular problem is to introduce a design standard. The successful application of this type of pattern results in a canonical convention that guarantees consistent design across different parts of an inventory or solution.
The canonical design patterns in this book are:
- Canonical Protocol (150)
- Canonical Schema (158)
- Canonical Expression (275)
- Canonical Resources (237)
- Canonical Versioning (286)
Centralization simply means limiting the options of something to one. Applying this concept within key parts of a service-oriented architecture establishes consistency and fosters standardization and reuse and, ultimately, native interconnectivity.
The following centralization patterns are covered in the upcoming chapters:
- Logic Centralization (136)
- Metadata Centralization (280)
- Process Centralization (193)
- Rules Centralization (216)
- Schema Centralization (200)
- Contract Centralization (409)
- Policy Centralization (207)
A common characteristic across centralization patterns is a trade-off between increased architectural harmony and increased governance and performance requirements. As explained shortly in the Measures of Pattern Application section, patterns can be applied to different extents. A key factor when assessing the application measure for centralization patterns is at what point the benefit outweighs the architectural impact.