Link to Martin Fowler’s definition and the address example I’ll be using: https://martinfowler.com/eaaCatalog/remoteFacade.html
I understand that the intention of the Remote Facade Pattern is to limit the traffic and the amount of calls made over the network, so instead of calling 3 methods separately over the network to set the address, you should make a Remote Facade that includes a single method to set all the data for the address.
The problem is that my teacher has given me the impression that a Remote Facade needs to be made on the client and not the server, but if the server only makes available 3 separate methods for setting all the address data and doesn’t have a single method that combines the job, then I can make a single method on my client that calls all 3 methods on the server, but that won’t result in any less traffic being sent, because 3 methods still have to be invoked over the network.
Is it wrong that the Remote Facade needs to be on the client and not the server or am I missing something?
In case it makes any difference, in terms of client/server I’m thinking about applications that would require a client and a server to communicate over the network like Socket and Web API.
I would really appreciate if you guys could help me out! Thanks in advance!