riak_core nodes on Heroku?

Samuel Elliott sam at lenary.co.uk
Mon Jun 18 07:33:53 EDT 2012

Thinking further on this problem, Heroku provides an add-on system
that could be helpful.

If we could build a suitable distribution system that we can host
remotely to heroku, but that would work (and perhaps not even rely on
IP addresses, instead relying on app/dyno ids), then I think we might
be able to solve this. Assuming we could deploy it to ec2, then the
latency wouldn't be *so* awful, and most other problems could be

That said, I don't know how happy erlang would be with us configuring
its distribution via environment variables, and whether we could build
something so that people can test distribution locally.

I will start taking a look at the possibility of doing this, but don't
hold your breath.


On Sun, Jun 17, 2012 at 12:47 PM, Ciprian Dorin Craciun
<ciprian.craciun at gmail.com> wrote:
>> Yes, distribution via other means seems sensible.
>    As Sam said, you could however solve these issues by:
>    * providing your own implementation of an `erl_epmd` solver;
>    * and your own implementation of an `inet_tcp_dist`;
>    * both using as communication an HTTP module (like `mochiweb` or
> `misultin`) multiplexing between the two;
>    But this road is very hard... If interested you could read one of
> my posts to the Erlang list exactly about this topic, but which
> remained unanswered...
>      http://erlang.org/pipermail/erlang-questions/2011-October/062004.html
>    (One ideea: use ZeroMQ for communication, but again all this goes
> if the previous assertion is true.)

Samuel Elliott
sam at lenary.co.uk
+44 (0)7891 993 664

More information about the riak-users mailing list