When using wrappers or adapters to extend legacy components and interfaces, what can we do to avoid building an all$-$to$-$all solution, where all the components have a wrapper for all the other components?

Question $1$ options:

We can use application layering to separate the interface, the processing and the data of the application.

We can use a message broker that knows how to transform all of the messages or calls to the proper interface.

We can use a simple client$-$server architecture.

We can use a publish$-$subscribe architecture in order to notify the components when an application changed.