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.
When managing several Varnish instance(s), keeping the configuration coherent between them can be hard. Monitoring and deploying configuration, restarting the instances in a synchronized fashion requires some knowledge. The Varnish Administration Console (VAC) , provides a full API that helps leveraging once difficult tasks.
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 recently launched Varnish API Engine version 2.0, and to gain a better understanding of the API management landscape, we tapped into the “wisdom of the crowd”, surveying 96 Varnish Summit participants. We asked how their businesses are using and managing APIs and how well they feel their current API-management solutions to be working.