Gaming is more than just big business -- it has a reach, importance and influence that belies its once niche status. Gaming has overtaken the film and music industries combined in terms of revenue, and has become an entertainment juggernaut -- a true cross-industry moneymaker. Gaming has also been acknowledged not just as a global cultural phenomenon but also as a major of engagement platform. After all, savvy politicians are making their way into the world of Among Us players streaming on Twitch, or hosting potential voters on their island in Animal Crossing.
When it comes to deploying video -- both on-demand and live -- content and delivering with a good quality of experience (QoE), there is no one-size-fits-all approach. But for almost any video streaming company, a multi-CDN strategy is needed to ensure that QoE and the ability to scale up to deliver it.
The single most frequent question I get from people discovering Varnish is "Do you support request collapsing?". And I must admit, it always catches me off guard, because of course, it has been doing so for years, and it's a caching server, so that's a must-have, right? (Yes, yes it is.)
For this reason, in this post, we are going to review some of the little features we take for granted but that also make Varnish a great origin shield.
Video traffic makes up at least 80% of the content that gets delivered, and as the demand for smooth video streaming continues to dominate, the ways in which content gets delivered are becoming more creative and more customized.
One of the most common ways to satisfy the unpredictable nature of video traffic is to adopt a hybrid approach, or a multi-CDN strategy, letting content owners, broadcasters and technology companies deploy resources flexibly where and as needed to deliver superior video experiences at scale.