Analysis

Compare patterns

Evaluate design patterns side by side across intent, tradeoffs, languages, and integration fit.

Choose patterns

Select up to 3 patterns

Abstract FactoryAdapterBridgeBuilderChain of ResponsibilityCommandCompositeDecoratorFacadeFactory MethodFlyweightInterpreterIteratorMediatorMementoObserverPrototypeProxySingletonStateStrategyTemplate MethodVisitor

Current selection

3 of 3 selected

You can now review the differences across the comparison table below.

Clear all

Analysis

Pattern comparison

Reviewing 3 patterns.

Criteria
behavioralIteratorView pattern
behavioralMediatorView pattern
behavioralStateView pattern
Basics
Categorybehavioralbehavioralbehavioral
Summary———
IntentProvide a way to access elements of an aggregate sequentially while hiding the underlying representation.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.
Decision factors
ProblemA collection needs to be traversed without exposing how it is stored internally.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.
Tradeoffs
  • Can add extra classes and abstraction for simple collections
  • May be unnecessary when built-in language iteration is already enough
  • The mediator can become large and complex if it takes on too much coordination logic.
  • Centralizing behavior can make the mediator a single point of failure if it is poorly designed.
  • Can introduce many small classes if the state graph is large
  • State transitions may become harder to trace if spread across multiple classes
Practical fit
Languages
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
Platforms
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
Integration notesIterator is useful for pagination, custom collections, ordered traversal, and any case where clients should not know the internal data structure.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.