Web service call duration
My team has some data stored in a database that is interested in other companies in our company and we are planning to create some web services so that they do not have direct access to our database.
We're not running very complex queries (think about it instantly once we're interested in the overhead), and we're wondering how long a web service call should take to conclude whether to use a web service or try better approaches.
We will be using RESTful web services. Any help providing the expected time range?
source to share
How fast is it needed? The main expense of any of these solutions (outside of the DB query itself) is simply data sorting (i.e. converting data from DB format to Web service format, XML, JSON, etc.).
So, if you are ready to "wash" the price of a database query, then where most of your efforts will end.
Second, sorting is the actual transfer time, which depends on your overall network speed.
A web service that returns a "perfect" representation will not be significantly slower than a more specialized mechanism (RPC, CORBA, raw socket protocol).
I would not capture the nature of the "web service" as such, but instead worry about transforming and moving data.
source to share
While there are no hard and fast rules, the default HTTP timeout on most web service systems is 120 seconds. You can determine the maximum time that the result should be obtained and make an appropriate decision if it is too short or sufficient. Since it appears to be an internal system, I am not suggesting that the actual web service will add too much overhead before the actual time it takes the DB to fetch the data.
source to share