For a long time Varnish developers wanted a monitoring tool with a feature set similar to Apache’s mod_status, which lets you monitor the status of threads. Varnish is already well-served by several other, similar utilities: varnishstat, which shows internal counters, and varnishlog, which stores session information related to serving a request.
Now that the dust has settled on this year’s IBC show, we at Varnish wanted to highlight some key trends that we saw and heard being discussed at the conference and on the show floor for those of you who may not have been able to make the trek to Amsterdam. This year, it was just as interesting to see what didn’t end up making a prominent appearance at the event as what did. Here are our five key observations:
Now that the dust has settled on this years Anga Com, it is worth looking at some of the key trends that we saw on the show floor and how they might affect media businesses over the coming year.
Hammering home the performance-performance-performance theme again and again, we’ve told the story of caching and protecting your backend many times. We’ve talked a lot about the ways in which Varnish Streaming Server lets you scale up to serve live and VoD streaming content no matter the demand on your platform. But a big part of this story is maximizing the power of the capacity you already have. Ultimately that is what caching is all about: you make copies of content you need to deliver so the copies are delivered, much faster than roundtrips to the backend could achieve while protecting the backend from overload.