Scaling Systems is Easy - Scaling Teams is Hard | Systems Thinking for Architects скачать в хорошем качестве

Scaling Systems is Easy - Scaling Teams is Hard | Systems Thinking for Architects

The Scaling Problem Nobody Talks About in Architecture Most discussions about scalability focus on infrastructure: more servers, more containers, more services. But in large systems, infrastructure is rarely the real bottleneck. The real constraint is how long it takes teams to agree on a change. In this video we examine why large systems slow down as organizations grow — even when the technology can scale easily. Because once systems reach a certain size, architecture stops being about machines and starts being about coordination. In this video we explore • Why scaling machines is easy • Why scaling teams is hard • How coordination complexity grows in engineering organizations • Why decision latency becomes the real bottleneck • How Conway’s Law shapes system architecture • Why microservices often appear in large organizations • The trade-off between technical simplicity and organizational scalability • Why architecture ultimately becomes a coordination structure Many architectural debates — monolith vs microservices, platform teams, domain boundaries — only make sense once you understand one thing: Architecture evolves to scale decision making. This is Systems Thinking for Architects.