Bridge Design Pattern (An Introduction for .NET Developers [.NET 5 and C#])

Подписаться 27 тыс.

Просмотров 3 тыс.

50% 1

In this video, I am going to walk through the Bridge Design Pattern. It is an Introduction video for .NET Developers [.NET 5 and C#].
The bridge pattern is a structural design pattern. The main intent of the pattern is to decouple an abstraction from its implementation so that they can vary independently.
The previous two videos in this Design Pattern series are:
1. Factory method design pattern: • Factory Method Design ...
2. Abstract factory design pattern: • Abstract Factory Desig...
3. Builder design pattern: • Builder Design Pattern...
4. Prototype design pattern: • Prototype Design Patte...
5. Adapter design pattern: • Adapter Design Pattern...
00:12 - Definition of Bridge pattern
00:45 - Explanation of the problem domain where bridge pattern will apply
03: 30 - Running the application to show response without bridge pattern
04:10 - Explanation of the problem with the implementation without bridge pattern
05:15 - Rework the code to implement bridge pattern
10:20 - Run the application using the bridge pattern

Наука

Опубликовано:

21 авг 2021

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 14

@iambiswajitsahoo Год назад

We cannot change an existing abstract class into an interface, although the interface now supports method implementation but that's another topic. Here the problem remains the same, by adding any methods to the INotificationProcessor you are bound to implement them in the implementation classes which is opposite of what bridge pattern is.

@thaingohoang5188 2 года назад

Thanks you so much !!!!!

@DotNetCoreCentral 2 года назад

@Thái Ngô Hoàng, thanks for watching!

@ashutoshsingh5568 2 года назад

Helps a lot to understand design patterns. Thanks

@DotNetCoreCentral 2 года назад

@Ashutosh Singh, thanks for watching!

@williamliu8985 2 года назад

Wonderful demonstration! It is true. I have only heard of the bridge design pattern before, but I have never understood it in depth. But compared to the model (kind of SOLID) I am using now, I do rely on this bridge design pattern. Amazing!

@DotNetCoreCentral 2 года назад

@William Liu, thanks for watching!

@microtechie4834 2 года назад

Great effort thanks

@DotNetCoreCentral 2 года назад

@Micro techie, thanks!

@Dodev 2 года назад

If I wanted to use email and text together, is the play to make separate interfaces for text / email? For example ITextNotificationProcessor etc.

@DotNetCoreCentral 2 года назад

@Dodev, yes, and in that case, you are more in the SOLID world.

@yogafromhome9327 2 года назад

Thank you for such good examples. I saw both decorator and bridge pattern videos from your channel. Here I'm little bit confused, probably. please help me to understand better. If we just don't concentrate on the names of the classes or interfaces. Then in this example, TextNotificationProcessor looks like decorator class(It resembles to cakedecrator class in decorator pattern video). Are both the bridge and decorator are somewhat same? Or Are both the patterns trying to solve the same problem?