How We Increased Uptime and Decreased Engineering StressWorking in the big data world can be a little chaotic. For us that means a stable flow of 20k events per second can spike to 50k over the course of an hour. It takes only seconds to look through our logs and find a perfect example: Things move fast and we need to be able to adapt and respond immediately when our systems are under stress. When a system goes “red” most people’s first instinct is to call the engineer who built it. Over time this can create silos of knowledge and an uneven load on the engineers. Another side-effect of this engineer-first thinking is that the priority is focused on fixing the problem, missing the importance of communication.
Any UX practitioners watching the HBO series Silicon Valley may have been screaming at their TVs during season 3’s final weeks. The fictional consumer-facing compression platform Pied Piper launched to dismal daily active user numbers, and viewers saw a perfect illustration of…
Has setting up a live stream ever given you a headache?It used to be the case that setting up a live stream involved many steps and a lot of technical expertise. JW Player wanted to make the process much easier, so we created JW Live.
Here's how JW Live is different
IntroductionFor publishers, a viral video is the holy grail of online video. Besides the immediate spike in ad revenue, a viral video can do wonders for brand recognition and long-term growth. Dollar Shave Club is a recent example of a small company that rode a viral video success to a billion dollar acquisition. There’s no question that publishers want their videos to go viral, but cracking the code to predictably creating viral content is a different beast. The goal of this article is to understand how to set your video up for virality: in particular, the necessary search engine optimization (SEO) that allows viewers to discover video content relevant to their interests. Finally, I’ll touch on the intangible UX factors that make a viral video special and how UX plays a role in searching and interacting with video content.
IntroductionJW Player receives an average of 45,000 log entries per second (or "pings") into a lambda architecture data pipeline. This equates to a daily data set that contains between 3 and 4 billion rows. To improve query performance and save storage costs the Data team at JW Player has started an initiative to re-define the data domain where pings are stored as sessions in a columnar format.
We’re pleased to announce the launch of our new support site! support.jwplayer.com features lots of cool new tools to assist with your questions and troubleshooting. Let’s take a quick tour and go over some of the more interesting changes: