zlacker

[parent] [thread] 4 comments
1. snovv_+(OP)[view] [source] 2018-05-25 06:02:57
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.

replies(2): >>akhilc+k1 >>zmb_+35
◧
2. akhilc+k1[view] [source] 2018-05-25 06:20:37
>>snovv_+(OP)
The beauty of Erlang/OTP!
replies(1): >>evanwe+ta
◧
3. zmb_+35[view] [source] 2018-05-25 07:11:47
>>snovv_+(OP)
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.
replies(1): >>segmon+VL
◧◩
4. evanwe+ta[view] [source] [discussion] 2018-05-25 08:29:45
>>akhilc+k1
Especially if you completely rewrite Mnesia.
◧◩
5. segmon+VL[view] [source] [discussion] 2018-05-25 14:24:02
>>zmb_+35
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
[go to top]