- HTTP - REST
- Named Pipes
- Message Queues
WCF requires data to be communicated and communication methods are defined at compile time, but the communication protocols, addresses, authentication methods, methods of serialization, encryption method and other details of the communication can be defined in time execution. The configuration of these items can be done without writing code, because for most of the more popular enough to just change an entry in the configuration file.
Some protocols have been implemented in WCF for interoperability with other languages and development platforms, and can be consumed by clients implemented in.. NET WCF also allows you to expose metadata about the service, facilitating the consumption of these.
Services using WCF in IIS or can run normal applications, whether the command line, graphical applications or Windows services. WCF can be used in various settings, allowing quick and efficient implementation of:
- communication between processes on the same machine (eg. named pipes)
- web APIs
- comunicação desconectada (ex: message queue, envie e esqueça)
- bi-directional communication (eg signature and publication)
The WCF was also implemented in the Mono framework, but only partially.
Translated automatically from my original post in Portuguese.