Thank you very much for your response. I checked them out and, as you 
pointed out, they would work. Nonetheless they are a bit out of my price 
range, so I was wondering if you knew which vendors/systems are usually 
used to run akka clusters.

On Tuesday, September 20, 2016 at 10:20:23 AM UTC-5, Johan Andrén wrote:
> Hi Juan,
> As far as I know (a bit dated knowledge) Heroku does not allow generic TCP 
> communication to the nodes at all, only HTTP on a port that you get from 
> the $PORT environment variable, which will be routed from the public 
> address through Herokus HTTP routing infrastructure, so I'm afraid that if 
> it is still like this it makes it impossible to run Akka Cluster on Heroku.
> There seems to be something nowadays called Private Spaces nowadays which 
> gives you a private virtual network between your nodes. If that really 
> allows connections from any of your nodes to any other on whatever TCP port 
> you like you will be able to run Akka Cluster in such an environment (
> ) 
> --
> Johan
> Akka Team
> On Tuesday, September 20, 2016 at 6:23:12 AM UTC+2, 
> wrote:
>> Hello everyone,
>> Currently, the project I am working on can be divided into a web frontend 
>> that uses Play! framework and several backend nodes that are developed in 
>> Akka. The goal was to set them up on different apps/dynos, so I would be 
>> able to scale the frontend horizontally and vertically, as well as manage 
>> the backend nodes. These backend nodes have no http interface and merely do 
>> the jobs that are sent to them by the frontend and return them. I set up an 
>> akka cluster to communicate between the nodes, and also to set up ssl 
>> between them. Locally, everything worked perfectly, but when I tried to 
>> deploy on Clever Cloud, I found out that the only way they can communicate 
>> is throught HTTP on port 80, and my cluster is communicating through TCP on 
>> port 2551. I tried setting up port 80 on the remoting configuration to 
>> listen on it, but it doesn't seem to work as my app appears to be non 
>> responsive. I started reading up on what could be done, and the only 
>> solution I found was to use RabbitMQ, and, as I understand it, that would 
>> mean that I would have to give up on using akka cluster and rewire the 
>> communications and security protocols, now to be used by this message 
>> broker. I would like to know if anyone has encountered a similar situation 
>> and has found a configuration that works so I can keep using akka cluster, 
>> or if I am missing something.
>> Thanks in advance.

>>>>>>>>>>      Read the docs:
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>>      Search the archives:
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to