Скачать или смотреть Bridge - Design Pattern in PHP | OOP Design Patterns | What and How to use it?

0:04 - Welcome all youtubers who watching this episode. My name Andrii and representing the channel MLA Automation. Who is first time hit please hit on Subscribe button, and Like button. On this channel you will be able to find awesome topics in programming. Currently we are learning PHP and today's episode related to serious of video about Design Patterns in PHP. ..
This time on our consideration in this lesson - Bridge

1:14 - Analogy
Let's say you have a site with multiple pages. You want to allow users to change the theme of your pages. What would you do? Did you create multiple copies of each page for each theme, or did you just make separate themes and load them according to user preferences? The Bridge pattern allows for the second approach.

1:53 - Short to say:
The Bridge pattern is a preference for layout over inheritance. Implementation details are passed from one hierarchy to another object with a separate hierarchy.

2:08 - Wikipedia
The Bridge pattern means decoupling the abstraction from the implementation so that both can be changed independently of each other.

2:26 - Example
Let's implement the above example with web pages. Let's make a WebPage hierarchy:

Link on the Code for Example(above):
https://gist.github.com/magamlag/0b7d...

What the difference between Adapter and Bridge patterns ?
08:46 - The Adapter and Bridge patterns have some common attributes. Both promote flexibility by providing a level of indirection to another object. Both involve forwarding requests to this object from an interface other than its own.

09:04 - The key difference between these patterns lies in their intents. Adapter focuses on resolving incompatibilities between two existing interfaces. It doesn't focus on how those interfaces are implemented, nor does it consider how they might evolve independently. It's a way of making two independently designed classes work together without reimplementing one or the other. Bridge, on the other hand, bridges an abstraction and its (potentially numerous) implementations. It provides a stable interface to clients even as it lets you vary the classes that implement it. It also accommodates new implementations as the system evolves.

As a result of these differences, Adapter and Bridge are often used at different points in the software lifecycle. An adapter often becomes necessary when you discover that two incompatible classes should work together, generally to avoid replicating code. The coupling is unforeseen. In contrast, the user of a bridge understands up-front that an abstraction must have several implementations, and both may evolve independently. The Adapter pattern makes things work after they're designed; Bridge makes them work before they are. That doesn't mean Adapter is somehow inferior to Bridge; each pattern merely addresses a different problem.


11:07 - When to use:
Use the Bridge pattern when you want to divide and organize a monolithic class that has several variants of some functionality (for example, if the class can work with various database servers)

11:18 - Greatful everyone who watch to very end of this video.

Reference on Resource
https://refactoring.guru/design-patterns
https://habr.com/ru/company/vk/blog/3...

SUBSCRIBE TO CHANNEL:
   / @mlaautomation6888  

Facebook - https://www.facebook.com/profile.php?...
Twitter -   / kachalov2010  

Don't forget pls to click on 'Like', its giving additional motivation to work on channel.
Thank you for watching, for subscription and see you soon.

#mlaautomation #bridge #designpatterns #tutorial #guide #interview #questions #answers #devleoper #programmer #oopphp #php