ASP.net Web API Series--Select the Web API or Wcf__.net

Http://www.nmtree.net/2014/10/19/asp-net-web-api-series-choosing-asp-net-web-api-or-wcf.html

WCF is a one-stop framework for. NET Platform Services Development, so why should there be a asp.net Web api? Simply put, the ASP.net Web API was designed and built with one thing in mind: HTTP, and WCF was designed primarily to consider soap and ws-*.

WCF has been around for years and, relatively speaking, the ASP.net Web API is a little child, but it does not mean that the ASP.net Web API is a substitute for WCF and that they have strengths on different occasions. The ASP.net Web API is very lightweight and cannot be compared to WCF in functionality and flexibility. If your service is based on TCP, or if you support more transport mechanisms, WCF is the best option. However, not all platforms support soap and ws-*, and the ASP.net Web API is even better when the client does not support these protocols.

Let's take a look at the difference between the two programming models: a service that gets employees of a company based on an employee ID. WCF code such as 1-1,asp.net Web API code like 1-2

1-1 WCF way to get employee information

[Serviceco"] Ntract] public interface Iemployeeservice {     [OperationContract]      [ WebGet (UriTemplate =  "/employees/{id}")]      Employee getemployee (string id); public class Employeeservice:iemployeeservice {     public Employee GetEmployee (string id)   ;    {         return

1 2 3 4 5 6 7 8 (9) "