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
structuralFacadeView pattern
behavioralMediatorView pattern
Basics
Categorystructuralstructuralbehavioral
SummarySeparate an abstraction from its implementation so the two can vary independently.Provide a simplified high-level interface that coordinates a complex subsystem behind a smaller and easier-to-use API.—
IntentDecouple abstractions from implementations so they can evolve independently.Provide a simplified high-level interface that coordinates a complex subsystem behind a smaller and easier-to-use API.Define an object that encapsulates communication between a set of objects, keeping them from referring to each other directly.
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.A client needs to perform a recurring workflow that spans several subsystem classes, but direct coordination makes the code noisy and tightly coupled.Multiple objects need to coordinate behavior, but direct references between them create tight coupling and complex dependencies.
Tradeoffs
  • Adds an extra layer of indirection.
  • Can increase the number of moving parts.
  • Makes abstractions and implementations easier to evolve independently.
  • Can become a dumping ground if boundaries are unclear.
  • May obscure useful lower-level capabilities from advanced consumers.
  • Simplifies the most common entry points for the system.
  • 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.
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
  • applications
  • apis
  • service layers
  • 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.Facades are useful when exposing a stable boundary over a multi-service or mixed-language backend, or when presenting a consistent UI entry point over multiple readiness checks.Mediator is useful for chat systems, form coordination, workflow orchestration, and any domain where many components must collaborate without knowing about each other.