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
2 of 3 selected
You can now review the differences across the comparison table below.
Analysis
Pattern comparison
Reviewing 2 patterns.
| Criteria | ||
|---|---|---|
| Basics | ||
| Category | behavioral | behavioral |
| Summary | — | — |
| Intent | Provide a way to access elements of an aggregate sequentially while hiding the underlying representation. | Allow an object to alter its behavior when its internal state changes by delegating state-specific behavior to separate state objects. |
| Decision factors | ||
| Problem | A collection needs to be traversed without exposing how it is stored internally. | An object behaves differently depending on its internal state, and conditional logic is becoming hard to manage. |
| Tradeoffs |
|
|
| Practical fit | ||
| Languages |
|
|
| Platforms |
|
|
| Integration notes | Iterator is useful for pagination, custom collections, ordered traversal, and any case where clients should not know the internal data structure. | State is useful for workflows, media players, order lifecycles, and any domain where behavior changes as the object moves through a lifecycle. |