In the lead up to KubeCon + CloudNativeCon North America 2019, we are posting a series of blogs covering what we expect to be some of the most prevalent topics at the event. In last week’s post, we walked through the journey from the monolithic to the microservices-based application, outlining the benefits of speed and scale that microservices bring, with Kubernetes as the orchestrator of it all.
For Enterprises, the choice is always to seek ease of operations without sacrificing higher performance and reliability, tighter security, and not to forget agility and speed for their core business applications. But should that choice be a hard bargain?
It seems almost silly to suggest that the public cloud must be multicloud-ready. But this statement introduces that there is still a distinction between cloud and multicloud requirements. As companies prepare their migration to cloud, they will need to simultaneously understand how their cloud architectures must explicitly consider a multicloud future.
But is there really a difference between cloud and multicloud?
When the discussion of cloud or multicloud comes up in our industry, the conversation almost invariably defaults to data centers. Whether it’s the move to data center fabrics or the role of disaggregation or the market-wide interest in automation and DevOps, all roads seem to point to the place-in-network (PIN) at the center of both public and private cloud.
In a previous blog, I introduced some research that PwC conducted on the changing buying patterns around data center networking. The research was conducted over several months, featuring 35 live interviews and 235 unique survey responses coming primarily from CIOs and VPs of IT from a mix of global companies.