3

I'm trying to figure out wether I should use SOAP or REST for a specific project. I will explain what the project is or needs to do, and I hope some of you will give me useful information about why I should use one over the other.

The project I need to work on is totally web service based. Every frond end implementation needs to access webservices to get all the information it needs. But Beyond that, we also have an Indesign plugin that talks to these webservices to upload documents and check validations on the document etc.

So to make it short, I need to access the web services via front end web gui's and via an indesign plugin. The latter makes me wonder wether I should use REST or SOAP.

Thanks alot for reading this and posting you feedback.

1 Answers1

2

I found this really great article on the advantages and disadvantages of SOAP vs REST: http://geeknizer.com/rest-vs-soap-using-http-choosing-the-right-webservice-protocol/

And my own humble opionion:
I don't like SOAP, I never did. It's been great at the time, but it just never felt "right". If you've ever tried to read one of these huge overloaded XML-documents and compared it to the REST output (which is JSON most of the time) you know what I mean. IMHO just feels "better".
One problem is that you have to document your REST API better, but that shouldn't be that big problem as long as it is not open to everyone.
Especially if you handle all your data with Webservices, I think you should go with the lighter and less bandwith consuming option: REST.
Also REST is the new and hip technology that everyone uses at the moment... ;)

About your indesign plugin: You should be able to include any library you want, so that shouldn't be a problem.

Simon Woker
  • 4,994
  • 1
  • 27
  • 41
  • +1 for REST. i hate soap and all the required extra steps it requires to do a simple call – Quamis May 16 '11 at 11:01
  • REST is not "mostly JSON". Choosing REST due to lower bandwidth usage is like buying a BMW because it comes in black. And REST is not new, it is 10 years old. – Darrel Miller May 16 '11 at 11:34
  • REST is old, sure, but it is new when you talk about it as usage for webservices. And if it's not **normally** JSON - what is it then? I know you can specify it in way you want, but in most popular APIs I see JSON as output. [I see, maybe I used the wrong words there] – Simon Woker May 16 '11 at 12:16
  • 2
    That's a nice article that you have linked too. I would nearly always prefer REST over SOAP, mostly based on my past experiences - they have always been much nicer and smoother with REST. I think RESt generally makes it easier for others to hook into your API too. The only thing that draws me to SOAP in this case is the requirement to post attachments through the mechanism. With complex transactions, sometimes the additional structure that SOAP enforces makes for a more solid base structure for the application. – John Wordsworth May 17 '11 at 00:14