A manifestation of the Normalized Systems design principle Separation of Concerns, is the use of a messaging or integration bus to integrate the use of various messaging protocols. The theorem clearly forbids the direct transformation between two external protocols and therefore technologies and consequently tasks. The obvious solution is to use an internal reference format or open standard protocol. 
For example, consider an integration project with N different messaging or protocol formats. Using direct transformations would require the creation of N(N-1)/2 connectors, while the selection of an internal reference format limits the number of transformations to N. The introduction of an additional protocol format would imply the need for N additional connectors in the case of direct transformations, while it requires only 1 or a single additional connector in the case of an integration bus.

This clearly illustrates the concept of stability. In the first case, the amount of additional coding work for the introduction of a new protocol increases in time with the overall size of the system. Although the required change remains the same, the necessary coding changes do not, and are even unbounded. In the second case, the required amount of coding changes remains constant in time for an identical change. The amount of coding effort is bounded, and therefore the integration bus pattern is stable with respect tot the introduction of an additional protocol.
ESB_versus_POINT_2_POINT.gif
ESB_versus_POINT_2_POINT.gif: Original uploader was Arkramer at nl.wikipedia
derivative work: Kriskras (talk)