Analysis
Compare patterns
Evaluate design patterns side by side across intent, tradeoffs, languages, and integration fit.
Choose patterns
Select up to 3 patterns
Current selection
3 of 3 selected
You can now review the differences across the comparison table below.
Analysis
Pattern comparison
Reviewing 3 patterns.
| Criteria | |||
|---|---|---|---|
| Basics | |||
| Category | behavioral | behavioral | behavioral |
| Summary | — | — | — |
| Intent | Define an object that encapsulates communication between a set of objects, keeping them from referring to each other directly. | Allow an object to alter its behavior when its internal state changes by delegating state-specific behavior to separate state objects. | Define the skeleton of an algorithm in a base class and let subclasses override selected steps without changing the overall structure. |
| Decision factors | |||
| Problem | Multiple objects need to coordinate behavior, but direct references between them create tight coupling and complex dependencies. | An object behaves differently depending on its internal state, and conditional logic is becoming hard to manage. | Several classes share the same algorithm structure, but some steps need to vary between implementations. |
| Tradeoffs |
|
|
|
| Practical fit | |||
| Languages |
|
|
|
| Platforms |
|
|
|
| Integration notes | Mediator is useful for chat systems, form coordination, workflow orchestration, and any domain where many components must collaborate without knowing about each other. | State is useful for workflows, media players, order lifecycles, and any domain where behavior changes as the object moves through a lifecycle. | Template Method is useful when you have repeated workflows with a common sequence of steps, such as processing orders, generating reports, and importing data. |