We use BERT (which is maybe outdated), but it works very well to talk between Ruby and Elixir.
It’s fast, simple to implement and there are packages for Ruby, Python, Java and other languages.
It’s a pity that it’s quite neglected now. 
railsmechanic
2
sashaafm
No one seems to have mentioned Erlang Ports or the Interfaces.
I’ve used Erlang Ports to interface with Ruby in the past and it was quite easy and successful. Erlang Ports and Port Drivers. There are also a couple of libs which making using Ports easier, like erlport.
For C you may use Erl_interface and for Java there’s JInterface. I’ve used the Java one before and I thought it was pretty good. There’s a complete Erlang ↔ Java mapping of types, and Java nodes will be seen by the BEAM like if they were Erlang nodes.
1
NobbZ
We have a N individual web applications which do not need to be on the same host and want to do communication between them. I do not think that ports are suitable for this-
1
hubertlepicki
OvermindDL1
Yeah 90% of the time I do a Port using the normal Erlang Term Format (there are libraries for it in about every language, and it is almost trivial to write your own as I’ve done a few times), 5% of the time I make another language into a Node, and the other 5% I’ve made a NIF.
But really, just using a Port with the normal erlang term format is so wonderful and easy to use while being nicely compact.
If however they are web applications and already have, say, JSON communication points, just use the existing ones, if you need to make something new I’d use either JSON or the erlang term format (if a library exists there for it, which it does for Ruby as I recall).
1
thx