4 ms·
I think what was cool with WhatsApp was just how few engineers was necessary to scale well. I would guess Signal has enough money to throw around that having Ja
by danielscrubs 6y ago
I think what was cool with WhatsApp was just how few engineers was necessary to scale well. I would guess Signal has enough money to throw around that having Java is a better deal, making the buss factor bigger and such.
- wahern 6y ago> I think what was cool with WhatsApp was just how few engineers was necessary to scale well. Probably because they started out using ejabberd, a very mature and widely deployed XMPP implementation.
- abernard1 6y agoThis is an odd take to me. It is common for a JVM app on a single box to process >100K messages a second with an eventing system. It is not as common, but relatively normal, to process >1M per node. With the cost of hardware, a company is usually "throwing around" money on maintainability of a much less supported runtime. Engineering time of something like JVM vs Erlang is much more substantial of a cost.
- danielscrubs 6y agoSignal just sent a Twitter message that Signal is back after technical difficulties. So maintainability might be up for discussion...
- Chyzwar 6y agoI worked once in a system that was sending messages to via message queue to Java based service. We once send 60k messages and a Java based system failed to process these over the whole night. Java have a high ceiling for writing high performance systems but in practice it is easy to make a massive ball of mug that performs extremely poorly. In many cases it is easier to write fast erlang/elxir/node application.