Our CEO, Lars Larsson, recently contributed an article to Internet of Business, about APIs, essentially the glue that binds connected software applications together. His article addresses the Achilles' heel of IoT development: API call performance. While most companies haven't yet experienced a disaster as a result of ignoring API call performance, the horizon looks filled with not-too-distant performance implosions. Now is the time to secure scalable performance and faster-than-needed throughput for API management - not when it is already too late.
The following article appeared originally on the JAX Magazine website in the lead-up to the JAX Finance event in London, April 27-29, 2016, republished here courtesy of JAX Magazine.
This post was written by Varnish Software's Denis Brækhus and originally published on API.Report on 8 February 2016.
When an API is born, its purpose in life might be very well-defined and the expected usage seem limited. The creators of the API solve a particular problem, and they do it in a good enough way to handle the initial volume of calls. Maybe the API is designed to scale given a certain projected usage increase. At this point, performance does not seem like an important consideration.
We’ve certainly heard the chorus of voices discussing APIs and API management of late. We are convinced, though, that we are singing a solo with our focus on the areas that we think are most important in API management: performance, scalability and stability. These are all crucial elements for implementing a successful API-first approach and API strategy, not to mention critical for the proliferation and maturation of the world of mobile apps and the internet of things (IoT). As essential as performance is, it has not been a priority in developing API management solutions - but failure to perform will not only be a showstopper but may have significant effects on the bottom line.