The bridge pattern is a design pattern used in software engineering which is meant to "decouple an abstraction from its implementation so that the two can vary independently". The bridge uses encapsulation, aggregation, and can use inheritance to separate responsibilities into different classes.
When a class varies often, the features of object-oriented programming become very useful because changes to a program's code can be made easily with minimal prior knowledge about the program. The bridge pattern is useful when both the class as well as what it does vary often. The class itself can be thought of as the implementation and what the class can do as the abstraction. The bridge pattern can also be thought of as two layers of abstraction.
The bridge pattern is often confused with the adapter pattern. In fact, the bridge pattern is often implemented using the class "adapter pattern", e.g. in the Java code below.
Variant: The implementation can be decoupled even more by deferring the presence of the implementation to the point where the abstraction is utilized.
Read more about Bridge Pattern: Structure
Famous quotes containing the words bridge and/or pattern:
“I was at work that morning. Someone came riding like mad
Over the bridge and up the road—Farmer Rouf’s little lad.
Bareback he rode; he had no hat; he hardly stopped to say,
“Morgan’s men are coming, Frau, they’re galloping on this way.”
—Constance Fenimore Woolson (1840–1894)
“For what is wedlock forcèd, but a hell,
An age of discord and continual strife?
Whereas the contrary bringeth bliss,
And is a pattern of celestial peace.”
—William Shakespeare (1564–1616)