Content on the Move: Top 5 Things You Need to Know About Dynamic Cloud Archives #2

Content on the Move: Top 5 Things You Need to Know About Dynamic Cloud Archives #2

Andy Hurt July 17, 2018

#2: They Reduce Capex Through Scalable Cloud Infrastructure

Welcome back to the blog miniseries “Content on the Move: Top 5 Things You Need to Know About Cloud Dynamic Archives,” where you’ll find me extolling the virtues of dynamic cloud archives. This entry is all about how they help you cut capital costs.

If you’re using an in-house infrastructure, then you know it’s a never-ending outpouring of capital (not to mention time) just to keep up with changes in industry equipment, software, formats, and standards. There’s little hope of staying 100 percent on top of it.

But in the cloud, you don’t have to, because everything is already updated and available. Virtual machines. Seamless feature releases. Endless scalability. You never have to worry about replacing outdated hardware or making cumbersome software upgrades to get new features or comply with the latest standards. The cloud service providers do it for you. You just sit back and let the operation work. And in most cases, you only pay for what you use, so you can scale up or down at will instead of letting expensive equipment sit idle in down times.

What does that have to do with a dynamic archive, you ask?

Traditional archives and MAM systems store content behind a firewall, likely on LTO tape, where it is inaccessible to anyone outside your organization — the very people to whom you might want to grant access. (Think media, sponsors, and other stakeholders.) But when you store your assets in a cloud-native platform, they are easily discoverable and distributable with permission-based accessibility. And when you use a cloud-native MAM application that is also tied to licensing, you turn what was once just a storage expense into revenue.

In other words, with the cloud as the basis for your dynamic archive, you not only save money and time maintaining your archiving operation, but you can start using it to do things such as content organization, social publishing, enriched metadata, advanced transcoding, and facial recognition. Things you’d be hard-pressed to do efficiently with an in-house, hardware-based infrastructure. (More on that in the next blog. Watch for it!)

Bottom line: Goodbye, capex! Hello, efficiency!