This is an example I've taken from what I've seen in various microservice-based projects.

The example is around an operation touching on multiple services and them having a veto on said operation's execution. The only reliable solution here is to centralise the state/behaviour we rely on for the validation, which often means vioaliting the loose coupling principle. This is a general problem I see on a daily basis in practice.

I'm not looking to manufacture a problem at all, which is why I took the very first example of a microservice layout I could find.