In the cloud the Enterprises no longer have access to the physical or virtual network that is being provided by each major Cloud Service Provider. You have basic networking constructs in the cloud that are quite different from each cloud provider that is a black box. It is required to have a consistent SDN transit approach to be effective in a Multi-cloud world into the future when 5G rolls out, Edge technologies and mainly within the oncoming containerized API Matrix evolution to come., Telecom providers with MEC will put pressure on the large cloud providers where the hardware within the Cloud eco-system will become commoditized. Various new players introduced into Multi-cloud will evolve very quickly and transform where VPC and VNET will be at the edge and it will be a containerized world. Nutanix Cloud Flow needs to tranistion to a business model similar to Aviatrix Transit SDN approach. Kubernetes containers will be a game changer in the future where Nutanix will need to shift its efforts in becoming a truly Multi-Cloud OS by adopting and building on network constructs that extend everywhere defying network latency and application latency. Nutanix cannot solely rely on native constructs of the Cloud Providers where they deliberately do not provide good network transit service so your forced into Cloud vendor lock-in.
The clustering approach that Nutanix is offering now will work with the large Cloud Providers but in the future it will be an Aviatrix SDN transit model across all clouds and distributed edges that will prevail in an SDN API future matrix world where everything will be interconnected to be at the heart of doing commerce.
*Wire speed encryption to and from On-prem to the Cloud and edge. Inside the cloud they support 90 Gig of encryption.is key.
*Multi-Cloud Segmentation with a consistent connection policy across clouds and edge.
*Service insertion and chaining works very well in the three layer supported model of Aviatrix where the Application Layer at the top has smart intelligence communicating with the transit Aviatrix layer which has smart intelligence built-in communicating with the Access layer of the Aviatrix model connecting to all clouds of the future. Next-Gen Firewall and F5 Big –I P SSL decryption in a service chain works better within a SASE type model. Insertion and Service chaingin handled very seamlessly sending traffic for inspection with an Aviatrix type of SDN model where Flow needs to go.
*Strong Visibility into the cloud with Aviatrix Co-pilot is another game changer to gain visibility into the black box of Cloud to assist with troubleshooting. The Aviatrix multi-cloud backbone of SDN services with Controllers and Gateways is where Nutanix needs to go with Flow.
*Intially it might be easy to adopt native cloud resources in a multi-cloud world you need to inject a portable adoptable mechanism that will support VPC and VNET at the Edge as well as in the Cloud and On-Prem.
*How do you maintain accuracy as things flow and change within all of the different environments?
*IP reachability, symmetry, multiple path flows, DR scenarios, and traffic end-to-end correctness is end goal. How does the overall framework stay the same as things grow and change?
*If you stretch work-loads across clouds latency how can Nutanix help with all clouds to optimize at the network layer, down into the container level, and up into the application level so customers experience is delightful to concentrate on their business of transformation? Work-load latency will also include automation, AI, Machine Learning, etc. My recommendation is to seriously consider where a containerized world will be heading to where there will be many clouds and a transit layer is the glue to all of these new Cloud worlds that will evolve doing commerice within an API matrix.