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

　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 What is Web API and why to use it ?.

Web Service

  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.

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

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





    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，参看《WCF服务上应用protobuf》，对外的服务采用ASP.NET WEB API。WCF的 TCP、Named Pipes，甚至UDP（在WCF 4.5中）绑定的性能要比HTTP强很多倍，这里有一个几年前的微软的测试报告《WCF 性能基准报告》，对外提供的服务采用Web API同时也是一个业界标准问题，用WebAPI就很容易的跨越ios，android，wp等移动终端平台，同时有很成熟的OAuth 解决安全问题。

 

 

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

  • 需要Web Service但是不需要SOAP
  • 需要在已有的WCF服务基础上建立non-soap-based http服务
  • 只想发布一些简单的Http服务，不想使用相对复杂的WCF配置
  • 发布的服务可能会被带宽受限的设备访问
  • 希望使用开源框架，关键时候可以自己调试或者自定义一下框架

 

 

 

Web API的主要功能

1. 支持基于Http verb (GET, POST, PUT, DELETE)的CRUD (create, retrieve, update, delete)操作

    通过不同的http动作表达不同的含义，这样就不需要暴露多个API来支持这些基本操作。

2. 请求的回复通过Http Status Code表达不同含义，并且客户端可以通过Accept header来与服务器协商格式，例如你希望服务器返回JSON格式还是XML格式。

3. 请求的回复格式支持 JSON，XML，并且可以扩展添加其他格式。

4. 原生支持OData。

5. 支持Self-host或者IIS host。

6. 支持大多数MVC功能，例如Routing/Controller/Action Result/Filter/Model Builder/IOC Container/Dependency Injection。

 

 

     WebAPI  vs  MVC

  • MVC主要用来构建网站，既关心数据也关心页面展示，而Web API只关注数据
  • Web API支持格式协商，客户端可以通过Accept header通知服务器期望的格式
  • Web API支持Self Host，MVC目前不支持
  • Web API通过不同的http verb表达不同的动作(CRUD)，MVC则通过Action名字表达动作
  • Web API内建于ASP.NET System.Web.Http命名空间下，MVC位于System.Web.Mvc命名空间下，因此model binding/filter/routing等功能有所不同
  • 最后，Web API非常适合构建移动客户端服务

 

 

    

发布服务在Web API和WCF之间该如何取舍呢？这里提供些简单地判断规则，

  • 如果服务需要支持One Way Messaging/Message Queue/Duplex Communication，选择WCF
  • 如果服务需要在TCP/Named Pipes/UDP (wcf 4.5)，选择WCF
  • 如果服务需要在http协议上，并且希望利用http协议的各种功能，选择Web API
  • 如果服务需要被各种客户端(特别是移动客户端)调用，选择Web API
posted @ 2014-06-23 15:02  PEPE YU  阅读(1047)  评论(0)  编辑  收藏  举报