The .Net framework has a number of technologies that allow you to create HTTP services such as Web Service, WCF and now Web API. There are a lot of articles over the internet which may describe to whom you should use. Now a days, you have a lot of choices to build HTTP services on .NET framework. In this article, I would like to share my opinion with you over Web Service, WCF and now Web API.
1) It is based on SOAP and return data in XML form.
2) It support only HTTP protocol.
3) It is not open source but can be consumed by any client that understands xml.
4) It can be hosted only on IIS.
1) It is also based on SOAP and return data in XML form.
2) It is the evolution of the web service(ASMX) and support various protocols like TCP, HTTP, HTTPS, Named Pipes, MSMQ.
3) The main issue with WCF is, its tedious and extensive configuration.
4) It is not open source but can be consumed by any client that understands xml.
5) It can be hosted with in the applicaion or on IIS or using window service.
1) To use WCF as WCF Rest service you have to enable webHttpBindings.
2) It support HTTP GET and POST verbs by [WebGet] and [WebInvoke] attributes respectively.
3) To enable other HTTP verbs you have to do some configuration in IIS to accept request of that particular verb on .svc files
4) Passing data through parameters using a WebGet needs configuration. The UriTemplate must be specified
5) It support XML, JSON and ATOM data format.
1) This is the new framework for building HTTP services with easy and simple way.
2) Web API is open source an ideal platform for building REST-ful services over the .NET Framework.
3) Unlike WCF Rest service, it use the full featues of HTTP (like URIs, request/response headers, caching, versioning, various content formats)
4) It also supports the MVC features such as routing, controllers, action results, filter, model binders, IOC container or dependency injection, unit testing that makes it more simple and robust.
5) It can be hosted with in the application or on IIS.
6) It is light weight architecture and good for devices which have limited bandwidth like smart phones.
7) Responses are formatted by Web API’s MediaTypeFormatter into JSON, XML or whatever format you want to add as a MediaTypeFormatter.
To whom choose between WCF or WEB API:
1) Choose WCF when you want to create a service that should support special scenarios such as one way messaging, message queues, duplex communication etc.
2) Choose WCF when you want to create a service that can use fast transport channels when available, such as TCP, Named Pipes, or maybe even UDP (in WCF 4.5), and you also want to support HTTP when all other transport channels are unavailable.
3) Choose Web API when you want to create a resource-oriented services over HTTP that can use the full features of HTTP (like URIs, request/response headers, caching, versioning, various content formats).
4) Choose Web API when you want to expose your service to a broad range of clients including browsers, mobiles, iphone and tablets.