Facade (Repository) Pattern Explained Simply: What It Is, When To Use It | iOS, Android, Web

This video was cut from a weekly LIVE Q&A session (I do one most Sundays). Hit the notification bell and/or follow my social media for updates on how/when you can join future Q&A sessions.

Topics:
- Defining/Explaining what the Facade/Repository Pattern is in OOP
- How this idea can carry over to Functional Style Code
- What does the word "Client" mean in computing
- When do I suggest you use the Facade/Repository Pattern (I give a very specific example to make it clear!)

Question: What is the difference between the Repository/Facade Pattern?
Answer: Essentially nothing; they are fundamentally the same pattern in the most general sense of the word pattern, as applied to software design. Some people prefer to say that the Repository is specific to Data Input/Output (network adapters, remote servers, databases) but where as the Facade applies to every situation in which the pattern described in the video is used. I don't really think that is a useful distinction, but I do think the word Facade, with is a French word roughly meaning "Front", is of limited usage to those who are not French speakers or who do not know about building architecture where the term is frequently used.

[ShubhamSinghMusic]

Can't find your social media links in your description Ryan

Can anyone help with this? (I'd like his Instagram link if possible please?)