Hi Antonio; thanks for the response. The point about tradeoffs, and finding the best solution based on our context, is a good one. I'll admit that I find myself pushing for certain "ideal" architectural patterns (e.g. here, keeping teams and their services decoupled) but those patterns need to tempered with our org's reality. In other words, there might be a valid reason why a given organization needs to keep some of its teams/systems coupled (and deal with the resulting downsides). In fact, speaking of my next article… I was thinking that one of my next ones will cover the necessity of tradeoffs. 🙂