Sounds like good engineering choices. I think of Twitter as having unlimited res... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		joshuaellinger on July 9, 2013 \| parent \| context \| favorite \| on: The Architecture Twitter Uses to Deal with 150M Ac... Sounds like good engineering choices. I think of Twitter as having unlimited resources but, of course, that can't be true. Two follow-on questions: 1. Did your changes make it back into open source or were they only relevant to Twitter? When you say upstream to you mean on Redis or earlier in the Twitter pipeline? 2. How much is Redis on the critical path? Is it 90% of the processing work in the large fanout cases?

bitbckt on July 9, 2013 [–]

1. Yes, most everything we changed is in the open source Redis code base. That's what I'm referring to as upstream, above.

2. Redis is in the critical path for a majority of API requests. I can't provide a specific percentage.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact