How to unify the call of the same type in meaning, but different in implementation methods?

Question

OOP

For example, you need to write an aggregator of services for sending SMS messages from a website. Each service has its own api, which implements a certain method a la send (actually send a message). But the name of this method and its signature can change from service to service. And you need to make sure that in those places of the code where business logic (BL) is described using sending messages, a single send method (of type SmsSender::send()) is used. How to correctly implement this, which pattern suits the most?

Answer 1

If you understand the problem correctly, then the adapter will suit you.