WCF vs ASP.NET Web API [closed]

I’ve spent a few months trying to grasp the concepts behind WCF and recently I’ve developed my first WCF service application.

I’ve struggled quite a bit to understand all the settings in the config file.
I am not convinced about the environment but it seems that you can do amazing stuff with it.

The other day I’ve found out that Microsoft has come out with a new thing called ASP.NET Web API.

For what I can read it’s a RESTful framework, very easy to use and implement.

Now, I am trying to figure out what are the main differences between the 2 frameworks and if I should try and convert my old WCF service application with the new API.

Could someone, please, help me to understand the differences and usage of each?

1Best Answer
11

The new ASP.NET Web API is a continuation of the previous WCF Web API project (although some of the concepts have changed).

WCF was originally created to enable SOAP-based services. For simpler RESTful or RPCish services (think clients like jQuery) ASP.NET Web API should be good choice.

Leave a Comment