Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
1–10 of 13 posts
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#2The published erlectrcity gem does not support maps, as they were only introduced into the language in 2013.
I forked it a while back to add support for maps. I'd recommend you use the fork: https://github.com/hamiltop/erlectricity
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#3I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#4I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?
Probably allows updating/extending old Rails apps using Elixir, without having to rewrite the old app.
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#5I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?
The main use case would be if you had a very mature Ruby library without an Erlang/Elixir equivalent. I haven't run into much that I personally need that isn't already available, but there are definitely some gaps that this could help people jump in the short term.
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#6I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?
Probably allows updating/extending old Rails apps using Elixir, without having to rewrite the old app.
Terraform is a good option there as well.
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#7We have a couple legacy Rails Elixir apps being slow-ported forward (low hanging fruit first). The real winner so far for us has been Exq [1], which is a Sidekiq-compatible job library.
What that means is you can selectively receive jobs in Elixir (e.g. high-perf Phoenix websocket/request handler) and process them in legacy Ruby Sidekiq workers when needed, or vice-versa use Elixir to process jobs whose functions you've ported forward.
If your Rails app is already setup use Sidekiq background jobs, I think this method is much-preferable to these direct communication libraries.
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#8I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?
The main use case would be if you had a very mature Ruby library without an Erlang/Elixir equivalent. I haven't run into much that I personally need that isn't already available, but there are definitely some gaps that this could help people jump in the short term.
Agreed. Currently working with a host of legacy ruby projects that we're slowly migrating to elixir. We've used hack-arounds to leverage the existing ruby projects up until now. If this library proves to be production-worthy, it'll be a great bridge for addressing some technical debt.
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#9Wow. It's crazy to think erlectricity is still kicking. That was one of my first open source projects, although to be fair mojombo has basically replaced everything I wrote with far better code over the years.
Re: Communicate Between Ruby and Elixir Using Erlang Ports and Erlectricity
#10I understand why the Ruby community has warmed up to Elixir and the Phoenix web-framework, however, I'm curious what the advantage or use-case of having Ruby talk to Elixir in an application is?
The main use case would be if you had a very mature Ruby library without an Erlang/Elixir equivalent. I haven't run into much that I personally need that isn't already available, but there are definitely some gaps that this could help people jump in the short term.
I work at an ISP with some gems that you just cannot find anywhere, in any language. We cannot just replace or rewrite them, some have been around for almost 10 years.