Bridge Pattern

This article discusses the bridge pattern. A somewhat complicated design that allows the developer to separate the interface from the implementation and allow the two to vary independently.

If I were to describe the purpose of a particular design pattern as to make one interface work with another, incompatible interface, hopefully you’d recognize it as the Adapter Pattern[1]. Certainly at its core that is what the Bridge Pattern does, however the Bridge Pattern is much more advanced than just making two interfaces work together. Its goal is the separation of the implementation and abstraction layers so that the two layers are able to vary independently.