The thing with microservices is that shit doesn't have to infect everything. If someone in another team is clueless, they'll mess up their microservices but not anyone else's. If they are in a monolith, it's 50/50 based on how much clout they have (either they mess it up for everyone, or they get talked down and don't get to mess up their stuff either).
Unless it's a shared library, which is why good microservices architecture limit the shared surface as much as possible.
> it's 50/50 based on how much clout they have (either they mess it up for everyone, or they get talked down and don't get to mess up their stuff either
This still happens with microservices though; people can still make terrible architecture decisions and standup terrible services you depend on.
Unless it's a shared library, which is why good microservices architecture limit the shared surface as much as possible.