Multi-cloud networking - Why has it taken so long?
Multi-cloud networking universe
A couple of terms to understand.
Private cloud: A private cloud describes a datacenter built with current cloud technologies that runs “on-premises,” or is hosted and managed by an organization or an enterprise itself.
Public cloud: a public cloud is a pool of virtual resources—developed from hardware owned and managed by a third-party company—that is automatically provisioned and allocated among multiple clients through a self-service interface. It’s a straightforward way to scale out workloads that experience unexpected demand fluctuations.
Today’s public clouds aren’t usually deployed as a standalone infrastructure solution, but rather as part of a heterogeneous mix of environments that leads to higher security and performance; lower cost; and a wider availability of infrastructure, services, and applications.
Multicloud: Enterprises might need services or resources from multiple IaaS or PaaS services, such as Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP). In this case they need to connect their networking infrastructure to multiple clouds.
Hybrid cloud: When enterprises build distributed applications that share resources on both private and public clouds, it is generally referred to as hybrid cloud.
Multicloud networking (MCN): MCN technology provides the capability to build a logical, software- defined, secure network for cloud applications across multiple private clouds, datacenters, and public clouds.
I'm not going to say anything new but as we all know the main driver for multi-cloud networking is a term, we all have heard at least once in our lives, digital transformation.
The trend that's been pushed by boards and CEOs.
Organizations large and small need to connect critical data, applications, and cloud services.
Cloud services were adopted because they give enterprises a faster path to launch new services using flexible platforms that can be consumed as a service.
But I like to say don’t be in such a rush to reach a goal before you are ready. Sometimes we learn such a valuable lessons along the way.
If you take a pause and ask yourself what about connecting critical apps and data that may still reside in enterprise DC, manufacturing environments or compute environments at the edge?
Someone remembers IOT?
As companies move more and more to the public cloud there are some core challenges they start to face and that's not just around skills gap, time constraints or visibility gaps, but as they move slowly to the cloud the native networking and security constructs that CSPs provide to them is around 80-90% of what organizations want in terms of functionalities within their networking and security posture.
One of the big gaps that seems to be ubiquitous across multiple CSPs is the lack of visibility and lack of control.
What we see is a general industry trend that lot of enterprises starting to take a multi-vendor approach to solve a lot of these skills, performance and architecture gaps pulling in different well-known tools ( various vendors ) .... NGFW, ThousandEyes for visibility, they're pulling in SD-WAN and trying to put it up there from networking transit capabilities .... etc
What they end up doing is recreating a level of complexity that they try to remove by pulling in all these tools and technologies into the cloud.
The answer is so simple: networking is not simple.
Many conversation with end customers show that they don’t perceive traditional networking technologies as programmable, cloud-native solutions for connecting diverse infrastructure, including private networks and public cloud infrastructure.
What they need is MCN platform that can function as one large logical network.
Comments
Post a Comment