A Gang of Four structural design pattern that separates an abstraction from its implementation so the two can vary and evolve independently, avoiding a combinatorial explosion of subclasses when both an abstraction and its implementation have several variants.
Facts
Core PrincipleDecouples an abstraction from its implementation so the two can vary independently, splitting a class hierarchy into an abstraction side and an implementation side connected at runtime. 2 Connections
Associated With
Erich Gamma, Pioneers Erich Gamma co-authored the 1994 Design Patterns book that named and catalogued the Bridge pattern among the original 23.
In Field
Sources
1. Wikipedia: Design Patterns (book)
Wikimedia FoundationLead section, first sentenceQuote, Lead section, first sentence
Design Patterns: Elements of Reusable Object-Oriented Software (1994) is a software engineering book describing software design patterns.
View the Source 2. Wikipedia: Bridge Pattern
Wikimedia FoundationLead section, first sentenceQuote, Lead section, first sentence
The bridge pattern is a design pattern used in software engineering that is meant to "decouple an abstraction from its implementation so that the two can vary independently", introduced by the Gang of Four.
View the Source Reader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.