How Discord Scaled Elixir to 5M Concurrent Users

Re:How Discord Scaled Elixir to 5M Concurrent Users by pmarreck on Tuesday July 11, 2017 @08:03PM (#14749126)

> while my Java apps take 2 minutes to start up, have several hundred millisecond HTTP response latency and hoard memory

yeah this is pretty much exactly why I turned away from Clojure and Scala and went for Elixir. Also, super ugly Java stacktraces that were not hard to trigger at all. The vast majority of errors in Elixir are wonderfully explanatory.

[ Parent | on HN ]

Re:How Discord Scaled Elixir to 5M Concurrent Users by amorphid on Wednesday July 12, 2017 @01:05AM (#14750231)

A lot of the Erlang-y error messages that bubble up into Elixir can get pretty gnarly. Earlier today I accidentally tried doing `Map.get(key, map)` (map should be first arg) in a `&handle_call/1` callback on a GenServer module, and it got ugly fast. I knew what the problem was from experience, but the Erlang-y error can be intimidating to see for the first time.

[ Parent | on HN ]

Re:How Discord Scaled Elixir to 5M Concurrent Users by yellowapple on Friday July 14, 2017 @11:25AM (#14770505)

Sometimes you have to jump into the source of some dependency (or even OTP itself) to really understand what's causing the error.

Thankfully, Erlang and Elixir tend to make this a lot less painful, in no small part due to their respective declarative/functional programming traits.

[ Parent | on HN ]