Thumb rules in choosing endpoint' binding

• If you require your service to be consumed by clients compatible with SOAP 1.1, use basicHttpBinding for interoperability
  
• If you require your service to be consumed within the corporate network, use netTCPBinding for performance
  
• If you require your service to be consumed over the internet and the client is a WCF compatible, use wsHttpBinding to reap full benefits of WS* specifications
  
• If you require your service to be accessible only in the same machine, use netNamedPipeBinding
  
• If you require your service to be queue messages, use netMsmqBinding
  
• If you require your service to act as server as well as client in a peer to peer environment, utilise netPeerTcpBinding setting

Binding	Security Default Configurable	Transport Protocol	Encoding Default Other	Host
basicHttpBinding	None, Transport, Message, Mixed	HTTP	Text/XML, MTOM	IIS, WAS
wsHttpBinding	Message, Transport, Mixed	HTTP	Text/XML, MTOM	IIS, WAS
netTcpBinding	Transport, Message, Mixed	TCP	Binary	WAS
netNamedPipeBinding	Transport,None	Named Pipe	Binary	WAS
netMsmqBinding	Message, Transport, None	TCP	Binary	WAS
netPeerTcpBinding	Transport	P2P	Binary	-