Why REST? by Aaron Skonnard

Download this episode

Download Video


As REST continues to grow in popularity, it’s important to stop and ask yourself why REST? REST is by no means a silver bullet but it does offer some advantages over traditional SOAP and WS-* architectures when it fits well into your scenario. There are also times when SOAP makes more sense because it offers features and capabilities that REST cannot provide. In the end, REST and SOAP are different architectural styles, each with their own pros and cons. Come and learn when to choose one over the other and why REST makes sense for many Web services.



This session is presented by Aaron Skonnard during Microsoft DevDays 2010 in The Hague in The Netherlands.




Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image


      Want to ask some questions about REST.


      REST specifies that the URI must be understandable and must use resources as endpoints.


      Below is the scenario. Suppose i need to search data by company name and company name contains characters like & or /. These are restricted characters in terms of URl. / specifies subpath and & specifies the queriy parameter collection


      How can we implement this in REST

    • User profile image

      Can someone re-upload this video. There is some media failure error

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.