Per that last paragraph, it's really the opposite. Microservices exist precisely to allow engineers — at least those in a sizeable organization — to be able to learn and retain knowledge of how *their* system works, end-to-end. They allow teams to focus on *their* particular domain, rather than needing to understand every other domain across the organization. I'm not saying that it just happens by magic with microservices; it requires intentional design, and it's not always easy to get right. But a company can grow to the size where it's unfeasible or impossible for any one person to understand its monolith; hence, microservices.