> Isn't "keep the same interface when you move to the cloud" a desirable thing? NO. I wish I could somehow bold that and make it 100 pt size. The cloud is th

> Isn't "keep the same interface when you move to the cloud" a desirable thing? NO. I wish I could somehow bold that and make it 100 pt size. The cloud is the interface. It’s a distributed multi-tenant operating system with accounts, ACLs, event logs, scheduled tasks, processes (lambda), and so forth. Most critically: it has a fully virtualised software defined network already! Layering anything on top is absolute madness. It’s complex enough as it is. The built-in networking is integrated into the monitoring, has the same RBAC model as everything else, and can be templated out using a uniform API and declarative deployment syntax. Something like Cisco will sit on top of that like a steaming hot turd on a manicured lawn. Last but definitely not least: the cloud-native network is hardware accelerated into FPGAs (Azure) or custom silicon (AWS). There is absolutely no way for a vendor like Cisco to even begin to approach the scalability or the latency of the native network in software. A customer of mine has made the catastrophic mistake of adopting Aviatrix instead of educating their network team (or simply making them redundant.) Aviatrix introduced a latency overhead of 3-5ms within the same zone compared to the native latency of 80 microseconds! That’s a brutal amount of overhead for everyone else to pay for “our network staff act like dinosaurs before the impact and I’m too scared to tell them their careers are over”.