We talked about change requests within the realm of a single microservice. But what if we need to deploy a feature that works within two or more microservices?
These kinds of features should be relatively rare and are one of the main causes of overhead in microservices compared with the monolith approach. In a monolith, this case is simply not possible as everything is contained within the walls of the monolith.
In a microservice architecture, meanwhile, this is a complex change. This involves at least two independent features on each involved microservice that resides in two different repos. It is likely that the repos will be developed by two different teams, or at least different people will be responsible for each of the features.
