(upbeat music) >> Welcome back to Las Vegas everybody. You're watching theCUBE coverage of AWS reinvent 2021. I tell you this place is packed. It's quite amazing here, over 20,000 people, I'd say it's closer to 25, maybe 27,000, and it's whole overflow, lots going on in the evenings. It's quite remarkable and we're really happy to be part of this. Jay Turner is here, he's the Vice President of Development and Operations, at PCCW Global. He's joined by Garrett Lowell, Vice President of Ecosystem Partnerships for the Americas at PCCW Global. Guys, welcome to theCUBE. Thanks for coming on. >> Thank you. >> Thank you so much. Jay, maybe you could take us through, for those people who aren't familiar with your company, what do you guys do, what are you all about? >> PCCW Global is the international operating wing of Hong Kong telecom. If it's outside of Hong Kong, it's our network. We've got about 695,000 kilometers of diverse cable, we've got about 43, 44 terabit of capacity came into business in 2005, if my brain is serving me correctly right now. We have a very diverse and vast portfolio ranging all the way from satellite teleports, all the way to IP transit. We're a Tier 1 service provider from that perspective as well. We do one of everything when it comes to networking and that's really, what was the basis of Console Connect, was inventing a platform to really enable our users to capitalize on our network and our assets. >> Okay. 2005, obviously you predated Cloud, you laid a bunch of fibers struck it in the ocean, I mean, global networks. There was a big trend to do that you had to think, you had to go bigger, go home in that business, (laughing) all right. Console Connect is your platform, is that right? >> Jay: Yes. >> So explain- >> Yeah, sorry, Console Connect is a software defined interconnection platform. We built a user self-service portal. Users can allocate ports, they get the LOAs issued to them directly from the platform. And then once they've got an active port or they've come in via one of our partnerships, they can then provision connectivity across our platform. That may be extending to their data centers or extending to their branch office, or it could be building a circuit into the Cloud via direct connect, could be building a circuit into an internet exchange. All of those circuits are going to be across that 685,000 kilometers of diverse fiber rather than going across the public internet. >> When you started, it took some time obviously to build out that infrastructure and then the Cloud came into play, but it was still early days, but it sounds like you're taking the AWS Cloud model and applying that to your business, eliminate all that undifferentiated heavy lifting, if you will, like the visioning in management. >> Yeah, we've heard many people, and that's kind of the impetus of this was, I want to be directly connected to my end point. And how do I do that? AWS, yes, they had direct connect, but figuring out how to do that as an enterprise was challenging. So we said, hey, we'll automate that for you. Just tell us what region you want to connect to. And we'll do all the heavy lifting and we'll just hand you back a villain tag. You're good to go. So it's a classic case, okay. AWS has direct connect. People will go, oh, that's directly competitive, but it's now you're adding value on top of that. Right? >> Yeah. >> Describe where you fit, Garrett, inside of the AWS ecosystem. You look around this hall and it's just a huge growing ecosystem, where you fit inside of that ecosystem and then your ecosystem. What's that like? >> Where we fit into the AWS ecosystem, as Jay alluded to, we're adding value to our partners and customers where they can come in, not only are they able to access the AWS platform as well as other Cloud platforms, but they're also able to access each other. We have a marketplace in our platform, which allows our customers and partners to put a description of their services on the marketplace and advertise their capabilities out to the rest of the ecosystem of PCCW Global and Console Connect. >> And you're doing that inside of AWS, is that right or at least in part? >> No, that's not inside of AWS. >> So your platform is your platform. >> Yes. >> Your relationship with AWS is to superpower direct connect. Is that right or? >> So we're directly connected to AWS throughout the globe. And this allows our customers and partners to be able to utilize not only the PCCW global network, but also to expand that capability to the AWS platform in Cloud. >> So wherever there's a Cloud, you plug into it, okay? >> Garrett: That's correct. >> Jay: Yeah. And then another advantage, the customer, obviously doesn't have to be directly co-located with AWS. They don't have to be in the same geographical region. If for some reason you need to be connected to U.S. west, but you're in Frankfurt, fine, we'll back all the traffic for you. >> Dave: Does that happen a lot? >> It actually does. >> How come? What's the use case there. >> Global diversity is certainly one of them just being able to have multiple footprints. But the other thing that we're seeing more of late is these Cloud-based companies are beginning to be attracted to where their customers are located. So they'll start seeing these packets of views and they'll go, well, we're going to go into that region as well, stand up a VPC there. We want our customers then being able to directly connect to that asset that's closest to them. And then still be able to back call that traffic if necessary or take it wherever. >> What's the big macro trends in your business? Broadly you see cost per bit coming down, you see data consumption and usage going through the roof. How does that affect you? What are some of the big trends that you see? >> I think one of the biggest ones and one that we targeted with Console Connect, we were hearing a lot of customers going, the world's changing so dynamically. We don't know how to do a one-year forecast of bandwidth, much less a three-year, which is what a lot of contracts are asking us for. So we said, hey, how about one day? Can you do one day? (Dave laughs) Because that's what our granularity is. We allow for anything from one day up to three years right now, and then even within that term, we're dynamic. If something happens, if suddenly some product goes through the roof and you've suddenly got a spike in traffic, if a ship drags its anchor through a sub sea cable, and suddenly you're having to pivot, you just come into the platform, you click a couple of buttons, 20 seconds later, we've modified your bandwidth for you or we've provisioned a new circuit for you, we've got your backup going, whatever. Really at the end of the day, it's the customer paying for their network, so the customer should be the one making those decisions. >> How's that affect pricing? I presume or so, I can have one day to a three-year term, for example if I commit to three years, I get a better deal. Is that right, or? >> You do, but at the end of the day, it's actually pretty much a moderate, a better deal. We don't want to force the hand of the customer. If you signed a 12 month contract with us, we're going to give you a 3% discount. >> So it's not really, that's not a motivation to do it. It's just (indistinct) reduce the transaction complexity. And that's why you will sign up for a longer term not to get the big discount. >> Correct. And then, like I said, even within a longer contract, we're still going to allow you to flex and flow and modify if you need to, because it's your network. >> What kind of constraints do you put on that? Do I have to commit to a flow? And then everything above that is, I can flex up. Is that how it works? >> Yeah. >> Okay. And then, the more I commit to, the better the deal is, or not necessarily? >> No, it's pretty much flat rate. >> Okay, I'm going to commit and I'm going to say, all right, I know I'm going to use X, or sign up for that and anything over it, you're pretty flexible, I might get a few points if I sign up for more, somebody might want to optimize that if they're big enough. >> And another really neat advantage, the other complaint we heard from customers, they go, I need three different direct connect, I need to be connected to three different parties, but I don't want to run three different cross-connects and I don't want to have three different ports. That's just an expense and I don't want. And we, fine, take your one gig port run one gig of services on it. If that's 20 different services, we're fine. We allow you to multiplex your port and provision as- >> So awesome. I love that model. I know some software companies who I would recommend to take a look at that pricing model. So Garrett, how do you segment the ecosystem? How do you look at that? Maybe you could draw and paint a picture of the idea of partners and what they look like. I know there's not just one category, but, >> Sure. Our ideal partners are internet exchangers, Cloud partners and SAS providers, because a big piece of our business is migration to the Cloud, and the flexibility of our platform allows and encourages our SAS providers and SI partners to perform migration to the Cloud much easier in a flexible format for their customers. >> What can you tell us, any kind of metrics you can give us around your business to give a sense of the scope, the scale? >> Well, of our business, (Dave laughs) one of the driving factors here, Gardner says that about 2023, I think, 40% of the enterprise workloads will be deployed in the Cloud, which is all fine and dandy, except in my head, you're just trading one set of complexities for another. Instead of having everything in a glass house and being able to understand that, now you're going, it's in the Cloud, now I need to manage my connectivity there. wait a minute, are my security policies still the same? Do they apply if I'm going across the public internet? What exposure have I just bought into myself to try to run this? The platform really aims at normalizing that as much as possible. If you're directly connected to AWS, at the end of the day, that's a really long ethernet cable. So your a glass house just got a lot bigger, but you're still able to maintain and use the exact same policies and procedures that you've been using. That's really one of our guiding principles, is to reduce that complexity and make it very simple for the user. >> I understand that, cause in the early days of Cloud, a lot of enterprises, the CIOs, they were concerned about security, then I think they realized, ah, AWS has pretty good security. CIA is using it. But still people would say to me, it's not that it's best security, it's just different. You know, we move slow, Dave. How do you accommodate, there's that diversity, I mean, AWS is obviously matured, but are you suggesting that you can take my security edicts in my glass house and bring those into your networks and ultimately into the Cloud? Is that how it works? >> That's the goal. It's not going to be a panacea more than likely, but the more edicts that we can allow you to bring across and not have to go back and revamp and, the better for you as a customer and the better really for us, because it normalizes things, it makes it much easier for us to accommodate more and more users. >> And is it such now in the eco, is all the diversity in the ecosystem, is it such that there's enough common patterns you guys can accommodate most of those use cases? >> Yeah, absolutely. One of the key components is the fact that the platform runs on our MPLS network, which is inherently secure. It's not on the public internet anywhere. We do have internet on demand capability. So in the event that a customer wants access to the internet, no problem. We can accommodate this. And we also have 5G capability built into the platform to allow flexibility of location and flexibility of, I would say, standing up new customer locations. And then the other component of the security is the fact that the customers can bring their own security and apply anywhere. We're not blocking, we don't have any port filters or anything of this nature. >> If would think 5G actually, I could see people arguing both sides, but my sense is 5G is going to be a huge driver for your business cause it's going to just create so much more demand for your services, I think. I can see somebody arguing the counter about it. What's your point of view on that? >> No, I think that's a fair assessment. I think it's going to drive business for everyone here on the show floor and it's pushing those workloads more toward the edge, which is not an area that people were typically concerned with. The edge was just the door that they walked through. That's becoming much different now. We're also going to start seeing, and we're already seeing it, huge trends of moving that data at the edge rather than bringing it all the way back to a central warehouse and help ending it. The ability to have a dynamic platform where you can see exactly what your network's doing and in the push of a button, modify that, or provision new connectivity in response to how your business is performing. >> Yeah, ultimately it's all about the applications that are going to be driving demand for more data. That's just a tailwind for you guys. >> Yeah. You look at, some of the car companies are coming on, Tesla, you're drive around with like eight CPUs and I think communicating back over the air. >> Dave: Yeah, right. >> You start scaling that and you start getting into some some real bottlenecks. >> Amazing business you guys having obviously capital intensive, but once you get in there, you got a big moat. That is a matter of getting on a flywheel and innovating. Guys, congratulations on all the progress and so much for coming on theCUBE. >> Thanks for the time. >> Thank you very much. >> Great to meet you guys. Good luck. All right, thank you for watching. This is Dave Vellante for theCUBE, the leader in High-Tech Coverage. We'll be right back. (upbeat music)

(upbeat music) >> Welcome back to Las Vegas everybody. You are watching theCube's coverage of AWS reinvent 2021. I'll tell you this place is packed. It's quite amazing here over 20,000 people, I'd say it's closer to 25, maybe 27,000. And there's a little overflow, lots going on in the evenings. It's quite remarkable. And we're really happy to be part of this. Jay Turner is here, he's the vice president of development and ops at PCCW Global. He's joined by Garrett Lowell, vice-president of ecosystem partnerships for the Americas at PCCW Global. Guys, welcome to theCube. Thanks for coming on. >> Thank you so much. >> So, Jay, maybe you could take us through for those people who aren't familiar with your company, what do you guys do? What do you all about? >> Yes, so PCCW Global is the international operating wing of Hong Kong Telecom. So if it's outside of Hong Kong, it's our network. We've got about 695,000 kilometers of diverse cable. We've got about 43, 44 terabit of capacity. Came into business in 2005 if my brain is serving me correctly right now. So we have a very diverse and vast portfolio ranging all the way from satellite teleports, all the way to IP transit. We're a tier one service provider from that perspective as well. So we do one of everything when it comes to networking and that's really what was the basis of Console Connect, was inventing a platform to really enable our users to capitalize on that our network and our assets. >> Okay, so 2005, obviously you predated cloud, you laid a bunch of fibers, it's getting in the ocean, I mean, global networks, I mean, there was a big trend to do that and you had to think, you had to go bigger or go home and that business. >> Jay: Yes you had to do. >> So and Console Connect is your platform, is that right? So explain. >> Yeah, sorry. Yeah, Console Connect is our software defined interconnection platform. So we built a user self-service portal. Users can allocate ports, they get the LOAs issue to them directly from the platform. And then once they've got an active port or they've come in via one of our partnerships, they can then provision connectivity across our platform. And that may be extending to their data centers or extending or their branch office, or it could be building a circuit into the cloud via direct connect, could be building a circuit into an internet exchange. And all of those circuits are going to be across that 685,000 kilometers of diverse fiber rather than going across the public internet. >> So, when you started, it took some time obviously to build out that infrastructure and then the cloud came into play, but it was still early days, but it sounds like you're taking the cloud model, AWS Cloud model and applying that to your business, eliminate all that undifferentiated, heavy lifting, if you will, the visioning and management. >> Yeah, we've heard many people and that's kind of the impetus of this was, I want to be directly connected to my end point. And how do I do that? And AWS, yes, they had direct connect, but figuring out how to do that as an enterprise was challenging. So we said, hey, we'll automate that for you. Just tell us what region you want to connect to. And we'll do all the heavy lifting, and we'll just hand you back a villain tag. You're good to go. >> So it's a classic case of, okay, AWS has direct connect, people they go, "Ah, that's directly competitive, but it's not, you're adding value on top of that." Right. So describe where you fit Garrett inside of the AWS ecosystem. You look around this hall and it's just a huge growing ecosystem, where you fit inside of that ecosystem and then your ecosystem, what's that like? >> Okay, so where we fit into the AWS ecosystem, as Jay alluded to, we're adding value to our partners and customers where they can come in, not only are they able to access the AWS platform as well as other cloud platforms, but they're also able to access each other. So we have a marketplace in our platform, which allows our customers and partners to put a description of their services on the marketplace and advertise their capabilities out to the rest of the ecosystem of PCCW Global and Console Connect. >> Okay, so and you're doing that inside of AWS? I that right? Or at least in part? >> No, that's not inside of AWS. >> Okay, so your platform is your platform. >> Yes. >> And then, so your relationship with AWS is to sort of superpower direct connect, is that right or? >> So we're directly connected to AWS throughout the globe. And this allows our customers and partners to be able to utilize not only the PCCW Global network, but also to expand that capability to the AWS platform in clouds. >> Wherever there's a cloud you plug into it? Okay. >> That's correct. >> And then another advantage there is the customer, obviously doesn't have to be directly co-located with AWS. They don't have to be in the same geographic region. If for some reason you need to be connected to US West, but you're in Frankfurt, fine, we'll back all the traffic for you. >> Does that happen a lot? >> It actually does. >> How come? Why, what's the use case there? >> Global diversity is certainly one of them, just being able to have multiple footprints. But the other thing that we're seeing more of late is these cloud-based companies are beginning to kind of be attracted to where their customers are located. So they'll start seeing these pockets of use and they'll go, well, okay, we're going to go into that region as well, stand up a VPC there. And so then we want to our customers then being able to directly connect to that asset, that's closest to them. And then still be able to back call that traffic if necessary or take it wherever. >> What are the big, sort of macro trends in your business? I mean, broadly you see cost per bit coming down, you see data consumption and usage going through the roof. How does that affect you? What are some of the big trends that you see? >> I think one of the biggest ones and one that we targeted with Console Connect, we were hearing a lot of customers going, the world's changing so dynamically. We don't know how to do a one-year forecast of bandwidth, much less a three-year, which is what a lot of contracts are asking us for. So we said, hey, how about one day? Can you do one day? (Dave laughing) Because that's what our granularity is. So we allow for anything from one day up to three years right now, and then even within that term, we're dynamic. So if something happens, suddenly some product goes through the roof and you've suddenly got a spike in traffic. If a ship drags its anchor through a sub sea cable, and suddenly you're having to pivot, you just come into the platform, you click a couple of buttons, 20 seconds later, we've modified your bandwidth for you, or we've provisioned a new circuit for you. We've got your backup going whatever. Really at the end of the day, it's the customer paying for their network, so the customer should be the one making those decisions. >> How's that affect pricing? I presume, so I can have one date or a three-year term. Presume if I commit to three years, I get a better deal, is that right or? >> You do, but I mean, at the end of the day, it's actually pretty much a moderate, a better deal. We don't want to force the hand of the customer. So yeah, if you signed a 12 month contract with us, we're going to give you a 3% discount. >> Yeah, so it's not really, that's not a motivation to do it. Is just you want to reduce the transaction complexity. And that's why you would sign up for a longer term not to get the big discount. >> Correct. And then, like I said, even within a longer contract, we're still going to allow you to flex and flow and modify if you need to because it's your network. >> What kind of constraints do you put on that? Do I have to commit to a floor and then everything above that is I can flex up? Is that how it works? Okay. And then the more I commit to the better the deal is, or not necessarily? >> No, it's pretty much flat, right. >> So, okay. So I'm going to come in and I'm going to say, all right, I know I'm going to use X, I'll sign up for that and anything over it. You're pretty flexible, I might get a few points if I sign up for more, somebody might want to optimize that if they're big enough. >> And another really neat advantage, and the other complaint we heard from customers, they go, I need three different direct connect, or I need to be connected to three different parties, but I don't want to run three different cross-connects and I don't want to have three different ports. That's just an expense I don't want. And we say, fine, take your one gig port, run one gig of services on it, if that's 20 different services, we're fine. So we allow you to multiplex your port and provision- >> It's awesome. I love that model. I know some software companies who I would recommend take a look at that pricing model. So, Garrett, how do you segment the ecosystem? How do you look at that way? Maybe you could draw paint a picture sort of the, the ideal partners and what they look like. I know there's not just one category, but. >> Sure, so our ideal partners are internet exchanges, cloud partners, and SAS providers, because a big piece of our business is migration to the cloud. And the flexibility of our platform allows and encourages our SAS providers and SI partners to perform migration to the cloud much easier and flexible in a flexible format for their customers. >> Yeah, so what can you tell us, any kind of metrics you can give us around your business to give a sense of the the scope, the scale. >> Well, of our business, kind of one of the driving factors here, Gardner says that about 2023, I think 40% of the enterprise workloads will be deployed in the cloud, which is all fine and dandy, except in my head, you're just trading one set of complexities for another. So now, instead of having everything in a glass house and being able to kind of understand that now you're going, well, okay, so it's in the cloud now I need to manage my connectivity there. And, oh, well, wait a minute, are my security policies still the same? Do they apply if I'm going across the public internet? What exposure have I just, bought into myself to try to run this? So the platform really aims at normalizing that as much as possible. If you're directly connected to AWS, at the end of the day, that's a really long ethernet cable. So you're a glass house just got a lot bigger, but you're still able to maintain and use the exact same policies and procedures that you've been using. So that's really one of our guiding principles is to reduce that complexity and make it very simple for the user. >> Well, I don't understand, 'cause in the early days of cloud, a lot of enterprises, CIO they were concerned about security. And I think they realized that AWS has pretty good security, well, CIA is using it. But still people would say to me, it's not that it's bad security, it's just different. We move slow, Dave. So how do you accommodate, now I don't know, does that diversity, I mean, AWS has obviously matured, but are you suggesting that you can take my security edicts in my glass house and bring those into your networks and ultimately into the cloud? Is that kind of how it works? >> That's the goal. It's not going to be a panacea more than likely, but the more edicts that we can allow you to bring across and not have to go back and revamp and the better for you as a customer and the better really for us, because it normalizes things, it makes it much easier for us to accommodate more and more users. >> It is such now in the eco, it was all the diversity in the ecosystem. Is it such that there's enough common patterns that you you guys can kind of accommodate most of those use cases? >> Yeah, absolutely. I think the, one of the key components is the fact that the platform runs on our MPLS network, which is inherently secure. It's not on the public internet anywhere. Now we do have internet on demand capability. So in the event that a customer wants access to the internet, no problem, we can accommodate this. And we also have 5G capability built into the platform to allow flexibility of location and flexibility of... I would say, standing up new customer locations. And then the other component of the security is the fact that the customers can bring their own security and apply anywhere. So we're not blocking, we don't have any port filters or anything of this nature. >> Well, I would think 5G actually, I mean, I could see people arguing both sides, but my sense is 5G is going to be a huge driver for your business, 'cause it's going to just create so much more demand for your services I think, I could see somebody arguing the counter, but what's your point of view on that? >> No. I think that's a fair assessment. I think it's going to drive business for everyone here on the show floor. And it's pushing those workloads more toward the edge, which is not an area that people were typically concerned with. The edge was just the door that they walked through. That's becoming much different now. And we're also going to start seeing, and we're already seeing it, huge trends of moving that data at the edge, rather than bringing it all the way back to a central warehouse in Hare pending it. So, again, the ability to have a dynamic platform where you can see exactly what your network's doing and in the push of a button, modify that, or provision new connectivity in response to how your business is performing. >> Yeah, and ultimately it's all about the applications that are going to be driving demand for more data. And that's just a tailwind for you guys. >> Yeah, yeah and then you look at some of the car companies are coming on, you know, Tesla, you're driving around with like eight CPU's in that thing, communicating back over the air. >> Dave: Yeah right. >> You start scaling that, and you start getting into some real bottleneck. >> Amazing business you guys having, obviously capital intensive, but once you get in there, you've got a big moat, and then it's a matter of getting on a flywheel and innovating. Guys, congratulations on all the progress and thanks so much for coming on theCube. >> Yeah. No, thanks for the time. >> Thank you very much. >> Yeah, great to meet you guys. Good luck. All right. Thank you for watching. This is Dave Vellante for theCube, the leader in high-tech coverage, right back. (upbeat music)

