Browser docs
- Aggregator Microservices
- API Gateway
- Client Session Pattern
- CQRS
- Data Access Object
- Data Bus
- Data Mapper
- Data Transfer Object
- Domain Model
- Event Driven Architecture
- Event Sourcing
- Hexagonal Architecture
- Layers
- Metadata Mapping
- Model-View-Controller
- Model-View-Intent
- Model-View-Presenter
- Model-View-ViewModel
- Naked Objects
- Repository
- Serialized Entity Pattern
- Service Layer
- Service Locator
- Service to Worker
- Unit Of Work
- Acyclic Visitor
- Bytecode
- Caching
- Chain of responsibility
- Circuit Breaker
- Command
- Component
- Data Locality
- Dirty Flag
- Double Buffer
- Extension objects
- Feature Toggle
- Game Loop
- Identity Map
- Intercepting Filter
- Interpreter
- Iterator
- Leader Election
- Mediator
- Memento
- Null Object
- Observer
- Parameter Object
- Partial Response
- Pipeline
- Poison Pill
- Presentation Model
- Priority Queue Pattern
- Retry
- Servant
- Sharding
- Spatial Partition
- Special Case
- Specification
- State
- Strategy
- Subclass Sandbox
- Template method
- Throttling
- Trampoline
- Transaction Script
- Type-Object
- Update Method
- Visitor
Double Dispatch
On this page
Intent
Double Dispatch pattern is a way to create maintainable dynamic behavior based on receiver and parameter types.
Class diagram
Applicability
Use the Double Dispatch pattern when
- the dynamic behavior is not defined only based on receiving object’s type but also on the receiving method’s parameter type.