News for hackers. Stuff that matters.
Re:The Architecture Twitter Uses to Deal with 150M Active Users by papsosouid on Monday July 08, 2013 @04:42PM (#6009154)
>Having more CPU [cores], RAM, and IO is not going to solve for the need to shard your Redis, which is bound by a single core

But they chose redis in the first place as part of their messy, crummy pile of barely working junkware solution. You wouldn't use redis in the first place if you were building a solution that scales up.

Re:The Architecture Twitter Uses to Deal with 150M Active Users by thezilch on Monday July 08, 2013 @07:31PM (#6010104)
So, now we also have to assume per-core software and support licenses to accompany our purchase of several $10M racks? What platform are we talking about now? Presumably I have to also purchase the IDE and toolchain licenses, per developer, too?

Twitter may have and will still make missteps, but you're being egregiously vague and unhelpful. Your comments are as vaporous as you make Twitter's architecture to be.

Re:The Architecture Twitter Uses to Deal with 150M Active Users by rozap on Monday July 08, 2013 @06:56PM (#6009929)
You're funny. I like you.