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
structuralCompositeView pattern
behavioralMediatorView pattern
behavioralStateView pattern
Basics
Categorystructuralbehavioralbehavioral
SummaryCompose objects into tree structures to represent part-whole hierarchies and let clients work with individual and composite objects through the same interface.——
IntentCompose objects into tree structures to represent part-whole hierarchies and let clients work with individual and composite objects through the same interface.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 system needs to treat individual objects and groups of objects uniformly, but the hierarchy becomes difficult to manage with separate code paths.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 make the design more abstract and harder to follow.
  • May require careful handling of operations that only apply to some nodes in the tree.
  • Makes recursive tree operations and client code much simpler.
  • 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 notesComposite is useful when a hierarchy of nested objects should expose a common interface, such as files and folders, menus and submenus, org charts, widget trees, or scene graphs.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.