Warner’s last mile on a long cloud journey

For more than a decade, Warner Music Group has been orchestrating an all-in cloud transformation. Its adoption of networking as a service may be the final note.




Thinkstock / Shulz / Getty Images

Warner Music Group is the epitome of a cloud veteran. The media giant’s advanced cloud architecture, which runs on Amazon Web Services and Microsoft Azure, dates back almost 12 years, making it one of the first enterprises to migrate nearly all its corporate assets to the cloud.

“It’s the whole company — everything we do,” WMG CIO Ralph Munsen tells CIO.com, of the company’s all-cloud architecture.

This month the company is celebrating yet another milestone in its multi-year cloud project: migrating its networking services to the cloud. 

Embracing networking as a service (NaaS) offers multiple benefits, ranging from cost savings, to increased security, to improved orchestration of networking services in a constantly changing corporate environment. By migrating interconnections and multiple network layers to the cloud, organizations can establish a more agile platform in which networking services and virtual circuits can be turned off and on dynamically with zero downtime due to the platform’s orchestration, Munsen says.

“When you want to add something, change its circuit, or change anything in that network, it’s just much easier. You go to one spot, make the change, and it takes effect immediately,” he adds.

Read More

Next Post

Leave a Reply

Your email address will not be published. Required fields are marked *


Notice: Undefined index: column in /home/budgethotels/public_html/newsen.org/wp-content/themes/jnews/class/Widget/Normal/Element/SocialCounterWidget.php on line 264

Notice: Undefined index: style in /home/budgethotels/public_html/newsen.org/wp-content/themes/jnews/class/Widget/Normal/Element/SocialCounterWidget.php on line 264

Recent News


Notice: ob_end_flush(): failed to send buffer of zlib output compression (0) in /home/budgethotels/public_html/newsen.org/wp-includes/functions.php on line 5107