Providing Rest Clients Nearly as Bad as Publishing SOAP Contracts

Even still, many developers and architects have continued to emotionally cling to the SOAP bad old days, wherein the contracts between a server and a client are to be well-defined and strictly-enforced. Semantically-versioned contracts is a common pattern, where the contracts themselves are held in a separate package, and compiled for consumption by consumers. Another is the published “ServiceClient” which exposes all methods and contracts for the consuming clientA to call serviceB. Both are architecturally troubling, because once more these contracts or clients are nothing more than another form of tight-coupling.

Once again, nobody moves unless everybody does, just not in as rigid a format as SOAP provided.

from: https://medium.com/it-dead-inside/isolating-your-microservices-through-loose-coupling-48b710e28de6