I'm going to answer the opposite! You can bind the application by checking the environment variable VCAP_SERVICES, this will be information about the associated Rabbit instance.
When you deploy an application instance, it runs on a virtual machine (called DEA). The application instance is assigned a port in the virtual machine. Inside, all DEAs can "see" each other, so there is no reason why an application should not talk on a private IP address in another application running on another DEA.
Obviously, you don’t know which private IP address or even the port of the application will work until it is pressed, so I would advise you that each application “register” its address through Rabbit after clicking it, so that other applications can find him.
source
share