|
|
|
|
|
by tomkin
3133 days ago
|
|
Twitter's biggest mistake was hiring thousands of people when they only needed 30. It doesn't need thousands of people. It doesn't even need 100. Twitter is not a technological marvel. It's something Oprah promoted, and Donald Trump bitches on. And now, it's an API with a (social) class-based access, and without irony, also promotes itself as a leader in conversation and exchange. |
|
You'll need 30 engineers just to build and maintain the datastores, caching mechanisms, and service deployment infrastructure. You then have the actual services, real time streaming platforms, streaming applications, batch infra (hadoop), analytics pipelines, notifications, security, anti-spam, recommendation/machine learning pipelines, ads infrastructure etc to name a few. Can't find it now, but there should be a circa 2011 architecture of twitter in one of the blogs somewhere. I recommend you have a look at it.
If you're comparing it with WhatsApp, note that WhatsApp messages are mostly 1->1 and it's easier to shard the servers by recipient. Also, not having to bother persisting all the messages forever simplifies the system by a lot.
[1] https://blog.twitter.com/engineering/en_us/a/2013/new-tweets...