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
structuralProxyView pattern
behavioralStateView 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.Provide a surrogate or placeholder for another object to control access to it.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 client needs to interact with an object indirectly because the real object may be expensive, sensitive, or remote.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.
  • Adds another layer of indirection
  • Can make the design more complex when the extra control is unnecessary
  • 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.Proxy is useful for lazy loading, access control, caching, logging, and remote service wrappers.State is useful for workflows, media players, order lifecycles, and any domain where behavior changes as the object moves through a lifecycle.