This week, I’m following up last week’s discussion on distributed system by sharing some advice on how to build them well. There are some key themes — reduce connections between components, prevent cascading errors, and buffer the components from each other.
From the internet this week, Alex Komoroske on schelling points in organizations, on unlearning from a decade of programming, and Evan Bottcher on platforms.
If you like reading about architecture, teams, and software in general, sign up for the next edition! You can check out the previous editions in the archive.
Scalability, scale-up, systems thinking, and collaboration
The 55th episode of “It Depends”, my weekly newsletter on software engineering is out. This one is a doozy, even if I say so myself. Don’t miss it.
This week I have put together a comprehensive look into scalability. I explain what it means, why we sometimes don’t have it, and what can we do to make scalable systems.
From the internet this week, @Sander_Mak on scale up at Picnic, a comprehensive review of literature on systems thinking in engineering, and @jessitron on why we need better software, not better coordination.
If you like reading about software engineering and teams that build software systems, sign up for the next edition and bring your friends! You can check out the previous editions in the archive.