Cloud-native architecture. The words themselves are likely to elicit a range of reactions, from apathy (“Do we even need that?”) to annoyance (“Don’t we have enough to do?”). In fact, the words should be music to the ears of mobile service providers—because “cloud-native” is a must-have for 5G.
What Does Cloud-Native Mean? A Definition and Examples:
“Cloud-native” isn’t marketing hype and it isn’t a complicated architectural template. The Cloud-native 5G NG Core was designed from the ground up to support the speed, scale and service requirements of the future, much in the same way that Amazon, Google, Netflix, and other cloud leaders have already done. In the simplest of definitions, a cloud-native 5G NG Core has three main characteristics:
- It breaks traditional, monolithic network functions into microservices that are autonomous, replaceable/changeable and stateless;
- It stores these microservices into containers that can be easily moved, arranged and managed;
- It uses a common management tool such as Kubernetes to dynamically orchestrate the various virtual network functions (VNFs) rather than using proprietary vendor VNF managers.
From a consumer standpoint, 5G means faster speed, lower latency, and a pervasive IoT (Internet of Everything) fabric, but for mobile operators, 5G is about network slicing, innovation velocity and reducing network operating costs. In order to meet the network demands of 5G, operators need a web-scale infrastructure with dynamically reconfigurable software services –similar to what the Amazon and Google have for cloud services.
The payoff of a cloud-native 5G NG Core is enormous. It allows you to develop and deploy new services/applications much faster using continuous Agile and DevOps methodologies, gives you a network that can hyperscale efficiently (because the NFs are stateless) and provides more agility and flexibility by moving microservices into Docker containers that can be centrally orchestrated through an open-source tool such as Kubernetes. As you can see, a cloud-native architecture doesn’t compete with the goals of NFV/5G, it supports them and in many cases turbocharges them.
Yes, you can try to build an NFV/5G network without a cloud-native architecture. But, sooner or later, you’re going to hit a wall in terms of the performance, scale and cost savings you achieve. Cloud-native isn’t a question of “If,” but “When.” If your NFV/5G vendor doesn’t have a clear path to cloud-native capabilities in their solutions today, you may not have a clear path to creating a cloud-based network in the future. It’s a path we set out on from the beginning when we first designed our virtual EPC to support microservices, containers and service automation/orchestration. If you want a cloud-native core from a leading NFV/5G vendor, talk to us to ensure you don’t find yourself playing an expensive game of cloud catch-up while your competitors lead the way with innovative new services and better customer experiences.