It should -- microservices require testing versioned interactions between services. Let's say you're changing the behaviour of a feature in service A that is c

It should -- microservices require testing versioned interactions between services. Let's say you're changing the behaviour of a feature in service A that is consumed by service B. Service A is at version 15, service B is at version 42. You have to deploy service A version, but it has to have the new change but still also be compatible with service B v42 (because that's what's running). Then, when service B v43 is deployed, service A has to start serving the new functionality. This gets exponentially more complicated with more services, more dependencies and more versions.