Twitter, When The Wall Came Down
- Bryan Cantrill tl;dr: "For Twitter, the wall is about to come down: the world is going to change — and it’s not going to change back. I keep wondering about “what is going to replace Twitter”, but I am increasingly of the belief that this is the wrong question, that no single thing is going to replace Twitter. That is, Twitter as an idea — a single social platform catering to all demographics and uses — will become like the evening nightly news or the morning newspaper: a relic from a bygone era."featured in #366
The Container Throttling Problem
- Dan Luu tl;dr: "At Twitter, most CPU bound services start falling over at around 50% reserved container CPU utilization and almost all services start falling over at not much more CPU utilization even though CPU bound services should, theoretically, be able to get higher CPU utilizations." This document describes potential solutions.featured in #278
Processing Billions Of Events In Real Time At Twitter
- Lu Zhang Chukwudiuto Malife tl;dr: "We process approximately 400 billion events in real time and generate petabyte (PB) scale data every day." The authors discuss existing challenges with the current architecture, new architecture, and how they evaluate performance.featured in #275