Different WCF Bindings, their differences and compatibility with other platforms

Question

I am looking for some good technical details on Topic of WCF bindings, I am interested to know following things.

1. List of Different WCF Bindings with its specia

Answer 1

To add to the accepted answer, if you want to bind your JSON request to an object in WCF, use webHttpBinding

Here's an example on this.

Answer 2

Choosing the right WCF binding

1. BasicHttpBinding: Basic web service communication. Exposes WCF services as legacy ASMX web services. Used for interoperability. No security by default.
2. WSHttpBinding: Web services with WS-* support. Supports transactions and reliable messaging.
3. WSDualHttpBinding: Web services with duplex contract and transaction support.
4. WSFederationHttpBinding: Web services with federated security. Supports transactions.
5. MsmqIntegrationBinding: Communication directly with MSMQ applications. Supports transactions.
6. NetMsmqBinding: Communication between WCF applications by using queuing. Supports transactions.
7. NetNamedPipeBinding: Communication between WCF applications on same computer. Supports duplex contracts and transactions.
8. NetPeerTcpBinding: Communication between computers across peer-to-peer services. Supports duplex contracts.
9. NetTcpBinding: Communication between WCF applications across computers. Supports duplex contracts and transactions.

Answer 3

• If you are required to create a binding that is globally inter-operable, use http binding.

• For internal use, but consumers are in separate servers use tcp binding. It less inter-operable, but using binary encoding which is faster.

• Use named pipe binding for intra-server communication, that is for consumers hosted in same servers. Named pipe binding is the fastest one in wcf allowed bindings.

Use bindings appropriately, make your project best.