Doing mobile app development? Need to optimize? One way to conserve battery is by piggybacking networking transmissions. To preserve battery life, the cellular radio in mobile devices gets put into a lower powered state after some inactivity, and then gets turned off after an additional period of inactivity. Once the radio is off, it takes some time for the radio to be turned on and for the radio to negotiate a new connection with a nearby cell tower.
The current implementation of the Apigee SDK follows a simplistic timed interval (60 sec. by default) for upload of secondary traffic. This guarantees that the radio will be in the high state (turned on if it was off) at least once per minute. We will be revving our SDK to build in a bounded, piggybacked strategy for secondary traffic.
This article by Lori MacVittie of F5 makes some good points that whoever becomes the de facto API in cloud infrastructure might win - and goes as far to say that the API replaces the CLI.
Generally agree but might take it a step further.
Just as we drove a 'de facto' standard CLI at Cisco, de facto standard "infrastructure APIs" likely will emerge. (Already seeing this happening with the AWS API)
But APIs represent a significant evolution. Why? CLI commands and output are unstructured. API commands and output are...
Some people thought it was unusual for a bunch of networking guys to start a company that wants to simplify the cloud services governance world. But we see parallels all the time between the evolution of networking technologies and web services (SOA, APIs, Cloud services, or whatever you want to call them).
One parallel - constantly shrinking 'islands of complexity' . When IP started happening in the network world, there were many complex technologies like SNA, IPX, CLNS, etc. First IP was used as a much simpler way to connect these 'islands of complexity' because there were such high...