Many thanks for the links. I'll definitely review them. I suppose the synchronisation of consumer and service compatibility is the biggest concern. So far, ev

Many thanks for the links. I'll definitely review them. I suppose the synchronisation of consumer and service compatibility is the biggest concern. So far, everybody is focusing solely on backwards compatibility, but not future compatibility, which is what the contracts are for. With regards to the backwards compatibility - breaking changes happen! As long as the service remains functional, and remains compatible with its consumer contracts (which can also change) I shouldn't need to worry about deprecating APIs. Anyone keeping deprecated functionality around in an environment where they control the both the services and the consumers is simply asking for problems. I can't see how it can be possible to not control the composition of microservices. Surely thats exactly what my CI pipeline is doing? Composing a network of compatible services?