Choosing Direct or Reverse Connection

There are two modes two use when connecting to another FrameWorX server, direct and reverse connections. Direct connections are most common.

In a direct connection, the FrameWorX that wants to read the data will initiate the connection, as in a typical server-client relationship. In a reverse connection, the FrameWorX that is providing the data will initiate the connection, opening a tunnel for the communication to occur.

Consider these points when deciding whether to use a direct or reverse connection:

• If your target server (the one you are connecting to) is behind a NAT or a firewall:
  • If you can create an inbound rule to allow FrameWorX communication, use a direct connection. See Creating a Direct Connection
  • If you cannot create an inbound rule, use a reverse connection. See Creating a Reverse Connection
• In any other case, use a direct connection. See Creating a Direct Connection

A typical use case for a reverse connection is when you have one GENESIS server running in the cloud and one on premise. The cloud server's FrameWorX needs to subscribe to data from the on-premise FrameWorX. Since the on-premise FrameWorX is hidden behind a NAT, we are unable to connect the on-premise FrameWorX server using direct connection. So, reverse connection must be used.