First In Class Time To Live

You already have a content team, pushing out high-quality, authoritative content in your field. You are already paying an enormous sum to your CMS provider to make sure that your viewers can retrieve that content quickly, likely through many different modalities. You have your website, sure, but you probably have an app provider too. You may have content that goes in other directions like digital billboards or on-air content. Odds are that over half of your content delivery is through other channels.

Your CMS provider has sold you a bill of goods that shows how quickly their website loads, but what they didn't likely mention is how quickly it actually updates when you publish a story. If you are enterprise-scale, I would expect that you have a CDN layer over your CMS so that it can handle the traffic volume. The cache-time on that CDN will likely be minutes or hours, so that when you publish your new story, it just sits there in the background waiting for a request outdated enough to render it. Your users are falling behind, even though you aren't.

In our case, you control the cache-time of each page individually, and they all default to 60 seconds. That means your new story content is not more than 60seconds behind your content team, by default, and you can make it faster than that if you like. Our unique architecture also extends that capability to every outside consumer of that content. Digital billboards? Not more than seconds behind. Your app vendor is not more than seconds behind.

I'm talking about a massive improvement in your Time To Live (TTL), but not only that. Our delivery metrics exceed every other CMS provider we have compared it to in other ways as well. You want pageload speed at scale? You bet. That fast loading content is recovered from our database in less than 120ms. You won't have users sitting there for 1-2-3 seconds waiting for that fresh content to load.

Do you have sudden bursts of intense traffic? Perhaps during severe storms, or other notable news events? Great! Viking CMS runs faster the more traffic you throw at it. We achieve our lowest latency when you need it the most. Our best performing sites have around 20-50K requests coming in every five minutes. That's a lot of work, but we've spread the load over multiple servers all sharing the same Memcached, so it really just "primes the pump" even more. Traffic is your friend, if you use it the way we are.