3 ms·
All those things you listed require additional background servers, redis, etc. In Elixir/Erlang, it's built into the runtime which is a huge advantage. And even
by cpursley 4y ago
All those things you listed require additional background servers, redis, etc. In Elixir/Erlang, it's built into the runtime which is a huge advantage. And even with standard things like handling http requests in Elixir -absolutely smokes Ruby in terms of performance. This leads to real cost savings as well
- silasb 4y agoThose built-ins that you are talking about are not as well rounded as a dedicated framework. These built-ins operate at a different operating model than running additional background servers. This typically means that everyone in the org needs to be an Elixir/Erlang expert instead of having experts in Redis, cloud native, ... For better or worse, this is likely a large obstacle for many orgs. The argument for using Elixir/Erlang is also more difficult when you have large companies like Github and Shopify demonstrating that Ruby can scale. EDIT: Let's not forget that it's mostly the DB that slows CRUD apps down. Not the language or the framework.
- grncdr 4y agoNo, they don't. You can absolutely run ActionCable with the postgres adapter in your main rails app server and require no additional services. Edit: this is also why I mentioned GoodJob, it supports the full ActiveJob API (delays, retries, etc), even comes with a nice Web UI, and it only requires Postgres.
- cpursley 4y agoI'm using Quantum as my job runner in Elixir. Doesn't require even Postgres. Can't do that in Rails or other stacks: https://github.com/quantum-elixir/quantum-core https://github.com/quantum-elixir/quantum-core ^ obviously it won't fit every use case (where you need 100% durability) but for that there's Oban which is awesome: https://getoban.pro https://getoban.pro