19 ms·
That's true, but I can't help but feel like it was an extremely low bar to hurdle. If "35.6 million tweets during the Brazil/Germany final" is to be believed, t
by saosebastiao 11y ago
That's true, but I can't help but feel like it was an extremely low bar to hurdle. If "35.6 million tweets during the Brazil/Germany final" is to be believed, that is only 5k tweets per second on average...maybe 50k peak due to heterogeneous volume during a sporting event. Call me uninformed if that's what it is, but that seems like something that should be easily handled by any decently architected system on the JVM. I couldn't even count the number of shit systems at Amazon that process that kind of volume with less than 4 9's of availability.
- aaronbrethorst 11y agohttp://highscalability.com/blog/2013/7/8/the-architecture-twitter-uses-to-deal-with-150m-active-users.html http://highscalability.com/blog/2013/7/8/the-architecture-tw...
- saosebastiao 11y agoFacebook is getting 43x the QPS of twitter, and they are doing it on MySQL. http://highscalability.com/blog/2010/11/4/facebook-at-13-million-queries-per-second-recommends-minimiz.html http://highscalability.com/blog/2010/11/4/facebook-at-13-mil...
- random3 11y agoYou're quoting a post which is 5 years old and comparing it with one that's two years old.