Bridge is a structural pattern that splits a large class — or a set of closely related classes — into two separate hierarchies: abstraction and implementation. These hierarchies can then evolve independently. Bridge replaces inheritance with composition: instead of inheriting the implementation, the abstraction holds a reference to it.
ℹ️Core idea: decouple an abstraction from its implementation so that the two can vary independently. Use it when you have orthogonal dimensions of variation — e.g. Shape × Renderer, Device × Remote Control.
Content is available with subscription.
Get full access to all courses on the platform for one year with a single payment.
▼
Unlike other platforms that charge per course, here you get everything for one price, and after one year of use there will be no automatic charge for the following year.