The round-trip time relies upon more on internet latency than whatever else. for example, to get from a mobile device to FitBit and back thru a proxy going for walks in Apigee, your API name travels from the tool to Apigee, then to FitBit, then back through Apigee. depending on in which FitBit’s servers are positioned, that can be whatever from 50 to 100 milliseconds slower (a median latency throughout the U.S.) to nearly the identical.
furthermore, the proxy in Apigee can do such things as cache common responses, dispose of unused bits of the response, and integrate a couple of API calls to the FitBit API right into a single API name from the tool. which means that an API strolling on Apigee may be quicker.
As for XML as opposed to JSON, the actual difference is within the ability for a customer app, consisting of a mobile app, to parse the information. Programmers have a much easier time consuming JSON than XML, due to the fact the information model is an awful lot less complicated and equal, or almost equal, to most programming languages. Parsing XML, then again, calls for a group of specialized information.
In a few cases, parsing XML uses more CPU on the purchaser, however it’s not always a massive difference. similarly, XML is “greater verbose,” however when you compress it, XML and JSON come to be being very similar considering that in the long run they commonly include the equal data.