(electronic music) >> From Santa Clara, California in the heart of Silicon Valley, its theCUBE. Covering Altitude 2020, brought to you by Aviatrix. (electronic music) >> Female pilot: Good morning, ladies and gentlemen, this is your captain speaking, we will soon be taking off on our way to altitude. (upbeat music) Please keep your seat belts fastened and remain in your seat. We will be experiencing turbulence, until we are above the clouds. (thunder blasting) (electronic music) (seatbelt alert sounds) Ladies and gentlemen, we are now cruising at altitude. Sit back and enjoy the ride. (electronic music) >> Female pilot: Altitude is a community of thought leaders and pioneers, cloud architects and enlightened network engineers, who have individually and are now collectively, leading their own IT teams and the industry. On a path to lift cloud networking above the clouds. Empowering enterprise IT to architect, design and control their own cloud network, regardless of the turbulent clouds beneath them. It's time to gain altitude. Ladies and gentlemen, Steve Mullaney, president and CEO of Aviatrix. The leader of multi-cloud networking. (electronic music) (audience clapping) >> Steve: All right. (audience clapping) Good morning everybody, here in Santa Clara as well as to the millions of people watching the livestream worldwide. Welcome to Altitude 2020, all right. So, we've got a fantastic event, today, I'm really excited about the speakers that we have today and the experts that we have and really excited to get started. So, one of the things I wanted to share was this is not a one-time event. This is not a one-time thing that we're going to do. Sorry for the Aviation analogy, but, you know, Sherry Wei, aviatrix means female pilot so everything we do has an aviation theme. This is a take-off, for a movement. This isn't an event, this is a take-off of a movement. A multi-cloud networking movement and community that we're inviting all of you to become part of. And why we're doing that, is we want to enable enterprises to rise above the clouds, so to speak and build their network architecture, regardless of which public cloud they're using. Whether it's one or more of these public clouds. So the good news, for today, there's lots of good news but this is one good news, is we don't have any PowerPoint presentations, no marketing speak. We know that marketing people have their own language. We're not using any of that, and no sales pitches, right? So instead, what are we doing? We're going to have expert panels, we've got Simon Richard, of Gartner here. We've got ten different network architects, cloud architects, real practitioners that are going to share their best practices and their real world experiences on their journey to the multi-cloud. So, before we start, everybody know what today is? In the U.S., it's Super Tuesday. I'm not going to get political, but Super Tuesday there was a bigger, Super Tuesday that happened 18 months ago. And Aviatrix employees know what I'm talking about. Eighteen months ago, on a Tuesday, every enterprise said, "I'm going to go to the cloud". And so what that was, was the Cambrian explosion, for cloud, for the enterprise. So, Frank Cabri, you know what a Cambrian explosion is. He had to look it up on Google. 500 million years ago, what happened, there was an explosion of life where it went from very simple single-cell organisms to very complex, multi-cell organisms. Guess what happened 18 months ago, on a Tuesday, I don't really know why, but every enterprise, like I said, all woke up that day and said, "Now I'm really going to go to cloud" and that Cambrian explosion of cloud meant that I'm moving from a very simple, single cloud, single-use case, simple environment, to a very complex, multi-cloud, complex use case environment. And what we're here today, is we're going to go undress that and how do you handle those, those complexities? And, when you look at what's happening, with customers right now, this is a business transformation, right? People like to talk about transitions, this is a transformation and it's actually not just a technology transformation, it's a business transformation. It started from the CEO and the Boards of enterprise customers where they said, "I have an existential threat to the survival of my company." If you look at every industry, who they're worried about is not the other 30-year-old enterprise. What they're worried about is the three year old enterprise that's leveraging cloud, that's leveraging AI, and that's where they fear that they're going to actually wiped out, right? And so, because of this existential threat, this is CEO led, this is Board led, this is not technology led, it is mandated in the organizations. We are going to digitally transform our enterprise, because of this existential threat and the movement to cloud is going to enable us to go do that. And so, IT is now put back in charge. If you think back just a few years ago, in cloud, it was led by DevOps, it was led by the applications and it was, like I said, before the Cambrian explosion, it was very simple. Now, with this Cambrian explosion, an enterprise is getting very serious and mission critical. They care about visibility, they care about control, they care about compliance, conformance, everything, governance. IT is in charge and that's why we're here today to discuss that. So, what we're going to do today, is much of things but we're going to validate this journey with customers. >> Steve: Did they see the same thing? We're going to validate the requirements for multi-cloud because, honestly, I've never met an enterprise that is not going to be multicloud. Many are one cloud today but they all say, " I need to architect my network for multiple clouds", because that's just what, the network is there to support the applications and the applications will run in whatever cloud it runs best in and you have to be prepared for that. The second thing is, is architecture. Again, with IT in charge, you, architecture matters. Whether its your career, whether its how you build your house, it doesn't matter. Horrible architecture, your life is horrible forever. Good architecture, your life is pretty good. So, we're going to talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network. If you don't get that right, nothing works, right? Way more important than compute. Way more important than storage. Network is the foundational element of your infrastructure. Then we're going to talk about day two operations. What does that mean? Well day one is one day of your life, where you wire things up they do and beyond. I tell everyone in networking and IT -- it's every day of your life. And if you don't get that right, your life is bad forever. And so things like operations, visibility, security, things like that, how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud, it's actually about how do I operationalize it? And that's a huge benefit that we bring as Aviatrix. And then the last thing we're going to talk and it's the last panel we have, I always sayyou can't forget about the humans, right? So all this technology, all these things that we're doing, it's always enabled by the humans. At the end of the day, if the humans fight it, it won't get deployed. And we have a massive skills gap, in cloud and we also have a massive skills shortage. You have everyone in the world trying to hire cloud network architects, right? There's just not enough of them going around. So, at Aviatrix, we said as leaders do, "We're going to help address that issue and try to create more people." We created a program, what we call the ACE Program, again, aviation theme, it stands for Aviatrix Certified Engineer. Very similar to what Cisco did with CCIEs where Cisco taught you about IP networking, a little bit of Cisco, we're doing the same thing, we're going to teach network architects about multicloud networking and architecture and yeah, you'll get a little bit of Aviatrix training in there, but this is the missing element for people's careers and also within their organizations. So we're going to go talk about that. So, great, great event, great show. We're going to try to keep it moving. I next want to introduce, my host, he is the best in the business, you guys have probably seen him multiple, many times, he is the co-CEO and co founder of theCUBE, John Furrier. (audience clapping) (electronic music) >> John: Okay, awesome, great speech there, awesome. >> Yeah. >> I totally agree with everything you said about the explosion happening and I'm excited, here at the heart of silicon valley to have this event. It's a special digital event with theCUBE and Aviatrix, where we're live-streaming to, millions of people, as you said, maybe not a million. >> Maybe not a million. (laughs) Really to take this program to the world and this is really special for me, because multi-cloud is the hottest wave in cloud. And cloud-native networking is fast becoming the key engine, of the innovations, so we got an hour and a half of action-packed programming. We have a customer panel. Two customer panels. Before that Gartner's going to come out, talk about the industry. We have global system integrators, that will talk about, how their advising and building these networks and cloud native networking. And then finally the ACE's, the Aviatrix Certified Engineers, are going to talk more about their certifications and the expertise needed. So, let's jump right in, let's ask, Simon Richard to come on stage, from Gartner. We'll kick it all off. (electronic music) (clapping) >> John: Hi, can I help you. Okay, so kicking things off, getting started. Gartner, the industry experts on cloud. Really kind of more, cue your background. Talk about your background before you got to Gartner? >> Simon: Before being at Gartner, I was a chief network architect, of a Fortune 500 company, that with thousands of sites over the world and I've been doing everything in IT from a C programmer, in the 90, to a security architect, to a network engineer, to finally becoming a network analyst. >> So you rode the wave. Now you're covering the marketplace with hybrid cloud and now moving quickly to multi-cloud, is really what everyone is talking about. >> Yes. >> Cloud-native's been discussed, but the networking piece is super important. How do you see that evolving? >> Well, the way we see Enterprise adapting, cloud. The first thing you do about networking, the initial phases they either go in a very ad hoc way. Is usually led by none IT, like a shadow IT, or application people, sometime a DevOps team and it just goes as, it's completely unplanned. They create VPC's left and right with different account and they create mesh to manage them and they have Direct Connect or Express Route to any of them. So that's the first approach and on the other side. again within our first approach you see what I call, the lift and shift. Where we see like enterprise IT trying to, basically replicate what they have in a data center, in the Cloud. So they spend a lot of time planning, doing Direct Connect, putting Cisco routers and F5 and Citrix and any checkpoint, Palo Alto device, that in a sense are removing that to the cloud. >> I got to ask you, the aha moment is going to come up a lot, in one our panels, is where people realize, that it's a multi-cloud world. I mean, they either inherit clouds, certainly they're using public cloud and on-premises is now more relevant than ever. When's that aha moment? That you're seeing, where people go, "Well I got to get my act together and get on this cloud." >> Well the first, right, even before multi-cloud. So there is two approach's. The first one, like the adult way doesn't scare. At some point IT has to save them, 'cause they don't think about the tools, they don't think about operation, they have a bunch of VPC and multiple cloud. The other way, if you do the lift and shift way, they cannot take any advantages of the cloud. They lose elasticity, auto-scaling, pay by the drink. All these agility features. So they both realize, okay, neither of these ways are good, so I have to optimize that. So I have to have a mix of what I call, the cloud native services, within each cloud. So they start adapting, like all the AWS Construct, Azure Construct or Google Construct and that's what I call the optimal phase. But even that they realize, after that, they are all very different, all these approaches different, the cloud are different. Identities is constantly, difficult to manage across clouds. I mean, for example, anybody who access' accounts, there's subscription, in Azure and GCP, their projects. It's a real mess, so they realized, well I don't really like constantly use the cloud product and every cloud, that doesn't work. So I have, I'm going multi-cloud, I like to abstract all of that. I still want to manage the cloud from an EPI point of view, I don't necessarily want to bring my incumbent data center products, but I have to do that and in a more EPI driven cloud environment. >> So, the not scaling piece that you where mentioning, that's because there's too many different clouds? >> Yes. >> That's the least they are, so what are they doing? What are they, building different development teams? Is it software? What's the solution? >> Well, the solution is to start architecting the cloud. That's the third phase. I called that the multi-cloud architect phase, where they have to think about abstraction that works across cloud. Fact, even across one cloud it might not scale as well, If you start having like ten thousand security agreement, anybody who has that doesn't scale. You have to manage that. If you have multiple VPC, it doesn't scale. You need a third-party, identity provider. In variously scales within one cloud, if you go multiple cloud, it gets worse and worse. >> Steve, weigh in here. What's your thoughts? >> I thought we said this wasn't going to be a sales pitch for Aviatrix. (laughter) You just said exactly what we do, so anyway, that's a joke. What do you see in terms of where people are, in that multi-cloud? So, like lot of people, you know, everyone I talk to, started at one cloud, right, but then they look and then say okay but I'm now going to move to Azure and I'm going to move to... (trails off) Do you see a similar thing? >> Well, yes. They are moving but there's not a lot of application, that uses three cloud at once, they move one app in Azure, one app in AWS and one app in Google. That's what we see so far. >> Okay, yeah, one of the mistakes that people think, is they think multi-cloud. No one is ever going to go multi-cloud, for arbitrage. They're not going to go and say, well, today I might go into Azure, 'cause I get a better rate on my instance. Do you agree? That's never going to happen. What I've seen with enterprise, is I'm going to put the workload in the app, the app decides where it runs best. That may be Azure, maybe Google and for different reasons and they're going to stick there and they're not going to move. >> Let me ask you guys-- >> But the infrastructure, has to be able to support, from a networking team. >> Yes. >> Be able to do that. Do you agree with that? >> Yes, I agree. And one thing is also very important, is connecting to the cloud, is kind of the easiest thing. So, the wide area network part of the cloud, connectivity to the cloud is kind of simple. >> Steve: I agree. >> IP's like VPN, Direct Connect, Express Route. That's the simple part, what's difficult and even the provisioning part is easy. You can use Terraform and create VPC's and Vnet's across your three cloud provider. >> Steve: Right. >> What's difficult is that they choose the operation. So we'll define day two operation. What does that actually mean? >> Its just the day to day operations, after you know, the natural, lets add an app, lets add a server, lets troubleshoot a problem. >> Something changes, now what do you do? >> So what's the big concerns? I want to just get back to the cloud native networking, because everyone kind of knows what cloud native apps are. That's been the hot trend. What is cloud native networking? How do you guys, define that? Because that seems to be the hardest part of the multi-cloud wave that's coming, is cloud native networking. >> Well there's no, you know, official Gartner definition but I can create one on the spot. >> John: Do it. (laughter) >> I just want to leverage the Cloud Construct and the cloud EPI. I don't want to have to install, like a... (trails off) For example, the first version was, let's put a virtual router that doesn't even understand the cloud environment. >> Right. If I have if I have to install a virtual machine, it has to be cloud aware. It has to understand the security group, if it's a router. It has to be programmable, to the cloud API. And understand the cloud environment. >> And one thing I hear a lot from either CSO's, CIO's or CXO's in general, is this idea of, I'm definitely not going API. So, its been an API economy. So API is key on that point, but then they say. Okay, I need to essentially have the right relationship with my suppliers, aka you called it above the clouds. So the question is... What do I do from an architectural standpoint? Do I just hire more developers and have different teams, because you mentioned that's a scale point. How do you solve this problem of, okay, I got AWS, I got GCP, or Azure, or whatever. Do I just have different teams or do I just expose EPI's? Where is that optimization? Where's the focus? >> Well, I think what you need, from a network point of view is a way, a control plane across the three clouds. And be able to use the API's of the cloud, to build networks but also to troubleshoot them and do day to day operation. So you need a view across the three clouds, that takes care of routing, connectivity. >> Steve: Performance. >> John: That's the Aviatrix plugin, right there. >> Steve: Yeah. So, how do you see, so again, your Gartner, you see the industry. You've been a network architect. How do you see this this playing out? What are the legacy incumbent client server, On Prem networking people, going to do? >> Well they need to.. >> Versus people like a Aviatrix? How do you see that playing out? >> Well obviously, all the incumbents, like Arista, Cisco, Juniper, NSX. >> Steve: Right. >> They want to basically do the lift and shift part, they want to bring, and you know, VMware want to bring in NSX on the cloud, they call that "NSX everywhere" and Cisco want to bring in ACI to the cloud, they call that "ACI Anywhere". So, everyone's.. (trails off) And then there's CloudVision from Arista, and Contrail is in the cloud. So, they just want to bring the management plane, in the cloud, but it's still based, most of them, is still based on putting a VM in them and controlling them. You extend your management console to the cloud, that's not truly cloud native. >> Right. >> Cloud native you almost have to build it from scratch. >> We like to call that cloud naive. >> Cloud naive, yeah. >> So close, one letter, right? >> Yes. >> That was a big.. (slurs) Reinvent, take the T out of Cloud Native. It's Cloud Naive. (laughter) >> That went super viral, you guys got T-shirts now. I know you're loving that. >> Steve: Yeah. >> But that really, ultimately, is kind of a double-edged sword. You can be naive on the architecture side and ruleing that. And also suppliers or can be naive. So how would you define who's naive and who's not? >> Well, in fact, their evolving as well, so for example, in Cisco, it's a little bit more native than other ones, because there really is, "ACI in the cloud", you can't really figure API's out of the cloud. NSX is going that way and so is Arista, but they're incumbent, they have their own tools, its difficult for them. They're moving slowly, so it's much easier to start from scratch. Even you, like, you know, a network company that started a few years ago. There's only really two, Aviatrix was the first one, they've been there for at least three or four years. >> Steve: Yeah. >> And there's other one's, like Akira, for example that just started. Now they're doing more connectivity, but they want to create an overlay network, across the cloud and start doing policies and things. Abstracting all the clouds within one platform. >> So, I got to ask you. I interviewed an executive at VMware, Sanjay Poonen, he said to me at RSA last week. Oh, there'll only be two networking vendors left, Cisco and VMware. (laughter) >> What's you're response to that? Obviously when you have these waves, these new brands that emerge, like Aviatrix and others. I think there'll be a lot of startups coming out of the woodwork. How do you respond to that comment? >> Well there's still a data center, there's still, like a lot, of action on campus and there's the wan. But from the cloud provisioning and cloud networking in general, I mean, they're behind I think. You know, you don't even need them to start with, you can, if you're small enough, you can just keep.. If you have AWS, you can use the AWS construct, they have to insert themselves, I mean, they're running behind. From my point of view. >> They are, certainly incumbents. I love the term Andy Jess uses at Amazon web services. He uses "Old guard, new guard", to talk about the industry. What does the new guard have to do? The new brands that are emerging. Is it be more DevOp's oriented? Is it NetSec ops? Is it NetOps? Is it programmability? These are some of the key discussions we've been having. What's your view, on how you see this programmability? >> The most important part is, they have to make the network simple for the Dev teams. You cannot make a phone call and get a Vline in two weeks anymore. So if you move to the cloud, you have to make that cloud construct as simple enough, so that for example, a Dev team could say, "Okay, I'm going to create this VPC, but this VPC automatically associates your account, you cannot go out on the internet. You have to go to the transit VPC, so there's lot of action in terms of, the IAM part and you have to put the control around them to. So to make it as simple as possible. >> You guys, both. You're the CEO of Aviatrix, but also you've got a lot of experience, going back to networking, going back to the, I call it the OSI days. For us old folks know what that means, but, you guys know what this means. I want to ask you the question. As you look at the future of networking, you hear a couple objections. "Oh, the cloud guys, they got networking, we're all set with them. How do you respond to the fact that networking's changing and the cloud guys have their own networking. What's some of the paying points that's going on premises of these enterprises? So are they good with the clouds? What needs... What are the key things that's going on in networking, that makes it more than just the cloud networking? What's your take on it? >> Well as I said earlier. Once you could easily provision in the cloud, you can easily connect to the cloud, its when you start troubleshooting applications in the cloud and try to scale. So that's where the problem occurred. >> Okay, what's your take on it. >> And you'll hear from the customers, that we have on stage and I think what happens is all the clouds by definition, designed to the 80-20 rule which means they'll design 80% of the basic functionality. And then lead to 20% extra functionality, that of course every Enterprise needs, to leave that to ISV's, like Aviatrix. Because why? Because they have to make money, they have a service and they can't have huge instances, for functionality that not everybody needs. So they have to design to the common and that, they all do it, right? They have to and then the extra, the problem is, that Cambrian explosion, that I talked about with enterprises. That's what they need. They're the ones who need that extra 20%. So that's what I see, there's always going to be that extra functionality. In an automated and simple way, that you talked about, but yet powerful. With the up with the visibility and control, that they expect of On Prem. That kind of combination, that Yin and the Yang, that people like us are providing. >> Simon I want to ask you? We're going to ask some of the cloud architect, customer panels, that same question. There's pioneer's doing some work here and there's also the laggards who come in behind their early adopters. What's going to be the tipping point? What are some of these conversations, that the cloud architects are having out there? Or what's the signs, that they need to be on this, multi-cloud or cloud native networking trend? What are some of the signal's that are going on in the environment? What are some of the thresholds? Are things that are going on, that they can pay attention to? >> Well, once they have the application on multiple cloud and they have to get wake up at two in the morning, to troubleshoot them. They'll know it's important. (laughter) So, I think that's when the rubber will hit the road. But, as I said, it's easier to prove, at any case. Okay, it's AWS, it's easy, user transit gateway, put a few VPC's and you're done. And you create some presents like Equinox and do a Direct Connect and Express Route with Azure. That looks simple, its the operations, that's when they'll realize. Okay, now I need to understand! How cloud networking works? I also need a tool, that gives me visibility and control. But not only that, I need to understand the basic underneath it as well. >> What are some of the day in the life scenarios. you envision happening with multi-cloud, because you think about what's happening. It kind of has that same vibe of interoperability, choice, multi-vendor, 'cause they're multi-cloud. Essentially multi-vendor. These are kind of old paradigms, that we've lived through with client server and internet working. What are some of the scenarios of success, that might be possible? Will be possible, with multi-cloud and cloud native networking. >> Well, I think, once you have good enough visibility, to satisfy your customers, not only, like to, keep the service running and application running. But to be able to provision fast enough, I think that's what you want to achieve. >> Simon, final question. Advice for folks watching on the Livestream, if they're sitting there as a cloud architect or CXO. What's your advice to them right now, in this market, 'cause obviously, public cloud check, hybrid cloud, they're working on that. That gets on premises done, now multi-cloud's right behind it. What's your advice? >> The first thing they should do, is really try to understand cloud networking. For each of their cloud providers and then understand the limitations. And, is what the cloud service provider offers enough? Or you need to look to a third party, but you don't look at a third party to start with. Especially an incumbent one, so it's tempting to say "I have a bunch of F5 experts", nothing against F5. I'm going to bring my F5 in the Cloud, when you can use an ELB, that automatically understand eases and auto scaling and so on. And you understand that's much simpler, but sometimes you need your F5, because you have requirements. You have like iRules and that kind of stuff, that you've used for years. 'cause you cannot do it. Okay, I have requirement and that's not met, I'm going to use Legacy Star and then you have to start thinking, okay, what about visibility control, above the true cloud. But before you do that you have to understand the limitations of the existing cloud providers. First, try to be as native as possible, until things don't work, after that you can start thinking of the cloud. >> Great insight, Simon. Thank you. >> That's great. >> With Gartner, thank you for sharing. (electronic music)

