Just like when developping an API, you build changes in backwards-compatible ways for the most part. If you have to make a backwards-incompatible change, you p

Just like when developping an API, you build changes in backwards-compatible ways for the most part. If you have to make a backwards-incompatible change, you probably need to make your service support two different API versions for a while, and hunt down services that are calling old stuff for a while. This is basically how you can move forward on improvements without coupling "improve this microservice" to "update every single other microservice that is calling to it". Though I believe part of the theory with microservices is that since you are working on such tiny surfaces, most services will never need to roll out a backwards incompatible change