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
behavioralMementoView pattern
behavioralStateView pattern
behavioralVisitorView pattern
Basics
Categorybehavioralbehavioralbehavioral
Summary———
IntentCapture and externalize an object's state so it can be restored to a previous point in time.Allow an object to alter its behavior when its internal state changes by delegating state-specific behavior to separate state objects.Separate an algorithm from the object structure it operates on by moving behavior into visitor objects.
Decision factors
ProblemAn object's internal state must be saved and restored later without exposing its implementation details.An object behaves differently depending on its internal state, and conditional logic is becoming hard to manage.You need to perform operations across a set of different object types without stuffing all the logic into the objects themselves.
Tradeoffs
  • Snapshots can consume memory if many states are stored.
  • Care must be taken to keep mementos immutable and hidden from outside code.
  • Can introduce many small classes if the state graph is large
  • State transitions may become harder to trace if spread across multiple classes
  • Requires updating the visitor interface when new element types are added
  • Can be awkward if the object structure changes often
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 notesMemento is useful for undo/redo, checkpoints, draft recovery, and any workflow where state history matters.State is useful for workflows, media players, order lifecycles, and any domain where behavior changes as the object moves through a lifecycle.Visitor is useful for AST processing, reporting, cart calculations, and exporting object structures to alternate formats.