Facade Pattern – Design Patterns (ep 9)

Video series on Design Patterns for Object Oriented Languages. This time we look at the Facade Pattern.

💙 BUY MY BOOK:

► The playlist

► Head First: Design Patterns

► Design Patterns: Elements of Reusable Object-Oriented Software

💪 Patreon Community

📚 Products I Recommend

[dimasahachko]

Listen dude, I am from Ukraine and, you know, the thing what you are doing here is really great. I mean I have looked through all russian speaking youtube and your course is really the best ad it's not even close. I'm so grateful to you. You are a wonderful teacher and you really can explain difficult things in easy to understand fashion. Thanks a lot for this. Wish you all the best. Move on man

[atoledo]

The facade lets the clients interact with the madness!
"there's not some order to this madness, it's just madness!" 🤪
Loved it

[mikhailbisserov]

Facade seems to be even simpler in my view. All those classes having complex relations is pretty irrelevant to the Facade pattern. The only thing important is that those classes are multiple and the client has to deal with all of them. So the Facade class combines interfaces of all needed classes into one interface. I.e. Client calls Facade.StartEngine, Facade.StopEngine, Facade.TurnLeft, Facade.TurnRight, and Facade class calls Engine.Start, Engine.Stop, Wheel.Left, Wheel.Right. It's useful for example in WCF services, when you have to expose many controllers' methods to an external client.

[skullwise]

This all you need from this video
7:21 to 8:52
15:00 to 15:45 :-)

[attilanyiri]

You are a great teacher Christoper, and I love how you share your inner thoughts on the topic aswell!

[SalahLFC]

I would like to add my example here. You are adding a new feature to your application and this involves C# developer, UI designer, Databade developer, Mobile App developer, QA and IT teams (all of them are classes). Top executives (client class) don't want to come and ask every team about what we are adding and who will do what, instead they will go to Project Manager (facade) and PM will be responsible to communicate to required teams.

[bhargav]

You classes are awesome. The way I see and write programs has changed completely after your design patterns videos in good way. Thank you sir

[arastusharma]

Loved it!! This man energy is unmatchable !!

[wegvS]

Your videos are the best about design patterns! Thank you for your work.

[CryptoJitsu]

The CLIENT explanation at 1:15 would have saved me years of confusion had I heard it ten years ago....so important

[ab]

Your energy gave me 5 extra years of life, so thanks!

[johnconnor]

You are a real ninja in explaining complicated stuff very easily. Thumb up!

[jonwood]

Thank you so much for all your help! Please keep making tutorials!

[HrishiKesav]

14:26 Forthlly....finally
Dude you are awesome. Understanding design patterns has never been easier for me. Goodwork and Thanks.

[tomaszgiba]

Great videos you have. Give pats to the cat.

[piyushtiwari]

First of all, great videos Christopher !! It would have been great to see a code example of Facade Pattern which I think you missed in the video.

[carlocentofanti]

I'm interested on the Law of Demeter video :) Thank you so much for this amazing series!! I love your videos and i hope you will continue as long as you can, I'm learning so many things from you. Oh i forgot one more thing... Thank you again! :)

[shbjqzj]

Thank you so much sir. No words to describe these videos how much it helped to understand the design pattern. Now i could feel that i will definitely learn all design patterns. May god bless you.

[NoKsMG]

Love your videos Cristopher, never lose that motivation and passion! :-)

[msohan]

Wonderful! Facade design pattern, simplified. Keep up the good work.