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
behavioralIteratorView pattern
behavioralStateView pattern
Basics
Categorystructuralbehavioralbehavioral
SummaryConvert the interface of a class or module into another interface clients expect.——
IntentAllow incompatible interfaces to work together without changing the consuming code.Provide a way to access elements of an aggregate sequentially while hiding the underlying representation.Allow an object to alter its behavior when its internal state changes by delegating state-specific behavior to separate state objects.
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 collection needs to be traversed without exposing how it is stored internally.An object behaves differently depending on its internal state, and conditional logic is becoming hard to manage.
Tradeoffs
  • Adds an extra layer of indirection.
  • Can hide useful vendor-specific capabilities if overused.
  • Keeps integration code isolated from core domain logic.
  • Can add extra classes and abstraction for simple collections
  • May be unnecessary when built-in language iteration is already enough
  • 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
  • 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.Iterator is useful for pagination, custom collections, ordered traversal, and any case where clients should not know the internal data structure.State is useful for workflows, media players, order lifecycles, and any domain where behavior changes as the object moves through a lifecycle.