Tuesday, 15 January 2013

When does SOAP make more sense than REST? -


In my understanding of the REST, the underlying assumption is that all functions are CRUD operation. Sometimes, you are not operating the CRUD and doing some more complex arguments. In this case, is SOAP more suitable? Or is it a matter of how complex a series of all operation CRWood operations, should be divided into a set of small CRUD operations in order to be called one after the other? But does it not perform such an operation that you are trying to make more cumbersome for writing? I am trying to understand how to get more sense to use SOAP instead of REST.

I work in the banking sector One of the largest banks in Russia we use Soba and We have a lot of webservices we like it, because:

  1. It's easy to decompose a work - & gt; One service
  2. It is easy to manage webservices ()
  3. Making a bug localized is very simple because you only have to rewrite the same service and you will have to re-assign all the arguments If we have found bugs then we will rewrite all the arguments)
  4. If we use soap webservices, then we are easy to create a map of organizations (later we together on the web server And other logical units).

No comments:

Post a Comment