What is the relationship between WCF, Rest and SOAP?

Solution 1:

WCF is a messaging framework for building distributed systems. Distributed systems is mostly just another word for web services.

What this means is that you can write methods in C# (or any of the .NET languages) and then apply a bunch of configurations to the code that make your code accessible to others and turn your code into a web service.

Those "bunch of configurations" are WCF. WCF allows you to expose your methods to other computers or applications using REST if you set up the WCF configurations around your C# code to expose it as a RESTful service. Or, you can easily take the same C# methods and make them available via the SOAP protocol.

If you have a method called "GetData()", you can set up the WCF configuration to make that method available in a service that is hosted in IIS. When someone calls that service, they can send an HTTP GET request to http://www.yourdomain.com/SomeService/GetData, and the GetData method will receive the message and send back a response. When you make a GET request over HTTP, you're using the REST. REST is pretty much tied to HTTP as the transport protocol. REST also has no standard message format. Whatever you want to send in your HTTP message, and however you want to send it is OK. You can send XML, or JSON, or just plain text. You can use POST, or GET or PUT or any of the HTTP verbs as well.

With SOAP, your messages can be sent to the service using any transport protocol -- you aren't tied to HTTP. SOAP messages are designed to be transport neutral. They are encoded in XML and the XML always has a head and a body node inside of an envelope node. There are lots of web standards around SOAP -- standards for putting security, sessions and other features into the header of the message, for example. Also, with SOAP, you get a WSDL, which I won't go into explaining here, but it makes it a LOT easier for clients to program against. Most programming languages have a method of taking a WSDL and converting it into strongly-typed methods and objects so that your service is easy to call.

REST is very popular on the internet and is as scalable as the internet (i.e. VERY scalable). SOAP is very popular in business-to-business applications.

Solution 2:

WCF isn't automatically REST or SOAP, but you can make it that way. What you need here is a tutorial:

WCF

http://www.codeproject.com/Articles/406096/A-beginners-tutorial-for-understanding-Windows

REST

http://rest.elkstein.org/

Here's some other interesting stuff:

WCF - REST / SOAP

https://msdn.microsoft.com/en-us/library/hh323708(v=vs.100).aspx

WCF and REST

https://msdn.microsoft.com/en-us/library/ee391967.aspx

Or you can do a google/bing/metacrawler/altavista search on your own.....

Solution 3:

From MSDN

The WCF programming model provides various capabilities, such as SOAP services, web HTTP services, data services, rich internet application (RIA) services, and workflow services. SOAP services support interoperability between systems that are built with Java, other platforms, and those that use messaging standards that are supported by Microsoft®. SOAP services also support transports such as HTTP, TCP, named pipes, and MSMQ. Web HTTP services and data services both support REST. Web HTTP services enable you to control the service location, request and response, formats, and protocols. Data services enable you to expose data models, and data-driven logic as services. WCF also includes two programming models: The service model and the channel model. The service model provides a framework for defining data contracts, service contracts and service behaviors. The channel model supports specifying formats, transports, and protocols.

Both SOAP and REST services can provide functionality to web applications, and both can be used to exchange information in the web's distributed environment. Each one has its own advantages, and limitations.