WCF services on IIS with net.tcp port sharing. Is it good solution according to performance issues?

Question

We are planning to develop a big set of WCF-services with net.tcp binding (about 50 services). They will be hosted on IIS.

As I understand, there are two way to realize it:

1. Create one site on IIS. Services will be deployed as a IIS application. So, all service will use the same port according to net.tcp binding for site (net.tcp port sharing feature).

2. Create 50 sites on IIS, one site for one service. Every site will have different port in net.tcp binding - so, every service will work by using different ports.

What kind of way is better according to performance issues? I couldn't find any information about performance of solutions with net.tcp port sharing.

Answer 1

NetTcpPortSharing is the WCF TCP port sharing service. It implements a centralized TCP listener so that multiple processes can listen on the same TCP port.
For more information you can refer this link. http://msdn.microsoft.com/hi-in/magazine/cc163357(en-us).aspx

Port sharing should not only be only one consideration to deploy your service. You have to design your deployment based on.

1. Application Pool.
2. Crash and recovery.
3. Server Hardware.
4. Nature of services (heavy data transaction)