The Bridge pattern is a structural design pattern that decouples an abstraction from its implementation by introducing two independent inheritance (or type) hierarchies connected through a dependency at the abstract level, allowing each hierarchy to be extended with new variants without modifying the other. Formally, one hierarchy consists of an abstraction with refined-abstraction subclasses, and the other consists of an implementation with concrete-implementation subclasses, with the coupling occurring between the abstract members of each hierarchy rather than between concrete members. This belongs to the domain of object-oriented software design, specifically the "structural" category of the Gang of Four design patterns, and it relates to broader principles of decoupling, dependency inversion, and type-based abstraction (including alternative realizations via protocols, first-class functions, or abstract base classes rather than strict class inheritance).
The Bridge pattern is a structural design pattern that decouples an abstraction from its implementation by introducing two independent inheritance (or type) hierarchies connected through a dependency…