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
structuralBridgeView pattern
structuralFlyweightView pattern
Basics
Categorystructuralstructuralstructural
SummaryConvert the interface of a class or module into another interface clients expect.Separate an abstraction from its implementation so the two can vary independently.—
IntentAllow incompatible interfaces to work together without changing the consuming code.Decouple abstractions from implementations so they can evolve independently.Use sharing to support large numbers of fine-grained objects efficiently by separating shared intrinsic state from per-object extrinsic state.
Decision factors
ProblemA client needs to talk to a legacy class or external service whose interface does not match the rest of the codebase.When an abstraction is tightly coupled to its implementation, changing one side forces changes in the other and makes the system harder to evolve.A system creates a large number of similar objects, but storing all of their state separately uses too much memory.
Tradeoffs
  • Adds an extra layer of indirection.
  • Can hide useful vendor-specific capabilities if overused.
  • Keeps integration code isolated from core domain logic.
  • Adds an extra layer of indirection.
  • Can increase the number of moving parts.
  • Makes abstractions and implementations easier to evolve independently.
  • 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
Practical fit
Languages
  • typescript
  • java
  • python
  • go
  • csharp
  • dotnet
  • react
  • angular
  • react-native
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • go
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
Platforms
  • applications
  • apis
  • service layers
  • integrations
  • web
  • backend
  • mobile
  • integration
  • ui
  • 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.Bridge is useful when you want one stable abstraction while swapping implementations for providers, environments, or device targets.Flyweight is useful when thousands or millions of similar objects need to be represented efficiently, such as trees, glyphs, tiles, or UI tokens.