The GoF patterns are also strictly applicable to code only. Fowler's patterns are not just for code but also for how data and system components are arranged and interconnected.
Also, some patterns are not necessary if they're already baked in the programming language. In some languages they are simply idioms. One has actually made the argument that design patterns are signs of programming language deficiency.
I'm just adding an answer since I had this question answered somewhat differently. According to POSA (the Pattern Oriented Software Architecture series of books), there are three levels of patterns :
Architectural Patterns (e.g. Layers, MVC, P2P )
Design Patterns (e.g. GoF patterns)
Idioms (e.g. language specific patterns like Pimpl, RAII in C++)
发布评论
评论（3）
GoF 模式也严格仅适用于代码。 福勒的模式不仅适用于代码，还适用于数据和系统组件的排列和互连方式。
此外，如果某些模式已经用编程语言编写，那么它们就不是必需的。 在某些语言中，它们只是习语。 实际上有人提出这样的论点：设计模式是编程语言缺陷的标志。
The GoF patterns are also strictly applicable to code only. Fowler's patterns are not just for code but also for how data and system components are arranged and interconnected.
Also, some patterns are not necessary if they're already baked in the programming language. In some languages they are simply idioms. One has actually made the argument that design patterns are signs of programming language deficiency.
我只是添加一个答案，因为我对这个问题的回答有所不同。 根据 POSA（面向模式的软件架构系列书籍），模式分为三个级别：
I'm just adding an answer since I had this question answered somewhat differently. According to POSA (the Pattern Oriented Software Architecture series of books), there are three levels of patterns :
Ward wiki 上的 CategoryPatterns 包含模式的分类列表。
前三个是 GoF 模式
然后是特定问题
Fowler 的模式是企业应用程序模式。 还有企业集成模式。 UI 模式也存在......等等......
CategoryPatterns on Ward's wiki contains a categorized list of patterns.
The first three are the GoF patterns
Then there are problem specific problems
Fowler's pattern are Enterprise Application Patterns. There are also Enterprise Integration Patterns. UI patterns also exist.. and so on...