Skip to content

The Bridge Pattern

software development, coding, pluralsight, design patterns1 min read

bridge pattern

The Bridge Pattern is useful in a system where both implementation and abstraction are likely to change (and thus, should be encapsulated).

Head First Design Patterns by Eric Freeman and Elisabeth Freeman provides a quick overview of the Bridge Pattern in its appendix.

Pluralsight's Design Patterns Library course has a module on the Bridge Pattern from John Sonmez.

The Bridge Pattern's goal is to decouple an implementation and an interface such that abstraction and implementation can be altered independently.


In the Bridge Pattern, two class hierarchies are created, one for the abstraction and one for the implementation.

An instance of the abstraction composes an instance of the implementation; thus, the abstraction and implementation can be varied independently.

Within the abstraction, methods in the base class are implemented in terms of the implementation, while subclasses are implemented in terms of the abstraction.

Common Uses

The Bridge Pattern is commonly used in user interfaces, as well as in systems related to object persistence.

Thanks for reading! I hope you find this and other articles here at ilyanaDev helpful! Be sure to follow me on Twitter @ilyanaDev.