The brave new world of networking services is automated, elastic, and chained.
That is to say, if you need to push traffic through a bunch of virtual middleboxes, you’re going to automate the creation of those middleboxes. Eventually, the days of standing up hardware services and plumbing them oh-so-carefully will be gone, because the world won’t wait for you to get it done. Automation is your answer.
And when you need to create more of them to support additional volume, the services will grow dynamically – more instances stood up and torn down as needed, depending on load.
And if you have a bunch of network services an application must pass through, you’ll set up traffic patterns in a service chain so that traffic flows through the virtual network services they need to without you having to rely on physical plumbing and clever routing.
All of this happens today in the worlds of OpenStack, containers, NFV, and microservices. In other words, this isn’t the “unicorn networking no one uses” that some of you complain about. This is real stuff.
To discuss microservice orchestration for networking is our sponsor, Sonus Networks. Bryan Hill, Vice President, Platform Engineering, joins us from Sonus to explore what microservices mean and how they are linked together in a cloud architecture.
We’ll also get into details about the orchestration mechanisms within OpenStack, discuss an OpenStack reference model, talk about how virtual network functions (VNFs) and microservices relate, and review several use cases.