5 ms·
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
by sandwichinvest 5y ago
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.
- mattbaker 5y agoI’m always curious to learn about things that make people cautious to run the BEAM in production. What makes it scary for you?
- dnautics 5y agoNHS and Boston MBTA both run BEAM in production, and arguably lives are at stake there (mostly indirectly but still) ...
- sandwichinvest 5y agoPure fear of the unknown, combined with fear of getting less-than-stellar tracebacks & profiling because Elixir's only one of the VM languages.
- mattbaker 5y agoMakes 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!
- hmmokidk 5y agoYou 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.