Difference Between Web Services, WCF and WEB API

-

Web Service

1.      It is based on SOAP and returns data in XML form.
2.      It supports 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.

WCF

1.      It is also based on SOAP and return data in XML form.
2.   It is the evolution of the web service(ASMX) and supports 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 within the application or on IIS or using window service.

WCF Rest

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 the  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.

Web API

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 service 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.

Thank You


I wish you liked this, I'll come with some other exciting parts of MVC operations soon until then enjoy coding and if you encounter any problem then feel free to ping me.


Comments

Post a Comment

Popular posts from this blog

ASP.Net MVC: ViewData, ViewBag and TempData with examples

-
In this section, I will explain the purpose of ViewData, ViewBag, and TempData with examples. ViewData 1. ViewData is derived from the ViewDataDictionary class and is basically a Dictionary object i.e. Keys and Values where Keys are String while Values will be objects. 2. Data is stored as Object in ViewData. 3. While retrieving, the data it needs to be Type Cast to its original type as the data is stored as objects and it also requires NULL checks while retrieving. 4. ViewData is used for passing value from Controller to View. 5. ViewData is available only for Current Request. It will be destroyed on redirection. Syntax:- C# Code: public class Parent1Controller : Controller { public ActionResult Index() { ViewData[ "Message" ] = "Welcome to Dotnet Builders Tutorials" ; return View(); } } .CSHTML CODE: < html > < head >     < meta name ="viewport" co
Read more

Send Mail with Attachment using MVC

-
Image
Introduction: In this section,  I am going to explain how to send mail with attachment using MVC. Here I created  View to get data like receiver mail and attached file. By using SMTP server it will generate mail with attachment. Model: using   System ; using   System.Collections.Generic ; using   System.Linq ; using   System.Web ; namespace  WebApplication2 . Models {      public   class  MailDetailsMod      {          public   string  MailTo  {  get ;  set ;   }          public  HttpPostedFileBase MailAttachment  {  get ;  set ;   }              } } View: @model WebApplication2.Models. MailDetailsMod @{     ViewBag.Title = "Send Mail With Attachment using MVC" ; } < center >     < h2 > Send Mail with Attachment </ h2 >     @ using (Html.BeginForm( "SendMail" , "Mail" , FormMethod .Post, new { enctype = "multipart/form-data" }))     {         < tabl
Read more