Skip to main content

Difference between Web API, WCF and Web Service

So now we have got the basic idea about Web API, now let’s do some comparison of Web API with WCF and web services.

Web Service
WCF
Web API
Web services are created as files with .asmx extension.
WCF create with .svc extension
Web API are simple class file with .cs(for C#) extension. Web API is inherited from “ApiController” and the class name must end with “Controller”.
It is SOAP based service and returns data in XML form.
It is also based on SOAP and returns data in XML form.
Web API is HTTP based service and by default, it returns data in JSON or XML form.
It supports only HTTP protocol.
It supports various protocols like TCP, HTTP, HTTPS, Named Pipes, and MSMQ.
It supports HTTP protocol.
It can be hosted only on IIS.
It can be hosted within the application or on IIS or using window service.
It can be hosted within the application or on IIS.
It is not open source but can be consumed by any client that understands XML.
It is not open source but can be consumed by any client that understands XML.
It is open source and can be consumed by any client that understands JSON or XML.
It requires SOAP protocol to receive and send data over the network, so it is not a  lightweight architecture
WCF supports various protocols and different types of binding due to which it is known as heavyweight architecture.
It is lightweight architecture and good for devices that have limited bandwidth like mobiles.
It can’t be used to create REST-ful services
We can create REST-ful services with WCF by enabling webHttpBindings, but service configuration is difficult.
Web API is an ideal platform for building REST-ful services, and its service configuration is very easy compared to WCF service.
It supports data transfer in XML format.
It supports XML, JSON, and ATOM data formats.
It supports XML and JSON data formats. Responses can be formatted by Web API’s MediaTypeFormatter into JSON, XML, or whatever format you want.
It doesn’t support MVC features
It doesn’t support MVC features
It also supports the MVC features such as routing, controllers, action results, filter, model binders, IOC container or dependency injection, and unit testing that makes it more simple and robust.
Labels:

Comments

Post a Comment

Popular posts from this blog

Error 405 : ASP.NET Core Web API PUT and DELETE Methods not allowed

Recently, while working with .Net core API I came across the issue of “Error 405 — Methods not Allowed” After some research, I found out that both GET and POST requests working fine but neither PUT nor DELETE requests working. Another thing is that the PUT and DELETE request was also working fine on my local machine but failed when we host on our Azure server. When I explored the issue on the web it led me to the conclusion that WebDAVModule seems to set PUT and DELETE request methods disabled by default and due to that PUT and DELETE throw 405 errors. To make the PUT and DELETE requests work, we need to override the WebDAVModule setting in web.config file by adding the below settings under “ system.webServer ”. < system.webServer >   < modules runAllManagedModulesForAllRequests = " false " >     < remove name = " WebDAVModule " />   </ modules > </ system.webServer > There may be 2 web.config files in y...
Post a Comment
Read more

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI . Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress). //Created new Workbook var hwb = new NPOI.HSSF.UserModel. HSSFWorkbook (); //Create worksheet with name. var sheet = hwb.CreateSheet( "new sheet" ); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue( "This is Merged cell" ); cell.CellStyle.WrapText = true ; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util. CellRangeAddress (0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra); Hope this solution helps you J
4 comments
Read more

How to set Swagger as the default start page for API hosted on the Azure web app?

I created an Asp.Net Core 2.x Web API and configured Swagger on it, below is the code added in Configure method under Startup.cs file, for full swagger configuration, check here //Add swagger configuration app.UseSwagger(); app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" ); }); On my local machine when I run the API it is automatically redirected to the Swagger page. However, when I hosted this API as an Azure web app it is not redirecting directly to the Swagger and to access the swagger, I had to append /swagger in the URL, for example, https://testapi.azurewebsites.net/swagger/ Solution: Set RoutePrefix to string.Empty under app.UseSwaggerUI like below: app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" );      c.RoutePrefix = string .Empty; // Set Swagger UI at apps root }); And that’s it, now when you b...
Post a Comment
Read more