zlacker

[parent] [thread] 2 comments
1. vvande+(OP)[view] [source] 2018-05-25 00:53:34
WhatsApp was a pretty well known case for Erlang[1], given that I'd think Phoenix would be a great fit.

[1] https://www.wired.com/2015/09/whatsapp-serves-900-million-us...

replies(2): >>segmon+C >>dasil0+Wc
◧
2. segmon+C[view] [source] 2018-05-25 01:04:47
>>vvande+(OP)
Erlang won't have helped twitter. Erlang has a very simple architecture, once they sent you a message and know it has reached your device, they no longer care about it. Twitter has to keep all the tweets, likes, retweets, show it all followers in real time. 100x more demanding than WhatsApp simple deliver and forget.
◧
3. dasil0+Wc[view] [source] 2018-05-25 04:25:45
>>vvande+(OP)
Phoenix will be much better than Rails out of the box for things that need a certain level of concurrency. However Twitter's problems were about scaling dependent writes, this is a data-store / architecture problem that really has nothing to do with the chosen language.
[go to top]