Cloud NetsSeptember 30, 2021
Episode 3 Multiservices over a Shared Virtualized Infrastructure
This is about running multiple network functions over the same shared virtualized network infrastructure.
Hi and welcome back to Cloud Nets, where networks meet cloud.
Today we’re going to talk about cloud-native or multiservice infrastructure and for that we brought our cloud-native or multiservice infrastructure expert, Run Almog.
Run. Thank you for joining.
Okay. So, what’s multiservice? We keep talking about it, but let’s understand what it is. The long answer is that just like in cloud, multiservice is a system in which you run multiple services or multiple network functions over the same shared virtualized infrastructure and with that, you can achieve hyperscale economics and a lot of efficiency and cost performance benefits.
Run, what’s the short answer?
I’ll break it down into three pieces. First off, its multiservice, right? The numerity of the services. Second, is the infrastructure or the architecture underneath the microservice architecture and third, is the resource sharing, which is as a result of it.
So, I’ll explain each and every one of them as a stand-alone. Multiservice is the ability to run a different service on top of an existing infrastructure, so you don’t have to have a dedicated hardware to run each and every one of your services in the network.
Second, is the microservice architecture; this is how we built it. In order to have multiple services, which is something that hyperscalers are doing all the time, you need to have an efficient infrastructure that supports this. So, one service will not be interrupted and will go independently without interrupting other services, which exists on the same infrastructure. This is what the microservice architecture grants us.
And we put those in containers in order to separate between the different parts.
Exactly, exactly. In order to operate them in a simple manner, we containerize each and every one of these and we are enabling to launch each and every such containerized service in a simple manner.
The outcome of this is better resource sharing, you have multiple resources which are network oriented in your infrastructure. In order to best utilize all of these, you have different services that utilize different resources in a different way in a different time. You want to have a mechanism that enables each and every service the required resources when it’s needed, where it’s needed. This is the outcome of microservice architecture and multi-service as we are implementing it.
So, practically when you put very different services on top of the same infrastructure, each utilizes different parts and different resources and therefore, you get very good utilization of this infrastructure which we paid for.
Exactly, exactly. Because the services have variants between them, if you use a dedicated box to run each and every one service, then there is a lot of wasted resources in it.
Okay. Now we understand what is cloud-native and multiservice architecture.
Remember, you need to remember only three things. One, is the multiservice itself running multiple services over an infrastructure. The second, is the microservice architecture, the fact that you run those in silos, in containers separated from each other and the third, is the outcome, the resource sharing, the great resource utilization you get when you run cloud-native multiservice applications. Now we know.
Thank you very much Run for explaining and thank you for watching and understanding.