Elixir: Practical Concurrency Cookbook

Re:Elixir: Practical Concurrency Cookbook by sandwichinvest on Sunday July 25, 2021 @04:24PM (#27952606)

Having reliable scheduling in the language itself seems like it would simplify a ton of software that's currently reliant on a lot of message queueing and cron duct tape. Running BEAM in production still scares me, but that's one reason to conquer the fear.

[ Parent | on HN ]

Re:Elixir: Practical Concurrency Cookbook by mattbaker on Sunday July 25, 2021 @04:42PM (#27952755)

I’m always curious to learn about things that make people cautious to run the BEAM in production. What makes it scary for you?

[ Parent | on HN ]

Re:Elixir: Practical Concurrency Cookbook by sandwichinvest on Monday July 26, 2021 @01:37PM (#27962409)

Pure fear of the unknown, combined with fear of getting less-than-stellar tracebacks & profiling because Elixir's only one of the VM languages.

[ Parent | on HN ]

Re:Elixir: Practical Concurrency Cookbook by mattbaker on Monday August 02, 2021 @10:48PM (#28045217)

Makes sense. For what it’s worth we’ve been really happy with traces, no issues there, and there are definitely profiling tools. Plus you can point Erlang’s Observer tool at a production BEAM node, it’s wildly useful!

[ Parent | on HN ]

Re:Elixir: Practical Concurrency Cookbook by dnautics on Sunday July 25, 2021 @10:18PM (#27954852)

NHS and Boston MBTA both run BEAM in production, and arguably lives are at stake there (mostly indirectly but still) ...

[ Parent | on HN ]

Re:Elixir: Practical Concurrency Cookbook by hmmokidk on Sunday July 25, 2021 @06:16PM (#27953439)

You may have done it already through RabbitMQ.

Also I want to comment that it is awesome and I love it. It’s simple and effective. OTP being bundled into the language is really very brilliant.

[ Parent | on HN ]