Microservices - The wind beneath the CNF wings
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 clea...