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
behavioralMediatorView pattern
behavioralMementoView pattern
behavioralStrategyView pattern
Basics
Categorybehavioralbehavioralbehavioral
Summary———
IntentDefine an object that encapsulates communication between a set of objects, keeping them from referring to each other directly.Capture and externalize an object's state so it can be restored to a previous point in time.Encapsulate a family of algorithms or behaviors behind a common contract so they can be selected and swapped cleanly.
Decision factors
ProblemMultiple objects need to coordinate behavior, but direct references between them create tight coupling and complex dependencies.An object's internal state must be saved and restored later without exposing its implementation details.A system needs to switch between interchangeable behaviors without hardcoding branching logic everywhere.
Tradeoffs
  • 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.
  • Snapshots can consume memory if many states are stored.
  • Care must be taken to keep mementos immutable and hidden from outside code.
  • Adds more moving parts than a direct conditional approach
  • Works best when behavior variations are real and likely to grow
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
  • Services
Integration notesMediator is useful for chat systems, form coordination, workflow orchestration, and any domain where many components must collaborate without knowing about each other.Memento is useful for undo/redo, checkpoints, draft recovery, and any workflow where state history matters.Strategies can cross codebases through shared contracts, API selection rules, or runtime configuration.