cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP execute snap vs REST post/Http client snap

alchemiz
Contributor III

Hi SMEs,

Good day, any reason why response from SOAP execute snap is taking much longer than with a REST/HTTP client snap?

Is this because SOAP execute snap have a large overhead compared with a REST/HTTP client snap? Or is there an underlying process in SOAP execute snap?

FYI, both snap is invoking a SOAP service also triggering the SOAP service in SoapUI and Postman have the same response time. 

Thanks,
alchemiz

1 REPLY 1

smudassir
Employee
Employee

In tools like postman, u have to prepare the entire request (url, headers, payload, etc) and then execute it.  And, in soapui too, first you will prepare the request though soapui generates a pre-populated envelope where you have to only supply the values.  Once the request (url, payload, etc) is ready then you will hit the request.  And, you get raw xml response which is not processed further.

In the soap snap, once you hit the execute button, it doesn't directly hit the endpoint.  It has to do some preprocessing (check if there are any placeholder values in the envelope to replace them with the values from the output of previous snap, remove empty elements from the envelope, etc).  Once the enveloped is evaluated and optimised then it hits the endpoint.  And, once the raw xml response is received, the snap will then process the response to convert into a snaplogic document so the next snap can consume this output.

Due to the pre and post processing involved in the snap, the response time for the execution of the snap could be slightly more than that of postman, soapui, etc.

HTH.  BTW, can you tell how much difference you see in the execution time of the snap vs soapui?