Skip to content



The Peer Transport is based on the WCF NetPeerTcp binding and uses a custom resolver hosted by Neuron ESB. Peer is a server-less, networking technology which provides a low latency and highly scalable Transport option for large networks/geographies. One of the advantages of Peer is that it can route between subnets. However, Peer also generates more network traffic than the other transports.

When using Peer, all Neuron ESB Parties are interconnected by a Peer mesh, which is self-regulating and self-optimizing. The Mesh that Parties connect to is based off of the top level Topic. Hence all traffic for a particular Topic and its sub topics flow across the same Mesh. The Peer Transport’s greatest strength is its high parallelism.

Peer does not provide delivery assurances; messages can be lost, and messages may arrive out of order.

The Peer Transport is a particularly good choice for multicasting applications where there are few publishers and many subscribers. Peer is also a reasonable choice any time the desired quality of service is low-latency, volatile messaging.

Note:  You cannot use Peer Transport configured Topics with IIS-hosted applications such as ASP.NET sites or SharePoint Server.

Using the Peer Transport has the following system requirements:

  • No additional requirements

Transactional considerations:

  • Peer Transport does not support transactions

Firewall considerations:

  • Ports must be open for the Client Port Range configured in the Peer Transport Property Page
  • The Peer Transport communicates with a custom resolver service hosted by the Neuron ESB service. The custom resolver service’s port is specified in the Peer Resolver Service property, located on the Ports tab of the Zone’s Detail Pane. This can be found by selecting Deployment ->Divisions->Zones from the navigation bar located on the left hand side of the Neuron ESB Explorer. Select the Ports tab for the specific Zone. The default port is 50005.
Peer Transport Property Table
Property NameRequiredDescription
Cleanup Interval (Seconds)                   YesDefault is 300.  This is the interval in which stale Party records will be removed from the custom resolver lookup table.
Client Base PortYesDefaults to 50100. This is the beginning port for the port range that the Parties use to communicate with the Peer network protocol.
Client Port RangeYesDefaults to 1000. This is the range of client ports, starting from the Client Base Port, that can are assigned to connected Parties. Each Party is assigned one client port dynamically by checking to see if the port is free.
Refresh Interval (Seconds)YesDefault is 120.  This is the number of seconds in which a connected Party will re-register itself with the custom resolver service
Was this article helpful?
Dislike 0
Next: TCP