Microservices - The wind beneath the CNF wings

-


null

In my last post, I discussed the pitfalls of microservices, which power CNFs. In this post, I will present the other side of the story.

We know that microservices dissect individual CNFs into a mesh of interdependent services that can be containerized independently of each other. I would like you to take a moment a relook at the usage of interdependence and independence carefully.

A given CNF is thus a combination of multiple microservices.

Our report “Containers and Telcos: Ready to Tango” chronicles and describes several CNFs.

Metaswitch for example, offers its virtual IMS (vIMS) as combination of multiple microservices such as SIP routing, HSS proxy, distributed timer database, in-memory open-source database, file-based open-source database and open-source configuration distribution service. Individual microservices have independent development and deployment schedules; and are therefore often managed by dedicated teams.

The methodology of microservice development also makes it clear as to why containers are able to leverage CI/CD constructs effectively. The 5G-PPP terms microservices as loosely coupled, but highly cohesive. The cohesiveness helps in quickly establishing connections with other microservices, while the loose coupling allows for independence and autonomy in the development cycles of individual microservices.

Microservices have been instrumental in initiating cloud nativity into telecom device engineering.

Microservices have positive implications for design, troubleshooting and scaling.

  • On the design front, microservice-based CNFs offer greater granularity into the CNF architecture. Designers are now able to fine-tune parameters at the level of individual processes rather than dealing with entire applications.
  • Microservices make it possible to design, test, operationalize and manage individual functional strands in a CNF.
  • Microservices facilitate the pinpoint scaling up of certain segments of the CNF to the required extent, helping in efficiently managing available resources.
  • Conversely, faulty or problematic microservices can be curtailed or brought down and repaired without obstructing the function of other well-functioning microservices in a CNF.

What is required for telcos and vendors is to keep their eyes open to the performance penalties exerted by microservices and deftly compensate them with the benefits that microservices bring to the table. This exercise requires a clear-headed approach to RoI calculations. The RoI assessment is particularly important for tier 2 and tier 3 telcos as so that they don’t end up wielding the short end of the stick.

All in all, CNFs are not really optional. The next generation of telco operations are bound to demand highly customized products. Telcos will continue to push for greater depth in adaptability and greater control in tunability of their devices. At present, there is nothing really that comes anywhere close to microservices in achieving these objectives.

Comments

  1. devopsenablercoMay 17, 2022 at 2:40 PM

    Extremely useful information which you have shared here about devops automation services. This is a great way to enhance knowledge for us, and also beneficial for us. Thank you for sharing an article like this.

    ReplyDelete

Post a Comment

Popular posts from this blog

SDN, NFV and Indian Telcos

-
  I returned with useful insights from the SDN-NFV India earlier this month. There were two discernible trends – optimistic solution vendors and cautious telcos. Indian telcos are worried about the following: Indian telcos, including the largest ones, are genuinely concerned about the solidity and stability of SDN and NFV products. Telcos think that vendors do not completely appreciate the difference between a service outage suffered by Facebook and an outage suffered by a licensed cellular operator. The former can be irritating, the latter can be catastrophic. Indian telcos are also looking towards concrete ways of making money from SDN and NFV. What works with telcos in the US may not work with Indian telcos. The above points were recurring themes. You could say that Indian telcos were never among the early adopters of technologies. You could also say that Indian telcos are bleeding far too heavily in the present to think rationally about overhauling their networks. Plenty has been s
Read more

Are CNFs, VNFs?

-
Image
The answer is yes. Our recent report “ The VNFO – Ripe for Change ” says this loudly and clearly. Pardon the atrocious image. But I hope it encapsulates the dilemma appropriately. It is important to reiterate the reasons for including containers under VNF and in essence, Kubernetes under VNFO. Both VMs and containers are virtualization methodologies. Thus, network functions synthesized using VMs and containers qualify as VNFs. In VNFs orchestrated by containers are sometimes referred to as cloud-native NFs (CNFs). Insight Research has also employed this term as early as 2020. Over time however, we have observed that the usage of CNFs is neither consistent nor uniform. Most ‘traditional’ MANOs such as ONAP, OSM and all proprietary offerings now support containers and Kubernetes. Containers are thus one more means towards achieving the end-objective of VNFs. In such situations, Insight Research finds it more appropriate to use VNF as an umbrella term and under this term, refer to VM or c
Read more

India - Don't forget 5G!

-
I recently conducted a poll on the prospects of 5G roll-out in India. I basically tried to gauge the perception about the availability of 5G in India - on or before 2021; or after that. Expectedly, the overwhelming response was the latter. India has too many challenges to surmount before 5G can make an appearance - the auction process, the operator finances and the choice of vendors. Each of these challenges is a topic for separate discussion. The uncertainty surrounding 5G in India is unfortunate. 5G does promise higher data rates than its predecessor, but that is not its only advantage. 5G institutionalizes network segmentation or 'slicing' according to the traffic profile. It is thus possible for low throughput IoT sensor traffic to co-exist with data-intensive video without the network designer breaking into a sweat. For India, which has ambitions of developing world-class manufacturing, logistics, transportation, healthcare, finance and governance frameworks; it is importa
Read more