In last week’s post, we discussed what cloud-native really means. It has to be more than just using VMs to run code in the cloud or containers on switches. That does not make the software cloud-native. We pointed out that customers are realizing that it undermines their ability to get the benefits from the cloud. In a recent discussion published on SDXCentral, Rakuten Mobile CTO Tareq Amin talked about the issues this caused:
“It is not good enough to move the software architecture from monolithic architecture that was built on proprietary hardware and say I’m going to shift to a virtual machine. To achieve the dream and the benefits of cloudification, the software architecture must evolve to support elasticity.”
We are not the only ones thinking about this. Earlier this week, Tom Nolle weighed in with a blog post entitled “Is Rakuten’s Inditement of Telecom Software on Target?”
Here’s a bold statement for you: “There is no magic that an Amazon Web Services, Google, and Microsoft could enable because the underlying software architecture is absolutely flawed. It needs to evolve.” This, from the CTO of Rakuten Mobile, as quoted in an SDxCentral piece. I agree, of course, and in fact I’ve been trying for months to get a reading on what senior planners and architects in the telecom space think about “cloud-native”.
The Wizard of Roz, Roz Roseboro, Consulting Analyst for Light Reading, published a column “A better mousetrap, or just a trap? Questions about Dish and AWS using the public cloud for 5G” that addressed how the cloud is changing telecom. She noted that Reliance Jio and Rakuten were among the more notable first movers on cloud-native mobile networks and Dish takes it to another level by using someone else’s public cloud infrastructure:
How will Dish differentiate itself? This is a question for all CSPs as they move to similar cloud-native architectures and functions but seems particularly critical in Dish’s case. Dish Chairman Charlie Ergen sounded like pretty much all of the other mobile network operators in the company’s press release, calling out automation and time to market as key outcomes of its strategy, saying “leveraging AWS and its extensive network of partners enables us to differentiate ourselves by operating our 5G network with a high degree of automation, utilizing the talent of AWS-trained developers and helping our customers bring new 5G applications to market faster than ever before.”
We see the benefits of combining a cloud-native architecture with the elasticity and price advantages of running compute-intensive applications in the cloud. Clearly, we are not alone.