Geek Answers Handbook

How expensive is a web service?

I had a good google search and nothing came out to answer my question. Since I know very little about web services (I just started using them, and have not created them in the last couple of months), I was wondering how much I should be fine to call a certain web service as often as I wish (in reasonable), or should I create requests that need to be done at a time.

To give an example, my application is designed to create job updates that will invoke a web service for certain types of updates. It seems like my options are that I could create data in my application for updates that require a web service, and pass all the information related to the web service, and then write a method in the web service to process the updated data. Alternatively, I could iterate through my entire update table (including updates other than those that require the web service) and call the web service as required during the update.

At the moment, it seems to me that it would be easier to transmit every update, rather than data related to the web service.

In terms of transferring data to the web service, each update will contain a small amount of data (3 lines with a length of not more than 120 characters). As for the number of updates, it will probably be no more than 200.

+4
source share
2 answers

I was interested to know if I should be fine to call a certain web service as often as I want (within reason), or I need to create requests to do at a time.

Web services or not, any calls made over the network will benefit from creating multiple requests so that they can be processed at a time. In your case, creating an object representing all updates will be a clear winner, especially in settings with slower connections.

, , ( , - ):

  • , ,
  • ,

2 6 - . .

, , ; - . 100 ​​1 (2 ), 200 ! , . , .

+5

.

10 - 100 ?

+1

More articles:


All Articles