Analysis

Compare patterns

Evaluate design patterns side by side across intent, tradeoffs, languages, and integration fit.

Choose patterns

Select up to 3 patterns

Current selection

3 of 3 selected

You can now review the differences across the comparison table below.

Analysis

Pattern comparison

Reviewing 3 patterns.

Criteria
behavioralMediatorView pattern
structuralProxyView pattern
creationalSingletonView pattern
Basics
Categorybehavioralstructuralcreational
Summary———
IntentDefine 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.Ensure a class has only one instance and provide a global access point to it.
Decision factors
ProblemMultiple 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.A system needs exactly one shared instance of a class, and that instance must be globally accessible without allowing uncontrolled duplication.
Tradeoffs
  • 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
  • Can make dependencies harder to test if the singleton is used everywhere
  • May introduce hidden global state that complicates debugging and concurrency
Practical fit
Languages
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
  • typescript
  • java
  • python
  • angular
  • react
  • react-native
  • csharp
  • dotnet
Platforms
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
  • Web
  • Backend
  • Mobile
  • UI kits
  • Cross-platform systems
Integration notesMediator 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.Singleton is useful for centralized services like configuration, logging, caching, and shared application state.