> The idea is that if the other area of code simply isn't accessible to you, you're forced to keep the concerns separate? Seems like this could be dealt with by

> The idea is that if the other area of code simply isn't accessible to you, you're forced to keep the concerns separate? Seems like this could be dealt with by applying more discipline and just making sure to design things to be more modular and.. separate. This is the hallmark of any good code base. Do we need an entirely different architecture, with all the pitfalls that microservices entail, because we can't seem to keep things clean and separate? Yes, because code is written by humans, and humans make mistakes. "Just have discipline and write good code" doesn't scale, especially in, as Uber's case, quickly growing organizations where large numbers of people new to the codebase are contributing.