<p>Has anyone ever used the <a href="https://www.dofactory.com/net/bridge-design-pattern" rel="nofollow noreferrer">Bridge pattern</a> in a real world application? If so, how did you use it? Is it me, or is it just the <a href="https://www.dofactory.com/net/adapter-design-pattern" rel="nofollow noreferrer">Adapter pattern</a> with a little dependency injection thrown into the mix? Does it really deserve its own pattern?</p>

A classic example of the Bridge pattern is used in the definition of shapes in an UI environment (see the
Bridge pattern Wikipedia entry
).  The Bridge pattern is a
composite
of the
Template
and
Strategy
patterns.
It is a common view some aspects of the Adapter pattern in the Bridge pattern.  However, to quote from
this article
:
At first sight, the Bridge pattern looks a lot like the Adapter pattern in that a class is used to convert one kind of interface to another. However, the intent of the Adapter pattern is to make one or more classes' interfaces look the same as that of a particular class. The Bridge pattern is designed to separate a class's interface from its implementation so you can vary or replace the implementation without changing the client code.