https://facebook/groups/1441095209496579/ common interview question in webservices .................................................................... SOAP vs REST ......................... Compared to SOAP, REST is a lighter-weight and less feature-rich approach to building web services. As such, it does not support the infrastructure built on top of SOAP (like WSDL, UDDI and WS-Security). JAX-WS supports a limited kind of REST API. SOAP vs REST ............................. youtube/watch?v=v3OMEAU_4HI&feature=related REST: .............. exposes RESOURCES which represent DATA point-to-point communication over HTTP supports multiple data formats(not just xml) emphasizes stateless communication uses HTTP GET/POST/DELETE SOAP: ........... exposes OPERATIONS which represent LOGIC loosely coupled distributed messaging supports only XML stateful and stateless/conversational communication strong typing supports asynchronous messaging uses HTTP post REST IS BETTER THAN SOAP ............................................... can be consumed by a web browser with javascript or ajax lightweight(doesnot require xml parsin and SOAP header for every message thus requires less bandwidht) SOAP IS BETTER THAN REST ................................................ rest only supports http/https thus theres no asynchronous messaging.because http is synchronous communication. rest is not secure as parameters are part of URI rest cant be governed as there is not service registry thus you have no idea whos consuming services rest and soap can co-exist REST GOOD FOR .................................. webservices exposing data over internet limited bandwitdh(small sized data) and resources(no xml parsing) combining content from many different sources on a web browser SOAP GOOD FOR .................................. enterprise services asynchronous messaging stateful/conversational operations
Posted on: Tue, 26 Aug 2014 05:58:04 +0000
Trending Topics
Recently Viewed Topics
© 2015