There are lots of talk on Web API and WCF REST regrading which one to use for REST Services . Many people are recommending Web API for REST service and they are saying stickily use Web API instead of WCF REST but personally I am not agree with it .The reasons are follows
- We should not be stick on any particular technology i.e Web API or REST , It must be decided according to project requirement whether the Web API or WCF REST is fit for project requirement.
- There are lots of technologies in market but first we need to analyze project scope and requirement and according to it we need to decide technology.
|
Scenario or Requirement
|
Web API
|
WCF REST
|
| Need support of MSMQ. |
No
|
Yes
|
| Need duplex communication |
No
|
Yes
|
| Need End to end message security |
No
|
Yes
|
| Need Distributed transaction. |
No
|
Yes
|
| One way messaging. |
No
|
Yes
|
| Need to handle Long pooling requests |
No
|
Yes
|
| Need support of REST service in existing WCF Service |
No
|
Yes
|
| Need same code to be supported on both SOAP and REST |
No
|
Yes
|
| Need REST in ASP.NET MVC |
Yes preferred
|
Yes
|
| Need only HTTP service |
Yes
|
Yes but not recommended
|
| Open source |
Yes
|
No
|
The above is the some differences according to the our project scenario and requirement.
Note
Learn WCF and REST Service on compilemode.com
Summary
I hope this article is useful for all readers , If you have any suggestion regarding this article then please contact me.
Post a Comment