WCF 、Web API 、 WCF REST 和 Web Service 的区别-白红宇

WCF 、Web API 、 WCF REST 和 Web Service 的区别

阅读量：5033 次

发布时间：2019-06-12

本文共 4773 字，大约阅读时间需要 15 分钟。

　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. For more information about Web API refers .

Web Service

It is based on SOAP and return data in XML form.

It support only HTTP protocol.

It is not open source but can be consumed by any client that understands xml.

It can be hosted only on IIS.

WCF

It is also based on SOAP and return data in XML form.

It is the evolution of the web service(ASMX) and support various protocols like TCP, HTTP, HTTPS, Named Pipes, MSMQ.

The main issue with WCF is, its tedious and extensive configuration.

It is not open source but can be consumed by any client that understands xml.

It can be hosted with in the applicaion or on IIS or using window service.

WCF Rest

To use WCF as WCF you have to enable webHttpBindings.

It support HTTP GET and POST verbs by [WebGet] and [WebInvoke] attributes respectively.

To enable other HTTP verbs you have to do some configuration in IIS to accept request of that particular verb on .svc files

Passing data through parameters using a WebGet needs configuration. The UriTemplate must be specified

It support XML, JSON and ATOM data format.

Web API

This is the new framework for building HTTP services with easy and simple way.

Web API is open source an ideal platform for building REST-ful services over the .NET Framework.

Unlike WCF Rest service, it use the full featues of HTTP (like URIs, request/response headers, caching, versioning, various content formats)

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.

It can be hosted with in the application or on IIS.

It is light weight architecture and good for devices which have limited bandwidth like smart phones.

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

Choose WCF when you want to create a service that should support special scenarios such as one way messaging, message queues, duplex communication etc.

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.

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

Choose Web API when you want to expose your service to a broad range of clients including browsers, mobiles, iphone and tablets.
http://www.dotnet-tricks.com/Tutorial/webapi/JI2X050413-Difference-between-WCF-and-Web-API-and-WCF-REST-and-Web-Service.html

WCF：基于RPC(远程过程调用(Remote Procedure Call) )机制

Web API:一个基于HTTP的ASP.NET

WebService:基于Web的服务

在开发实践中如何进行选择？

可以参照知名互联网企业，无论是google，facebook,baidu,新浪还是腾讯。他们对外开放的接口都是基于Http的Web API，在服务内部框架都是基于SOA架构设计的，通讯机制都是采用RPC机制的，例如Google Protocol Buffers ，Facebook thift。我们完全也可以这样搭配，在内部通讯采用WCF + Protobuf-NET，参看《》，对外的服务采用ASP.NET WEB API。WCF的 TCP、Named Pipes，甚至UDP（在WCF 4.5中）绑定的性能要比HTTP强很多倍，这里有一个几年前的微软的测试报告《》，对外提供的服务采用Web API同时也是一个业界标准问题，用WebAPI就很容易的跨越ios，android，wp等移动终端平台，同时有很成熟的OAuth 解决安全问题。

当你遇到以下这些情况的时候，就可以考虑使用Web API了。