What are different bindings supported by WCF?

WCF includes predefined bindings. They cover most of bindings widely needed in day to day application. But just incase you find that you need to define something custom WCF does not stop you. So let’s try to understand what each binding provides.
BasicHttpBinding: - This binding is used when we need to use SOAP over HTTP. This binding can also be configured to be used as HTTPS. It can be also configured to send data in plain text or in optimized form like MTOM.
WsHttpBinding: It is same like BasicHttpBinding. In short it uses SOAP over HTTP. But with it also supports reliable message transfer, security and transaction. Reliable message is supported by WS-ReliableMessaging, security with WS-Security, and transactions with WS-AtomicTransaction.
NetTcpBinding:- This binding Sends binary-encoded SOAP, including support for reliable message transfer, security, and transactions, directly over TCP. The biggest disadvantage of NetTcpBinding is that both server and client should be also made in .NET language. NetNamedPipesBinding:-Ths binding Sends binary-encoded SOAP over named pipes.
This binding is only usable for WCF-to-WCF communication between processes on the same Windows-based machine.
Note: An interprocess control (IPC) protocol is used for exchanging information between two applications, possibly running on different computers in a network. The difference between Named pipes and TCP is that named pipes have good performance in terms of communication with in processes. But when it comes to communicate across network TCP holds the best choice. So if you are using WCF to communicate with process it’s the best choice to use in terms for performance. Named pipes do not perform when the traffic is heavy as compared to TCPIP.
NetMsmqBinding:- This binding sends binary-encoded SOAP over MSMQ. This binding can only be used for WCF-to-WCF communication.