> Presumably your API says what types of data the caller should expect. As long as you don't change that, they should be able to deal with the response changing

> Presumably your API says what types of data the caller should expect. As long as you don't change that, they should be able to deal with the response changing. The point I wanted to get across was that although a client won't break, I'd still want to talk to those pulling data from the system. I was disagreeing with the statement "you can make as many changes to your service as you want without any coordination." > But really it's more about the fact that if you have a single monolith, if you want to make a change, you have to coordinate with everyone at the company, whereas if you have microservices, you only have to coordinate with those who are affected by the change. Yes, it does lower the hurdles to getting something out.