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
behavioralMementoView pattern
creationalPrototypeView pattern
behavioralStrategyView pattern
Basics
Categorybehavioralcreationalbehavioral
Summary———
IntentCapture and externalize an object's state so it can be restored to a previous point in time.Specify the kinds of objects to create using a prototypical instance, and create new objects by cloning that prototype.Encapsulate a family of algorithms or behaviors behind a common contract so they can be selected and swapped cleanly.
Decision factors
ProblemAn object's internal state must be saved and restored later without exposing its implementation details.Creating new objects from scratch can be expensive or repetitive when the system needs many similar variants.A system needs to switch between interchangeable behaviors without hardcoding branching logic everywhere.
Tradeoffs
  • Snapshots can consume memory if many states are stored.
  • Care must be taken to keep mementos immutable and hidden from outside code.
  • Can be difficult if the object graph contains deep references that need custom clone behavior
  • May require careful handling of mutable state to avoid shared-reference bugs
  • 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 notesMemento is useful for undo/redo, checkpoints, draft recovery, and any workflow where state history matters.Prototype is useful when object creation is expensive, when many near-identical objects are needed, or when cloning preconfigured templates is simpler than rebuilding them.Strategies can cross codebases through shared contracts, API selection rules, or runtime configuration.