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
structuralAdapterView pattern
structuralFlyweightView pattern
behavioralMementoView pattern
Basics
Categorystructuralstructuralbehavioral
SummaryConvert the interface of a class or module into another interface clients expect.——
IntentAllow incompatible interfaces to work together without changing the consuming code.Use sharing to support large numbers of fine-grained objects efficiently by separating shared intrinsic state from per-object extrinsic state.Capture and externalize an object's state so it can be restored to a previous point in time.
Decision factors
ProblemA client needs to talk to a legacy class or external service whose interface does not match the rest of the codebase.A system creates a large number of similar objects, but storing all of their state separately uses too much memory.An object's internal state must be saved and restored later without exposing its implementation details.
Tradeoffs
  • Adds an extra layer of indirection.
  • Can hide useful vendor-specific capabilities if overused.
  • Keeps integration code isolated from core domain logic.
  • Adds complexity because state must be split into shared and unshared parts
  • Can be harder to understand when many objects depend on an external context
  • Snapshots can consume memory if many states are stored.
  • Care must be taken to keep mementos immutable and hidden from outside code.
Practical fit
Languages
  • typescript
  • java
  • python
  • go
  • csharp
  • dotnet
  • react
  • angular
  • react-native
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
Platforms
  • applications
  • apis
  • service layers
  • integrations
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
Integration notesAdapters are useful when exposing a stable boundary over a legacy API, vendor SDK, or payload format mismatch.Flyweight is useful when thousands or millions of similar objects need to be represented efficiently, such as trees, glyphs, tiles, or UI tokens.Memento is useful for undo/redo, checkpoints, draft recovery, and any workflow where state history matters.