REST vs SOAP


This article is to compare REST vs SOAP. There is huge difference between REST and SOAP. Comparing SOAP and REST is not just right as they are different things. It is like comparing orangutan and octopus, I have high regard for both of them. But still, as it is a popular topic lets have a discussion on SOAP vs REST.
Roy Fielding was a member of the team that wrote the specification for HTTP and co-founder of Apache HTTP server project. He introduced the word REST and the concept in his doctoral thesis in 2000. REST disruptively took over as an architectural style for web services implementation.
  • SOAP stands for Simple Object Access Protocol. REST stands for REpresentational State Transfer.
  • SOAP is a XML based messaging protocol and REST is not a protocol but an architectural style.
  • SOAP has a standard specification but there is none for REST.
  • Whole of the web works based on REST style architecture. Consider a shared resource repository and consumers access the resources.
  • Even SOAP based web services can be implemented in RESTful style. REST is a concept that does not tie with any protocols.
  • SOAP is distributed computing style and REST is web style (web is also a distributed computing model).
  • REST messages should be self-contained and should help consumer in controlling the interaction between provider and consumer(example, links in message to decide the next course of action). But SOAP doesn’t has any such requirements.
  • REST does not enforces message format as XML or JSON or etc. But SOAP is XML based message protocol.
  • REST follows stateless model. SOAP has specifications for stateful implementation as well.
  • SOAP is strongly typed, has strict specification for every part of implementation. But REST gives the concept and less restrictive about the implementation.
  • Therefore REST based implementation is simple compared to SOAP and consumer understanding.
  • SOAP uses interfaces and named operations to expose business logic. REST uses (generally) URI and methods like (GET, PUT, POST, DELETE) to expose resources.
  • SOAP has a set of standard specifications. WS-Security is the specification for security in the implementation. It is a detailed standard providing rules for security in application implementation. Like this we have separate specifications for messaging, transactions, etc. Unlike SOAP, REST does not has dedicated concepts for each of these. REST predominantly relies on HTTPS.
  • Above all both SOAP and REST depends on design and implementation of the application.
  1. REST is over HTTP, but SOAP can be over any transport protocols such HTTP, FTP, STMP, JMS etc.

Comments

Post a Comment

Popular posts from this blog

Launch iPhone simulator without Xcode.

To launch simulator you have to way. 1. Using Terminal 2. Using UI. 1 Using UI. ->    Open Finder and then press   shift +  cmnd + g   or Go -> Go to Folder then enter this address /Applications/ Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications the double click on simulator.app. 2 Using Terminal  Open terminal and then press this command open / Applications / Xcode . app / Contents / Developer / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app or open `xcode-select --print-path` / Platforms / iPhoneSimulator . platform / Developer / Applications / iPhone\ Simulator . app To run application follow this, http://cocoamanifest.net/articles/2011/12/running-your-ios-app-in-the-simulator-from-the-command-line.html
Read more

How to Make REST api call in Objective-C.

We can call using this. NSString * twitterUrl = @ "YourUrlString" ; NSString * resp = [ self makeRestAPICall : twitterUrl ]; and method is -( NSString *) makeRestAPICall : ( NSString *) reqURLStr { NSURLRequest * Request = [ NSURLRequest requestWithURL :[ NSURL URLWithString : reqURLStr ]]; NSURLResponse * resp = nil ; NSError * error = nil ; NSData * response = [ NSURLConnection sendSynchronousRequest : Request returningResponse : & resp error : & error ]; NSString * responseString = [[ NSString alloc ] initWithData : response encoding : NSUTF8StringEncoding ]; NSLog (@ "%@" , responseString ); return responseString ; } 1 2 3 4 @ interface ViewController : UIViewController < NSURLConnectionDelegate > {      NSMutableData * _responseData ; }
Read more

id vs NSObject

There's often confusion about the difference between the following three declarations in Objective-C: id foo1; ->   It simply declares a pointer to some Objective-C object,  If you don't want (or can't have) any type checking, then use   id . if you do want compile-time type checking, you must decide between the second and third cases.. NSObject *foo2; ->  declaring a generic pointer of type NSObject* id<NSObject> foo3; ->   pointer to  any  object that behaves like an NSObjec , "foo3 is a pointer to an object of any type that behaves like an NSObject" , ( you really don't care what class the object is, you only care that it  behaves  like an NSObject.) The first one is the most common. It simply declares a pointer to some Objective-C object (see  /usr/include/objc/objc.h ).  id  gives the compiler no information about the actual type of the object, so the compiler cannot do compile-time type ...
Read more