(electronic music) >> From Santa Clara, California in the heart of Silicon Valley, its theCUBE. Covering Altitude 2020, brought to you by Aviatrix. (electronic music) >> Female pilot: Good morning, ladies and gentlemen, this is your captain speaking, we will soon be taking off on our way to altitude. (upbeat music) Please keep your seat belts fastened and remain in your seat. We will be experiencing turbulence, until we are above the clouds. (thunder blasting) (electronic music) (seatbelt alert sounds) Ladies and gentlemen, we are now cruising at altitude. Sit back and enjoy the ride. (electronic music) >> Female pilot: Altitude is a community of thought leaders and pioneers, cloud architects and enlightened network engineers, who have individually and are now collectively, leading their own IT teams and the industry. On a path to lift cloud networking above the clouds. Empowering enterprise IT to architect, design and control their own cloud network, regardless of the turbulent clouds beneath them. It's time to gain altitude. Ladies and gentlemen, Steve Mullaney, president and CEO of Aviatrix. The leader of multi-cloud networking. (electronic music) (audience clapping) >> Steve: All right. (audience clapping) Good morning everybody, here in Santa Clara as well as to the millions of people watching the livestream worldwide. Welcome to Altitude 2020, all right. So, we've got a fantastic event, today, I'm really excited about the speakers that we have today and the experts that we have and really excited to get started. So, one of the things I wanted to share was this is not a one-time event. This is not a one-time thing that we're going to do. Sorry for the Aviation analogy, but, you know, Sherry Wei, aviatrix means female pilot so everything we do has an aviation theme. This is a take-off, for a movement. This isn't an event, this is a take-off of a movement. A multi-cloud networking movement and community that we're inviting all of you to become part of. And why we're doing that, is we want to enable enterprises to rise above the clouds, so to speak and build their network architecture, regardless of which public cloud they're using. Whether it's one or more of these public clouds. So the good news, for today, there's lots of good news but this is one good news, is we don't have any PowerPoint presentations, no marketing speak. We know that marketing people have their own language. We're not using any of that, and no sales pitches, right? So instead, what are we doing? We're going to have expert panels, we've got Simon Richard, of Gartner here. We've got ten different network architects, cloud architects, real practitioners that are going to share their best practices and their real world experiences on their journey to the multi-cloud. So, before we start, everybody know what today is? In the U.S., it's Super Tuesday. I'm not going to get political, but Super Tuesday there was a bigger, Super Tuesday that happened 18 months ago. And Aviatrix employees know what I'm talking about. Eighteen months ago, on a Tuesday, every enterprise said, "I'm going to go to the cloud". And so what that was, was the Cambrian explosion, for cloud, for the enterprise. So, Frank Cabri, you know what a Cambrian explosion is. He had to look it up on Google. 500 million years ago, what happened, there was an explosion of life where it went from very simple single-cell organisms to very complex, multi-cell organisms. Guess what happened 18 months ago, on a Tuesday, I don't really know why, but every enterprise, like I said, all woke up that day and said, "Now I'm really going to go to cloud" and that Cambrian explosion of cloud meant that I'm moving from a very simple, single cloud, single-use case, simple environment, to a very complex, multi-cloud, complex use case environment. And what we're here today, is we're going to go undress that and how do you handle those, those complexities? And, when you look at what's happening, with customers right now, this is a business transformation, right? People like to talk about transitions, this is a transformation and it's actually not just a technology transformation, it's a business transformation. It started from the CEO and the Boards of enterprise customers where they said, "I have an existential threat to the survival of my company." If you look at every industry, who they're worried about is not the other 30-year-old enterprise. What they're worried about is the three year old enterprise that's leveraging cloud, that's leveraging AI, and that's where they fear that they're going to actually wiped out, right? And so, because of this existential threat, this is CEO led, this is Board led, this is not technology led, it is mandated in the organizations. We are going to digitally transform our enterprise, because of this existential threat and the movement to cloud is going to enable us to go do that. And so, IT is now put back in charge. If you think back just a few years ago, in cloud, it was led by DevOps, it was led by the applications and it was, like I said, before the Cambrian explosion, it was very simple. Now, with this Cambrian explosion, an enterprise is getting very serious and mission critical. They care about visibility, they care about control, they care about compliance, conformance, everything, governance. IT is in charge and that's why we're here today to discuss that. So, what we're going to do today, is much of things but we're going to validate this journey with customers. >> Steve: Did they see the same thing? We're going to validate the requirements for multi-cloud because, honestly, I've never met an enterprise that is not going to be multicloud. Many are one cloud today but they all say, " I need to architect my network for multiple clouds", because that's just what, the network is there to support the applications and the applications will run in whatever cloud it runs best in and you have to be prepared for that. The second thing is, is architecture. Again, with IT in charge, you, architecture matters. Whether its your career, whether its how you build your house, it doesn't matter. Horrible architecture, your life is horrible forever. Good architecture, your life is pretty good. So, we're going to talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network. If you don't get that right, nothing works, right? Way more important than compute. Way more important than storage. Network is the foundational element of your infrastructure. Then we're going to talk about day two operations. What does that mean? Well day one is one day of your life, where you wire things up they do and beyond. I tell everyone in networking and IT -- it's every day of your life. And if you don't get that right, your life is bad forever. And so things like operations, visibility, security, things like that, how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud, it's actually about how do I operationalize it? And that's a huge benefit that we bring as Aviatrix. And then the last thing we're going to talk and it's the last panel we have, I always sayyou can't forget about the humans, right? So all this technology, all these things that we're doing, it's always enabled by the humans. At the end of the day, if the humans fight it, it won't get deployed. And we have a massive skills gap, in cloud and we also have a massive skills shortage. You have everyone in the world trying to hire cloud network architects, right? There's just not enough of them going around. So, at Aviatrix, we said as leaders do, "We're going to help address that issue and try to create more people." We created a program, what we call the ACE Program, again, aviation theme, it stands for Aviatrix Certified Engineer. Very similar to what Cisco did with CCIEs where Cisco taught you about IP networking, a little bit of Cisco, we're doing the same thing, we're going to teach network architects about multicloud networking and architecture and yeah, you'll get a little bit of Aviatrix training in there, but this is the missing element for people's careers and also within their organizations. So we're going to go talk about that. So, great, great event, great show. We're going to try to keep it moving. I next want to introduce, my host, he is the best in the business, you guys have probably seen him multiple, many times, he is the co-CEO and co founder of theCUBE, John Furrier. (audience clapping) (electronic music) >> John: Okay, awesome, great speech there, awesome. >> Yeah. >> I totally agree with everything you said about the explosion happening and I'm excited, here at the heart of silicon valley to have this event. It's a special digital event with theCUBE and Aviatrix, where we're live-streaming to, millions of people, as you said, maybe not a million. >> Maybe not a million. (laughs) Really to take this program to the world and this is really special for me, because multi-cloud is the hottest wave in cloud. And cloud-native networking is fast becoming the key engine, of the innovations, so we got an hour and a half of action-packed programming. We have a customer panel. Two customer panels. Before that Gartner's going to come out, talk about the industry. We have global system integrators, that will talk about, how their advising and building these networks and cloud native networking. And then finally the ACE's, the Aviatrix Certified Engineers, are going to talk more about their certifications and the expertise needed. So, let's jump right in, let's ask, Simon Richard to come on stage, from Gartner. We'll kick it all off. (electronic music) (clapping) >> John: Hi, can I help you. Okay, so kicking things off, getting started. Gartner, the industry experts on cloud. Really kind of more, cue your background. Talk about your background before you got to Gartner? >> Simon: Before being at Gartner, I was a chief network architect, of a Fortune 500 company, that with thousands of sites over the world and I've been doing everything in IT from a C programmer, in the 90, to a security architect, to a network engineer, to finally becoming a network analyst. >> So you rode the wave. Now you're covering the marketplace with hybrid cloud and now moving quickly to multi-cloud, is really what everyone is talking about. >> Yes. >> Cloud-native's been discussed, but the networking piece is super important. How do you see that evolving? >> Well, the way we see Enterprise adapting, cloud. The first thing you do about networking, the initial phases they either go in a very ad hoc way. Is usually led by none IT, like a shadow IT, or application people, sometime a DevOps team and it just goes as, it's completely unplanned. They create VPC's left and right with different account and they create mesh to manage them and they have Direct Connect or Express Route to any of them. So that's the first approach and on the other side. again within our first approach you see what I call, the lift and shift. Where we see like enterprise IT trying to, basically replicate what they have in a data center, in the Cloud. So they spend a lot of time planning, doing Direct Connect, putting Cisco routers and F5 and Citrix and any checkpoint, Palo Alto device, that in a sense are removing that to the cloud. >> I got to ask you, the aha moment is going to come up a lot, in one our panels, is where people realize, that it's a multi-cloud world. I mean, they either inherit clouds, certainly they're using public cloud and on-premises is now more relevant than ever. When's that aha moment? That you're seeing, where people go, "Well I got to get my act together and get on this cloud." >> Well the first, right, even before multi-cloud. So there is two approach's. The first one, like the adult way doesn't scare. At some point IT has to save them, 'cause they don't think about the tools, they don't think about operation, they have a bunch of VPC and multiple cloud. The other way, if you do the lift and shift way, they cannot take any advantages of the cloud. They lose elasticity, auto-scaling, pay by the drink. All these agility features. So they both realize, okay, neither of these ways are good, so I have to optimize that. So I have to have a mix of what I call, the cloud native services, within each cloud. So they start adapting, like all the AWS Construct, Azure Construct or Google Construct and that's what I call the optimal phase. But even that they realize, after that, they are all very different, all these approaches different, the cloud are different. Identities is constantly, difficult to manage across clouds. I mean, for example, anybody who access' accounts, there's subscription, in Azure and GCP, their projects. It's a real mess, so they realized, well I don't really like constantly use the cloud product and every cloud, that doesn't work. So I have, I'm going multi-cloud, I like to abstract all of that. I still want to manage the cloud from an EPI point of view, I don't necessarily want to bring my incumbent data center products, but I have to do that and in a more EPI driven cloud environment. >> So, the not scaling piece that you where mentioning, that's because there's too many different clouds? >> Yes. >> That's the least they are, so what are they doing? What are they, building different development teams? Is it software? What's the solution? >> Well, the solution is to start architecting the cloud. That's the third phase. I called that the multi-cloud architect phase, where they have to think about abstraction that works across cloud. Fact, even across one cloud it might not scale as well, If you start having like ten thousand security agreement, anybody who has that doesn't scale. You have to manage that. If you have multiple VPC, it doesn't scale. You need a third-party, identity provider. In variously scales within one cloud, if you go multiple cloud, it gets worse and worse. >> Steve, weigh in here. What's your thoughts? >> I thought we said this wasn't going to be a sales pitch for Aviatrix. (laughter) You just said exactly what we do, so anyway, that's a joke. What do you see in terms of where people are, in that multi-cloud? So, like lot of people, you know, everyone I talk to, started at one cloud, right, but then they look and then say okay but I'm now going to move to Azure and I'm going to move to... (trails off) Do you see a similar thing? >> Well, yes. They are moving but there's not a lot of application, that uses three cloud at once, they move one app in Azure, one app in AWS and one app in Google. That's what we see so far. >> Okay, yeah, one of the mistakes that people think, is they think multi-cloud. No one is ever going to go multi-cloud, for arbitrage. They're not going to go and say, well, today I might go into Azure, 'cause I get a better rate on my instance. Do you agree? That's never going to happen. What I've seen with enterprise, is I'm going to put the workload in the app, the app decides where it runs best. That may be Azure, maybe Google and for different reasons and they're going to stick there and they're not going to move. >> Let me ask you guys-- >> But the infrastructure, has to be able to support, from a networking team. >> Yes. >> Be able to do that. Do you agree with that? >> Yes, I agree. And one thing is also very important, is connecting to the cloud, is kind of the easiest thing. So, the wide area network part of the cloud, connectivity to the cloud is kind of simple. >> Steve: I agree. >> IP's like VPN, Direct Connect, Express Route. That's the simple part, what's difficult and even the provisioning part is easy. You can use Terraform and create VPC's and Vnet's across your three cloud provider. >> Steve: Right. >> What's difficult is that they choose the operation. So we'll define day two operation. What does that actually mean? >> Its just the day to day operations, after you know, the natural, lets add an app, lets add a server, lets troubleshoot a problem. >> Something changes, now what do you do? >> So what's the big concerns? I want to just get back to the cloud native networking, because everyone kind of knows what cloud native apps are. That's been the hot trend. What is cloud native networking? How do you guys, define that? Because that seems to be the hardest part of the multi-cloud wave that's coming, is cloud native networking. >> Well there's no, you know, official Gartner definition but I can create one on the spot. >> John: Do it. (laughter) >> I just want to leverage the Cloud Construct and the cloud EPI. I don't want to have to install, like a... (trails off) For example, the first version was, let's put a virtual router that doesn't even understand the cloud environment. >> Right. If I have if I have to install a virtual machine, it has to be cloud aware. It has to understand the security group, if it's a router. It has to be programmable, to the cloud API. And understand the cloud environment. >> And one thing I hear a lot from either CSO's, CIO's or CXO's in general, is this idea of, I'm definitely not going API. So, its been an API economy. So API is key on that point, but then they say. Okay, I need to essentially have the right relationship with my suppliers, aka you called it above the clouds. So the question is... What do I do from an architectural standpoint? Do I just hire more developers and have different teams, because you mentioned that's a scale point. How do you solve this problem of, okay, I got AWS, I got GCP, or Azure, or whatever. Do I just have different teams or do I just expose EPI's? Where is that optimization? Where's the focus? >> Well, I think what you need, from a network point of view is a way, a control plane across the three clouds. And be able to use the API's of the cloud, to build networks but also to troubleshoot them and do day to day operation. So you need a view across the three clouds, that takes care of routing, connectivity. >> Steve: Performance. >> John: That's the Aviatrix plugin, right there. >> Steve: Yeah. So, how do you see, so again, your Gartner, you see the industry. You've been a network architect. How do you see this this playing out? What are the legacy incumbent client server, On Prem networking people, going to do? >> Well they need to.. >> Versus people like a Aviatrix? How do you see that playing out? >> Well obviously, all the incumbents, like Arista, Cisco, Juniper, NSX. >> Steve: Right. >> They want to basically do the lift and shift part, they want to bring, and you know, VMware want to bring in NSX on the cloud, they call that "NSX everywhere" and Cisco want to bring in ACI to the cloud, they call that "ACI Anywhere". So, everyone's.. (trails off) And then there's CloudVision from Arista, and Contrail is in the cloud. So, they just want to bring the management plane, in the cloud, but it's still based, most of them, is still based on putting a VM in them and controlling them. You extend your management console to the cloud, that's not truly cloud native. >> Right. >> Cloud native you almost have to build it from scratch. >> We like to call that cloud naive. >> Cloud naive, yeah. >> So close, one letter, right? >> Yes. >> That was a big.. (slurs) Reinvent, take the T out of Cloud Native. It's Cloud Naive. (laughter) >> That went super viral, you guys got T-shirts now. I know you're loving that. >> Steve: Yeah. >> But that really, ultimately, is kind of a double-edged sword. You can be naive on the architecture side and ruleing that. And also suppliers or can be naive. So how would you define who's naive and who's not? >> Well, in fact, their evolving as well, so for example, in Cisco, it's a little bit more native than other ones, because there really is, "ACI in the cloud", you can't really figure API's out of the cloud. NSX is going that way and so is Arista, but they're incumbent, they have their own tools, its difficult for them. They're moving slowly, so it's much easier to start from scratch. Even you, like, you know, a network company that started a few years ago. There's only really two, Aviatrix was the first one, they've been there for at least three or four years. >> Steve: Yeah. >> And there's other one's, like Akira, for example that just started. Now they're doing more connectivity, but they want to create an overlay network, across the cloud and start doing policies and things. Abstracting all the clouds within one platform. >> So, I got to ask you. I interviewed an executive at VMware, Sanjay Poonen, he said to me at RSA last week. Oh, there'll only be two networking vendors left, Cisco and VMware. (laughter) >> What's you're response to that? Obviously when you have these waves, these new brands that emerge, like Aviatrix and others. I think there'll be a lot of startups coming out of the woodwork. How do you respond to that comment? >> Well there's still a data center, there's still, like a lot, of action on campus and there's the wan. But from the cloud provisioning and cloud networking in general, I mean, they're behind I think. You know, you don't even need them to start with, you can, if you're small enough, you can just keep.. If you have AWS, you can use the AWS construct, they have to insert themselves, I mean, they're running behind. From my point of view. >> They are, certainly incumbents. I love the term Andy Jess uses at Amazon web services. He uses "Old guard, new guard", to talk about the industry. What does the new guard have to do? The new brands that are emerging. Is it be more DevOp's oriented? Is it NetSec ops? Is it NetOps? Is it programmability? These are some of the key discussions we've been having. What's your view, on how you see this programmability? >> The most important part is, they have to make the network simple for the Dev teams. You cannot make a phone call and get a Vline in two weeks anymore. So if you move to the cloud, you have to make that cloud construct as simple enough, so that for example, a Dev team could say, "Okay, I'm going to create this VPC, but this VPC automatically associates your account, you cannot go out on the internet. You have to go to the transit VPC, so there's lot of action in terms of, the IAM part and you have to put the control around them to. So to make it as simple as possible. >> You guys, both. You're the CEO of Aviatrix, but also you've got a lot of experience, going back to networking, going back to the, I call it the OSI days. For us old folks know what that means, but, you guys know what this means. I want to ask you the question. As you look at the future of networking, you hear a couple objections. "Oh, the cloud guys, they got networking, we're all set with them. How do you respond to the fact that networking's changing and the cloud guys have their own networking. What's some of the paying points that's going on premises of these enterprises? So are they good with the clouds? What needs... What are the key things that's going on in networking, that makes it more than just the cloud networking? What's your take on it? >> Well as I said earlier. Once you could easily provision in the cloud, you can easily connect to the cloud, its when you start troubleshooting applications in the cloud and try to scale. So that's where the problem occurred. >> Okay, what's your take on it. >> And you'll hear from the customers, that we have on stage and I think what happens is all the clouds by definition, designed to the 80-20 rule which means they'll design 80% of the basic functionality. And then lead to 20% extra functionality, that of course every Enterprise needs, to leave that to ISV's, like Aviatrix. Because why? Because they have to make money, they have a service and they can't have huge instances, for functionality that not everybody needs. So they have to design to the common and that, they all do it, right? They have to and then the extra, the problem is, that Cambrian explosion, that I talked about with enterprises. That's what they need. They're the ones who need that extra 20%. So that's what I see, there's always going to be that extra functionality. In an automated and simple way, that you talked about, but yet powerful. With the up with the visibility and control, that they expect of On Prem. That kind of combination, that Yin and the Yang, that people like us are providing. >> Simon I want to ask you? We're going to ask some of the cloud architect, customer panels, that same question. There's pioneer's doing some work here and there's also the laggards who come in behind their early adopters. What's going to be the tipping point? What are some of these conversations, that the cloud architects are having out there? Or what's the signs, that they need to be on this, multi-cloud or cloud native networking trend? What are some of the signal's that are going on in the environment? What are some of the thresholds? Are things that are going on, that they can pay attention to? >> Well, once they have the application on multiple cloud and they have to get wake up at two in the morning, to troubleshoot them. They'll know it's important. (laughter) So, I think that's when the rubber will hit the road. But, as I said, it's easier to prove, at any case. Okay, it's AWS, it's easy, user transit gateway, put a few VPC's and you're done. And you create some presents like Equinox and do a Direct Connect and Express Route with Azure. That looks simple, its the operations, that's when they'll realize. Okay, now I need to understand! How cloud networking works? I also need a tool, that gives me visibility and control. But not only that, I need to understand the basic underneath it as well. >> What are some of the day in the life scenarios. you envision happening with multi-cloud, because you think about what's happening. It kind of has that same vibe of interoperability, choice, multi-vendor, 'cause they're multi-cloud. Essentially multi-vendor. These are kind of old paradigms, that we've lived through with client server and internet working. What are some of the scenarios of success, that might be possible? Will be possible, with multi-cloud and cloud native networking. >> Well, I think, once you have good enough visibility, to satisfy your customers, not only, like to, keep the service running and application running. But to be able to provision fast enough, I think that's what you want to achieve. >> Simon, final question. Advice for folks watching on the Livestream, if they're sitting there as a cloud architect or CXO. What's your advice to them right now, in this market, 'cause obviously, public cloud check, hybrid cloud, they're working on that. That gets on premises done, now multi-cloud's right behind it. What's your advice? >> The first thing they should do, is really try to understand cloud networking. For each of their cloud providers and then understand the limitations. And, is what the cloud service provider offers enough? Or you need to look to a third party, but you don't look at a third party to start with. Especially an incumbent one, so it's tempting to say "I have a bunch of F5 experts", nothing against F5. I'm going to bring my F5 in the Cloud, when you can use an ELB, that automatically understand eases and auto scaling and so on. And you understand that's much simpler, but sometimes you need your F5, because you have requirements. You have like iRules and that kind of stuff, that you've used for years. 'cause you cannot do it. Okay, I have requirement and that's not met, I'm going to use Legacy Star and then you have to start thinking, okay, what about visibility control, above the true cloud. But before you do that you have to understand the limitations of the existing cloud providers. First, try to be as native as possible, until things don't work, after that you can start thinking of the cloud. >> Great insight, Simon. Thank you. >> That's great. >> With Gartner, thank you for sharing. (electronic music) >> Welcome back to ALTITUDE 2020. For the folks in the live stream, I'm John Furrier, Steve Mullaney, CEO of Aviatrix. For our first of two customer panels with cloud network architects, we've got Bobby Willoughby, AEGON Luis Castillo from National Instruments and David Shinnick with FactSet. Guys, welcome to the stage for this digital event. Come on up. (audience clapping) (upbeat music) Hey good to see you, thank you. Customer panel, this is my favorite part. We get to hear the real scoop, we get the Gardener giving us the industry overview. Certainly, multi-cloud is very relevant, and cloud-native networking is a hot trend with the live stream out there in the digital events. So guys, let's get into it. The journey is, you guys are pioneering this journey of multi-cloud and cloud-native networking and are soon going to be a lot more coming. So I want to get into the journey. What's it been like? Is it real? You've got a lot of scar tissue? What are some of the learnings? >> Absolutely. Multi-cloud is whether or not we accept it, as network engineers is a reality. Like Steve said, about two years ago, companies really decided to just bite the bullet and move there. Whether or not we accept that fact, we need to not create a consistent architecture across multiple clouds. And that is challenging without orchestration layers as you start managing different tool sets and different languages across different clouds. So it's really important to start thinking about that. >> Guys on the other panelists here, there's different phases of this journey. Some come at it from a networking perspective, some come in from a problem troubleshooting, what's your experiences? >> From a networking perspective, it's been incredibly exciting, it's kind of once in a generational opportunity to look at how you're building out your network. You can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years, but it just never really worked on-prem. So it's really exciting to look at all the opportunities that we have and all of the interesting challenges that come up that you get to tackle. >> And effects that you guys are mostly AWS, right? >> Yeah. Right now though, we are looking at multiple clouds. We have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon. >> And you've seen it from a networking perspective, that's where you guys are coming at it from? >> Yup. >> Awesome. How about you? >> We evolve more from a customer requirement perspective. Started out primarily as AWS, but as the customer needed more resources from Azure like HPC, Azure AD, things like that, even recently, Google analytics, our journey has evolved into more of a multi-cloud environment. >> Steve, weigh in on the architecture because this is going to be a big conversation, and I wanted you to lead this section. >> I think you guys agree the journey, it seems like the journey started a couple of years ago. Got real serious, the need for multi-cloud, whether you're there today. Of course, it's going to be there in the future. So that's really important. I think the next thing is just architecture. I'd love to hear what you, had some comments about architecture matters, it all starts, every enterprise I talked to. Maybe talk about architecture and the importance of architects, maybe Bobby. >> From architecture perspective, we started our journey five years ago. >> Wow, okay. >> And we're just now starting our fourth evolution over network architect. And we call it networking security net sec, versus just as network. And that fourth-generation architecture should be based primarily upon the Palo Alto Networks and Aviatrix. Aviatrix to new orchestration piece of it. But that journey came because of the need for simplicity, the need for a multi-cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along. >> I guess the other question I also had around architecture is also... Luis maybe just talk about it. I know we've talked a little bit about scripting, and some of your thoughts on that. >> Absolutely. So for us, we started creating the network constructs with cloud formation, and we've stuck with that for the most part. What's interesting about that is today, on-premise, we have a lot of automation around how we provision networks, but cloud formation has become a little bit like the new manual for us. We're now having issues with having to automate that component and making it consistent with our on-premise architecture and making it consistent with Azure architecture and Google cloud. So, it's really interesting to see companies now bring that layer of abstraction that SD-WAN brought to the wound side, now it's going up into the cloud networking architecture. >> Great. So on the fourth generation, you mentioned you're on the fourth-gen architecture. What have you learned? Is there any lessons, scratch issue, what to avoid, what worked? What was the path that you touched? >> It's probably the biggest lesson there is that when you think you finally figured it out, you haven't. Amazon will change something, Azure change something. Transit Gateway is a game-changer. And listening to the business requirements is probably the biggest thing we need to do upfront. But I think from a simplicity perspective, like I said, we don't want to do things four times. We want to do things one time, we want be able to write to an API which Aviatrix has and have them do the orchestration for us. So that we don't have to do it four times. >> How important is architecture in the progression? Is it do you guys get thrown in the deep end, to solve these problems, are you guys zooming out and looking at it? How are you guys looking at the architecture? >> You can't get off the ground if you don't have the network there. So all of those, we've gone through similar evolutions, we're on our fourth or fifth evolution. I think about what we started off with Amazon without Direct Connect Gateway, without Transit Gateway, without a lot of the things that are available today, kind of the 80, 20 that Steve was talking about. Just because it wasn't there doesn't mean we didn't need it. So we needed to figure out a way to do it, we couldn't say, "Oh, you need to come back to the network team in a year, and maybe Amazon will have a solution for it." We need to do it now and evolve later and maybe optimize or change the way you're doing things in the future. But don't sit around and wait, you can't. >> I'd love to have you guys each individually answer this question for the live streams that comes up a lot. A lot of cloud architects out in the community, what should they be thinking about the folks that are coming into this proactively and, or realizing the business benefits are there? What advice would you guys give them on architecture? What should be they'd be thinking about, and what are some guiding principles you could share? >> So I would start with looking at an architecture model that can spread and give consistency to the different cloud vendors that you will absolutely have to support. Cloud vendors tend to want to pull you into using their native tool set, and that's good if only it was realistic to talk about only one cloud. But because it doesn't, it's super important to talk about, and have a conversation with the business and with your technology teams about a consistent model. >> And how do I do my day one work so that I'm not spending 80% of my time troubleshooting or managing my network? Because if I'm doing that, then I'm missing out on ways that I can make improvements or embrace new technologies. So it's really important early on to figure out, how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on? >> Bobby, your advice there, architecture. >> I don't know what else I can add to that. Simplicity of operations is key. >> So the holistic view of day two operations you mentioned, let's can jump in day one as you're getting stuff set up, day two is your life after. This is kind of of what you're getting at, David. So what does that look like? What are you envisioning as you look at that 20-mile stair, out post multi-cloud world? What are some of the things that you want in the day two operations? >> Infrastructure as code is really important to us. So how do we design it so that we can start fit start making network changes and fitting them into a release pipeline and start looking at it like that, rather than somebody logging into a router CLI and troubleshooting things in an ad hoc nature? So, moving more towards a dev-ops model. >> You guys, anything to add on that day two? >> Yeah, I would love to add something. In terms of day two operations you can either sort of ignore the day two operations for a little while, where you get your feet wet, or you can start approaching it from the beginning. The fact is that the cloud-native tools don't have a lot of maturity in that space and when you run into an issue, you're going to end up having a bad day, going through millions and millions of logs just to try to understand what's going on. That's something that the industry just now is beginning to realize it's such a big gap. >> I think that's key because for us, we're moving to more of an event-driven or operations. In the past, monitoring got the job done. It's impossible to monitor something that is not there when the event happens. So the event-driven application and then detection is important. >> Gardner is all about the cloud-native wave coming into networking. That's going to be a serious thing. I want to get your guys' perspective, I know you have each different views of how you come into the journey and how you're executing. And I always say the beauty's in the eye of the beholder and that applies to how the network's laid out. So, Bobby, you guys do a lot of high-performance encryption, both on AWS and Azure. That's a unique thing for you. How are you seeing that impact with multi-cloud? >> That's a new requirement for us too, where we have an increment to encrypt. And then if you ever get the question, should I encrypt, should I not encrypt? The answer is always yes. You should encrypt when you can encrypt. For our perspective, we need to migrate a bunch of data from our data centers. We have some huge data centers, and getting that data to the cloud is a timely expense in some cases. So we have been mandated, we have to encrypt everything, leave in the data center. So we're looking at using the Aviatrix insane mode appliances to be able to encrypt 10, 20 gigabits of data as it moves to the cloud itself. >> David, you're using Terraform, you've got FireNet, you've got a lot of complexity in your network. What do you guys look at the future for your environment? >> So many exciting that we're working on now as FireNet. So for our security team that obviously have a lot of knowledge base around Palo Alto, and with our commitments to our clients, it's not very easy to shift your security model to a specific cloud vendor. So there's a lot of SOC 2 compliance and things like that were being able to take some of what you've worked on for years on-prem and put it in the cloud and have the same type of assurance that things are going to work and be secure in the same way that they are on-prem, helps make that journey into the cloud a lot easier. >> And Louis, you guys got scripting, you got a lot of things going on. What's your unique angle on this? >> Absolutely. So for disclosure, I'm not an Aviatrix customer yet. (laughs) >> It's okay, we want to hear the truth, so that's good. Tell us, what are you thinking about? What's on your mind? >> When you talk about implementing a tool like this, it's really just really important to talk about automation focus on value. When you talk about things like encryption and things like so you're encrypting tunnels and encrypting the path, and those things should be second nature really. When you look at building those back-ends and managing them with your team, it becomes really painful. So tools like Aviatrix that add a lot automation it's out of sight, out of mind. You can focus on the value, and you don't have to focus on this. >> So I got to ask you guys. I see Aviatrix was here, they're supplier to this sector, but you guys are customers. Everyone's pitching your stuff, people knock on you, "Buy my stuff." How do you guys have that conversation with the suppliers, like the cloud vendors and other folks? What's it like? We're API all the way? You've got to support this? What are some of your requirements? How do you talk to and evaluate people that walk in and want to knock on your door and pitch you something? What's the conversation like? >> It's definitely API driven. We definitely look at the API structure that the vendors provide before we select anything. That is always first of mine and also, what problem are we really trying to solve? Usually, people try to sell or try to give us something that isn't really valuable, like implementing a Cisco solution on the cloud doesn't really add a lot of value, that's where we go. >> David, what's your conversation like with suppliers? Do you have a certain new way to do things? As it becomes more agile, essentially networking, and getting more dynamic, what are some of the conversations with either in commits or new vendors that you're having? What do you require? >> Ease of use is definitely high up there. We've had some vendors come in and say, "Hey, when you go to set this up, "we're going to want to send somebody on-site." And they're going to sit with you for a day to configure it. And that's a red flag. Well, wait a minute, do we really, if one of my really talented engineers can't figure it out on his own, what's going on there and why is that? Having some ease of use and the team being comfortable with it and understanding it is really important. >> Bobby, how about you? Old days was, do a bake-off and the winner takes all. Is it like that anymore? What's evolving? Bake-off last year for but still win. But that's different now because now when you get the product, you can install the product in AWS and Azure, have it up running in a matter of minutes. So the key is that can you be operational within hours or days instead of weeks? But do we also have the flexibility to customize it, to meet your needs? Because you don't want to be put into a box with the other customers when you have needs that are past their needs. >> I can almost see the challenge that you guys are living, where you've got the cloud immediate value, depending how you can roll up any solutions, but then you might have other needs. So you've got to be careful not to buy into stuff that's not shipping. So you're trying to be proactive and at the same time, deal with what you got. How do you guys see that evolving? Because multi-cloud to me is definitely relevant, but it's not yet clear how to implement across. How do you guys look at this baked versus future solutions coming? How do you balance that? >> Again, so right now, we're taking the ad hoc approach and experimenting what the different concepts of cloud are and really leveraging the native constructs of each cloud. But there's a breaking point for sure. You don't get to scale this like someone said, and you have to focus on being able to deliver, developers their sandbox or their play area for the things that they're trying to build quickly. And the only way to do that is with some consistent orchestration layer that allows you to-- >> So you expect a lot more stuff to becoming pretty quickly in that area. >> I do expect things to start maturing quite quickly this year. >> And you guys see similar trend, new stuff coming fast? >> Yeah. Probably the biggest challenge we've got now is being able to segment within the network, being able to provide segmentation between production, non-production workloads, even businesses, because we support many businesses worldwide and isolation between those is a key criteria there. So the ability to identify and quickly isolate those workloads is key. So the CIOs that are watching are saying, "Hey, take that hill, do multi-cloud." And then you have the bottoms up organization, "Pause, you're like off a little bit, it's not how it works." What is the reality in terms of implementing as fast as possible? Because the business benefits are clear, but it's not always clear on the technology how to move that fast. What are some of the barriers, what are the blockers, what are the enablers? >> I think the reality is that you may not think you're multi-cloud, but your business is. So I think the biggest barrier there is understanding what the requirements are and how best to meet those requirements in a secure manner. Because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that it was a tier-three application and the data center, it doesn't have to be a tier-three application in the cloud. So, lift and shift is not the way to go. >> Scale is a big part of what I see is the competitive advantage by these clouds and used to be proprietary network stacks in the old days, and then open systems came, that was a good thing. But as cloud has become bigger, there's an inherent lock-in there with the scale. How do you guys keep the choice open? How are you guys thinking about interoperability? What are some of the conversations that you guys are having around those key concepts? >> When we look at from a networking perspective, it's really key for you to just enable all the class to be able to communicate between them. Developers will find a way to use the cloud that best suits their business needs. And like you said, it's whether you're in denial or not, of the multi-cloud fact that your company is in already that's it becomes really important for you to move quickly. >> Yeah. And a lot of it also hinges on how well is the provider embracing what that specific cloud is doing? So, are they swimming with Amazon or Azure and just helping facilitate things, and they're doing the heavy lifting API work for you? Or are they swimming upstream and they're trying to hack it all together in messy way? And so that helps you stay out of the lock-in because there, if they're using Amazon native tools to help you get where you need to be, it's not like Amazon is going to release something in the future that completely makes you have designed yourself into a corner. So the closer, more than cloud-native they are, the more, the easier it is to deploy. >> Which also need to be aligned in such a way that you can take advantage of those cloud-native technologies. Will it make sense? TGW is a gamechanger in terms of cost and performance. So to completely ignore that, would be wrong. But if you needed to have encryption, TGW is not encrypted, so you need to have some type of Gateway to do the VPN encryption. So, the Aviatrix tool will give you the beauty of both worlds. You can use TGW or the Gateway. Real quick on the last minute we have, I want to just get a quick feedback from you guys. I hear a lot of people say to me, "Hey, pick the best cloud for the workload you got, then figure out multicloud behind the scenes." Do you guys agree with that? Do I go more to one cloud across the whole company or this workload works great on AWS, that workload works great on this. From a cloud standpoint, do you agree with that premise, and then when is multi-cloud stitching altogether? >> From an application perspective, it can be per workload, but it can also be an economical decision, certain enterprise contracts will pull you in one direction to add value, but the network problem is still the same. >> It doesn't go away. >> You don't want to be trying to fit a square into a round hall. If it works better on that cloud provider, then it's our job to make sure that service is there and people can use it. >> I agree, you just need to stay ahead of the game, make sure that the network infrastructure is there, security is available and is multi-cloud capable. >> At the end of the day, you guys are just validating that it's the networking game now. Cloud storage, compute check, networking is where the action is. Awesome. Thanks for your insights guys, appreciate you coming on the panel. Appreciate it, thanks. (upbeat music) >> John: Our next customer panel, got great another set of cloud network architects, Justin Smith with Zuora, Justin Brodley with EllieMae and Amit Utreja with Coupa. Welcome to stage. (audience applauds) (upbeat music) >> All right, thank you. >> How are ya? >> Thank you. Thank You. >> Hey Amit. How are ya? >> Did he say it right? >> Yeah. >> Okay he's got all the cliff notes from the last session, welcome back. Rinse and repeat. We're going to go into the hood a little bit. And I think they nailed what we've been reporting, we've been having this conversation around, networking is where the action is because that's at the end of the day you got to move packet from A to B and you got workloads exchanging data. So it's really killer. So let's get started. Amit, what are you seeing as the journey of multicloud as you go under the hood and say, "Okay, I got to implement this. "I have to engineer the network, "make it enabling, make it programmable, "make it interoperable across clouds." That almost sounds impossible to me. What's your take? >> Yeah, it seems impossible but if you are running an organization which is running infrastructure as a code it is easily doable. Like you can use tools out there that's available today, you can use third party products that can do a better job. But put your architecture first, don't wait. Architecture may not be perfect, put the best architecture that's available today and be agile, to iterate and make improvements over the time. >> We get to Justin's over here, so I have to be careful when I point a question to Justin, they both have the answer. Okay, journeys, what's the journey been like? Is there phases, We heard that from Gardner, people come into multicloud and cloud native networking from different perspectives? What's your take on the journey, Justin? >> Yeah, from our perspective, we started out very much focused on one cloud and as we've started doing acquisitions, we started doing new products to the market, the need for multicloud becomes very apparent, very quickly for us. And so having an architecture that we can plug and play into and be able to add and change things as it changes is super important for what we're doing in the space. >> Justin, your journey. >> Yes. For us, we were very ad hoc oriented and the idea is that we were reinventing all the time, trying to move into these new things and coming up with great new ideas. And so rather than it being some iterative approach with our deployments that became a number of different deployments. And so we shifted that toward and the network has been a real enabler of this. There's one network and it touches whatever cloud we want it to touch, and it touches the data centers that we need it to touch, and it touches the customers that we needed to touch. Our job is to make sure that the services that are available in one of those locations are available in all of the locations. So the idea is not that we need to come up with this new solution every time, it's that we're just iterating on what we've already decided to do. >> Before we get the architecture section, I want to ask you guys a question? I'm a big fan of let the app developers have infrastructure as code, so check. But having the right cloud run that workload, I'm a big fan of that, if it works great. But we just heard from the other panel, you can't change the network. So I want to get your thoughts, what is cloud native networking? And is that the engine really, that's the enabler for this multicloud trend? What's you guys take? We'll start with Amit, what do you think about that? >> Yeah, so you're going to have workloads running in different clouds and the workloads would have affinity to one cloud or other. But how you expose that it's a matter of how you are going to build your networks. How you're going to run security. How you're going to do egress, ingress out of it so -- >> You said networking is the big problem to solve. >> Yes. >> What's the solution? What's the key pain points and problem statement? >> The key pain point for most companies is how do you take your traditionally on premise network and then blow it out to the cloud in a way that makes sense. You have IP conflicts, you have IP space, you have public IPs on premise as well as in the cloud. And how do you kind of make sense of all of that? And I think that's where tools like Aviatrix make a lot of sense in that space. >> From our side, it's really simple. It's a latency, it's bandwidth and availability. These don't change whether we're talking about cloud or data center, or even corporate IT networking. So our job when these all of these things are simplified into like, S3, for instance and our developers want to use those. We have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources. We have to support these requirements and these wants, as opposed to saying, "Hey, that's not a good idea." No, our job is to enable them not to disable them. >> Do you guys think infrastructure is code? Which I love that, I think that's the future in this. We even saw that with DevOps. But as you start getting the networking, is it getting down to the network portion where its network as code? Because storage and compute working really well, we're seeing all Kubernetes on service mesh trend. Network has code, reality is it there? Is it still got work to do? >> It's absolutely there, you mentioned net DevOps and it's very real. In Coupa we build our networks through terraform and not only just terraform, build an API so that we can consistently build VNets and VPC all across in the same way. >> So you guys are doing it? >> Yup. And even security groups. And then on top and Aviatrix comes in, we can peer the networks bridge all the different regions through code. >> Same with you guys. >> Yeah. >> What do you think about this? >> Everything we deploy is done with automation and then we also run things like Lambda on top to make changes in real time, we don't make manual changes on our network. In the data center, funny enough, it's still manual but the cloud has enabled us to move into this automation mindset. And all my guys, that's what they focus on is bringing, now what they're doing in the cloud into the data center, which is kind of opposite of what it should be or what it used to be. >> It's full DevOps then? >> Yes. >> For us, it was similar on-prem is still somewhat very manual, although we're moving more and more to ninja and terraform type concepts. But everything in the production environment is code, confirmation terraform code and now coming into the data center same (mumbles). >> So I just wanted to jump in Justin Smith, one of the comment that you made, because it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud. And once you have your strategic architecture, what do you do? You push that everywhere. So what you used to see at the beginning of cloud was pushing the architecture on-prem into cloud. Now, I want to pick up on what you said, do you others agree that the center of gravity is here, I'm now pushing what I do in the cloud back into on-prem? And then so first that and then also in the journey, where are you at from zero to 100 of actually in the journey to cloud? Are you 50% there, are you 10%? Are you evacuating data centers next year? Where are you guys at? >> Yeah, so there's there's two types of gravity that you typically are dealing with, with the migration. First is data, gravity and your data set, and where that data lives. And then the second is the network platform that wraps all that together. In our case, the data gravity solely mostly on-prem but our network is now extending out to the app tier, it's going to be in cloud. Eventually, that data, gravity will also move to cloud as we start getting more sophisticated but in our journey, we're about halfway there. About halfway through the process, we're taking a handle of lift and shift and -- >> Steve: And when did that start? >> We started about three years ago. >> Okay, okay. >> Well for Coupa it's a very different story. It started from a garage and 100% on the cloud. So it's a business plan management platform, software as a service run 100% on the cloud. >> That was was like 10 years ago, right? >> Yes. >> Yeah. >> You guys are riding the wave of the architecture. Justin I want to ask you, Zuora, you guys mentioned DevOps. Obviously, we saw the huge observability wave, which essentially network management for the cloud, in my opinion. It's more dynamic, but this is about visibility. We heard from the last panel you don't know what's being turned on or turned off from a services standpoint, at any given time. How is all this playing out when you start getting into the DevOps down (mumbles)? >> This is the big challenge for all of us is visibility. When you talk transport within a cloud, very interestingly we we have moved from having a backbone that we bought, that we own, that would be data center connectivity. Zuora's a subscription billing company, so we want to support the subscription mindset. So rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy. My backbone is in the cloud. I use the cloud providers interconnections between regions to transport data across and so if you do that with their native solutions, you do lose visibility. There are areas in that that you don't get, which is why controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it. >> Great conversation. I loved what you said earlier latency, bandwidth, I think availability were your top three things. Guys SLA, just do ping times between clouds it's like, you don't know what you're getting for round trip time. This becomes a huge kind of risk management, black hole, whatever you want to call it, blind spot. How are you guys looking at the interconnect between clouds? Because I can see that working from ground to cloud on per cloud but when you start dealing with multiclouds workloads, SLAs will be all over the map, won't they just inherently. How do you guys view that? >> Yeah, I think we talked about workload and we know that the workloads are going to be different in different clouds, but they're going to be calling each other. So it's very important to have that visibility, that you can see how data is flowing at what latency and what availability is there and our authority needs to operate on that. >> So use the software dashboard, look at the times and look at the latency -- >> In the old days, Strongswan Openswan you try to figure it out, in the new days you have to figure out. >> Justin, what's your answer to that because you're in the middle of it? >> Yeah, I think the key thing there is that we have to plan for that failure, we have to plan for that latency in our applications. If certain things are tracking in your SLI, certain things are planning for and you loosely coupled these services in a much more microservices approach. So you actually can handle that kind of failure or that type of unknown latency and unfortunately, the cloud has made us much better at handling exceptions in a much better way. >> You guys are all great examples of cloud native from day one. When did you have the tipping point moment or the epiphany of saying a multiclouds real, I can't ignore it, I got to factor that into all my design principles and everything you're doing? Was there a moment or was it from day one? >> There are two reasons, one was the business. So in business, there were some affinity to not be in one cloud or to be in one cloud and that drove from the business side. So as a cloud architect our responsibility was to support that business. Another is the technology, some things are really running better in, like if you're running Dotnet workload or your going to run machine learning or AI so that you would have that preference of one cloud over other. >> Guys, any thoughts on that? >> That was the bill that we got from AWS. That's what drives a lot of these conversations is the financial viability of what you're building on top of. This failure domain idea which is fairly interesting. How do I solve our guarantee against a failure domain? You have methodologies with back end direct connects or interconnect with GCP. All of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for. Our job is to deliver the frames and the packets, what that flows across, how you get there? We want to make that seamless. And so whether it's a public internet API call or it's a back end connectivity through direct connect, it doesn't matter. It just has to meet a contract that you've signed with your application, folks. >> Yeah, that's the availability piece. >> Justin, your thoughts on that, any comment on that? >> So actually multiclouds become something much more recent in the last six to eight months, I'd say. We always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough, why complicate it further? But the realities of the business and as we start seeing, improvements in Google and Azure and different technology spaces, the need for multicloud becomes much more important. As well as our acquisition strategies are matured, we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud. And if they're on a cloud, I need to plug them into our ecosystem. And so that's really changed our multicloud story in a big way. >> I'd love to get your thoughts on the clouds versus the clouds, because you compare them Amazon's got more features, they're rich with features. Obviously, the bills are high to people using them. But Google's got a great network, Google's networks pretty damn good And then you got Azure. What's the difference between the clouds? Where do they fall? Where do they peak in certain areas better than others? What are the characteristics, which makes one cloud better? Do they have a unique feature that makes Azure better than Google and vice versa? What do you guys think about the different clouds? >> Yeah, to my experience, I think the approach is different in many places. Google has a different approach very DevOps friendly and you can run your workloads with your network can span regions. But our application ready to accept that. Amazon is evolving. I remember 10 years back Amazon's network was a flat network, we would be launching servers in 10.0.0/8, right. And then the VPCs came out. >> We'll have to translate that to English for the live feed. Not good. So the VPCs concept came out, multi account came out, so they are evolving. Azure had a late start but because they have a late start, they saw the pattern and they have some mature setup on the network. >> They've got around the same price too. >> I think they're all trying to say they're equal in their own ways. I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architect your own solution. For example, Amazon has a very regional affinity, they don't like to go cross region in their architecture. Whereas Google is very much it's a global network, we're going to think about as a global solution. I think Google also has advantage that it's third to market and so has seen what Azure did wrong, it seeing what AWS did wrong and it's made those improvements and I think that's one of their big advantage. >> They got great scale too. Justin thoughts on the cloud. >> So yeah, Amazon built from the system up and Google built from the network down. So their ideas and approaches are from a global versus original, I agree with you completely that is the big number one thing. But the if you look at it from the outset, interestingly, the inability or the ability for Amazon to limit layer to broadcasting and what that really means from a VPC perspective, changed all the routing protocols you can use. All the things that we had built inside of a data center to provide resiliency and make things seamless to users, all of that disappeared. And so because we had to accept that at the VPC level, now we have to accept that at the WAN level. Google's done a better job of being able to overcome those things and provide those traditional network facilities to us. >> Just a great panel, we could go all day here, it's awesome. So I heard, we will get to the cloud native naive questions. So kind of think about what's naive and what's cloud, I'll ask that next but I got to ask you I had a conversation with a friend he's like, "WAN is the new LAN?" So if you think about what the LAN was at a data center, WAN is the new LAN, cause you keep talking about the cloud impact? So that means ST-WAN, the old ST-WAN kind of changing. There's a new LAN. How do you guys look at that? Because if you think about it, what LANs were for inside a premises was all about networking, high speed. But now when you take the WAN and make it, essentially a LAN, do you agree with that? And how do you view this trend? Is it good or bad or is it ugly? What you guys take on this? >> Yeah, I think it's a thing that you have to work with your application architects. So if you are managing networks and if you're a server engineer, you need to work with them to expose the unreliability that it would bring in. So the application has to handle a lot of the difference in the latencies and the reliability has to be worked through the application there. >> LAN, WAN, same concept is that BS? Can you give some insight? >> I think we've been talking about for a long time the erosion of the edge. And so is this just a continuation of that journey we've been on for last several years. As we get more and more cloud native and we talked about API's, the ability to lock my data in place and not be able to access it really goes away. And so I think this is just continuation. I think it has challenges. We start talking about WAN scale versus LAN scale, the tooling doesn't work the same, the scale of that tooling is much larger. and the need to automation is much, much higher in a WAN than it wasn't a LAN. That's why you're seeing so much infrastructure as code. >> Yeah. So for me, I'll go back again to this, it's bandwidth and its latency that define those two LAN versus WAN. But the other thing that's comes up more and more with cloud deployments is whereas our security boundary and where can I extend this secure aware appliance or set of rules to protect what's inside of it. So for us, we're able to deliver VRFs or route forwarding tables for different segments wherever we're at in the world. And so they're trusted to talk to each other but if they're going to go to someplace that's outside of their network, then they have to cross the security boundary, where we enforce policy very heavily. So for me, there's it's not just LAN, WAN it's how does environment get to environment more importantly. >> That's a great point in security, we haven't talked it yet but that's got to be baked in from the beginning, this architecture. Thoughts on security, how you guys are dealing with it? >> Yeah, start from the base, have app to app security built in. Have TLS, have encryption on the data at transit, data at rest. But as you bring the application to the cloud and they're going to go multicloud, talking to over the internet, in some places, well have app to app security. >> Our principles day, security is day zero every day. And so we always build it into our design, build into our architecture, into our applications. It's encrypt everything, it's TLS everywhere. It's make sure that that data is secure at all times. >> Yeah, one of the cool trends at RSA, just as a side note was the data in use encryption piece, which is homomorphic stuff was interesting. Alright guys, final question. We heard on the earlier panel was also trending at re:Invent, we think the T out of cloud native, it spells cloud naive. They have shirts now, Aviatrix kind of got this trend going. What does that mean to be naive? To your peers out there watching the live stream and also the suppliers that are trying to supply you guys with technology and services, what's naive look like and what's native look like? When is someone naive about implementing all this stuff? >> So for me, because we are in 100% cloud, for us its main thing is ready for the change. And you will find new building blocks coming in and the network design will evolve and change. So don't be naive and think that it's static, evolve with the change. >> I think the biggest naivety that people have is that well, I've been doing it this way for 20 years, I've been successful, it's going to be successful in cloud. The reality is that's not the case. You got to think some of the stuff a little bit differently and you need to think about it early enough, so that you can become cloud native and really enable your business on cloud. >> Yeah for me it's being open minded. Our industry, the network industry as a whole, has been very much I'm smarter than everybody else and we're going to tell everybody how it's going to be done. And we fell into a lull when it came to producing infrastructure and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours, or weeks or months in some cases, is really important in and so >> - >> It's naive being closed minded, native being open minded. >> Exactly. For me that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old school way. >> All right, I know we're at a time but I got to asked one more question, so you guys so good. Give me a quick answer. What's the BS language when you, the BS meter goes off when people talk to you about solutions? What's the kind of jargon that you hear, that's the BS meter going off? What are people talking about that in your opinion you here you go, "That's total BS?" What triggers you? >> So that I have two lines out of movies if I say them without actually thinking them. It's like 1.21 gigawatts are you out of your mind from Back to the Future right? Somebody's giving you all these wiz bang things. And then Martin Maul and Michael Keaton in Mr Mom when he goes to 220, 221, whatever it takes. >> Yeah. >> Those two right there, if those go off in my mind where somebody's talking to me, I know they're full of baloney. >> So a lot of speeds and feeds, a lot of speeds and feeds a lot of -- >> Just data. Instead of talking about what you're actually doing and solutioning for. You're talking about, "Well, it does this this this." Okay to 220, 221. (laughter) >> Justin, what's your take? >> Anytime I start seeing the cloud vendors start benchmarking against each other. Your workload is your workload, you need to benchmark yourself. Don't listen to the marketing on that, that's just awful. >> Amit, what triggers you in the BS meter? >> I think if somebody explains to you are not simple, they cannot explain you in simplicity, then it's all bull shit. >> (laughs) That's a good one. Alright guys, thanks for the great insight, great panel. How about a round of applause to practitioners. (audience applauds) (upbeat music) >> John: Okay, welcome back to Altitude 2020 for the digital event for the live feed. Welcome back, I'm John Furrier with theCUBE with Steve Mullaney, CEO Aviatrix. For the next panel from Global System Integrated, the folks who are building and working with folks on their journey to multicloud and cloud-native networking. We've got a great panel, George Buckman with DXC and Derrick Monahan with WWT, welcome to the stage. (Audience applauds) >> Hey >> Thank you >> Groovy spot >> All right (upbeat music) >> Okay, you guys are the ones out there advising, building, and getting down and dirty with multicloud and cloud-native networking, we just heard from the customer panel. You can see the diversity of where people come in to the journey of cloud, it kind of depends upon where you are, but the trends are all clear, cloud-native networking, DevOps, up and down the stack, this has been the main engine. What's your guys' take of this journey to multicloud? What do you guys think? >> Yeah, it's critical, I mean we're seeing all of our enterprise customers enter into this, they've been through the migrations of the easy stuff, ya know? Now they're trying to optimize and get more improvements, so now the tough stuff's coming on, right? They need their data processing near where their data is. So that's driving them to a multicloud environment. >> Yeah, we've heard some of the Edge stuff, I mean, you guys are-- >> Exactly. >> You've seen this movie before, but now it's a whole new ballgame, what's your take? Yeah, so, I'll give you a hint, our practice is not called the cloud practice, it's the multicloud practice, and so if that gives you a hint of how we approach things. It's very consultative. And so when we look at what the trends are, like a year ago. About a year ago we were having conversations with customers, "Let's build a data center in the cloud. Let's put some VPCs, let's throw some firewalls, let's put some DNS and other infrastructure out there and let's hope it works." This isn't a science project. What we're starting to see is customers are starting to have more of a vision, we're helping with that consultative nature, but it's totally based on the business. And you've got to start understanding how lines of business are using the apps and then we evolve into the next journey which is a foundational approach to-- >> What are some of the problems some of your customers are solving when they come to you? What are the top things that are on their mind, obviously the ease of use, agility, all that stuff, what specifically are they digging into? >> Yeah, so complexity, I think when you look at a multicloud approach, in my view is, network requirements are complex. You know, I think they are, but I think the approach can be, "Let's simplify that." So one thing that we try to do, and this is how we talk to customers is, just like you simplify in Aviatrix, simplifies the automation orchestration of cloud networking, we're trying to simplify the design, the plan, and implementation of the infrastructure across multiple workloads, across multiple platforms. And so the way we do it, is we sit down, we look at not just use cases, not just the questions we commonly anticipate, we actually build out, based on the business and function requirements, we build out a strategy and then create a set of documents, and guess what? We actually build it in a lab, and that lab that we platform rebuilt, proves out this reference architectural actually works. >> Absolutely, we implement similar concepts. I mean, they're proven practices, they work, right? >> But George, you mentioned that the hard part's now upon us, are you referring to networking, what specifically were you getting at there when you said, "The easy part's done, now the hard part?" >> So for the enterprises themselves, migrating their more critical apps or more difficult apps into the environments, ya know, we've just scratched the surface, I believe, on what enterprises are doing to move into the cloud, to optimize their environments, to take advantage of the scale and speed to deployment and to be able to better enable their businesses. So they're just now really starting to-- >> So do you guys see what I talked about? I mean, in terms of that Cambrian explosion, I mean, you're both monster system integrators with top fortune enterprise customers, you know, really rely on you for guidance and consulting and so forth, and deploy their networks. Is that something that you've seen? I mean, does that resonate? Did you notice a year and a half ago all of a sudden the importance of cloud for enterprise shoot up? >> Yeah, I mean, we're seeing it now. >> Okay. >> In our internal environment as well, ya know, we're a huge company ourselves, customer zero, our internal IT, so, we're experiencing that internally and every one of our other customers as well. >> So I have another question and I don't know the answer to this, and a lawyer never asks a question that you don't know the answer to, but I'm going to ask it anyway. DXC and WWT, massive system integrators, why Aviatrix? >> Great question, Steve, so I think the way we approach things, I think we have a similar vision, a similar strategy, how you approach things, how we approach things, at World Wide Technology. Number one, we want a simplify the complexity. And so that's your number one priority. Let's take the networking, let's simplify it, and I think part of the other point I'm making is we see this automation piece as not just an after thought anymore. If you look at what customers care about, visibility and automation is probably at the top three, maybe the third on the list, and I think that's where we see the value. I think the partnership that we're building and what I get excited about is not just putting yours and our lab and showing customers how it works, it's co-developing a solution with you. Figuring out, "Hey, how can we make this better?" >> Right >> Visibility is a huge thing, just in security alone, network everything's around visibility. What automation do you see happening, in terms of progression, order of operations, if you will? What's the low hanging fruit? What are people working on now? What are some of the aspirational goals around when you start thinking about multicloud and automation? >> So I wanted to get back to his question. >> Answer that question. >> I wanted to answer your question, you know, what led us there and why Aviatrix. You know, in working some large internal IT projects, and looking at how we were going to integrate those solutions, you know, we like to build everything with recipes. Network is probably playing catch-up in the DevOps world but with a DevOps mindset, looking to speed to deploy, support, all those things, so when you start building your recipe, you take a little of this, a little of that, and you mix it all together, well, when you look around, you say, "Wow, look, there's this big bag of Aviatrix. "Let me plop that in. That solves a big part "of my problems that I had, the speed to integrate, "the speed to deploy, and the operational views "that I need to run this." So that was what led me to-- >> John: So how about reference architectures? >> Yeah, absolutely, so, you know, they came with a full slate of reference architectures already out there and ready to go that fit our needs, so it was very easy for us to integrate those into our recipes. >> What do you guys think about all the multi-vendor inter-operability conversations that have been going on? Choice has been a big part of multicloud in terms of, you know, customers want choice, they'll put a workload in the cloud if it works, but this notion of choice and interoperability has become a big conversation. >> It is, and I think that our approach, and that's the way we talk to customers is, "Let's speed and de-risk that decision making process, "and how do we do that?" Because interoperability is key. You're not just putting, it's not just a single vendor, we're talking, you know, many many vendors, I mean think about the average number of cloud applications a customer uses, a business, an enterprise business today, you know, it's above 30, it's skyrocketing and so what we do, and we look at it from an interoperability approach is, "How do things inter-operate?" We test it out, we validate it, we build a reference architecture that says, "These are the critical design elements, "now let's build one with Aviatrix "and show how this works with Aviatrix." And I think the important part there, though, is the automation piece that we add to it and visibility. So I think the visibility is what I see lacking across industry today. >> In cloud-native that's been a big topic. >> Yep >> Okay, in terms of Aviatrix, as you guys see them coming in, they're one of the ones that are emerging and the new brands emerging with multicloud, you've still got the old guard encumbered with huge footprints. How are customers dealing with that kind of component in dealing with both of them? >> Yeah, I mean, we have customers that are ingrained with a particular vendor and you know, we have partnerships with many vendors. So our objective is to provide the solution that meets that client. >> John: And they all want multi-vendor, they all want interoperability. >> Correct. >> All right, so I got to ask you guys a question while we were defining Day-2 operations. What does that mean? You guys are looking at the big business and technical components of architecture, what does Day-2 operations mean, what's the definition of that? >> Yeah, so I think from our perspective, with my experience, we, you know, Day-2 operations, whether it's not just the orchestration piece in setting up and let it automate and have some, you know, change control, you're looking at this from a Day-2 perspective, "How do I support this ongoing "and make it easy to make changes as we evolve?" The cloud is very dynamic. The nature of how fast it's expanding, the number features is astonishing. Trying to keep up to date with the number of just networking capabilities and services that are added. So I think Day-2 operations starts with a fundamental understanding of building out supporting a customer's environments, and making the automation piece easy from a distance, I think. >> Yeah and, you know, taking that to the next level of being able to enable customers to have catalog items that they can pick and choose, "Hey I need this network connectivity "from this cloud location back to this on-prem." And being able to have that automated and provisioned just simply by ordering it. >> For the folks watching out there, guys, take a minute to explain as you guys are in the trenches doing a lot of good work. What are some of the engagements that you guys get into? How does that progress? What happens there, they call you up and say, "Hey I need some multicloud," or you're already in there? I mean, take us through how someone can engage to use a global SI, they come in and make this thing happen, what's the typical engagement look like? >> Derrick: Yeah, so from our perspective, we typically have a series of workshops in the methodology that we kind of go along the journey. Number one, we have a foundational approach. And I don't mean foundation meaning the network foundation, that's a very critical element, we got to factor in security and we got to factor in automation. So when you think about foundation, we do a workshop that starts with education. A lot of times we'll go in and we'll just educate the customer, what is VPC sharing? You know, what is a private link in Azure? How does that impact your business? We have customers that want to share services out in an ecosystem with other customers and partners. Well there's many ways to accomplish that. Our goal is to understand those requirements and then build that strategy with them. >> Thoughts George, on-- >> Yeah, I mean, I'm one of the guys that's down in the weeds making things happen, so I'm not the guy on the front line interfacing with the customers every day. But we have a similar approach. We have a consulting practice that will go out and apply their practices to see what those-- >> And when do you parachute in? >> Yeah, when I parachute in is, I'm on the back end working with our offering development leads for networking, so we understand and are seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to meet their connectivity needs. So the patterns are similar. >> Right, final question for you guys, I want to ask you to paint a picture of what success looks like. You don't have to name customers, you don't have to get in and reveal who they are, but what does success look like in multicloud as you paint a picture for the folks here and watching on the live stream, if someone says, "Hey I want to be multicloud, I got to to have my operations Agile, I want full DevOps, I want programmability and security built in from Day-zero." What does success look like? >> Yeah, I think success looks like this, so when you're building out a network, the network is a harder thing to change than some other aspects of cloud. So what we think is, even if you're thinking about that second cloud, which we have most of our customers are on two public clouds today, they might be dabbling in it. As you build that network foundation, that architecture, that takes in to consideration where you're going, and so once we start building that reference architecture out that shows, this is how to approach it from a multicloud perspective, not a single cloud, and let's not forget our branches, let's not forget our data centers, let's not forget how all this connects together because that's how we define multicloud, it's not just in the cloud, it's on-prem and it's off-prem. And so collectively, I think the key is also is that we provide them an HLD. You got to start with a high level design that can be tweaked as you go through the journey but you got to give it a solid structural foundation, and that networking which we think, most customers think as not the network engineers, but as an after thought. We want to make that the most critical element before you start the journey. >> George, from your seat, how does success look for you? >> So, you know it starts out on these journeys, often start out people not even thinking about what is going to happen, what their network needs are when they start their migration journey to the cloud. So I want, success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud. >> Steve: Good point. >> Guys, great insight, thanks for coming on and sharing. How about a round of applause for the global system integrators? (Audience applauds) (Upbeat music) >> The next panel is the AVH certified engineers, also known as ACEs. This is the folks that are certified, they're engineering, they're building these new solutions. Please welcome Toby Foss from Informatica, Stacey Lanier from Teradata, and Jennifer Reed with Viqtor Davis to the stage. (upbeat music) (audience cheering) (panelists exchanging pleasantries) >> You got to show up. Where's your jacket Toby? (laughing) You get it done. I was just going to rib you guys and say, where's your jackets, and Jen's got the jacket on. Okay, good. >> Love the Aviatrix, ACEs Pilot gear there above the Clouds. Going to new heights. >> That's right. >> So guys Aviatrix aces, I love the name, think it's great, certified. This is all about getting things engineered. So there's a level of certification, I want to get into that. But first take us through the day in the life of an ACE, and just to point out, Stacy is a squad leader. So he's, he's like a-- >> Squadron Leader. >> Squadron Leader. >> Yeah. >> Squadron Leader, so he's got a bunch of ACEs underneath him, but share your perspective a day in the Life. Jennifer, we'll start with you. >> Sure, so I have actually a whole team that works for me both in the North America, both in the US and in Mexico. So I'm eagerly working to get them certified as well, so I can become a squad leader myself. But it's important because one of the critical gaps that we've found is people having the networking background because you graduate from college, and you have a lot of computer science background, you can program you've got Python, but networking in packets they just don't get. So, just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical. Because you're going to get an issue where you need to figure out where exactly is that happening on the network, Is my issue just in the VPCs? Is it on the instance side is a security group, or is it going on prem? This is something actually embedded within Amazon itself? I mean, I troubleshot an issue for about six months going back and forth with Amazon, and it was the VGW VPN. Because they were auto scaling on two sides, and we ended up having to pull out the Cisco's, and put in Aviatrix so I could just say, " okay, it's fixed," and actually helped the application teams get to that and get it solved. But I'm taking a lot of junior people and getting them through that certification process, so they can understand and see the network, the way I see the network. I mean, look, I've been doing this for 25 years when I got out. When I went in the Marine Corps, that's what I did, and coming out, the network is still the network. But people don't get the same training they got in the 90s. >> Was just so easy, just write some software, and they were, takes care of itself. I know, it's pixie dust.  >> I'll come back to that, I want to come back to that, the problem solved with Amazon, but Toby. >> I think the only thing I have to add to that is that it's always the network's fault. As long as I've been in networking, it's always been the network's fault. I'm even to this day, it's still the network's fault, and part of being a network guy is that you need to prove when it is and when it's not your fault. That means you need to know a little bit about 100 different things, to make that work. >> Now you got a full stack DevOps, you got to know a lot more times another hundred. >> Toby: And the times are changing, yeah. >> This year the Squadron Leader and get that right. What is the Squadron Leader firstly? Describe what it is. >> I think is probably just leading on the network components of it. But I think, from my perspective, when to think about what you asked them was, it's about no issues and no escalations. So of my day is like that, I'm happy to be a squadron leader. >> That is a good outcome, that's a good day. >> Yeah, sure, it is. >> Is there good days? You said you had a good day with Amazon? Jennifer, you mentioned the Amazon, and this brings up a good point, when you have these new waves come in, you have a lot of new things, new use cases. A lot of the finger pointing it's that guy's problem , that girl's problems, so how do you solve that, and how do you get the Young Guns up to speed? Is there training, is it this where the certification comes in? >> This is where the certifications really going to come in. I know when we got together at Reinvent, one of the questions that we had with Steve and the team was, what should our certification look like? Should we just be teaching about what AVH troubleshooting brings to bear, but what should that be like? I think Toby and I were like, No, no, no, no. That's going a little too high, we need to get really low because the better someone can get at actually understanding what's actually happening in the network, and where to actually troubleshoot the problem, how to step back each of those processes. Because without that, it's just a big black box, and they don't know. Because everything is abstracted, in Amazon and in Azure and in Google, is abstracted, and they have these virtual gateways, they have VPNs, that you just don't have the logs on, is you just don't know. So then what tools can you put in front of them of where they can look? Because there are full logs. Well, as long as they turned on the flow logs when they built it, and there's like, each one of those little things that well, if they'd had decided to do that, when they built it, it's there. But if you can come in later to really supplement that with training to actual troubleshoot, and do a packet capture here, as it's going through, then teaching them how to read that even. >> Yeah, Toby, we were talking before we came on up on stage about your career, you've been networking all your time, and then, you're now mentoring a lot of younger people. How is that going? Because the people who come in fresh they don't have all the old war stories, like they don't talk about it, There's never for, I walk in bare feet in the snow when I was your age, I mean, it's so easy now, right, they say. What's your take on how you train the young People. >> So I've noticed two things. One is that they are up to speed a lot faster in generalities of networking. They can tell you what a network is in high school level now, where I didn't learn that til midway through my career, and they're learning it faster, but they don't necessarily understand why it's that way here. Everybody thinks that it's always slash 24 for a subnet, and they don't understand why you can break it down smaller, why it's really necessary. So the ramp up speed is much faster for these guys that are coming in. But they don't understand why and they need some of that background knowledge to see where it's coming from, and why is it important, and that's old guys, that's where we thrive. >> Jennifer, you mentioned you got in from the Marines, it helps, but when you got into networking, what was it like then and compare it now? Because most like we heard earlier static versus dynamic Don't be static is like that. You just set the network, you got a perimeter. >> Yeah, no, there was no such thing. So back in the day, I mean, we had Banyan vines for email, and we had token ring, and I had to set up token ring networks and figure out why that didn't work. Because how many of things were actually sharing it. But then actually just cutting fiber and running fiber cables and dropping them over shelters to plug them in and all crap, they swung it too hard and shattered it and now I got to figure eight Polish this thing and actually should like to see if it works. I mean, that was the network , current cat five cables to run an Ethernet, and then from that I just said, network switches, dumb switches, like those were the most common ones you had. Then actually configuring routers and logging into a Cisco router and actually knowing how to configure that. It was funny because I had gone all the way up, I was the software product manager for a while. So I've gone all the way up the stack, and then two and a half, three years ago, I came across to work with Entity group that became Viqtor Davis. But we went to help one of our customers Avis, and it was like, okay, so we need to fix the network. Okay, I haven't done this in 20 years, but all right, let's get to it. Because it really fundamentally does not change. It's still the network. I mean, I've had people tell me, Well, when we go to containers, we will not have to worry about the network. And I'm like, yeah, you don't I do. >> And that's within programmability is a really interesting, so I think this brings up the certification. What are some of the new things that people should be aware of that come in with the Aviatrix A certification? What are some of the highlights? Can you guys share some of the highlights around the certifications? >> I think some of the importance is that it doesn't need to be vendor specific for network generality or basic networking knowledge, and instead of learning how Cisco does something, or how Palo Alto does something, We need to understand how and why it works as a basic model, and then understand how each vendor has gone about that problem and solved it in a general. That's true in multicloud as well. You can't learn how Cloud networking works without understanding how AWS and Azure and GCP are all slightly the same but slightly different, and some things work and some things don't. I think that's probably the number one take. >> I think having a certification across Clouds is really valuable because we heard the global s eyes as you have a business issues. What does it mean to do that? Is it code, is it networking? Is it configurations of the Aviatrix? what is, he says,the certification but, what is it about the multiCloud that makes it multi networking and multi vendor? >> The easy answer is yes, >> Yes is all of us. >> All of us. So you got to be in general what's good your hands and all You have to be. Right, it takes experience. Because every Cloud vendor has their own certification. Whether that's SOPs and advanced networking and event security, or whatever it might be, yeah, they can take the test, but they have no idea how to figure out what's wrong with that system. The same thing with any certification, but it's really getting your hands in there, and actually having to troubleshoot the problems, actually work the problem, and calm down. It's going to be okay. I mean, because I don't know how many calls I've been on or even had aviators join me on. It's like, okay, so everyone calm down, let's figure out what's happening. It's like, we've looked at that screen three times, looking at it again is not going to solve that problem, right. But at the same time, remaining calm but knowing that it really is, I'm getting a packet from here to go over here, it's not working, so what could be the problem? Actually stepping them through those scenarios, but that's like, you only get that by having to do it, and seeing it, and going through it, and then you get it. >> I have a question, so, I just see it. We started this program maybe six months ago, we're seeing a huge amount of interest. I mean, we're oversubscribed on all the training sessions. We've got people flying from around the country, even with Coronavirus, flying to go to Seattle to go to these events where we're subscribed, is that-- >> A good emerging leader would put there. >> Yeah. So, is that something that you see in your organizations? Are you recommending that to people? Do you see, I mean, I'm just, I guess I'm surprised or not surprised. But I'm really surprised by the demand if you would, of this MultiCloud network certification because there really isn't anything like that. Is that something you guys can comment on? Or do you see the same things in your organization? >> I see from my side, because we operate in a multiCloud environments that really helps and some beneficial for us. >> Yeah, true. I think I would add that networking guys have always needed to use certifications to prove that they know what they know. >> Right. >> It's not good enough to say, Yeah, I know IP addresses or I know how a network works. A couple little check marks or a little letters body writing helps give you validity. So even in our team, we can say, Hey, we're using these certifications to know that you know enough of the basics and enough of the understandings, that you have the tools necessary, right. >> I guess my final question for you guys is, why an ACE certification is relevant, and then second part is share with the live stream folks who aren't yet ACE certified or might want to jump in to be aviatrix certified engineers. Why is it important, so why is it relevant and why should someone want to be a certified aviatrix certified engineer? >> I think my views a little different. I think certification comes from proving that you have the knowledge, not proving that you get a certification to get an army there backwards. So when you've got the training and the understanding and you use that to prove and you can, like, grow your certification list with it, versus studying for a test to get a certification and have no understanding of it. >> Okay, so that who is the right person that look at this and say, I'm qualified, is it a network engineer, is it a DevOps person? What's your view, a little certain. >> I think Cloud is really the answer. It's the, as we talked like the edges getting eroded, so is the network definition getting eroded? We're getting more and more of some network, some DevOps, some security, lots and lots of security, because network is so involved in so many of them. That's just the next progression. >> Do you want to add something there? >> I would say expand that to more automation engineers, because we have those now, so I probably extend it beyond this one. >> Jennifer you want to? >> Well, I think the training classes themselves are helpful, especially the entry level ones for people who may be "Cloud architects" but have never done anything in networking for them to understand why we need those things to really work, whether or not they go through to eventually get a certification is something different. But I really think fundamentally understanding how these things work, it makes them a better architect, makes them better application developer. But even more so as you deploy more of your applications into the Cloud, really getting an understanding, even from people who have traditionally done Onprem networking, they can understand how that's going to work in Cloud. >> Well, I know we've got just under 30 seconds left. I want to get one more question then just one more, for the folks watching that are maybe younger than, that don't have that networking training. From your experiences each of you can answer why should they know about networking, what's the benefit? What's in it for them? Motivate them, share some insights of why they should go a little bit deeper in networking. Stacy, we'll start with you, we'll go then. >> I'll say it's probably fundamental, right? If you want to deliver solutions, networking is the very top. >> I would say if you, fundamental of an operating system running on a machine, how those machines start together is a fundamental changes, something that start from the base and work your way up. >> Jennifer? >> Right, well, I think it's a challenge. Because you've come from top down, now you're going to start looking from bottom up, and you want those different systems to cross-communicate, and say you've built something, and you're overlapping IP space, note that that doesn't happen. But how can I actually make that still operate without having to re IP re platform. Just like those challenges, like those younger developers or assistant engineers can really start to get their hands around and understand those complexities and bring that forward in their career. >> They get to know then how the pipes are working, and they're got to know it--it's the plumbing. >> That's right, >> They got to know how it works, and how to code it. >> That's right. >> Awesome, thank you guys for great insights, ACE Certified Engineers, also known as ACEs, give them a round of applause. (audience clapping) (upbeat music) >> Thank you, okay. All right, that concludes my portion. Thank you, Steve Thanks for having me. >> John, thank you very much, that was fantastic. Everybody round of applause for John Furrier. (audience applauding) Yeah, so great event, great event. I'm not going to take long, we got lunch outside for the people here, just a couple of things. Just to call the action, right? So we saw the ACEs, for those of you out of the stream here, become a certified, right, it's great for your career, it's great for not knowledge, is fantastic. It's not just an aviator's thing, it's going to teach you about Cloud networking, MultiCloud networking, with a little bit of aviatrix, exactly like the Cisco CCIE program was for IP network, that type of the thing, that's number one. Second thing is learning, right? So there's a link up there to join the community. Again like I started this, this is a community, this is the kickoff to this community, and it's a movement. So go to community.avh.com, starting a community of multiCloud. So get get trained, learn. I'd say the next thing is we're doing over 100 seminars across the United States and also starting into Europe soon, we will come out and we'll actually spend a couple hours and talk about architecture, and talk about those beginning things. For those of you on the livestream in here as well, we're coming to a city near you, go to one of those events, it's a great way to network with other people that are in the industry, as well as to start alone and get on that MultiCloud journey. Then I'd say the last thing is, we haven't talked a lot about what Aviatrix does here, and that's intentional. We want you leaving with wanting to know more, and schedule, get with us and schedule a multi hour architecture workshop session. So we sit down with customers, and we talk about where they're at in that journey, and more importantly, where they're going, and define that end state architecture from networking, computer, storage, everything. Everything you've heard today, everybody panel kept talking about architecture, talking about operations. Those are the types of things that we solve, we help you define that canonical architecture, that system architecture, that's yours. So many of our customers, they have three by five, plotted lucid charts, architecture drawings, and it's the customer name slash Aviatrix, network architecture, and they put it on their whiteboard. That's the most valuable thing they get from us. So this becomes their 20 year network architecture drawing that they don't do anything without talking to us and look at that architecture. That's what we do in these multi hour workshop sessions with customers, and that's super, super powerful. So if you're interested, definitely call us, and let's schedule that with our team. So anyway, I just want to thank everybody on the livestream. Thank everybody here. Hopefully it was it was very useful. I think it was, and Join the movement, and for those of you here, join us for lunch, and thank you very much. (audience applauding) (upbeat music)

ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 all right so we've got a fantastic event today really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a take-off of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any powerpoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got Simone Rashard Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the u.s. it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Frank kibrit you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission critical they care about visibility they care about control they care about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers do they see the same thing we're gonna validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're gonna talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day 2 operations what does that mean well day 1 is one day of your life that's who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do I operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix as leaders knew we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CC IES where Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of Tube John Fourier okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel two customer panels before that Gartner is going to come on talk about the industry we have a global system integrators we talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask someone rashard to come on stage from Gartner we'll check it all up [Applause] [Music] okay so kicking things off certain started gartner the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer in the 90 to a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering at the marketplace with hybrid cloud and now moving quickly to multi cloud is really I was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow whitey or application people or some kind of DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right with a different account and they create mesh to manage them and their direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides the data that are sent removing that to that cloud and I ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the adduct way doesn't scale at some point idea has to save them because they don't think about the two they don't think about operations they have a bunch of VPC and multiple clouds the other way that if you do the left and shift wake they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these ways are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct then that's I would I call the up optimal phase but even that they they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS has accounts there's subscription and in adarand GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that I still wanna manage the cloud from an API to interview I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they really building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway I'm just a joke what do you see in terms of where people are in that multi cloud a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in deserve one app in individuals one get happened Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never going to happen what I've seen with enterprise is I'm gonna put the workload in the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking team be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run Network part of the cloud connectivity to the cloud is kind of simple I agree IPSec VP and I reckon Express that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud provider right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean this is the day-to-day operations after it you know the natural let's add an app let's add a server let's troubleshoot a problem so what so your life something changes how would he do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's been a hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi-cloud wave that's coming as cloud native networking well there's no you know official garner definition but I can create one on another spot it's do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't even understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose api's where is that optimization where's the focus well I take what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of the cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of you right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plane out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that plane out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and ship or they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco monks bring you star in the cloud recall that each guy anywhere right so everyone what and and then there's cloud vision for my red star and contrail is in the cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not truly cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive clown that close one letter yeah so that was a big con surgeon i reinvent take the tea out of cloud native its cloud naive i went super viral you guys got t-shirts now i know you love it but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling out but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in cisco you it's a little bit more native than other ones because they're really ACI in the cloud you call you you really like configure api so the cloud and nsx is going that way and so is Arista but they're incumbent they have their own tools it's difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know and network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week oh the only b2 networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like AV X and others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in AWS you can user it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck Nets a cops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this program their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it via line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this VP see but this VP see automatically being your associate to your account you cannot go out on the internet you have to go to the transit VP C so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI mace which for us old folks know that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objectives oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well I as I said earlier that once you you could easily provision in the cloud you can easily connect to that cloud is when you start troubleshooting application in the cloud and try to scale so this that's where the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead the 20% extra functionality that of course every enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always gonna be that extra functionality the in in an automated and simple way that you talked about but yet powerful with up with the visibility and control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggards who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some the signals that are going on in their environment what are some of the threshold or things that are going on that there can pay attention to well well once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robber will hit the road but as I said it's easier to prove it it's okay it's 80s it's easy user transit gateway put a few V pcs and you're done and use create some presents like equinox and do Direct Connect and Express route with Azure that looks simple is the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not button tell me that I need to understand the basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi-vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server and internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this market because honestly public check hybrid cloud they're working on that that gets on-premise is done now multi-class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what their cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start to it especially an incumbent one so it's tempting to say on and I have a bunch of f5 experts nothing against f5 I'm going to bring my five in the cloud when you can use a needle be that automatically understand ease ease and auto-scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that net I'm going to use legacy stuff and then you have to start thinking okay what about visibility control about the tree cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming someone in charge with Gardner thanks for sharing thank you appreciate it [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of them data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement with aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for aviatrix already working in Amazon and now works in Missouri as well before we knew it GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake assure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build are done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments and David should Nick with fact set guys welcome to the stage for this digital event come on up [Music] hey good to see you thank you okay okay customer panelist is my favorite part we get to hear the real scoop we got the gardener giving us the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with the live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and it's soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets in different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation 'el opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on pram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into mortal multi-cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi-cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you you know had some comments about architecture matters it all starts I mean every Enterprise that I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep adverse adjusters network and that fourth generation or architectures be based primarily upon Palo Alto Networks an aviatrix a matrix doing the orchestration piece of it but that journey came because of the need for simplicity okay I need for multi-cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having to to automate that component and making it consistent with our on-premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that SD when brought to the to the wine side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was some of the there was a path that's probably the biggest list and there is when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those there we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gate without a transit Gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and in evolve later and maybe optimize or change the way you're doing things in the future but don't sit around and wait you can I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's the David yeah talking as earlier about day two operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice the architect I don't know what else I can do that simplicity of operations is key alright so the holistic view of day to operation you mentioned let's can jump in day one is your your your getting stuff set up day two is your life after all right this is kinda what you're getting at David so what does that look like what are you envisioning as you look at that 20 mile stair out post multi-cloud world what are some of the things that you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router CLI and troubleshooting things on in an ad hoc nature so moving more towards the DevOps model is anything on that day - yeah I would love to add something so in terms of day 2 operations you can you can either sort of ignore the day 2 operations for a little while where you get well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to realize it's it's such a such a big gap I think that's key because for us we're moving to more of an event-driven or operations in the past monitoring got the job done it's impossible to modern monitor something there's nothing there when the event happens all right so the event-driven application and then detect is important yeah I think garden was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the networks laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an intern crypt and they they ever get the question should I encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you've got a lot of complexity in your network what do you guys look at the future for yours environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance of things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting and get a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok we want to hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I see AV traces here they're they're a supplier to the sector but you guys are customers everyone's pitching you stuff people are not gonna buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like where API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like um it's definitely it's definitely API driven we we definitely look at the at that the API structure of the vendors provide before we select anything that that is always first in mind and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking become more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what it what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on site and they're gonna sit with you for your day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important Bobby how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's the Volvic bake-off last year first you win so but that's different now because now when you you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so the key is is they can you be operational you know within hours or days instead of weeks but but do we also have the flexibility to customize it to meet your needs could you want to be you won't be put into a box with the other customers we have needs that surpass their cut their needs yeah I almost see the challenge that you guys are living where you've got the cloud immediate value to make an roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's a there's a breaking point for sure you don't you don't get to scale this I like like Simone said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've got a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization think pause you're kind of like off a little bit it's not how it works I mean what is the reality in terms of implementing you know and as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers one of the blockers what are the enabler I think the reality is is that you may not think you're multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements in a secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to allow these clouds and used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the moment from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business team and and like like you said it's whether whether you're in denial or not of the multi cloud fact that your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or sure and just helping facilitate things they're doing the you know the heavy lifting API work for you or they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know makes you have designed yourself into a corner so the closer they're more cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will it make sense tgw is a game-changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool give you the beauty of both worlds you can use tgw with a gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go Mull one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint do you agree with that premise and then wit is multi clouds did you mall together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction that add value but the the network problem is still the same doesn't go away yeah yeah I mean you don't want to be trying to fit a square into a round hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the network infrastructure is there secure is available and is multi cloud capable yeah I'm at the end of the day you guys just validating that it's the networking game now how cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John fritz T Blaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Cooper welcome to stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move a pack from A to B and you get workloads exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your take yeah I mean it's it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to ET rate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like - we started out very much focused on one cloud and as we started doing errands we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are of and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really that's the enabler for this multi cloud trend but you guys taken we'll start with Amit what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it's the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make them a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea now our job is to enable them not to disable them do you think you guys think infrastructure as code which I love that I think it's that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network as code because storage and compute working really well is seeing all kubernetes on ServiceMaster and network is code reality is it there is it still got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way we get to do it yeah and even security groups and then on top and aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us it was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made because it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on Prem and wait and then so first that and then also in the journey where are you at from zero to a hundred of actually in the journey to cloud do you 50% there are you 10% yes I mean are you evacuating data centers next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together right in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's going to be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of you know lift and shift and when did that start and we started about three years ago okay okay go by it's a very different story it started from a garage and one hundred percent on the clock it's a business spend management platform as a software-as-a-service one hundred percent on the cloud it was like ten years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you Sora you guys mentioned DevOps I mean obviously we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this layer this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interestingly we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for soar as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth availability with your sim pop3 things guys SLA I mean you just do ping times are between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads I mean s LA's will be all over the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and whatever ability is our is there and our authority needs to operate on that so it's so you use the software dashboard look at the times and look at the latency in the old days strong so on open so on you try to figure it out and then your days you have to figure out just what she reinsert that because you're in the middle of it yeah I mean I think the the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that start thinking start tracking in your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment was it was it from day one no there were two reasons one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot Network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting is how do I solve or guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just in your thoughts on anything any common uh so actually a multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are how could people using them but Google's got a great network Google's networks pretty damn good and then you got a sure what's the difference between the clouds who with they've evolved something whether they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is approaches different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network and spend regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the yeah I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architectural solution for example amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has advantages its third to market and so has seen what Asia did wrong it seemed with AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the inability or the ability for Amazon to limit layer 2 broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional Network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you could talking about the cloud impact so that means st when the old st way is kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high-speed but now when you take the win and make it essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah I think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you are a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there Lanois same concept is that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's where is what you're seeing so much infrastructure as code yeah yes so for me I'll go back again to this its bandwidth and its latency right that bet define those two land versus win but the other thing that's comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to to protect what's inside of it so for us we're able to deliver vr af-s or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning this architecture thoughts on security are you guys are dealing with it yeah start from the base have apt to have security built in have TLS have encryption on the data I transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principles day Security's day zero every day and so we we always build it into our design build into our architecture into our applications it's encrypt everything it's TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff is interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive and think that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's are you being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total BS but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's getting a bang and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need to benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great time how about a round of applause DX easy solutions integrating company than we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba corkle will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products have incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the Lyons cloud connectivity is a new line of networking services so we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services and aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a VA Church were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed to work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole and their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT maybe Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John Ford with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we just heard from the customer panel you can see the diversity of where people come in to the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are exactly you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we're having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the and then we evolved into the next journey which is a foundational approach to what are some of the problem statement customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they digging into yeah so complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we tis anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard part's now upon us are you referring to networking what is specifically were you getting at Terrance's the easy parts done now so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the - so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it not okay in our internal environment as you know we're a huge company or as customers so we're experiencing that internal okay and every one of our other customers so I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c + w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking let's simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I would I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better right visibility's a huge thing jump in security alone network everything's around visibility what automation do you see happening in terms of progression order of operations if you will it's a low-hanging fruit what are people working on now what are what are some of the aspirational goals around when you start thinking about multi cloud and automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were gonna integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of a VHS let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference textures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi-cloud in terms of you know customers want choice they didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and be risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an interoperability approach is how do things interoperate we test it out we validate it we build a reference architecture it says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it in visibility so I think the visibility is what's what I see lacking across the industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in they're one of the ones that are emerging and the new brands emerging but multi-cloud you still got the old guard incumbents with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question while we were defining day two operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve the the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonish trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is that what's what happens do they call you up and say hey I need some multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's looks like typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got a factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what is VP she's sharing you know what is a private Lincoln or how does that impact your business we have customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I then is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to beep their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't forget in reveal kind of who they are but what does success look like in multi-cloud as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in that as you build that network foundation that architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off from and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen what what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good point guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators Hey [Applause] [Music] okay welcome back from the live feed I'm chef for with the cube Steve Eleni CEO of aviatrix my co-host our next panel is the aviatrix certified engineers also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foster min from Attica Stacy linear from Teradata and Jennifer Reid with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds towards a new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like a Squadron Leader Roger and leader yeah Squadron Leader so he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer will start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm eagerly working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but now working in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hmm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the VP C's and on the instance side is a security group or is it going on print and this is something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and I actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be we'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in network have always been the network's fault sure and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another hundred and these times are changing they see your squadron leader I get that right what is what is a squadron leader first can you describe what it is I think it probably just leading all the network components of it but are they from my perspective when to think about what you asked them was it's about no issues and no escalation soft my day is like that's a good outcome that's a good day it's a good day Jennifer you mentioned the Amazon thing this brings up a good point you know when you have these new waves come in you have a lot of new things newly use cases a lot of the finger-pointing it's that guys problem that girls problem so what is how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in those where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Stephen the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear but what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are full logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about you know that's dimmer fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young P so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way or you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and that's old guys that's where we thrive Jennifer you mentioned you you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static cuz back then you just said the network you got a perimeter yeah no there was no such thing ya know so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it now I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this within the program abilities it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global si you help the business issues what does it mean to do that is it code is that networking is it configuration is that aviatrix what is the amine oxy aviatrix is a certification but what is it about the multi cloud that makes it multi networking and multi vendor and easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that's hops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not going to solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six months ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed a good is that watching leader would put there yeah something that you see in your organizations are you recommending that to people do you see I mean I'm just I would guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I say from my side because we operate in the multi cloud environment so it really helps an official for us I think I would add that networking guys have always needed to use certifications to prove that they know what they know it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters buying helps give you validity so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics enough of the understandings that you have the tools necessary right so okay I guess my final question for you guys is why an eighth certification is relevant and then second part is share what the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why shouldn't someone want to be an ace-certified I'm used to right engineer I think my views a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get no I mean they're backwards so when you've got the training and the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding it okay so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network definition getting eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that's just the next progression I don't say I expend that to more automation engineers because we have those nails probably well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but I've never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who've tradition down on prime networking they can understand how that's going to work in the cloud too well I know we got just under 30 seconds left but I want to get one more question than just one more for the folks watching that are you may be younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacey we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions no we're going use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you've come from top-down now you're gonna start looking from bottom up and you want those different systems to cross communicate and say you've built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the how the pipes are working you guys know what's going some plumbing that's right and they gotta know how it works I had a code it it's right awesome thank you guys for great insights ace certain ABS your certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not gonna take long we got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the Cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community aviatrix comm starting a community a multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as to start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more importantly where they're going and define that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we solve we help you define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their twenty-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] you

[Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] you you you you [Music] [Music] [Music] [Music] ladies and gentlemen please take your seats good morning ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 alright so we've got a fantastic event today I'm really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a takeoff of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any PowerPoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got some owners chart of Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the US it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every Enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Franco Bree you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission-critical they care about visibility they care about control that about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers did they see the same thing we're going to validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're going to talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day two operations what does that mean well day 1 is one day of your life who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do i operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix we as leaders ooh we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CCI es what Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when to try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of joob John Ferrier [Applause] okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel to customer panels before that Gartner is going to come out and talk about the industry we have a global system integrators they talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask some own rashard to come on stage from Gartner we'll kick it all up [Applause] [Music] okay so kicking things off certain started gardener the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer the ninety-two a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering in the marketplace with hybrid cloud and now moving quickly to multi cloud is really was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow IT or application people are sometime a DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right as with different account and they create mesh to manage them and they have direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides that the atoms that are sent removing that to that cloud they ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the ad hoc way doesn't scale at some point idea has to save them because they don't think about the - they don't think about operations we have a bunch of VPC and multiple clouds the other way that if you do the left and shift week they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these words are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct and that's what I call the optimal phase but even that they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS as accounts there's subscription and in as ER and GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that still wanna manage the cloud from an epi xx view I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they read they building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third-party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway up just a joke what do you see in terms of where people are in that multi cloud like a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in Azure one app in individuals one get app in Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never gonna happen what I've seen with enterprise is I'm gonna put the work load and the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking King be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run network part of the cloud connectivity to the cloud is kind of simple you know I agree IPSec VPN and I reckon Express route that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud providers right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean it's just the day-to-day operations after you know the natural let's add an app that's not a server let's troubleshoot a problem so what ending so your life if something changes now what do you do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's the hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi cloud wave that's coming as cloud native networking well there's no you know official gardener definition but I can create one on another spot is do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose API guys where is that optimization where's the focus well I think what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of that cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of view right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plan out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that playing out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and chip are they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco wants bring you star in the cloud they call that each guy anywhere right so everyone what and and then there's cloud vision for my red star and Khan trailers in a cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not really cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive well not so close one letter yeah so that was a big culture to reinvent take the tea out of cloud native it's cloud naive that went super viral you guys got t-shirts now I know you love yeah but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling up but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in Cisco you it's a little bit more native than other ones because they're really scr in the cloud you can't you you really like configure API so the cloud and NSX is going that way and so is Arista but they're incumbent they have their own tools is difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know a network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week I was only be two networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like aviation others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in a table us you can use it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck net sec Ops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this ability their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it V line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this V PC but this V PC automatically being your associate your account you cannot go out on the internet you have to go to the transit VPC so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI days which for us old folks know what that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objections oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well as I said earlier that once you you could easily provision in the cloud you can easily connect to the cloud is when you start troubleshooting application in the cloud and try to scale so this that's what the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead to 20% extra functionality that of course every Enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always going to be that extra functionality that in an automated and simple way that you talked about but yet powerful with up with the visible in control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggers who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some of the signals that are going on their environment what are some of the thresholds or things that are going on that there can pay attention to well one once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robbery will hit the road but as I said it's easier to prove it it's okay it's a TBS it's easy use a transit gateway put a few V PCs and you're done and you create some presents like equinox and do Direct Connect and Express route with Azure that looks simple as the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not but I'm telling you that I need to understand a basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server an internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know you not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this because honestly public cloud check hybrid cloud they're working on that that kids on premise is done now multi class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what there's cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start with especially an incumbent one so it's tempting to say I have a bunch of f5 experts nothing against f5 I'm going to bring my five in a cloud when you can use a needle be that automatically understand is ease and auto scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that met I'm going to use legacy stuff and then you have to start taking okay what about visibility control about the three cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming summit in charge with Gardner thanks for sharing thank you appreciate it thanks [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of that data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement myth aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for her aviatrix already working in Amazon and now works in Missouri as well before we knew what GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake measure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build or done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments David should Nick with fact set guys welcome to the stage for this digital event come on up [Applause] [Music] hey good to see you thank you okay okay customer pal this is my favorite part we get to hear the real scoop against a gardener given this the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with a live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and the soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets and different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation --all opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on bram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we're we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into more of a multi cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you had some comments about architecture matters it all starts I mean every Enterprise I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep versus Justice Network and that fourth generation architectures be based primarily upon Palo Alto Networks an aviatrix I have a trick to in the orchestration piece of it but that journey came because of the need for simplicity ok the need for a multi cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having the to automate that component and making it consistent with our on premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that sty and brought to the do the web side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was the middle it was a path that's probably the biggest lesson there is that when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective we like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those now we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gateway about a trans a gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and it evolved later and maybe optimized for change the way you're doing things in the future but don't sit around and wait you can't I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's David yeah talking as we prepare about a day to operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice to the architect I don't know what else I can do that simplicity of operations is key right all right so the holistic view of j2 operation you mentioned let's could jump in day one is you're you're you're getting stuff set up day two is your life after all right this is kind of what you're getting at David so what does that look like what are you envisioning as you look at that 20 miles their outpost multi-cloud world what are some of the things then you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router seoi and troubleshooting things on in an ad hoc nature so moving more towards a DevOps model there's anything on that day - yeah I would love to add something so in terms of date to operations you can you can either sort of ignore the day - operations for a little while where you get well well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to to realize it's it's such as such a big gap I think that's key because for us we're moving to more of an event-driven operations in the past monitoring got the job done it's impossible to modern monitor something that it's nothing there when the event happens all right so the event-driven application and then detection is important yeah I think Gardner was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the network's laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an equipment to encrypt and they they never get the question should i encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you got a lot of complexity in your network what do you guys look at the future for your environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance or things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting you got a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok wanna hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like encryption and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I'll see aviatrix is here they're their supplier to the sector but you guys are customers everyone's pitching you stuff these people are not gonna here to buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like we're API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like it's definitely it's definitely API driven we we definitely look at the at the PAP i structure of the vendors provide before we select anything that that is always first of mine and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking and more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what do what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on-site and they're gonna sit with you for a day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important probably how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's involving take off last year first you win so but that's different now because now you and you when you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so key is is that it can you be operational you know within hours or days instead of weeks right but do we also have the flexibility to customize it to meet your needs could you want to be you want to be put into a box with the other customers we have needs that surpassed or cut their needs yeah I almost see the challenge of you guys are living where you've got the cloud immediate value depending on roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's it there's a breaking point for sure you don't you don't get to scale this I like like Seamon said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've spent a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah you know part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization take pause you're kind of like off it's not how it works I mean what is the reality in terms of implementing you know in as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers what are the blockers what are the enablers I think the reality is is that you may not think your multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements Inc and then secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to lot of these clouds and they used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the problem from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business need and and like like you said it's whether whether you're in denial or not of the multi cloud fact that then your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or Azure and just helping facilitate things they're doing the you know the heavy lifting API work for you or are they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know you have designed yourself into a corner so the closer they're more than cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will they make sense tgw is a game changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool gives you the beauty of both worlds you can use tgw or the Gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go mole to one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint you agree with that premise and then witness multi-cloud stitch them all together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction to add value but the the network problem is still the same go away yeah yeah I mean you don't want to be trying to fit a square into a round Hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the then they're working for structure is there secure is available and is multi cloud capable yeah I'm at the end the day you guys just validating that it's the networking game now cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate Thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John for its Dee Mulaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Koopa Pokemon stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move attack from A to B and you get work gloves exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your taking yeah I mean it it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to iterate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer but okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like to we started out very much focused on one cloud and as we started doing Atkins we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are available and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really got the enabler for this multi cloud trend but you guys taken we'll start with a mint what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it means the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's a latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea our job is to enable them not to disable them do you think I do you guys think infrastructure has code which I love that I think that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network is code because stores and compute working really well is seeing all kubernetes and service master and network is code reality is that there is got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way three guys do it yeah and even security groups and then on top an aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah think about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made cuz it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on-prem and what and then so first that and then also in the journey where are you at from 0 to 100 of actually in the journey to cloud do you 50% there are you 10% are you vacuum datacenters next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's gonna be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of lift and shift and when did that start and we started about three years ago okay okay cool bye it's a very different story it started from a garage and 100% on the clock it's a business spend management platform as a software as a service 100% on the cloud it was like 10 years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you is or you guys mentioned DevOps I mean honestly we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interesting we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for as or as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth I think availability with your sim pop3 things guys SLA I mean you just do ping times between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads SLA is will be all of the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and what our ability is hour is there and our authority needs to operate on that so it's solely use the software dashboard look at the times and look at the latency in the old day is strong so on open so on you try to figure it out and then your day is you have to figure out just what's your answer to that because you're in the middle of it yeah I mean I think the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that's starting start tracking your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment over that was it from day one now there are two divisions one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting how do I solve our guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public Internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just on your thoughts on that I think any comment on that so actually multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are hiking people using them but Google's got a great network he googles networks pretty damn good and then you got Asher what's the difference between the clouds who where they evolve something where they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is the approach is different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network can span regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the I mean I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architect your own solution for example Amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has a banjo it's third to market and so it has seen what a sure did wrong it's seen what AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the the inability or the ability for Amazon to limit layer two broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you get talking about the cloud impact so that means st when the old st winds kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high speed but now when you take a win and make the essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah i think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you're a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there land when same concept as that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's what you're seeing so much infrastructure as code yeah yeah so for me I'll go back again to this its bandwidth and its latency right that that define those two land versus when but the other thing that comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to protect what's inside of it so for us we're able to deliver VRS or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning that's architecture thoughts on security are you guys are dealing with it yeah start from the base have app to app security built-in have TLS have encryption on the data a transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principals day security is day zero every day and so we we always build it into our design we want our architecture into our applications its encrypt everything its TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff was interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive insane that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's not me being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total B yes but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's giving you all these and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need a benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great pen how about a round of applause DX easy solutions integrating company that we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba porco will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs its critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products that incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the lance cloud connectivity there's a new line of networking services that we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services an aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a v8 church we were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed for work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole in their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT infrastructure baby Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John fray with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we start from the customer panel you can see the diversity of where people come into the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yep yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we were having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying we're starting to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the apps and then we evolved into that next journey which is a foundational approach to what are some of the problem statements customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they did digging into yeah some complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard parts now upon us are you referring to networking what is specifically were you getting at Tara says the easy parts done that so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises that are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the >> so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean - does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it okay in our internal environment as you know we're a huge company or as customers are in 30 so we're experiencing that internal okay and every one of our other customers so I I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c @ w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking but simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the at the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I what I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better Bank visibily is a huge thing jump in security alone network everything's around visibility what automation you see happening in terms of progression order of operations if you will it's the low-hanging fruit what are people working on now and what are what are some of the aspirational goals around when you start thinking about multi cloud an automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were going to integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of athe let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference architectures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi cloud in terms of you know customers want choice didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and D risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an Billee approach is how do things interoperate we test it out we validate it we build a reference architecture says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it invisibility so I think the visibility is what's what I see lack in cross industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in there one of the ones that are emerging and the new brands emerging with multi cloud you still got the old guard incumbent with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question what we were defining day to operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve that the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonishing trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is the what's what happens there they call you up and say hey I need multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got to factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what does VPC sharing you know what is a private link and asher how does that impact your business you know customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I've been is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to meet their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't again reveal kind of who they are but what does success look like in multi-cloud as you as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in is you build that network foundation at architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi-cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off Prem and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen with what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators [Applause] [Music] okay welcome back from the live feed I'm chef for with the q Steve Valenti CEO of aviatrix my co-host our next panel is the aviatrix certified engineer is also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foss from informatica Stacy linear from Teradata and Jennifer Reed with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds story to new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like it Squadron Leader Roger and leader yeah Squadron Leader he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer we'll start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm really working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but networking in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the V PC is and on the instant side is a security group or is it going on print and is this something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be will good I'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in never I've always been the network's fault and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another 100 and these times are changing yeah they say you're Squadron Leader I get that right what is what is the squadron leader first can you describe what it is I think probably just leading all the network components of it but not they from my perspective when to think about what you ask them was it's about no issues and the escalation soft my day is a good outcome that's a good day it's a good day again every mission the Amazon this brings up a good point you know when you have these new waves come in you have a lot of new things new we use cases a lot of the finger-pointing it's that guys problem that girls problem so what how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in was where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Steve and the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear like what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are four logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about yeah that's never fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young piece so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way here you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and old guys that's where we thrive Jennifer you mentioned you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static because back then you just said the network you got a perimeter yeah I know there was no such thing yeah no so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it and how I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this with and programmability is it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global s eyes cover the business issues what does it mean to do that is it code is that networking is the configuration is that aviatrix what is the I mean obviate races the ACE certifications but what is it about the multi cloud that makes it multi networking and multi vendor easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that is ops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not gonna solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed good is that watching leader would put there yeah is that something that you see in your organization's are you recommending that to people do you see I mean I'm just I guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I see from my side because we operate in the multi cloud environment so it really helps and it's beneficial for us yeah I think I would add that uh networking guys have always needed to use certifications to prove that they know what they know right it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters by your name helps give you validity um so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics and enough of the understandings that you have the tools necessary right so I guess my final question for you guys is why an eighth certification is relevant and then second part is share with the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why should someone want to be an ace-certified I'm used to write engineer I think my view is a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get know I mean they're backwards so when you've got the training in the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding of ok so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network initially eating eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that it's just the next progression I would say I expand that to more automation engineers because we have those nails probably extended as well well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but have never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who have tradition down on Prem networking they can understand how that's going to work in the cloud - well I know we've got just under 30 seconds left but I want to get one more question and just one more for the folks watching that are you maybe younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacy we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions networking use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you you've come from top-down now you're gonna start looking from bottom-up and you want those different systems to cross communicate and say you built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the pilot pipes are working and some plumbing that's right works at how to code it that's right awesome thank you guys for great insights ace certain babies you're certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not going to take long we've got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the Aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community a bh6 comm was starting a community at multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more important where they're going and to find that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we saw we help you cook define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their 20-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] [Applause] [Music] you

>> Hey, welcome back already, Jeffrey. Here with the Cube, we are high Top San Francisco in the Salesforce Tower and the brand new A century's Thean Novation hub opened up, I don't know. Six months ago or so, we were here for the opening. It's a really spectacular space with a really cool Cinderella stare. So if you come, make sure you check that out. We're talking about a cloud in the evolution of cloud and hybrid cloud. And clearly two players that are right in the middle is helping customers get through this journey and do these migrations. Our center and h. P. E s were excited to have our next guest, Melissa Bessie. She is the managing director, Intelligent cloud and infrastructure strategic partnerships at a center. Melissa. Welcome. And joining us from HP is David Stone. He's the VP of ecosystem sales. They have a great to see you. >> Thanks for having me. >> So let's just jump into it. The cloud discussion has taken over for the last 10 years, but it's really continuing to evolve. It was kind of this this new entrance with aws kind of coming on the scene. One of the great lines of Jeff Basil's talks about is they had no competition for seven years. Nobody recognized that the the bookseller out on the left hand ah, edges coming in to take the river structure business. But as things have moved to Public Cloud, now there's hybrid cloud. No, no. All applications or work clothes are right for a public cloud. So now, while the enterprises are trying to figure this out, they want to make their moves. But it's complicated. So first of all, let's talk about some of the vocabulary hybrid cloud versus multi cloud one of those terms mean to you and your customers started Melissa. >> Sure. So when you think of multi cloud, right, we're seeing a big convergence of I would say multi Kludd operating model that really has to integrate across all the clouds. So you have your public cloud providers. You have your sass like, uh, sales force at work day, you have your pass right? And so when you think of multi cloud, any customers goingto have a plethora of all of these types of clouds and really being able to manage across those becomes critical. When you think of hybrid cloud hybrid cloud is really thinking about the placement of ill. We usually look at it from a data perspective, right? Are you going to put your data in the public or in the private space? And so you can't look at it from that perspective, and it really enables that data movement across both of those clouds. >> So what would you see? David and your, uh, your customers? I say that a >> lot of the customers that we see today or confused right the people who have gone to the public cloud have scratched their heads and said, Jeez, what do I do? It's not as cheap as I thought it was gonna be. So the ones who were early adopters or confused the ones who haven't moved yet are really scratching their head as well, Right, because if you don't have the right strategy, you'll end up getting boxed in. You'll pay a ton of money to get your data in, and you'll pay a ton of money to get your data out. And so all of our customers, you know, want the right hybrid strategy, and I think that's where the market and I know a center and HPD clearly see them, the market really becoming a hybrid world. >> It's interesting, Melissa, You said it's based on the data, and you just talked about moving data in and out where we more often hear it talked about workload. This kind of horses for courses, you know, it's a workload specific should be deployed in this particular kind of infrastructure configuration. But you both mentioned data, and there's a lot of conversation kind of pre cloud about data, gravity and how expensive it is to move the date and the age old thing. Do you move the compute to the data, or do you move the data to the compute? A lot of advantages if you have that data in the cloud, but you're highlighting a couple of the ah, the real negatives in terms of potential cost implications. And we didn't even get into regulations and some of the other things that drive workloads to stay in the data center. So how should people start thinking about these variables when they're trying to figure out what to do next? >> Ex enters position Definitely like when we started off on our hybrid cloud journey was to capture the workload and once you have that workload you could really balance. It's the public benefits of speed, innovation and consumption with the private benefits of actually regulation, data, gravity and performance. Right? And so our whole approach and big bet has been able is been to basically we had really good leading public capabilities because we got into the market early. But we knew our customers were not going to be able to migrate their entire estate over to public. And so in doing that, we we said, OK, if we create a hybrid capability that is highly automated, that is consumed like public, Um and that is standard. We'd be able to offer our customers a weight of pick, really the right workload in the right place at the right price. And that was really what? Our whole goal waas. >> Yeah, and so just the Adama Melissa said, I think we also think about at least, uh, you know, keeping the data in a place where you want but then being cloud adjacent. So getting in the right data centers and we often use the cloud saying to bring the cloud to the data right? So if you have the right hybrid strategy. You put the data where it makes the most sense where you want to maintain the security and privacy. Ah, but then have access to the AP eyes and whatever else you might need to get the full advantages of the public cloud. >> Yeah, and we hear a lot of the data center providers like quinyx and stuff talking about features like Direct Connect and Noted Toe have this proximity between the public cloud and the and the stuff that's in your private cloud so that you do have no low latent see, and you can when you do have to move things or you do need to access that data. It's not so far away. Um, I'm curious about the impact of companies like Salesforce with Salesforce Tower here in San Francisco at the Centre Offices and Office 3 65 and Work Day on how kind of the adoption of the SAS applications have changed. The conversation about Cloud or what's important and not important, needs to be security. I don't trust eating outside my data center Now, one might argue that public clouds are more secure in some ways than in private cloud. You have disgruntled employees per se running around the data centers on plugging things. So how? How is the adoption of things like Officer 65? Clearly, Microsoft's leverage that in a big way to grow their own cloud presence changed the conversation about what's good about Cloud. What's not good about Chlo? Why should we move in this direction? But if you have thought >> no, look, it's a great question, and I think if you think about that, his Melissa said, the use cases right and Microsoft is have sex. Feli successfully pivoted their business to it as a service model, right? And so what I think it's done is it's opened up innovation, and a lot of the sales forces of the world have adapted their business models. And that's truly to your point, a sass based offer. And so when you could do a work day or a salesforce dot com implementation shirt, it's been built that it's tested and everything else I think, what then becomes the bigger question in the bigger challenges. Most companies air sitting on 1000 applications that have been built over time, and what do you do with those? And so in many cases, you need to be connected to those SAS space providers. But you need the right hybrid strategy again. To be able to figure out how to connect those SAS based service is to whatever you're gonna do with those 1000 workloads and those 1000 workloads running on different things that you need the right strategy to figure out where to put the actual workloads and is people they're trying to go. I know one of the questions that comes up is Do you my grade or do you modernize? And so as people put that strategy together, I think how you tied to those SAS based service is clearly ties into your hybrid strategy, >> I would agree. And so, as David mentioned, right, that's where the clouded Jason see, you're seeing a lot of blur between public and private. I mean, Google's providing bare metal is a service, so it is actually dedicated hybrid cloud capabilities. Right? So you're seeing a lot of everyone. And as as David talked about all of the surrounding applications around your s a P around Oracle, when we created our ex enter hyper cloud, we were going after the enterprise workload. But there is a lot of legacy and other ones that need that data and or the sales force data, whatever the data is right and really be able to utilize it when they need to in a real low leagues. >> So let's I want to get unpacked. The ah central hybrid cloud. Um, what is that exactly is that is that your guys own cloud is, you know, kind of a solution set. I've heard that mentioned a couple of times. So what is the centre? Hyper cloud? >> So eccentric hybrid cloud was a big bet we made as we saw the convergence of multi cloud. We really said, We know we everything is not gonna go public and in some cases it's all coming back. And so customers really needed a way to look at all of their workloads, right? Because part of the issue with the getting the cost of the benefits out of public is the workload goes. But you really don't earn able to get out of the data center. We terminate the wild animal park because there's a lot of applications that right Are you going to modernize? Are you goingto let them to end of life? so there's a lot of things you have to consider to truly exit a data center strategy. And so its center hybrid cloud is actually a big bet we made. It is a highly automated, standard private cloud capability that really augments all of the leading capability we had in the cloud area. It is it's differentiated women, a big bet with HP. It's differentiated on its hardware. One of the reasons when we're going after the enterprise was they need large compute. They have large computer and large storage requirements, and what we were able to dio is when we created this used some of our automation differentiation. We have actually a client that we had an existing Io environment. We were actually able to achieve some significant benefits just from the automation. We got 50% in the provisioning of applications. We got 40% in the provisioning in the V m on, and we were able to take a lot of what I'll call the manual tasks and down Thio. It was like 62% reduction in the effort as well as a 33% savings overall in getting things production ready. So this capability is highly automated. It will actually repeat the provisioning at the application level because we're going after the enterprise workloads and it will create these. It's an asset that came from the government. So it's highly secured. Um, and it really was able to preserve. I think, what our customer needed and being able to span that public private capability they need out there in the hybrid world. >> Yeah, you could say I don't know that there's enough talk aboutthe complexity of the management in these worlds. Nobody ever wants to talk about writing this a sideman piece of the software, right? It's all about the core functionality. Let's shift gears a little bit. Talk about HBC. A lot of conversation about high performance computing, a lot going on with a I and machine learning now, which you know most of those benefits are going to be realized in a specific application, right? It's a machine learning or artificial intelligence apply to a specific application. So again, you guys big, big iron and been making big iron for ah, long time. What is this kind of hybrid cloud open up in terms of HB Ito have the big, heavy big heavy metal instead it and still have kind of the agility and flexibility of a cloud type of infrastructure. >> Yeah, no, I think it's a great question. I think if you think about what HB strategy has been in this area and high performance compute, we bought the company SG eye on. As you've seen, the announcements were hopefully gonna close on the Kree acquisition as well. And so we see in the world of the data continuing to expand in huge volumes, the need to have incredible horsepower to drive that associated with it. Now all of this really requires Where's your data being created and where's it actually being consumed? And so you need to have the right edge to cloud strategy and everything. And so in many cases, you need enough compute at the edge to be able to compute in do stuff in real time. But in many cases, you need to feed all that data back into ah, Mother Cloud or some sort of mother HP, you know, e type of high performance, confused environment that can actually run the more advanced a I in machine learning type of applications to really get the insights and tune the algorithms and then push some of those AP eyes and applications back to the edge. So it's it's an area of huge investment. It's an area where because of the late and see, uh, and you know things like autonomous driving and things like that. You can't put all that stuff into the public cloud. But you need the public cloud or you need cloud type capability if you will have able to compute and make the right decisions at the right time. So it's about having the right computer technology at the right place at the right time. The right cost and the right perform a >> lot of rights. Yeah, good opportunity for a center. So I mean, it's it's funny as we talk about hybrid cloud and and that kind of new new verbs around Cloud and cloud like things is where we're gonna see the same thing. Kind of the edge, the edge versus the data center comparison in terms of where the data is, where the processing is because it's gonna be this really dynamic situation, and how much can you push out? I was like the edge because there was no air conditioning a lot of times, and the power might not be that grade. And maybe connectivity is a little bit limited. So, you know, EJ offers a whole bunch of different challenges that you can control for in a data center. But it is going to be this crazy kind of hybrid world there, too, in terms of where the allocation of those resource is. Are you guys getting deeper into that model, Melissa? >> So we're definitely working with HP again to create some of all call it our edge. Manage. Service is again going back to what we're saying about the data, right? We saw the centralization of data with a cloud with the initial entrance into the cloud. Now we're seeing the decentralization of that data back out to the edge. Um, with that right in these hybrid cloud models, you're really going to need. They require a lot of high performance compute, especially for certain industries, right? If you take a look at gas, oil and exploration, if you look at media processing right, all of these need to be able to do that. One of the things and depending on where it's located, if it's on the edge. How you're gonna feed back the data as we talked about. And so we're looking at How do you take this foundation? Right. This all colonic center hybrid. Um, architecture. I take that and play that intermediate role. I'm gonna call it intermediary. Right, Because you really need a really good you know, global data map. You need a good supply chain, right? Really? To make sure that the data, no matter where it's coming from, is going to be available for that application at the right time, with right, the ability to do it at speed. And so all of these things air factors as we look at our hole ex center, hybrid cloud strategy, right? And being able to manage that EJ decor and then back out to cloud exactly >> right. And I wonder if you could share some stories because the value proposition I think around cloud is significantly shifted for those who are paying attention, right? It's not about cost. It's not about cost savings. I mean, there's a lot of that in there, and that's good. But really, the opportunity is about speed, speed and innovation and enabling more innovation across your enterprise. with more people having more access to more data to build more APS and really to react. Are people getting that or they still the customer still kind of encumbered by this this kind of transition phase. They're still trying to sort it out. Or do they get it? That that really this opportunity is about speed, Speed, speed? No, >> go ahead. I mean, we use a phrase first offices here. No cloud, right. So to your point, you know, how do you figure out the right strategy? But I think within that you you get what's the right application and how do you fit it into the overall strategy of what you're trying to do? >> And I think the other thing that we're seeing is, um, you know, customers are trying to figure that out. We have a whole right. When you start with that application map, you know, there could be 500 to 1000 workloads, write applications. And how are you going to some? You're gonna retain some? You're gonna retire some. You're gonna reap age. You're gonna re factor for the cloud or for your private cloud capability. Whatever it is you're going to be looking at doing? Um, I think, you know, we're seeing early adopters like even the papers killers themselves, right? They recognize the speed. So, you know, we're working with Google. For instance. They wanted to get into the bare metal as a service capability. Write them, actually building it. Getting it out to market would take so much longer. We already had this whole ex center hybrid cloud architecture that was cloud adjacent, so we had sub millisecond latency, and so their loved ones, Right? Everyone's figuring out that utilizing all of these, I'll call it platforms and pre book capabilities. Many of our partners have them as well is really allowing them that innovation, get products to market sooner, be able to respond to their customers because it is, as we talked about this multi cloud were lots of things that you have to manage if you can get pieces from multiple plate, you know, from a partner right that can provide Maur of the service is that you need it really enables the management of right, >> right, So gonna wrap it up. I won't give you the last word in terms of what's the what's the most consistent blind spot that you see when you're first engaging with a customer who's who's relatively early on this journey that that they miss that you see over and over and over. And you're like, you know, these are some of the things you really gotta think about that they haven't thought about >> Yeah, so for me, I think it's the cloud isn't about a destination. It's about an experience. And so how do you get you talked about the operations? But how do you provide that overall experience? I like to use a simple analogy that if you and I needed a car for five or 10 or 15 minutes, you go get a new bir. Uh, because it's easy. It's quick. If you need a car for a couple days to do a rent a car, we need a car for a year. You might do at least you need a car for 34 years. You probably buy it right. And so if you use that analogy and think whom I need a workload or in the application for 56 years putting something out, persistent workload that you know about on a public cloud, maybe the right answer, but it might be a lot more cost prohibitive. But if you need something that you can stand up in five minutes and shut right back down, the public cloud is absolutely the right way to go is long as you can deal with the security requirements and stuff. So if you think you think about what are the actual requirements, is it costs is a performance. You've talked about speed and everything else it really trying to figure out you get an experience and the only experience that can really hit you. What you need to do today is a having the right hybrid strategy and every company and a century was out way in front of the market on Public Cloud, and now they've come to the realization, and so has many other places. The world is going to be hybrid, and it's gonna be multi cloud. And as long as you can have an experience and a partner that can manage, you know, help you to find the right path, you'll be on the right journey. >> I think the blinds, but we run into is it does start off as a cost savings activity, and they're really. It really is so much more about how you're going to manage that enterprise workload. How are we gonna worry about the data? Are you gonna have access to it? Are you gonna be able to make it fluid, right. The whole essence of cloud, right? What? It What it disrupted was the I thought that something had to stay in one place, right? And that you were the real time decisions were being made where things needed to happen. Now, through all the different clouds as well as that, you had to own it yourself, right? I mean, everyone always thought Okay, uh, I'll take all of the I T. Department. Very protective of everything that wanted to keep. Now it's about saying, All right, how do I utilize the best of each of these multi clouds to stand up? What? I'll call what their core capability is as a customer, right? Are they do in the next chip design or hey, you know, doing financial market models right? That requires a high performance capability, right? So when you start to think about all of this stuff, right, that's the true power. Is is having a strategy that looks at those outcomes. What am I trying to achieve in getting my products and service is to market and touching the car customers I need versus Oh, I'm gonna move this out to an infrastructure because that's what God will save me. Money, Right, Bench. Typically the downfall we see because they're not looking at it from the workload of the application. >> Same old story, right? Focus on your core differentiator and outsource the heavy lifting on the stuff that that's not your core. All right, Well, Melissa David, Thanks for taking a minute and really enjoyed the conversation. Is Melissa? He's David. I'm Jeff. Rick, you're watching. The Cube were high above the San Francisco skyline in the sales force. Tyra. The essential innovation up. Thanks for watching. We'll see you next time.

(dramatic music) >> Hey, welcome back everybody. Jeff Frick here with theCUBE. We're in our Palo Alto studio for a CUBE conversation. It's really a great thing that we like to take advantage of. A little less hectic than the show world and we're right in the middle of all the shows, if you're paying attention. So we're happy to have a CUBE alumni on. He's been on many, many times. Saar Gillai , he's now the CEO of Teridion. And Saar, welcome. I don't think we've talked to you since you've been in this new role. >> Yeah, it's been about a year I think. >> Been 'about a year. So give us kind of the update on Teridion. What it's all about and really more importantly, what attracted you to the opportunity? >> Sure. First of all, great to be here. I don't know where John is. I'm looking for him. He ran away. Maybe he knew I was coming. >> Somewhere over the Atlantic I think. 35,000 feet. >> I'll follow up on that later but hey, you're here. So, you know Teridion, let's talk about maybe the challenge that Teridion is addressing first so people will understand that, right. So if you look about what's going on these days with the advent of Cloud. and how people are really accessing stuff, things have really moved in the past. Most of the important services that people access were in a data center and were accessed through the LAN so the enterprise had control over them and if you wanted to access an app, if it didn't work, somebody when into the LAN, played around with some CISCO router and things maybe got better. >> But at least you had control. >> You had control and if you look at what's happened over the last decade, but certainly in the last five years, with SAS and the Cloud. Stating the obvious, more and more of your services now are actually being accessed through your WAN and in many cases, that actually means the internet itself. If you're accessing Salesforce or Box or Ignite or any of these services. The challenge with that is that now means that a critical part of your user experience, you don't control. The vendor doesn't control because you can make the best SAS up in the world but, and those apps are increasingly very dynamic. Caching doesn't solve this problem and the problem is now, okay, but I'm experiencing it over the internet. And while the internet is a great tool obviously, it's not really built for reliabilty, consistency, and consistent speed. Reality, if you look at the internet, it was designed to sent one packet to NORAD and tell them that some nuclear missile died somewhere. That's what it was designed for right? So the packet will get there but the jitter and all these things may work and so what happens is that, now you have a consistency problem. Historically, people will say well, that's all been addressed through traditional caching and that's true. Caching still has it's place. The reality is though that caching is more for stuff that doesn't change a lot and now, it's all very dynamic. If you're uploading a file, that's not a caching activity. If you're doing something in Salesforce, it's very dynamic. It's not cached. At Teridion, we looked at this problem. Teridion's been around about four years. I've been there for about a year. We felt that the best way to solve this problem was actually to leverage some of the Cloud technology that already exists to solve it. So what we do, actually, is we build an overlay network on top of the public Cloud surface area. So instead of traditionally, the way people did things is they would build a network themselves but today the public Cloud guys honestly are spending gazillions of dollars building infrastructure. Why not leverage it the same way that you don't buy CPUs, why buy routers? What we do is we create a massive overlay network on demand on the public Cloud surface area. And public Cloud means not just Amazon or Google but also people like AliCloud, DigitalOcean, Vulture, any Cloud provider really, some Russian Cloud providers. And then we monitor the internet conditions and then we build a fast path. If you think about it almost like a ways, a fast path for your packet from wherever the customer is to your service thereby dramatically increasing the speed but also providing much higher reliabilty. >> So, lot of thoughts. If I'm hearing right, you're leveraging the public Cloud infrastructure so they're pipes, if you will. >> And they're CPUs. >> And they're CPUs but then you're putting basically waypoints on that packet's journey to reroute to a different public Cloud infrastructure for that next leg if that's more appropriate. >> Yeah, and basically what I'm doing is I'm basically just saying if there's a, if your server's here whether they're on a public Cloud or somewhere else, it doesn't matter, and a customer is here, through some redirection, I will create a router on a public Cloud so a soft router, somewhere close from a network perspective to a user and somewhere close to the server and then between them, I'll create an overlay fast path. And then, what is goes over will be based on whatever the algorithm figures out. The way we know where to go over is we also have a sensor network distributed throughout the public Cloud surface areas and it's constantly creating a heat map of where there's capacity, where there's problems, where there's jitter and we'll create a fast path. Typically that fast path will give you, one of the challenges, I'll give you an example. So let's say you're on Comcast and let's say you've got 40 meg let's say, your connection at home. And then you connect to some server and theoretically that server has much more, right? But reality is, when you do that connection, it's not going to be 40 meg. Sometimes it's 5 meg, okay? So we'll typically give you almost your full capacity that you have from your first provider all the way there by creating this fast path. >> So how does it compare, we hear things about like Direct Connect between Equinix and Amazon or a lot of peer relationships that get set up. How does what you're doing kind o' compare, contrast, play, compare to those solutions? >> Direct Connect is sort of a static connection. If you have an office and you want to have a Direct Connection, it's got advantages and it's useful in certain areas. Part of the challenge there is that first of all, it has a static capacity. It's static and it has a certain capacity. What we do, because it's completely software oriented, is we'll create a connection and if you want more capacity, we'll just create more routers. So you can have as much capacity as you want from wherever you want where with Direct Connect, you say I want this connection, this connection, this much capacity and it's static. So if you have something very static, then that may be a good solution for you but if you're trying to reach people at other places and it's dynamic, and also you want variable capacities. For example, let's say you say I want to pay for what I use. I don't want to pay for a line. Historically, when you're using these things, you say okay, if the maximum I may want is 40 meg, you say okay, give me a 40 meg line. That's expensive. >> Right, right. >> But what if you say I want 40 meg only for a few hours a day right? So in my case, you just say look, I want to do this many terabytes. And if you want to do it at 40 meg, do it at 40 meg. It doesn't matter. So it's much more dynamic and this lends itself more to the modern way of people thinking of things. Like the same way you used to own a server and you had to buy the strongest server you needed for the end of the month because maybe the finance guy needed to run something. Today you don't do that right? You just go to public Cloud and when it's the end of the month, you get more CPUs. We're the same thing. You just set a connection. If you need more capacity, then you'll get more capacity that you need. We had a customer that we were working with that was doing some mobile stuff in China and all of a sudden, they needed to do 600,000 connections a minute from China. And so we just scaled up. You don't have to preconfigure any of this stuff. >> Right, right. So that's really where you make the comparison of public Cloud for networking because you guys are leveraging public Cloud infrastructure, you're software based so that you can flex so you don't have the old model. >> It's completely elastic, like I said. It's very similar. Our view is the compute in the last decade, obviously, compute has moved from a very static I own everything mode to let's use dynamic resources as much as possible. Of course, there's been a lot of advantage to that. Why wouldn't your connectivity, especially your connectivity outside which is increasing your connectivity also use that paradigm. Why do you need to own all this stuff? >> Right, right. As you said before we turned the cameras on the value proposition to your customers who are the people that basically run these big apps, is the fact that they don't have to worry about that but net is just flat out faster to execute the simple operations like uploading or downloading something to BOX. >> And again, you mentioned BOX, they're one of our big customers and we have a massive network if you thing about how much BOX uploads in a given day, right? 'Cause there's a lot of there traffic that goes through us. But if you think about these SAS providers, they really need to focus on making their app as good as possible and advancing it and making it as sophisticated as possible and so, the problem is then there's this last edge which is from their server all the way to the customer, they don't really control. But that is really important to the customer experience, right? If you're trying to upload something to BOX or trying to use some website and it's really slow, your user experience is bad. It doesn't matter if it's the internet's fault. You're still as a customer, So this gives them control. They give us that ability and then we have control that we can give it much faster speed. Typically in the US, it may be two to five times faster. If you're going outside the US, it could be much faster sometimes. In China, we go 15 times faster. But also, it's consistent and if you have issues, we have a knock, we monitor, we can go look at it. If some customer says I have a problem, right? We'll immediately be able to say okay, here's the problem. Maybe there's a server issue and so forth as opposed to them saying I have a problem and the SAS vendor saying well, it's fine on our side. >> Right, right. So, I'm curious on your go to market. Obviously, you said BOX is a example of a customer. You've got some other ones on the website. Who are these big application service providers, that term came up the other day, like flashback to 1990. 1998 >> I call them SAS >> It's funny, we were talking about the old days. >> To me, it's all the same, as a service guy. >> But then, as you go to market then going to include going out directly through the public Clouds in some of their exchanges so that basically, I could just buy a faster throughput with the existing service. Where do you go from here? I imagine, who doesn't want faster internet service period? >> Yeah, we started off going to the people who have the biggest challenge and easier to work with a small company right? You want to work with a few big guys. They also help you design your solution, make sure it's good. If you can run BOX and Traffic and Ignite. Traffic can probably handle other things, last year for example. We are looking at potentially providing some of the service, for example, if you're accessing S3 for example, we can access S3 at least three times faster. So we are looking potentially at putting something on the web where you could just go to Amazon and sign up for that. The other thing that we're looking at, which is later in the year, probably is that we haven't gotten a lot of requests from people that said hey, since the WAN is the new LAN, right, and they want to also try to use this technology for their enterprise WAN between branch offices where SD-WAN is sort of playing today, we've gotten a lot of requests to leverage this technology also in SD-WAN and so we're also looking at how that could potentially play out because again, people just say look, why can't I use this for all my WAN connectivity? Why is it only for SAS connectivity? >> Right, right. I mean it makes sense. Again, who doesn't want, the network never goes fast enough, right? Never, never, never. >> It's not only speed. I agree with you but it's not only speed. What you find, what people take for granted in the LAN but they only notice it when now they're running over the LAN is that it's a business critical service. So you want it to be consistent. If it's up, it needs to have latency, jitter, control. It needs to be consistent. It can't be one second it's great, the next second it's bad and you don't know why and visibility. No one's ever had that problem. >> I'm just laughing. I'm thinking of our favorite Comcast here. If they're not a customer, you need to get them on your list. Help make some introductions hopefully. >> So, people take that for granted when they're LAN and then when they move to the Cloud, they just assume that it's going to continue but it doesn't actually work that way. Then they get people from branch offices complaining that they couldn't upload a doc or the sales person was slow and all these problems happen and the bigger issue is, not only is this a problem, you don't have control. As a person providing a service, you want to have control all the way so you can say "yeah, I can see it. "I'm fixing it for you here. "I fixed it for you." And so it's about creating that connection and making it business critical. >> It's just a funny thing that we see over and over and over where cutting edge and brand new quickly becomes expected behavior very, very quickly. The best delivery by the best service, suddenly you have an expectation that that's going to be consistent across all your experiences with all your apps. So you got to deliver that QS. >> Yeah, and I think the other thing that we notice, of course, is because of the explosion of data right? It's true that the internet's capacity is growing but data is growing faster because people want to do more because CPUs are stronger, your handset is stronger and so, so much of it is dynamic. Like I said before, historically, some of this was solved by just let's cache everything. But today, everything is dynamic. It's bidirectional and the caching technology doesn't do that. It's not built for that. It's a different type of network. It's not built for this kind of capacity so as more and more stuff is dynamic, it becomes difficult to do these things and that's really where we play. And again, I think the key is that historically, you had to build everything. But the same way that you have all these SAS providers not building everything themselves but just building the app and then running on top of the public Cloud. The same thing is why would I go build a network when the public Cloud is investing a hundred billion dollars a year in building massive infrastructure. >> Yeah, and they are, big infrastructure. Well Saar, thanks for giving us the update and stopping by and we will watch the story unfold. >> Great to be here. >> Alright. And we'll send John a message. >> I'll have to track him down. >> Alright, he's Saar, I'm Jeff. You're watching theCUBE. It's a CUBE conversation at our Palo Alto Studio. Thanks for watching. We'll see you next time. (dramatic music)

>> Live from Orlando, Florida. It's theCUBE. Covering Microsoft Ignite. Brought to you by Cohesity and theCUBE's ecosystem partners. >> Welcome back everyone to theCUBE's live coverage of Microsoft Ignite here in Orlando. I am your host Rebecca Night, hosting, co-hosting along side Stu Miniman. We are joined today by Steven Rosenthal. He is the senior product specialist at QTS Data Centers. Thank you so much for coming on theCUBE. >> You're welcome, thank you. >> So let's start by finding out a little bit more about QTS, based in Kansas City. What do you do? What are you all about? >> Yeah, so QTS is based in Overland Park, Kansas. We have our operations based in, actually right outside of Atlanta in Suwanee, Georgia where actually I'm from. And we have 16 data centers across the United States, about six million square feet of data center floor. We cater to everybody from hyperscalers, the hyperscalers of the world that everybody, I think, knows about, to enterprises, to federal customers. We have product lines that cover, again, hyperscale, co-location, private cloud; which I think we'll talk about today and mannered services around that private cloud offering. >> I know Stu is dying to talk private cloud with you but-- (Stu Laughs) Can you just tell us a little bit about how you fit in precisely with the Microsoft Ecosystem? >> Yeah, so, we fit in because we will offer Azure Management, so for customers that will have work loads up on Azure, we can help manage that and we also have dedicated connections through our connectivity products that will get you to Azure from our data centers. So, that's how we kind of fit into this ecosystem. >> Alright, so, just to geek out on that one little bit, when I talk to a lot of service providers, things like AWS direct connect, and Azure Express Route are one of the things we're seeing just massive adoption on being able to take my own stuff and plug it in or use services from the public clouds. Do you offer all of those? >> So we have AWS Direct Connect in our Chicago data center that we can cross connect to you, to that via our other data centers. We're also utilizing the software to find networks as back-up fabric and megaport to get you to those direct routes into Azure and AWS. >> Okay, great. So you do have the way to, 'cause the discussion has been, for a few years it went from hosting to service providers and, oh wait, public cloud is the enemy. And now I think we've matured a lot. It's like, yes, of course there's competition there, but as SoftDel and Microsoft said, look we're going to compete against people, we're going to partner with a lot of people. And, of course, your customer's are using everything. >> Yeah, I don't think it's just a line. We definitely partner with the public cloud offerings. It's not if you can't beat them join them, there is a workload for public cloud, there's workloads for private clouds and we can get into that into detail, but there is absolutely a partnership that we can have there and not a competitive partnership. >> Yeah and I actually, let's bridge that discussion over to the private cloud discussion. You know, I will give you the one there is no answer for it, but how are customer's sorting this thing out? How are you dealing with it? What do they put where? How do you help them with that discussion? >> You know, what we're finding is customers are anywhere from all into public cloud, to I'm kind of just dabbling in it and maybe putting my toe into it. And we can go in and help them along their cloud journey. So, because of the integrative products that we have within QTS, we can help you from just being a co-location customer to kind of dipping your toe in a little bit with some public clouds. Getting you that direct access via AWS Direct Connect or via software to find networking, helping you manage that, but there is workloads out there that customers just want to know where their data is. Where is my data? When you go to a public cloud, I'm not saying it's not safe, it's not secure, but we all know there's issues that sometimes they go down and there's customers, for compliancy reasons, for whatever reason they have, they want to know my data is in Suwanee, Georgia and due to the private cloud, and we know it's always there, we can provide that to the customer. >> Do you think that customer anxiety of where is my data will always exist for certain clients or do you think we will actually get to a point in the cloud computing evolution where people feel really secure? >> You know, I think if you look over the last few years, people are a lot more secure today than they were three years ago, two years ago or even one year ago. So, if I had a crystal ball, I think people will get a little bit more comfortable, but I think customer's in finance-- >> Healthcare. >> Healthcare. They're all going to really be nervous about where that data is, so there's always going to be that need for that. Certain workloads, I want here. The rest of it, yeah, we can put up in public cloud, but I want to know that this data resides in this data center. >> Yeah. I mean, governance and compliance is obviously going to play into that. So, let's talk about the private cloud. In our research, we started a few years ago, we said, what customer's need is true private cloud. And we said that because cloud should really be an operating model and the public cloud really set the bar as to, how I consume, how I manage, how I don't have to get into some of the pieces, so, to do that, you really need to kind of modernize the platform. Maybe bring us through your journey as to how you've seen it versus just kind of, I had a bunch of servers in Iraq, versus how do you define what is private cloud for your environment today? >> Yeah, so at QTS, we define the entire stack is dedicated to a customer. That's everything from the Nutanix hardware that we use and we decide to use as our infrastructure base for this. All the way up to the Cisco 9K's that we support. Everything is dedicated to that customer. So, there's no multi-tendency at all within that. So, there's no noisy neighbors, there's nobody next to you that you may not know what they're doing. Our journey started about a year ago, maybe a little bit more. Where we saw that, as everyone probably did, the evolution of the customer going to that true hybrid model. That not everything is going to public. They, again, not to repeat myself, but there are some workloads that stay within the private cloud and they needed somewhere to put that. Customers also were looking for more of an optics model than a capics model. We can host that for them within our data centers, provide all the data center services that we provide to our COLO customer's around duplicate power and the security that we provide and allow them to host that within our data centers. So that's what we're seeing in our customers and that's what is really driving that. >> Alright. When Nutanix positions the enterprise, it really is about that simplicity that they can offer. Service providers often have different metrics as to how you determine. What lead you to the Nutanix solution? How does that fit in your over all operations? >> Yeah. Honestly, we did, for lack of better terms, a bake off. We looked at competitors out there but Nutanix, by far, they have a right to be in that Gartner Magic Quadrant because, one, their support is just excellent, that we have found from them everything that we needed from them. They were right there and helping us. Up until now and we don't think they're going anywhere either, right? Nutanix has been one of our best technology partners that we've brought on board. And we see the benefits of the hyper-converged environment, allowing us, you talked about people want that cloud experience >> Right. >> The loud experience is, I want to be able to swipe my credit card and have a server running in five minutes. That's not what dedicated private clouds are, but they might want it less than 30 days, less than 60 days. Having hyper-converged there, we can provide that to the customer, get them up and running in a matter of weeks, not a matter of months. You know with their traditional architecture. >> One of the things we're hearing a lot at this conference is the importance of having the right kinds of partners and making sure that there is a lot of trust embedded in the relationship. >> Right. >> You just described, choosing Nutanix, having this bake off, how else do you walk through the, can you walk our viewers through the process of how you choose the right people that you want to do business with, from sort of a business mindset stand point, but also, complimentary functionality? >> I think a couple things. One, we obviously look at the technology. Technology for us is, if not number one, it's up there as pretty close to number one. Does the technology meet the needs of our customers? Can we provide the service with the service level agreements that we have in place? Around our hosted private cloud, we have 100% SLA around that, so we want to make sure that we can meet that for the customer. So, the technology has to be there. Then, outside the technology, the support. This is technology, technology's going to have issues. If we can make sure we have the support to back that up, so if a customer or we have an issue with the infrastructure, we can bring that back online as quick as possible. Then we look at, how closely they can do, you know, co-market with us, especially Nutanix. We do a lot of things co-marketing with Nutanix. We put on panels within our data centers. We've been doing this for the past, almost a year now, with Nutanix, ourselves, maybe we'll have AWS sit on it, we'll have Cohesity sit on it, and bring in customers or prospects into our data centers and have different topics around there, so all of that kind of mixed together, provides a really good partnership for us. >> Great. >> Steve, we talked a little bit about how Azure on the public cloud fits in. How does Microsoft fit in on the private cloud discussion? >> So, most of our customers are running Windows. I mean that's really where it fits in. >> Of course. >> Currently, our hosted private cloud runs VMRS as a hypervisor-- >> Right. >> But most of the customers are running Windows as their operating system. >> Absolutely. Still, I mean, from the early days until today, the applications sits on top. Microsoft has all the business apps up there. Been a lot of announcements at the show. Windows Server 2019, talking a lot about the shift to SaaS. How are you seeing, is that still a big driver for your customers, the generational shifts of Windows and what about the changing workloads? I'm curious about how those impact you. >> Yeah, absolutely. The changing workloads definitely drives our business and as you pointed out, a lot of those are going to either Office 365, going up to Azure. We're getting a lot more customers asking us for Azure these days. I don't want to put AWS against Azure, but we are at the Microsoft show, obviously. We're getting a lot of customers who are driving their business up to Azure and to be able to support that within our community is really important to be able to support that customer, so we are definitely seeing that drive towards those types of workloads. >> You're an industry veteran. You've been in IT for 25 years. I wonder if you could talk about this point in time that we're at now. It feels like an inflection point, but maybe I'm wrong. Can you sort of paint this point in time, in the greater context of the cloud computing revolution. >> I think hybrid is the word. Right? I know it's a marketing word. I know a lot of people use it, but I think it really has hit today. Where you have companies that say, hey, we are all in on public cloud and I think that's a great marketing term, but if you really look at all of their workloads, they don't have everything up there, but even if they have 90%, 10% of their workloads are Legacy applications that they would have to re-write to be able to really work in the public cloud and these applications are running just fine where they are, they don't want to touch them. So, I think that hybrid model is where we are today and it's only going to grow. >> Steven, I'm curious, we watched for a while, public cloud polled on the data center apps, but now we have the Edge out there. You talk about IOT, you talk about what machine to machine type technology is going to push things back out, not going to be in some central location. Is that having an impact yet on your business, how would you play in some of these IOT environments? >> Yeah, we are constantly looking at the new technologies out there, especially the autonomous cars is something that we are looking at very heavily and they require, there's something like six terabytes of data that gets passed back and forth between that car and whatever service is running that car and that's got to be somewhere on the Edge, but I think if you look back at how people were defining private cloud a couple years ago, how are people are defining Edge is very different. And over the next year or two, we will get more common, how people are defining Edge Computing will become a lot more common. So, we're looking at how do we plan that market? Do we have to have data centers closer to the Edge, wherever that edge is, in cities that you typically don't see data centers. You're probably going to have a different type of data center within that city too. >> Oh, yeah. Absolutely. The edge is very different if you are a telecom provider versus an enterprise, what you said. That data center is going to be a pop, is it going to be something in a wireless tower-- >> Is it going to be in a closet somewhere that supports it? >> It's all going to be something that just fits on a wrist at some point in the future, right? (all laughing) >> Yeah. It's going to fit right there. >> Yeah, check on my data. So, getting back to the cities that you don't necessarily think of. I mean, you're a tech, a cutting edge tech company, based in Kansas City, the Heartland. >> Right. >> How do you find, is it difficult to recruit talent because frankly even the companies in Silicone Valley and Washington and Boston, they're having trouble recruiting talent. Where do you come down? >> I think it's not only recruiting the talent, it's keeping the talent; which QTS is very good about keeping the talent. I think if you look at our attrition rate, it's probably some of the lowest in the industry 'cause we have a culture that people want to stay in, but even though our headquarters are in Overland Park, Kansas, again, our, really our operations headquarters are outside of Atlanta, Georgia in Suwanne which is probably just about 30 miles north. So, we have Georgia Tech that we can pull from, you have Emory that you can pull from and, you know, the entire Georgia University system. I don't want to leave anybody out that we can pull from. And we have data centers around the country, even in Silicone Valley, we have Santa Clara, which we can pull from the Silicone Valley individuals. Dallas has a lot of tech companies, so we're not just pulling from one market, we're pulling from 16 different markets across the country, which helps us a lot not just to dry up a single market. >> You said that QTS has a culture that people want to stay and Microsoft is touting its culture as collaborative, inclusive. Describe QTS's culture. >> Our culture, a lot of people ask me that and it's like, you got to live it. It's very, very family-oriented. I know a lot of people say that, but we live it. We care about each other. Nobody walks around going, it's not my job. Everybody is there to support the customer. We are very customer-focused, you can see that in our NPS scores. Our NPS scores are very high in the industry, probably some of the highest out there. So, and that goes back to just how we take care of our customers. And we look, goes back to your question about, what do we look for in partners, Nutanix probably has a very high NPS score and we want to make sure that our partners are treating our customers as we want to treat our customers. >> Great. Well, Steven, thank you so much for coming on theCUBE. >> Thank you. Appreciate it. >> I'm Rebecca Knight for Stu Miniman, we will have more from Microsoft Ignite, coming up in just a little bit.

>> Live, from Orlando, Florida, it's theCUBE, covering Microsoft Ignite. Brought to you by Cohesity and theCUBE's ecosystem partners. >> Welcome back, everyone, to theCUBE's live coverage of Microsoft Ignite. I'm your host, Rebecca Knight. Joined, of course, by my esteemed co-host, Stu Miniman. We have one guest for this segment, Bernard Golden. He is the vice president of Cloud Strategy at Capital One. Thank you so much for coming on the show Bernard. >> Well, thank you so much for inviting me to be on. >> You are famous in the world of cloud. You're named by wired.com as one of the most ten influential people in cloud computing. I'd love to just ask you a very broad question to start, and that is where are we right now with the cloud? Where do you see, what are sort of the biggest issue, the biggest challenges that you see with companies adopting and embracing the cloud right now? >> Well, unlike a lot of people, I think we're still a lot earlier in cloud adoption than other people do, maybe. If it were a baseball game, I'd say, maybe, the pitcher's coming out for the top of the second inning. And I think the barriers tend to be two-fold. One is, for traditional enterprises, there's still a lot of, we have a lot of embedded, a lot of legacy, a lot of investment, sunk costs, how can we step away from that, should we step away from that? So you hear a lot of discussion around what's the right role, hybrid clouds, so forth, and so on. For companies like Capital One that have said, "we're going all in on cloud," and Capital One has announced it's going all in on public cloud. Then the challenge becomes how do I adopt the practices of the organizations around the frontier of cloud? Because you have to really adapt a whole range of things. It's not just ... a lot of people treat cloud computing as kind of like it's a data center at the end of a wire. I have my traditional practices, my traditional models, my traditional tools, my traditional cost models. All of those things have to change. And so, I think for companies like Capital One, and we certainly have faced those things I would say, but for those companies that make the break to say "yeah, we're going to go all out on cloud," then it's how do I restructure the entire way I do information technology? >> Yeah, and Bernard, I agree with a lot of what you were saying. You and I have had conversations about cloud over the years. I've read lots of what you've written. Amazon would agree it's still day one, right? >> It's their phrase. >> Microsoft, I want to get you, not as Capital One, but just as a watcher of the industry, I remember a few years back, Microsoft put out TV ads like "to the cloud." At least made me cringe when I saw some of it. When I look at Microsoft today, they play strongly in SAS, they've got public cloud, they've got all the virtualization in various business products for private cloud. So they play a lot of places, they have a lot of strengths, they understand application, they understand data, they're well positioned. They might not be number one in many of these areas, but a strong customer base. And they're doing good, but I'd like to see them do even more. I'm curious of your viewpoint. >> Well I guess what I'd say is, if you look at the universe or the aggregate of cloud providers, Gartner says there's three that really matter, up in the upper right-hand quadrant of the Magic Quadrant. And that's what I call AMG, Amazon, Microsoft, Google. If you look at Gartner, they've said these are the three that really have both a vision and the ability to execute. >> We believe Alibaba might be making its way in there at this point. >> You know, Alibaba's quite interesting. I've had some interactions with Alibaba, before I joined Capital One, and they're tremendously capable technically, they have huge ambition, so I wouldn't dismiss them or write them off. They don't have much presence in the U.S., at least Capital One is primarily a U.S.-based company. But also, because of the fact that Alibaba doesn't have much presence in U.S., and not that much in Europe, they tend to not be so present, but I would definitely follow them going forward, for sure. >> Sorry, I took you off track, talking about Microsoft's positioning in the marketplace. >> Well, so they're clearly one of the three players. I would say they've had a pretty dramatic turnaround from where they were, say, four or five years ago. You can track that, maybe, to their CEO. I think they're making a strong play in this space, and obviously are committed to it. >> I think Capital One is an adopter and pushing on many of the disruptive technologies. I remember the first Echo Dot that I got, it was actually a Capital One giveaway at a conference, I bumped into you at the Serverless conference. A lot of this show is talking about the business productivity, the applications. There's lots of Azure, but I haven't heard as much about Azure, there's some announcements around Kubernetes. I had a great conversation at the Serverless booth, but if you look at the cloud piece, I want to get your viewpoint as to how Microsoft's doing, where customers are. I know we're in, especially, Serverless' very early days. But get your viewpoints on how those fit into the overall position, and anything you could say about Capital One there would be great, too. Capital One, as I said, is all-in on public cloud computing. It's announced it's going to close all of its data centers. And, as I said, the second challenge that organizations face is really when they go all-in, they go "now I have to really adapt all my practices." So, Capital One is looking at things like containers, serverless, it sponsors the serverless conference, so it's very much engaged with those kinds of things. This conference, I mean, unlike AWS that basically says "all we do is AWS," Microsoft has a very broad range of products, and they have to represent all of them at their conference. So, it's certainly not an only-Azure conference, and that's to be expected. I've said in a number of the sessions, and it's part of my job, I have to track what's going on with all these providers. And so I've tracked what's gone on in the sessions. I've been pretty impressed with some of the stuff that Azure has put forward. But there's other sessions as well. And they have to cover all the rest of their stuff. >> As you said, Capital One is all-in on the public cloud, but it is a multi-cloud world. And a lot of companies are still sort of struggling to figure out "how do I make this work, where do I go?" Can you walk us through your decision process at Capital One, and then also maybe tease out some best practices about how other organizations should make decisions? >> Well, I can't say a ton about Capital One, and about how we've looked at it, other than what we publicly announced, which is "we're all in on public cloud." Our CIO has been up on stage at AWS, very strong adapter of AWS. What I would say, is that, for most organizations, there's sort of two factors you might think about in terms of looking at using multiple clouds. One is from a risk communication strategy. Do you want to have all your eggs in one basket? And that's probably for most enterprises it's not that much of a problem in the sense that they own something of everything, no matter what. You'll never find any enterprise that only uses one thing. In any technology place, and even if they do, then they buy another company that's on a different one. But, from a risk communication strategy you might want that, and then, you might also be looking at opportunistic deployment of workloads if you want to take advantage of superior functionality available from one cloud provider or another. So, do you really like the machine learning that comes out of Azure, well you might decide to put workloads based on that. Or if you like something about certain kinds of database offerings, you might look at that. If you want a certain breadth of services, you might look at AWS, so there's a criteria you have to establish about what you want to accomplish with your applications, or what you want to do around risk management. >> Great, Bernard, what other things have you been seeing at the conferences, what's exciting you? Any takeaways for people that haven't been at the show? Or any things you'd recommend people go poke at? >> As I said, I attended a number of sessions yesterday. I was pretty impressed with the Cosmos DB multi-master. I used to run engineering groups at a database company, and I'll tell you, there's a huge revolution going on in databases, from all the providers, and having some domain experience, there's stuff that gets announced and I go, "how do they that?" I mean, that's amazing. So that was pretty impressive. There were a couple of announcements around Express Route. One, they've announced the 100 Gig Connectivity, which is pretty amazing, I think. And the second thing, this didn't get a lot of coverage and all that, is they announced that basically, let's say you're a corporation with stuff in Argentina and Switzerland. You can basically put Express Route connections into the Microsoft fiber backbone and then just transit your data across their private fiber backbone, which is pretty, pretty interesting. So, I thought that was pretty interesting. I think the rest of it is slipping my mind at the moment. >> I tell you, that is fascinating, because I remember, I've been watching since when AWS came out it had Direct Connect. It was, well, this is really interesting, there's some use cases, but Amazon, Azure, and Google, all of those versions, just hearing massive adoption as people go to a hosting colo service provider, and that can get them, I have the stuff that I'm going to own, and then I'm going to have the stuff, the public cloud in it, physics still exist, but I'm going to get them closer with high band with low-latency connections, so it's a real game-changer as to how I build my applications, and build that ... The hybrid cloud, or multi-cloud, which is something we've been kind of looking at as it's a challenging thing to do, over time. >> Yeah, it's interesting, because there was a time when the huge challenge was the skinny straw. If you had 100 megs, that was a pretty skinny straw. And now, that's really opened up a lot. And these direct connects are pretty good cross-connect performance. That was the pretty interesting era, I thought. >> Great, Bernard, thank you so much for coming on theCUBE. It was a pleasure having you. >> Thank you so much for inviting me. >> I'm Rebecca Knight for Stu Miniman, we will have more from theCUBE's live coverage of Microsoft's Ignite coming up in just a little bit. (techno music)

>> Narrator: Live from the Moscone Center it's theCUBE, covering AWS Summit San Francisco 2018. Brought to you by Amazon Web Services. >> Hello everyone and welcome back to our exclusive Cube Coverage here in San Francisco, California for Amazon Web Services AWS Summit 2018. We are all day covering the regional event for Amazon Web Services. I'm John Furrier with Stu Miniman, our next guest is Steve Hall, vice president of partnerships at a company called, CloudCheckr. Cloud check with an r dot com. Companies we see in the ecosystem doing great stuff really capturing the growth of the cloud. Steve, welcome to theCUBE. >> Thank you for having me. >> So I got to ask you, so you guys are like Switzerland, you guys are involved in a lot of the stuff. Before I go into some of the pointed questions, we'll have to get your thoughts on the cloud, but take a minute first to explain what CloudCheckr does, your core business, and why are you calling yourself "Switzerland". Is it like you play nice with all the clouds? Is that where all the cryptocurrency is going to go? I mean give us a straight scoop. >> Sure you bet, so CloudCheckr is a cloud management platform, right, that helps organizations get visibility in control across their public cloud estate. So, you know the challenges that we're seeing really typically fall into two categories. It's "I thought it was going to save me money when going to the cloud" and "I thought that my data was going to be less secure going into the cloud". CloudCheckr helps solve both those problems by helping you reduce costs, eliminate waste, all that good stuff, as well as, identify your attack surface and make sure that its protected. >> John: Is it SaaS offering or is it more... >> SaaS offering, born in the cloud for the cloud. We focus as you said, Switzerland, we really focus on sort of a management layer that sits across a multi-cloud environment where you're not just looking at Amazon and AWSs, but also the Azures and GCPs of the world to make sure that you have kind of that unified single pane of glass that everyone kind of wishes for but they don't necessarily know how to get. >> Yeah and I get the joke on Switzerland with the cryptocurrency. There's legit people are going to Switzerland but metaphorically you guys are, you're independent you want to play with all clouds cause you got to look at the holistic picture. What's the critical thing that you're seeing right now? We had a guest on earlier talking about you leave the lights on so to speak. You know the EC2 is running a lot of inefficiencies. You got security. Are you guys kind of like a dashboard, single pane of management glass in there? Is it other services? What specifically are you guys focused on right now? Obviously the growth of the cloud is what it is. You guys, that's a tailwind for you guys. >> Yeah I mean. >> The key thing that you do? >> So I mean I think the biggest thing that we see driving our business right is the economics around the cloud. Everyone's moving, the workloads are you know obviously whether they're in the early days or kind of more mature, everyone thinks that by moving to the cloud they're going to save money. And there's data out there to suggest that there's upwards of 30 to 40 percent wastage happening inside of the cloud environments today just because people, using that analogy, leave light switches on, and they didn't even realize that they, they didn't know how to find them, right. So where we see a lot of pain, right, is what do I do, right? Where do I start? And so partnering with not only the native tools that Amazon brings to bear, you know trusted advisor and specter, all the other cool tools... >> So is a new term being developed called cloud sprawl? Stu we talked about server sprawl. I mean you've got Lambda now. I mean is it cloud sprawl? Is that an issue? >> Oh there's so surely. And cloud spend sprawl, right. You know it's this shadow IT thing that goes on. Somebody told me a story of the CMO at Bank of America got a phone call a couple of years ago from the CEO after a Superbowl ad that ran and said what is this thing that you're doing? And she said oh we just turned it on in the cloud. And he's like did you talk to IT? Did you have anybody do it? And she's like why would I do that? Why would I even bother? I can just go do it myself. So how do I get my arms around that. Right obviously is somewhat of an opportunity but also challenge. >> Steve you talk about getting your arms around something. When we talk to customers, you know IT is heterogeneous. >> Steve: Right. >> So you know yes public cloud and people are growing and using more Amazon, but there's other clouds, there's by service providers, and oh yeah I've still probably got some data centers because you know there's 35 years after you stopped building those a few years back for you to do that. How do you help them get around there? And I'd love to hear how are you seeing Amazon maturing and working in some of those environments. It used to be Amazon is all in public cloud only. Then it was oh there's the VMWare stuff, there's the RedHat stuff. Oh hey they're starting to work with service providers even. What are you seeing and how are you involved in that? >> Yeah you bet. I mean again I think you touch on again probably the biggest problem which is visibility, right? And transparency. And how do I create accountability around all of that because there's new roles that are emerging inside of these organizations to try to do things with this cloud stuff as well as a lot of questions are being asked. They don't even know how to answer them. And so you know where Amazon I think is really maturing, we'll start there, right is not only providing a lot of just the native tooling, it's somewhat kind of yes Amazon focused but focused really on kind of providing that, that visibility that they need. Where I think CloudCheckr really kind of steps in is sort of a little bit deeper level view of what they have as well as how do you cross-pollinate that with the other environments. Whether it's a hybrid environment or another cloud provider that you want to again kind of bring into one singular view. That's really how we try to help. And then I think that the other piece that you touched on, which is there's this whole managed service provider and reseller community that's really quite mature in fact within the AWS ecosystem. Which I think is one of the things that AWS really kind of differentiates itself with by empowering partners to be able to build a practice around AWS. Because again another challenge that we see is cloud is great, but I don't have the people to do it. Or I don't know what the people that I do have don't know what to do and so having a trusted like a managed service provider to turn to to go do that stuff is like a blessing. >> What sort of areas, where can that local managed service provider, where can they help? You know is it just cause they have localized people? But what services od they have, is it just enabling people to get up into the cloud? Or are there things that they're doing between you know the service provider and Amazon with direct connect and the like? >> Well I think that so the first thing honestly ends up becomes billing truthfully. And that sounds so boring in many respects, but okay I get a bill, but the billing is really... >> Stu: Yeah the CFO doesn't think it's boring. >> But they don't. As well as you get the bill, how do I make sense of it right? And so you know clients are looking for managed service providers to sort of make sense of all of this cost data and usage data and give them sort of the view of who's using what and how much should we spend right? Because money talks. And so that is driving a different conversation for managed service providers. So building, we're seeing a lot of our partners working up new practices around cost optimization and how to build an entire, not only just billing portal, but a practice on top of that to help optimize the environment for... >> Well there's such a huge opportunity there. I've talked to customers that were like I dedicated engineer to do financial engineering rather than architecting. >> Yeah, yeah. >> So there's an opportunity when you see that it's like oh wait, do you want a head count of a highly trained engineer? >> Right. >> Or you know is there, that's what the partner can help with right? >> Yeah and there's a couple of different ways that they can do it too. We see partners, some that are hiring the smart guy in the room, putting him in a back room and doing the analytics and analysis around that data. Others are literally just creating white labeled portals and putting it in front of their customers. So there's lots of different ways that AWS makes it easy for a partner to build new products and actually turn their seven percent margins into 20 percent margins by building more services and solutions around the AWS infrastructure. >> Steve I want to get your industry expertise on something. You're the vice president of partnerships and you know we always talk on theCUBE, Stu, myself, Dave Vellante, Jeff, Rick, and the team around what it's like to compete in a modern era. And we commented on Amazon's competitive strategy. For the first time they've got to actually deal with heavy dose of competition. >> Steve: Yeah. >> And no one's going to give up the market share. They've got to fight tooth and nail. You deal with all the cloud providers. But people are learning there's a new kind of partnership. If everything's API based you've got SAASified, platform as a service kind of going away to infrastructure as a service. You have this cloud fabric, global reach with regions, all kinds of new moving parts. How is it changing partnerships? How do, how should people who are in trying to partner with the big clouds. >> Steve: Yep. >> Is there a posture, is there an approach, is there a playbook that you see that's different than the old way? The old was you know, press the pavement, press the palms together, you get dinner, you get coffee, whenever you do a deal, longer time horizon. Now it's you've got to have services, you got the data, whole different landscape. What's your thoughts on the partner equation. How should people partner, what's the playbook? >> And I'll speak on for CloudCheckr's perspective. So we've been going to REInvent and these summits for the last five, six years, right. So I remember when this was 500 people in a room, right. You know and there's 10 vendors exhibiting. And here you have 7,000 plus people now that are, you know where you have lots of vendors that you're very familiar with, right. That are large scale kind of like global vendors. So definitely the competitive landscape has changed and it's partly just like you said, the opportunity, right. This is a... I heard somebody say it's probably market cap of a a trillion dollars in public cloud right at the end of the day. So everyone sees the opportunity but how do you actually make good use of it as a partner to the cloud providers? First of all you solve a real problem. Right? There's a lot of... I tend to see a lot people that are just cloud dipping their solutions and kind of coming to market around things because they want a piece of the pie. But if you really focus yourself on how do I solve some of the most pressing needs. And that's where again we see, you know, our product helping customers around cost and security but even our partners. >> So the ecosystem is the key. You've got to be part of a ecosystem. Is that the criteria? >> You got to play, well yeah, it's not just go to coffee and have drinks. Right you know what I mean. It's connect with the people inside of your community. Whether it's at these events or whether it's in your local AWS offices or in the smaller sort of settings to say what are your customers asking for right? And how can we help you with that? I mean it's pretty obvious stuff. >> So Steve, you mentioned security a few times. You know if you go back a few years it was like oh I'm going to be less secure if I go to cloud. Now most people realize it's an opportunity for me to readdress security. >> Yeah. >> And chances are security's better because when's the last time I really updated all my security. >> Yeah. >> What are the hot buttons? What are you seeing? What's Amazon doing well? What does the industry as a whole need to do better? >> Absolutely well I mean you touched on it. Security used to be the reason not to go and now it is the reason to go. And I think companies realize oh my God they've got hundreds of security engineers. We have two. So I think that their infrastructure's probably more secure. What we're seeing as the hot press buttons. I mean I think the last 18 months, 12 months have been all about S3 buckets, right. You know and all of this data that's been exposed sitting out there on the internet. And I think AWS did a fabulous job of changing some of the configurations to allow customers not to stab themselves in the foot. But I think that a lot of it ends up being human error, right. You know really it's the human element inside of security that continues to plague the industry. And the cloud only makes it harder because now you don't have IT people doing IT. You've got business people doing IT, right. Back to the Bank of America example. So, sorry Bank of America. So my point is yeah I think that you know it's really back to how do we create solutions that non-IT people can use and make sense of it so that we can put common sense good controls in place. >> Business models are critical nailing the business model's critical. >> Steve: Yeah. >> Alright Steve final question for you. I want to kind of just put you on the spot a little bit here. You guys are trying to solve a real big need in the market place. Becoming a trusted source for cloud optimization, cloud costs, I mean it's going to impact obviously financial workflows and rolling the data up so a lot of moving parts at AWS and other clouds. >> Yeah. >> So are you guys using machine learning and AI because if Werner Vogels says hey look at all the magic that can happen in the cloud, how are you guys using all these data points? How are you rolling them up? Can you share >> Yeah. >> the philosophy, the tech. >> Yeah. >> Are you guys cutting edge? Are you on the front bleeding edge? What... >> Absolutely. >> Are you guys eating your own job food? I mean I'm obviously putting you on the spot there. >> Yeah, no no that's fine. I mean so we are absolutely using machine learning and artificial intelligence on the back end. Using AWS technology in fact to empower a lot of that inside of the project or platform. And it is all about taking all of these disparate data sources, I called them machine exhaust, of the cloud right that's kind of coming out. How do I put good sense to that? And CloudCheckr really is that layer above all of that whether it's your cloud trail logs or your cloud watch metrics or your cloud usage report, putting it all into one place and then doing machine learning and predictive analytics around that. That's exactly what CloudCheckr's all about. >> So it's an interpretation challenge, right. >> Right, right I mean, go ahead. >> Yeah so Steve it's just we talked about kind of the heterogeneous nature and you brought up a term a service area. >> Steve: Yeah. >> When we start adding in things like IOT, service area's going to grow exponentially and the heterogeneous nature >> Yes. is just going to go up you know. >> Steve: Yeah. >> The same. Is CloudCheckr going to help there? Is that something your customers are ready for? >> I think they're already there right. So I mean I think a lot of our customers, like the use cases that we see are either big data analytics or IOT or you know some other use case around why they're using public cloud to begin with. And so really it's about as that expansion increased usage occurs, how do I protect that attack surface? How do I look for known good state information and then lock my doors and windows if you will? As well as how do I make sure that I'm using the right resources in the right way? So that again I have that visibility and transparency and then you can have the right controls and automation around it to do something about it. >> Steve thanks for coming on theCUBE. Really appreciate it. Check out CloudCheckr. >> Thanks. >> Again this is one of those things as you use the cloud there's going to be more bells and whistles, more services to watch and instrument. Obviously cost containment and managing the growth is certainly going to be something to watch using the data and managing that's what CloudCheckr does. Of course theCUBE is bringing all the data here at the trusted source for all the action at AWS Summit 2018. I'm John Furrier, Stu Miniman. More coverage after this short break. (upbeat music)

>> So, we see this picture, right, of the hybrid cloud. And we've talked about how we do that for the private cloud. So, let's look over at the public cloud, and let's dig into this a little bit more deeply. You know, we're taking this incredible power of the VMware Cloud Foundation and making it available for the leading cloud providers in the world. And, with that, the partnership that we announced almost two years ago with Amazon, and on this stage, last year, we announced our first generation of products. No better example of the hybrid cloud. And for that, it's my pleasure to bring to the stage my friend, my partner, the CEO of AWS. Please welcome Andy Jassy. (crowd applauding) (upbeat music) Thank you, Andy. You know, you honor us with your presence. You know, and it really is a pleasure to be able to come in front of this audience and talk about what our teams have accomplished together over the last year. Can you give us some perspective on that, Andy, and what customers are doing with this? >> Well, first of all, thanks for having me. I really appreciate it. It's great to be here with all of you. You know, the offering that we have together, VMware Cloud and AWS, is very appealing to customers because it allows them to use the same software they've been using to manage their infrastructure for years, but be able to deploy it in AWS. And we see a lot of customer momentum, and a lot of customers using it. You see it in every imaginable vertical business segment. In transportation, you see it with Stagecoach. In media and entertainment you see it with Discovery Communications. In education, MIT and Cal Tech, in consulting, Accenture and Cognizant and DXC. You see it in every imaginable vertical business segment. And the number of customers using the offering is doubling at every quarter. So, people are really excited about it. And I think that probably the number one use case we see so far, although there are a lot of them, is customers who are looking to migrate on-premises applications to the cloud. And a good example of that is MIT, where they're right now in the process of migrating, in fact they just did migrate 3,000 VMs from their data centers to VMware Cloud and AWS. And this would've taken them years before, to do in the past, but they did it in just three months. >> Yeah, it was really, really spectacular. And they're just a fun company, and, you know, to work with, and the team there. But we're also seeing other use cases, as well. And, you know, probably the second most common example is, well I'll say, on demand capabilities for things like disaster recovery. And we have great examples of customers using it for that. And, one in particular is Brink's, right? Everybody knows the Brink's security trucks, and you know, armored trucks coming by. And they had a critical need to retire a secondary data center that they were using, you know, for DR. So we quickly built a DR protection environment for 600 of the VMs. You know, they migrated their mission-critical workloads, and voila, stable and consistent DR, and now they're eliminating that site, and looking for other migrations, as well. >> It saved 10 to 15 percent in the process, doin' it. >> Yeah, it was just great. You know, one of the things I believe, Andy, customers should never spend capital on DR, ever again, with this kind of capability in place. It is just that game changing. You know, and, obviously we've been working on expanding our reach. We promised to make the service available a year ago, with the global footprint of Amazon. And now we've delivered on that promise. And, in fact, today, or yesterday if your an Aussie, right down under, we announced in Sydney as well. And now we're in US, Europe, and in APJ. >> Yeah, it's really, I mean it's very exciting. Of course, Australia is one of the most virtualized places in the world, and it's pretty remarkable how fast European customers have started using the offering, too, in just the quarter that's been out there. And probably, of the many requests customers have had, you've had, probably the number one request has been that we make the offering available in all of the regions that AWS has regions. And, I can tell you, by the end of 2019, we'll largely be there, including with GovCloud. So, GovCloud-- >> Oh yeah, you guys have been, that's been huge for you guys. >> Yeah, it's a government-only region that we have, that a lot of federal government workloads live in. And, we are pretty close together having the offering, FedRAMP authority to operate, which is a big deal and a game-changer for governments, because then they'll be able to use the familiar tools that they use in VMware not just to run their workloads on premises, but also in the cloud as well, with the data privacy requirements and security requirements they need. So it's a real game-changer for government, too. >> Yeah, and as you can see by the picture here, basically before the end of next year, everywhere that you are, and have an availability zone, we're going to be there running on top of you. >> Giddyup! >> Yeah, let's get with it (laughs). Okay, we're a team, go faster, okay. You know, and, it's not just making it available, but this pace of innovation. And, you know, you guys have really taught us a few things in this respect. And since we went life, in the Oregon region, we've been on a quarterly cadence of major releases. M2 was really about mission-critical at scale, and we added our second region. We added our Hybrid Cloud Extension. With M3, we moved the global rollout, and we launched in Europe. With M4, we really added a lot of these mission-critical governance aspects, started to attack all of the industry certifications. And today, we're announcing M5, alright? And, with that, I think we have this little cool thing that we're doing with EBS and storage. >> Yeah, well you know, two of the most important priorities for customers are cost and performance. And so, we have a couple things to talk about today that we're bringing to you that I think hit both of those. On the storage side, we've combined the elasticity of Amazon Elastic Block Store, or EBS, with VMware's vSAN. And we've provided now a storage option that you'll be able to use that is much, it's very high-capacity and much more cost-effective. You'll start to see this initially on the VMware Cloud native USR5 instances, which are compute instances that are memory-optimized. And so, this will change the cost equation. You'll be able to use EBS by default, and it'll be much more cost-effective for storage or memory-intensive workloads. It's something that you guys have asked for, it's been very frequently requested, and it hits preview today. And then, the other thing is that we've worked really hard together to integrate VMware's NSX along with AWS's Direct Connect, to have a private, even higher performance connectivity between on-premises and the cloud. So, you know, very, very exciting new capabilities that show deep integration between the companies. >> Yeah, you know, and that aspect of the deep integration has really been the thing that we committed to. You know, we have large engineering teams that are working literally every day, right, on bringing together, and how do we fuse these platforms together at a deep and intimate way, so that we can deliver new services. Just like Elastic DRS, and the vSAN EBS, really powerful capabilities. And, that pace of innovation continues. So, M Next maybe, maybe M, maybe six? I dunno, we'll see. Alright, but we're continuing this toward pace of innovation. You know, completing all of the capabilities of NSX, you know, full integration for all of the direct-connect capabilities, really expanding that. You know, improving license capabilities on the platform. We'll be adding PKS on top of, for expanded developer capabilities. >> Yeah! >> So just, oh, thank you. (audience applauding) I think that was formerly known as storage Chad, so anyway, alright. And, you know, we're continuing this pace of innovation, going forward, but I think we also have a few other things to talk about today, Andy. >> Yeah, I think we have some news that hopefully people here will be pretty excited about. We have a pretty big database business in AWS, and it's both on the relational and on the non-relational side. And the business does billions of dollars in revenue for us. And, on the relational side, we have a service called Amazon Relational Database Service, or Amazon RDS, that we have hundreds of thousands of customers using, because it makes it much easier for them to set up, operate, and scale their databases. And, so many companies now are operating in hybrid mode, and will be for a while. And a lot of those customers have asked us, can you give us the ease of manageability of those databases, but on premises? And so, we talked about it, and we thought about it, and we worked with our partners in VMware, and I'm excited to announce today, right now, Amazon RDS on VMware. (audience applauding) And so that will bring all the capabilities of Amazon RDS to VMware's customers for their on-premises environments. So, what you'll be able to do is, you'll be able to provision databases, you'll be able to scale the compute, or the memory, or the storage for those database instances. You'll be able to patch the operating system or database engines. You'll be able to create read replicas, to scale your database reads. And you can deploy those replicas either on premises or in AWS. You'll be able to deploy in high-availability configuration by replicating the data to different VMware clusters. You'll be able to create online backups that either live on premises, or in AWS. And then, you'll be able to take all those databases, and if you eventually want to move them to AWS, you'll be able to do so rather easily. You have a pretty smooth path. This is going to be available in a few months. It'll be available on Oracle, SQL Server, MySQL, Postgres, and MariaDB. I think it's very exciting for our customers. And I think it's also a good example of where we're continuing to deepen the partnership, and listen to what customers want, and then innovate on their behalf. >> Absolutely. Thank you, Andy, it is thrilling to see this. (audience applauding) And as we said when we began the partnership, it was a deep integration of our offerings and our go-to-market. But also building this bi-directional hybrid highway to give customers the capabilities where they want it. Cloud, on premise, right, on premise to the cloud, it really is a unique partnership that we've built, the momentum we're feeling to our customer base, and the cool innovations that we're doing. Andy, thank you so much for joining us here, >> Yeah, thanks for having me. >> At the Emerald 2018. >> Thank you guys. Appreciate it. (upbeat music)

>> Voiceover: Live from the Javits Center in New York City, it's The Cube, covering Inforum 2017. Brought to you by Infor. >> Welcome back to The Cube's coverage of Inforum. I am your host, Rebecca Knight, along with my co-host, Dave Vellante. We're joined by Terry Wise. He is the Vice President of Alliances for AWS. Thanks so much for coming on the program again. >> It's great to be here, yeah, thanks. >> So we are now a few years into this relationship with Infor. Where are we? Put things in perspective for us. >> Oh it's a great question. I think in some respects, this is arguably the most mature and strategic relationship we have. We've been working with Infor for, I've been at Amazon now nine years, and a better part of my nine years, we've been working with Infor, you know. In the early days it was awesome, before Infor bought the company. And, they've always done a great job of pushing us to be more enterprise-centric, more innovative in our platform and services. So it's very mature from that perspective. But I'd say, also at the same time, we're just entering a whole new days. We'd like to call it Day One at Amazon. If you look at some of the things that Charles and the team announced today with Coleman, and some of the new functionality and the growth of the cloud, I mean, we really are still at the early stages of this relationship, which is exciting. >> You know what's interesting to me Terry is, you know, Andy always talks about the fly wheel. He was, sort of, the first to use that terminology. And I was sitting in the endless meeting yesterday, and Infor was going through its architecture. And I just saw a lot of fly wheel in there. I mean, there is DynamoDB in there. I certainly saw S3. I think there was Kinesis, in terms of time series stuff. I think I saw Redshift in there. And so I wonder if you could talk about how this company, specifically, but generally, how people are leveraging net fly wheel of innovation to drive value for their customers. >> Yeah. And again, I think this goes back to the relationship we've had with Infor for so many years. Cloud is not just about cheap computing storage. It's really about platform and innovation that comes from that platform. And, you know, and partners and customers, like Infor, that have been with us a while, and they've got the skillsets internally, they've got great vision for how they want to take their customers with application functionality. They're really ripe to be able to take advantage of all the innovative platform services we build. Kinesis, Lambda for serverless computing. We're talking about some neat things around Edge. You heard Charles and Duncan today talk about Lex and some of the AI capabilities we have that are underpinning Coleman and some other new offerings. So they really are, kind of, the poster child for adopting our new services and driving innovation on top of our platform for their customer base. >> So where, if you can, look into your crystal ball a little bit. Where will we be a year from now, three years from now, with these technologies? >> So if I look out a year, I think, you know, rapid global expansion. You know, we're long past in many respects, sort of the, the early questions around cloud. Is it secure? Is it cost-effective? Is it robust and reliable? We're really past that if I look out across the globe. And now it's a question of how can we help enterprises adapt faster. And that's really, probably, the single biggest question I get from enterprise customers is, "This is great. Help me move quickly." And I think one of the neat things about the Infor relationship is, because they've packaged all of this innovation, into a set of business applications, they're actually helping customers move to the cloud quite a bit faster, and get that great value prop of cost efficiency, security, innovation, et cetera. Looking out three years, I think Duncan and the team did a very nice job today talking about the interaction ad user experience of how you're going to engage with business software moving forward. It's going to be very voice-driven. It's going to be predictive in nature so it's actually going to tell you what you need to think about versus going to a terminal or even a mobile device. So much left to do in that space. But I really do think, you know, three years from now, machine-learning won't be a buzz word, nor will artificial intelligence. It'll just be a bigger part of our daily lives. >> We were talking to Chip Coyle a little bit about trying to debunk some of the myths in cloud, specifically Amazon cloud. And I mentioned Oracle, saying that core enterprise apps really aren't going to the cloud, that's why you need Oracle. And they've got a strategy to do that, you've seen it. But then you going to see Infor, 55% of their business is in your cloud. They look like core enterprise apps. So is it, my question is, help us debunk that myth. But is it narrowly confined to companies like Infor, or are there examples of others? I mean, certainly there are companies, you guys have unbelievable logo chart. But when you peel back the onion, many of those apps are cloud-native or emerging apps. Those core of enterprise apps, we're seeing it from Infor. I wonder if you can add some color to that and are there other examples? >> Absolutely, I mean, I think there's others in the market that may be uncomfortable with the change that's happening with cloud, and therefore might be incented to try to slow that down. But I will say, the vast majority of all software companies we're engaging with are moving mission-critical enterprise apps to AWS. Some built natively in SaaS, like Infor is done. Others that are enabling, certifying their applications, SAP is another good example. You can kind of go across the stack, Adobe, AutoDesk, Siemens PLM, for product lifecycle management. And if you think about, you know, that's putting companies' core IP, the product development into the cloud to take advantage of all this agility, scale, cost-savings, et cetera. So it's been happening for a long time. Di-so is another great one, very innovative but somewhat conservative french company. They were very early on in the journey with us. And again, that's, you know, IP used to design airplanes, the things we fly around it. So it's been happening for a long time. It's accelerating. And I would say the other trend we're seeing is the companies out there that are resisting, we're hearing more and more from customers that, "Hey, that company is not helping move me to the future. Can you help me find an alternative?" So there's this big movement for enterprises to actually migrate out of legacy platforms, whether that's hardware or software, and move in to the cloud-native platforms, which are the future. >> So we see, we've been talking on The Cube for years about this whole digital transformation and how it's going to allow companies to play in different industries. Amazon, obviously. Retailer just purchased Whole Foods, getting into grocery. It's a content company. So Walmart said, "Alright, we're not going to put our stuff "in the Amazon cloud." Netflix obviously does. How do you deal with that? The obvious competitive fears of some of the customers that you have for AWS? How do you message that? And what do you tell the world? >> Sure, the first thing is, I mean, AWS, while it is part of Amazon.com, we are a separate operating group. And we've been that way since the beginning. So yeah, Amazon is a customer, just like Netflix or Nordstrom, or any of the other, you know, millions that we serve. Now a very hard customer and a very good customer. And they help drive our innovation road map. But we don't treat them any differently than we do, Netflix or the others. And part of that has to do with how we protect and secure the information that those companies put on AWS. So there's some companies out there, the one you just mentioned, that's still may be a bit uncomfortable, for whatever reasons, competitive reasons, putting information or having third parties put information related to their business on AWS. Yeah, I think that's unfortunate, I think. And it also talks about two different philosophies. We take very much a customer-centric view of the business. What's best for the customer. And if one of our partners has a better capability, we've got plenty of partners that have similar products to what we offer, but if it's the better product for the customer, we're more than happy to support that. Whereas others out there take a very competitive focus to the market. Where it's, they're watching what their competitors are doing. They're trying to head them off at the pass, or copy what their competitors are doing. In the long term, I don't think that's a fantastic strategy 'coz you're never really innovating on behalf of the customer. You're never giving them the best solution. You're actually preventing them from getting something that could be beneficial to that customer. And we just don't believe that's a long-term great business strategy for our customers and for ourselves. >> We recently saw the announcement of Amazon purchasing Whole Foods. Can you talk a little bit about this for our viewers. And talk about where, how you see the future of grocery and retail, where it's going. >> Sure, so we've announced our intention to purchase Whole Foods. It has not happenned. There's still some work to do there. But I think, you know, anytime we look at, you know, how we're going to expand, either organically or through acquisition, it's about, what are the synergies between our existing business, what the customers are looking for, and how can we create a better experience for that customer. How can we do it at scale? How can we innovate around that model? And then, you know, how can we make that a great long-term experience for the customer that ultimately drives the success and growth of our business, but also the partners that we bring in, whether again through acquisition or through third party partnership. This is kind of a, you look at this as a natural move as we look at what our customers are telling us, "Hey make it easier for us to purchase groceries and "household items." You know, and do it in a hybrid way, both, you know, combination of online and more from the physical presence. >> Terry I wonder if you could talk about, we mentioned the Edge before. And as you build out your partner strategy and the partner ecosystem. Talk more about the Edge, where it fits. Analytics at the Edge, and Amazon being the cloud, so what's your point of view on what happens at the Edge, what moves back to the cloud, the expense of moving things back to the cloud. What's your thought on that whole thing? >> Well, there's so many use cases for Edge computing. I mean, take the mining industry. You're putting huge trucks in the middle of nowhere that may have limited or very expensive connectivity. And they're capturing all kinds of, you know, information, during the natural operation of that machine. And it just makes sense that you want some level of data processing, storage, and analytics to happen on that machine. It could be a cruise ship, it could be a naval vessel, it could be an airplane. There's, you know, lots and lots of different applications there. But by doing some of that processing at the Edge, you're actually limiting the amount of data you have to send back to the central cloud. But of course, if you want to take full advantage of the analytics, you actually have to match that data with all the historical data and other real-time data that's resided in the cloud to get the result you're looking for. So it really becomes, you know, kind of this hybrid computing model. So some of it is efficiency around how much data you're sending back and forth. Some of it is just efficiency around processing, the point of data capture. Some due to connectivity reasons. Some due to other. It really is kind of this interesting new extension of hybrid cloud, if you will. We're very excited about it. >> You've made some moves in that area. I mean, Snowball was, I think, you know, one of the first. And there are other sort of Edge, what I would consider Edge-like devices or solutions. How dogmatic are you about everything living in the cloud? I mean, those are steps. Should we expect, you know, increasingly extending the reach of the cloud or is it just really going to all, your world come back to the AWS clouds? >> Yeah, yeah. It'll certainly be an extension of the cloud. That's already been happening. I mean, if you look at hybrid cloud. I think we've always been a supporter of hybrid cloud if you look at our roadmap going back many, many years with virtual private cloud, with Direct Connect, with some of the newer capabilities like Snowball, and, of course, Greengrass, our Edge capabilities. We're really extending the reach out to be much more of a hybrid store. 'Coz we recognize that not all the data today exist in the cloud or AWS in the future, you know. We think most applications will run in the cloud because the value proposition is so strong across so many different dimensions. But today, there's plenty of other places we have to connect to, again to capture the data. Now, I do think the vast majority of the data that we're capturing will be either pre-processed or sent natively into AWS to create a massive data leg so that you can start to drive these innovative machine-learning and artificial intelligence applications. The predictive analytics, the algorithms. They just don't work if you don't, they don't work effectively if you don't have massive amounts of data and you continuously refresh that data so that the algorithms can continue to learn. >> I want to double click on something you said about the value. To capture most of the value, your belief is that it's going to be in the cloud, one cloud. And others obviously have different view for a variety of different reasons. I buy the cost argument. You didn't make that argument, I'm making it. The marginal cost of having a single cloud. You know, standard, how much an A it is, superior. I'll grant that. What else is there though? Is it speed? Is it innovation? Is it standardization across the base? >> The single biggest value that I hear from customers today, but they love it, they love the cheap hosting fees, the efficiency part of it, but it really is the speed and agility. It's certainly the security model as well. I would say that most, almost every organization now that we talk to, once we've had the chance to educate them, if they haven't already done so themselves, has determined that the cloud-computing security model is much more effective than they could deliver on their own. We can just invest more. We can experiment more. We can have have multiple certifications across different industries, which every customer gets to take advantage of. But I would just come back, it's the ability to move quickly whether it's moving into new market. I was just in Europe, we were talking about it. It's so volatile there right now on so many dimensions with Brexit and some of the nationalistic politics things that are happening. Potentially the opening up more of the Middle East with the sovereign wealth funds comin' into play. There's just so much opportunity that enterprises need to be able to move quickly. And if they have to go stand up a data center somewhere else, or they can't deploy the software quickly, they're at a competitive disadvantage. So the single biggest driver from what I hear from customers and what I'm seeing is agility. >> Yeah, okay, so just to clarify, I said, cost not price. But we can debate that some other time. (Terry laughs) You just came back from Europe. You mentioned Brexit. What about things like GDPR which has taken effect but the penalties go in effect May of 18. Obviously that puts a lot of pressure on the cloud provider, as well as your customers. What are you hearing in Europe? And generally and specifically GDPR. >> Yeah, I mean, I would say the regulatory environment everywhere, but specifically in Europe, continues to evolve and it's fairly fluid. We've spent many years working with the various different regulatory bodies. The Article 29 Working Party. That's actually been crafting a lot of this legislation. So we're heavily influencing, because, if you step back, people said you couldn't do cloud, but they didn't explicitly say you could. (Rebecca and Dave laugh) So, customers are meant to, "How do I interpret this?" And some, you know, like, if I look at Nel, and I look at Societe Generale, and I look at BMW, and some of, you know, our forward-leaning European customers, Siemens is another great one, who was one of the original companies to put PII in the cloud. Here's a big German company putting PII in AWS a number of years ago. So we figured out how to get, not get around, but interpret the regulations, and then also ensure that we've got the features and capabilities to make sure that they comply with those regulations. So the full audit trail, the ability to encrypt data, the ability to make sure that data storage and localization is complying with, whether it's a country-level regulation or an industry-level regulation. So we continue to spend a lot of time and effort, monitoring and influencing that. And then building the services to make sure our customers fully comply. >> Well, you've always done well with permutations and complexity and automating that, so it's going to be fun to watch. >> Rebecca: It will indeed. >> Great. >> Terry thanks so much for joining us. We really appreciate it. It's been a lot of fun talking to you. >> Yeah, great, thanks, appreciate it. >> I'm Rebecca Knight for Dave Vellante. We will have more from Inforum just after this. (upbeat music)

>> Voiceover: Live from San Francisco, it's the CUBE covering AWS Summit 2017. Brought to you by Amazon Web Services. (electronic music) >> Welcome back to the CUBE. We have spent a great day in San Francisco at the AWS Summit. My co-host, George Gilbert, and I are very excited next to be talking to Eric Pan, the Senior Director of Alliances Marketing at Equinix. And Eric and I know each other when I worked at NetUP and you worked at VMware, so it's great to see you again. >> Back in the day. >> Back in the day. >> Eric: Yeah. It's great to be here, Lisa. >> It's great to have you on the CUBE. >> Eric: Thank you. >> So tell us about Equinix and what you're doing to help customers get to the cloud. >> Yes, love to. So Equinix was founded in 199-- ... 1998. We really have established what we call an interconnection data center platform. So Platform Equinix is a company that helps customers to interconnect with their trading partners, with networks, and customers. >> Excellent. And so one of the things that I actually just read yesterday, a press release, that Equinix just became part of the AWS partner network as an advanced technology partner. >> Eric: Right. >> Big news. >> Big news. So we've had a relationship with AWS for many years. We've established 14 points of presence around the world for what AWS calls their Direct Connect, which is, it's a great way for customers to be able to manage their hybrid clouds or mainline, if you will, directly into AWS, privately and bypassing the Internet entirely. So for us to be able to gain this certification, this badge if you will, it's a proud day at Equinix. >> Well, congratulations. Fantastic. I'm sure a lot of hard work has gone into that. >> Eric: Yes. >> So help us, talk though from a customer perspective, where they want to say, "I don't really want to apply any more of my real estate, and I, you know, I don't want to buy a lot more gear, but I have some stuff with legacy apps. And I'm actually starting to build out more in Amazon." What's that scenario? How do you help with that scenario? >> Right, so this is a very typical scenario we see every day with our customers. If I may just color this with what we call interconnection, Interconnection is, it is a set of ideas and concepts that we've established through many years of observing how our customers have worked with us and have built their infrastructure, both on-premises and into the cloud. So what you're referring to is really a hybrid cloud situation or scenario. And where a customer ideally says, "I would like to put the majority of my workloads and applications and maybe even data up in the cloud." But we know that's not practical. There's a lot of different reasons. Some of the reasons are data sovereignty or compliance or regulatory concerns. We see a lot of customers that have very specific hardware devices. For hardware maybe, certification or validation for certain things. So those sort of customers will come to Equinix. They'll place their own equipment within our data center. They'll manage that or they'll have a managed service provider come and help them with that. But they'll also be able to directly connect up into AWS. So that's one of the beauties of working with Equinix from our customers' perspective, is they get the best of both worlds. So they get to move their equipment out of their own data center, but they still have the look-and-feel or the management capability of on-premises. And then they also get to enjoy all the benefits of working in the cloud with AWS. >> So you've grown since early 2016, as we were chatting about before, Equinix has grown customer connections to AWS >> Eric: Yes, 250. >> 250% That's massive. >> Eric: Over 250%, yes. >> Over 250. Tell me just to get a little bit, kind of following on what you were just saying, what type of business would choose that route versus going, either keeping some on-prem then going right right to AWS or a cloud? Give us an understanding of really who this target market is. >> Sure, so really any and all enterprises would need to have this capability. The concept here with Direct Connect, it's really AWS' concept and where they say, "If you have certain applications that may be really heavy and are very compute-intensive or very data-intensive, you'll want to run those applications in AWS, and you want to make sure that you have good user experience around that." So Direct Connect privately connects from the end-user to AWS without zig-zagging through the Internet. You get predictability and performance. And what's really the most important thing is great user experience. >> And are you seeing the rise of enterprise as being more and more comfortable with migrating business-critical workloads? >> Oh absolutely yes. Yes, I went to Andy Jassy's fireside chat earlier today >> Lisa: Yeah, it was fantastic wasn't it? >> And he had a whole list of customers that are running business-critical applications. So we see a lot of customers that do that. And we also see, on the flip-side, a lot of customers, like what we were speaking about earlier in the hybrid cloud sense, that are running business-critical applications in AWS but they need to have their data local. So marked by regulatory or compliance issues in health care or in retail environments where PCI compliance demands that you have private data. And then in countries like, I'm just going to give you two examples, Canada and Germany, they have very stringent data sovereignty rules where you must have data in-country from operating on that data. So a lot of customers will use Direct Connect to connect up into AWS, but they'll also be able to maintain their data privacy if they need to. >> Just a drill down on that scenario, you know, there's debate as to, is there one cloud, one ring to rule them all? Or where is the sweet spots of different clouds? Would Equinix be for a customer who has a mission-critical application that's been running for years, that's got an Oracle database? They want to add some low-latency analytics, machine learning where they're scoring or predicting. So they want to put something close to where it's running. So they take the equipment from their data center, put it in Equinix, add around that application the low-latency stuff. >> Eric: Yes. >> And then maybe the digital experience part is in Amazon. >> Right. Yes. So we see many customers doing that very thing. And we also have a very close relationship with NetApp as a storage provider. And NetApp has an offering called NPS, or NetApp Private Storage. So symbiotically, we work together to provide what NetApp has as a ... Data Fabric, which they call. And in that scenario, the whole entire concept is based on running heavy applications or business applications in the cloud but having your data privately and distributed locally or close to where people live, work, and play. >> George: Okay. >> So one of the topics, actually, in, you mentioned attending Andy Jassy's fireside chat. I think we all did. It was fantastic. >> And one of the things that was really interesting was that he was talking about of all of the buzzwords, and as marketers, you know, we both know this, that IOT is the buzzword that he has seen really come to fruition. >> Eric: Come to life, right. >> The fastest. >> That was a fascinating part of his discussion. So we, Equinix, are at the center of, if you will, some of the things that are going on in the IOT world. So IOT, if you can imagine the Internet, a thing says that there's lots of different little devices or big devices like cars or huge devices like hydroelectric dams or jet engines. Those are all producing vast amounts of data that have to go somewhere. And the companies that, like Andy used GE for example in the wind turbines, the companies that need to look at that data, that are having to store that data or do something with it, they typically say, "Well, if we are based in one geographical city, and all this data is coming in from all over the world or all over some region, you need to have natural ingestion points for that data. So we, Equinix, are at the center of where data comes in. And then the next piece is, well, now that we have all this data or now that the organization has all this data in one place or maybe distributed in a few places, how do they then go operate on that? So the scenarios that we spoke about earlier, in where you have an application running up in AWS, to look at that data or, in some cases, there may be, like Andy talked about the Snowball and the Edge computing, Edge computing is something that Equinix very much puts forward as one of the concepts in our interconnection ideas. So that, it's kind of loud there. >> Sorry for the overhead announcement (laughs) >> So the idea around having all of these big data ingestion points, having Edge compute or cloud compute, Equinix becomes a really logical place for customers to be able to do all of that. And then, of course, there's all the data visualization. There's all the data analytics that have to occur with the data scientists. So maybe some of those analytics are running in AWS, but maybe some of the visualization pieces are running in other companies. I won't name the companies, but we all know who the data visualization companies are. >> Lisa: (laughs) >> So your points of presence are about 150 if ... >> Yes, we have 150 data centers in 40 of the biggest business-rich metros around the world. >> Now, do you see a need for a mini-data center or a point of presence that's more like when AOL had those dial-in >> Eric: (laughs) >> I mean, literally, it could've been one box that received phone calls and then ran them out over the network. And the reason I ask is when we have billions of devices, you might want points of presence in the thousands or hundreds of thousands even. >> Eric: Right. That is a very interesting question, and I kind of liken this to something that maybe is an easier idea to understand. A lot of us live in big cities. A lot of us work or ... A lot of us, yes, work at a big company. Some of us don't. A lot of us conduct our banking with big banks or small banks. So if you can imagine the world of maybe retail or banking where there's lots of little branch offices, those could be, we could think of those as maybe the mini-data center idea that you've brought up earlier. So in what Equinix calls interconnection, we have a concept that we call Edge Hub or Communications Hub, which is an idea in where we want to shorten the distance between where users live, work, and play and where the application is running. And so by doing that and simplifying the network topology, in the case that we're talking about, IOT, yes. You would definitely want to do that. So think of a branch office connecting up to a hub, if you will, a communications hub, as a natural ingestion point to bring in that data. >> So last question, Eric, as we wrap up here. We talked about the tremendous growth that Equinix has had just in the last not even 18 months alone and also the great news yesterday that you're very proud of and should be, as becoming an advanced technology partner of Amazon. So last word to you, what's next as an advanced technology partner of AWS? >> Wow. Well, if I can just maybe borrow some of Andy Jassy's words, we're not done here yet. There's no end in sight where Equinix goes. We continue to grow. We have over a third of the Fortune 500 customers that we've managed to attract and that are happy customers. We want to continue down that road and have 100% of the Fortune 500 customers. And we want to make all of our customers happy in working in this new era that we call cloud computing. >> Fantastic. Well, I think we can feel the momentum coming from you and very much Matt Schpive, the guys and the gals from AWS that were on stage today. So, Eric Pan, it's so great to see you after a few years of back in the day. >> Great to see you. Thanks for having me here. >> Absolutely, and for Eric Pan and my co-host George Gilbert, I'm Lisa Martin. You've been watching the CUBE live from the Amazon Web Services Summit in San Francisco. We will be right back. (futuristic electronic music)

live from san jose in the heart of Silicon Valley it's the cube covering AWS summit 2016 hey welcome back everyone we are live in Silicon Valley for AWS Amazon Web Services summit in Silicon Valley this is the cube silicon angles flagship program we go out to the events and extract the signal from the noise i'm john for with my co-host Lisa Martin our next guest is Lowell anderson senior manager product marketing of AWS Amazon Web Services welcome to the cube thanks for having me it's great to be here first time cube alumni welcome to the cube alumni list love to get you on because you know you're in the product team and you're in go to market as well as you gotta look into the product suites and one of the things that's been super impressive of AWS over the years since I've been following you guys for a decade since you started in the cube of the past four years is the tsunami of product releases the cadence of jesse's law I call it yeah and Amazon's law which is just constant slew of releases more and more every time not just reinvented yeah you get the summit's which are exploding right there were tiny right years ago right got new york and here what's what's coming out now what's the secret sauce how do you guys do it and give us some insight into what's what's happening here well you know for us innovations in our blood it's a part of our DNA it's what we do we're really except to over 460 new services and features and we'll hit over a thousand this year of new services and features launched compared to last year when we hit like 720 I think something about in that range so the innovation train train keeps going and you know the way we do it is we number one we really focus on our customers one of the benefits of the cloud is that we can innovate and roll out changes really rapidly for them so just that the whole cloud environment allows us to innovate very quickly and very rapidly so that that's exciting and you see that in just a number of releases that we think that I just asked the previous guest on how do you explain the Phenom that is AWS and you know Andy Jassy went to business school the same year us I did and back then the competitive strategy ethos was built some proprietary technology build a fence protected with guards and guys with guns and old you fold the line yeah with open source though the new model is you can't do that anymore so there's one the open source is now a Tier one citizen right and two there's no real walls to build around proprietary technology so the name of the game is speed yeah it's all about speed and the cloud really enables that agility that's one of the biggest benefits that our customers talk about is how freeing up breaking down the walls of your data center effectively so that now your compute and your analytics and your storage expand beyond the walls of that building as rapidly as possible and and the use of open source as you measured I mean we're we're big proponents of open source we have a lot of open source services that that we support as well and and trying to help the developer community really bring those types of technologies to the cloud and enable that's a big part of our success as well it's clear that the competitive strategy game in this new world that Andy and the team are executing is really just more features faster than the competition there is kind of an arms race going on but that is the open source game so with that what is the are the big announcements here obviously this show is much more developer focused yeah yes more getting get getting the weeds breakout sessions one of the key goods that are being talked about here down here in Silicon Valley we really wanted to bring some more technical topics to the table and talk in that vein talk about a couple really key areas around focused around big data and what we're doing to help enable both small and large enterprises use data across their companies in in a more and to develop more competitive applications and make it cheaper make it easier to use and make it more performant than they could possibly imagine without the cloud so using big data is one of the key themes of the conference that we had today and then the other thing that we wanted to talk about was this movement from how we've been architecting services our applications in the past from being based on server to using server list which is really a whole new architectural concept that's allowing our customers to build applications in ways that they could never do before and do it at a cost that they could never make feasible in the past there's some great examples of customer successes that dr. Matt would talked about in the keynote one redfin I think we've all in orcutt have experiences with buying and selling homes but i loved how we talked about friends don't let friends build data centers that in the future it's most organizations are going to run their own data centers are not going to run their own Dana centers and move to AWS benefits like becoming data-driven big data the more users more data more insight you also talked about some of the things coming up you mentioned it to about building with services versus building with servers talk to us about some of the if you could spend a little bit on some of those examples one that particularly spoke to me was what alumina is doing and germs of genome sequencing I got my masters in biological sciences a long time ago and that wasn't even a thought back then or certainly was a massively expensive Todd was a little bit more about how alumina is doing that with AWS and scaling at cost to really facilitate breakthroughs they're saving lives right right well you know that's an exciting example because people that weren't able to see the keynote alumina is the largest genomic secant sequencing company in the world and they've really been able to implement a new architecture that's brought genomic sequencing from an industry that was done you know just for very specific scientific purposes to now something that can be done all over the world to support disease research yeah and and its really the power of big data that's made that happen and the reason they selected AWS for that is really just the breadth and depth of the big data services that we provide along with the global deployments that we support with genomic data they mentioned that for many many many many countries in the world they don't want that genomic data to move outside the boundaries of their specific geographic region and so sensitivity eight AWS is one of the few very few cloud providers that has that level of geographic specificity so you can keep the data within that specific compliance issues as well with that too lots of compliance issues of course genomic sequencing lots of federal and health care and HIPAA type requirements surrounding all of that type of information that AWS with our focus on security you know is able to achieve so so number one you know it's this Geographic capability which is a lot of luminarias lee deploy this in a global way but second it's really just a depth of services that we offer whether it's the data warehousing using redshift whether it's the ability to process that data at scale on Hadoop using EMR whether it's the ability to then deliver that data across the world and visualize it and upload it from all those different genomic machines that they've that they put into their individual customers research facilities all of that is capability that AWS is able to deliver to them at a cost I think one of the things he talked about they were looking for I think a hundred percent reduction or a hundred times reduction in cost over trying to do this themselves and and we've achieved that help working together with them you know they've been able to achieve that well I got to get your thoughts on the hybrid cloud because you know I'll see Amazon gets was traditionally pigeon-holed as just public cloud the lines are blurring clearly the success you guys are having it's been moving into the enterprise obviously the CIA delia beat IBM on that was a again different instance in the gov cloud but again in the enterprise deals you're seeing yeah it's up against the Oracles and the IBM's yeah what and they're all talking hybrid yeah yeah how are you guys are dressing it from a product standpoint how do you talk to a customer says hey amazon slow down i love you guys but yeah we need a hybrid on-premise solution yeah that's great great great question i think you know first of all I would say that what we've always said at AWS is really in the fullness of time we expect that you know no Enterprise is really going to want to run their own data center and so we still see that as the end vision that that's that we're gonna achieve in the long run and that most of our customers want to achieve in the long run as well but a critical conversations that they have what are their requirements and you got here is it migration of data yeah that's it so that said you know there's there's a lot of work to do between now and this in this long-term vision and so you know a few of those things that need to be addressed like data migration and we're working really hard to help enterprises move data up into the cloud it seems like it'd be a simple thing right you you take a picture you upload it to dropbox what why is that so hard but when you're talking about terabytes of data that have been in the corporate data centers with applications for years and years and years moving that volume of data up to the cloud is a significant about moving back to the enterprise and then vice versa again making it available for them to use and to and to move back and forth is a critical component so we've done a lot of work on a specific set of features and capabilities to make that happen amazon direct connect or AWS direct connect is one of those services that allows our enterprise customers to establish a high bandwidth connection to AWS regions so that they can move data back and forth the interconnect or to direct connect not going through the internet yes direct connect allows them to leverage private backhaul to establish a really high bandwidth connection and so we'd curity wise alone that's a big deal absolutely it is and then earlier or last year we announced amazon s3 transfer acceleration which is a service that allows them to utilize our backhaul to actually accelerate the upload of data into s3 before you has to use the internet to upload data to s3 and now what we've done is really extended that down to customers where if we can accelerate the transfer of their data to s3 will do that using our backhaul network for them so the next question on top that compounds the problem with data which you guys are solving and because this is I agree is a big challenge for enterprise customers IOT just complicates the hell out of it so yeah that's all about moving data around putting computer where the edges yeah this whole edge of the network definition really plays into some of the train around serverless concepts that you were mentioning earlier how does that relate to the data equation yeah so a couple of things let's touch on IOT for so I OT brings a whole new level of complexity in terms of the number of devices and the distribution of data that you need to bring up into the cloud and so we released this service we call AWS IOT last year at reinvent and what that does is it makes it really easy for customers to acquire data from billions of devices that might be generating trillions of messages at a time and when you think about IOT devices it becomes almost more complex because these devices may or may not be online all the time they may not have a high bandwidth connection they may not have the processing capability on the device itself to be able to update and optimize and do a lot of complex computing so you need a specialized service that can work with those devices when there's intermittent connections pull very small messages from those devices and ingest them on a huge huge scale and so aw SI io t is a service that does that allows our customers to ingest those billions of messages and then connect them to AWS endpoints big data services like red shift and s3 and Kinesis and lambda to process that data and generate applications that could never really be conceived before and today i thought i thought that the the whole discussion from iRobot was super interesting about how they're using AWS IOT to connect their what they call their home robots it's as you know their Roomba vacuum devices to the cloud and and really enable a whole new set of applications and vision for the connected home really interesting stuff enabled by the clouds well before at least answer question I just want to quote been Keogh who was with iRobot his analyst over there Sarah scientist transition I won't get your reaction to maybe Lisa you can chime in he just tweeted transition to the cloud colon treat servers like cattle not pets transition to server less cloud architecture yeah Crete servers like roaches wow that's a pretty bold statement yeah yeah it is but note note not a pet yeah I don't cuddle like a roach Amy's not not cattle it's roaches put the roaches out so taught some mean serverless sure caring servers to roaches let's talk about that that's that yeah let's talk about the evolution a little bit i mean if you went back you know a few years back to when i was writing software as a graduate from from college when you wanted to start off a project first thing you had to do was go buy a server have it delivered find a place to put it plug it in cola network guys get aboard cole router your security what you had it all plugged in you had to put the operating system on it and then you could put your development system on it and then you could finally get started to be months later before you could actually get the project started and it seems strange to even talk about it now but back then this was a a key thing that that limited our ability to start projects forget the cost yeah it's the time and then when you when you finally got it done and you release the application and you wanted to scale it you had to buy more servers and put them in the racks and figure out where to put them and so this just slowed everything down and so when we move to the cloud and we got the ability to lease or really rent servers in the cloud it took away a lot of the hardware aspects of that but still when you had to scale you still needed to provision more servers and you still needed to maintain and patch those operating systems in that software stack and so now what's happening with serverless and with services like lambda is all that goes away now it doesn't mean there aren't servers under the hood of course lambda has lots of servers under the hood that are cranking away and implementing your code at lightning speed but the difference is is you don't have to manage them anymore you don't have to think about them you don't have to worry about them and so with lambda all you do is is load your code up into the cloud it's executed instantaneously when you need it to be executed it scales on demand so as your application scale we can scale the number of lamb functions in parallel to execute your code depending on the load that you're putting on it and you only pay when that code is actually running so you're no longer paying every month for those servers that are sitting in that room whether you're using them or not so we've talked a lot about the services a tremendous amount of services that that AWS is offering compared with the three that you started with ten years ago we've talked about hybrid cloud the opportunities there enterprise in fact you're CTO just last week in London was talking about the challenges with enterprise are really kind of the shift that they want to help customers grow through a lot of capabilities a lot of speeds and feeds what's the the message brother who's the target audience as we wrap up here who are you selling these services to within organizations as we see the empowerment moving from IT to the c-suite two lines of business who are you going after to share with them and get them to come on board as customers whether it's Enterprise yeah yeah I think that's a really good question and it speaks a little bit to our evolution of as a company as well wear when AWS started over 10 years ago really focused on our developer messaging but what we've seen is the just the impact of the cloud is so significant that across the entire suite of different whether that's executives whether that's IT managers whether that's developers there's a significant value proposition that that really at every level across the organization high level of interest and so we're starting to see I think you saw today just across all sizes of companies across all industries and in even within government and an education and public sector a strong interest in motion there's really no industry or government type of agency that's not you know right now looking at not just are they going to move to the cloud but how quickly can we get to the cloud and so that's that's really expanded the scope gray synopsis that actually what dr. Matt would talked about with how infiltrated amazon is into of all the industries big in public sector big and startups born in the cloud now getting to be big and enterprise yeah so low we got one minute left I want to get your thoughts on as an insider at Amazon I'll see you out in the field here you talk to customers in the product marketing you have to look at that 20 mile stare in the marketplace but also talk to the folks internally engineering product management or talk about the coolest things that are going on right now in AWS that people should know about is the machine learning is it lamb does it rip yeah Reds what's the fastest growing what's the coolest tech yeah what is what are the jewels on the table right now that we should look at it and then explore and discover more about you touch on so many cool things I mean the fastest growing service now today is Aurora Aurora is our own my sequel database engine that runs on RDS and it's responsive that's been tremendous it it really offers enterprise-class database capability at a tenth the cost of on-premises solution so that's been that's really our fastest-growing service now it's really exciting in terms of this other stuff that we're just seeing tremendous excitement about you mentioned machine learning predictive analytics a lot of the work that we've been doing at amazon it's been part of our history at amazon for a long time mike says that was thing all everyone wants that right right right so machine learning of course is is something that you know we're gonna continue to see significant cars coming soon I don't know about flying cars it's certainly not on our roadmap that I'm aware of but you know who knows what Steve or what Jeff is working on right now so but we don't have flying cars on our super exciting I'm yeah I'm sure this is but it's again it's a software driven world mark injury since new thesis is not software eating the world but software powering the world and I think that's a whole nother concept its patents you know it's a global economy so a lot of great stuff always a great surprise to see the coolness yeah they did to us the new stuff thanks so much for sharing thank you in the cube this is the cube bringing you all the goodness of AWS here at if your summit in Silicon Valley I'm John Ford Lisa Martin you're watching the q