In Twitter’s early days, only one celebrity could tweet at a time

Re:In Twitter’s early days, only one celebrity could tweet a... by snovv_crash on Friday May 25, 2018 @02:02AM (#17151002)

Before bring acquired, WhatsApp had what, 30 employees?

How did they do it? I know they used custom BSD servers so that a single box could keep close to 1M TCP connections open. I'm sure with a fixed target to aim for and all scope known upfront a small crack team of devs could do something similar for Twitter.

[ Parent | on HN ]

Re:In Twitter’s early days, only one celebrity could tweet a... by zmb_ on Friday May 25, 2018 @03:11AM (#17151315)

One-to-one vs. many-to-many messaging. The amount of work you need to do to deliver a WhatsApp message is constant and small -- just route the message to a single recipient's mailbox. The amount of work Twitter has to do to deliver a message grows as a function of followers. One celebrity tweeting another celebrity means you have to deliver the message to the mailboxes of the followers of both -- millions of times more work than WhatsApp per message. In addition, Twitter persists all the messages while WhatsApp doesn't.

[ Parent | on HN ]

Re:In Twitter’s early days, only one celebrity could tweet a... by segmondy on Friday May 25, 2018 @10:24AM (#17153973)

This! Everyone keep's saying it's BSD Erlang and jumping on the Erlang train. Fine tools btw, but WhatsApp is super simple compared to Twitter. rolls eyes

[ Parent | on HN ]

Re:In Twitter’s early days, only one celebrity could tweet a... by akhilcacharya on Friday May 25, 2018 @02:20AM (#17151084)

The beauty of Erlang/OTP!

[ Parent | on HN ]

Re:In Twitter’s early days, only one celebrity could tweet a... by evanweaver on Friday May 25, 2018 @04:29AM (#17151651)

Especially if you completely rewrite Mnesia.

[ Parent | on HN ]