REST, SOAP/WS-* and WCF概览

很多地方提到REST vs. WS-* (SOAP), 今天google了一下并整理了一些观点,算是个速查链接:

David Chappell:
 
 
A RESTful approach is a natural for data-oriented applications that focus on create/read/update/delete scenarios. Lots and lots of apps fit this model, especially on the public Internet. A solution based on WS-* makes more sense for service/method-oriented applications, especially those that need more advanced behaviors such as transactions and more-than-basic security. (Doubt this last point? Look up "Security" in the index of the Richardson/Ruby book: Exactly one page number is listed.)
 
IBM guys' research:
use RESTful services for tactical, ad hoc integration over the Web (à la Mashup) and to prefer WS-* Web services in professional enterprise application integration scenarios with a longer lifespan and advanced QoS requirements.
 
WCF provides same programming model for REST and WS-*
 

Introduced as part of the .NET Framework 3.0, WCF enables developers to build services leveraging their present .NET Framework development skills. WCF combines and extends the capabilities of Microsoft's existing distributed systems technologies, including Enterprise Services, Net Peer, .NET Remoting, COM+, MSMQ, and ASMX to deliver a unified development experience.  

With the .NET Framework 3.5 release, WCF added support for building REST style services. REST, an architectural style for building distributed hypermedia driven applications, involves building resource-oriented services by defining resources that implement uniform interfaces using standard HTTP verbs (GET, POST, PUT, and DELETE), and that can be located/identified by a URI.

 

 

 
A Brief Introduction to SOAP/WS-* (Making Sense of all these Crazy Web Service Standards)

A Brief Introduction to REST

你可能感兴趣的:(REST)