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
structuralBridgeView pattern
behavioralMediatorView pattern
structuralProxyView pattern
Basics
Categorystructuralbehavioralstructural
SummarySeparate an abstraction from its implementation so the two can vary independently.——
IntentDecouple abstractions from implementations so they can evolve independently.Define an object that encapsulates communication between a set of objects, keeping them from referring to each other directly.Provide a surrogate or placeholder for another object to control access to it.
Decision factors
ProblemWhen an abstraction is tightly coupled to its implementation, changing one side forces changes in the other and makes the system harder to evolve.Multiple objects need to coordinate behavior, but direct references between them create tight coupling and complex dependencies.A client needs to interact with an object indirectly because the real object may be expensive, sensitive, or remote.
Tradeoffs
  • Adds an extra layer of indirection.
  • Can increase the number of moving parts.
  • Makes abstractions and implementations easier to evolve independently.
  • The mediator can become large and complex if it takes on too much coordination logic.
  • Centralizing behavior can make the mediator a single point of failure if it is poorly designed.
  • Adds another layer of indirection
  • Can make the design more complex when the extra control is unnecessary
Practical fit
Languages
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • go
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
Platforms
  • web
  • backend
  • mobile
  • integration
  • ui
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
Integration notesBridge is useful when you want one stable abstraction while swapping implementations for providers, environments, or device targets.Mediator is useful for chat systems, form coordination, workflow orchestration, and any domain where many components must collaborate without knowing about each other.Proxy is useful for lazy loading, access control, caching, logging, and remote service wrappers.