(corporate electronic xylophone jingle intro) >> Good afternoon and welcome back to our very last segment of Tuesday's live broadcast here on theCUBE from AWS re:Invent in fabulous Las Vegas, Nevada. My name is Savannah Peterson and I am joined here by the brilliant Paul Gillin. Paul, end of our first day. You holding up, are you still feeling overwhelmed with fire hose... >> Savannah, yet my feet are killing me. (savannah laughs) >> Yeah, we've done so much walking in these chairs. >> 14,000 steps already today. It's not even dinner time. >> Hey, well, at least you've earned your dinner, Paul. I love that. I love that. I'm very excited about our next guests. We have Krishna and Sowmya joining us from Tata Consultancy Services. Now, I was impressed when I was doing my background research on you all. The Tata Group has locations in 150 different spots, 46 different countries. You have over 600,000 employees on the team. We are talking about absolutely massive scale here but, today we're going to be focused specifically on the Tata Consultancy Services. Sowmya, can you tell me what you all do? What is that team specifically in charge of? >> Yeah, TCS, first of all, thank you very much for inviting us. >> Savannah: Our pleasure. >> Maybe the last session but, we'll make it very lively. >> Savannah: It's going to be the best session. That's the best part of the day. >> Yes, that's the attitude. From a company standpoint, we are a 50 plus year old company. Part of the Tata group. We focus on IT services. We are categorized as industry verticals and we have horizontal services where AWS is one of the horizontal services that we have. And, when I talk about TCS, we focus a lot more on growth and transformation of our customers. That is one of the key objectives of the current company's growth, I would say. So, that is TCS in a nutshell. >> Extraordinarily important topic to be focused on right now. Growth, transformation, pretty much the core topics of the show. I know you're on the hospitality and transportation side of the business, which is very exciting. And, we're going to dig into that a little bit more. Krishna, you're overseeing the world. Tell us a little bit more about your role within the whole ecosystem. >> Yeah, thank you for the opportunity. Great meeting all of you. It's been awesome experience here. re:Invent is coming back, catching up, right? 50,000 people compared to 25,000 last year. So, great to see and meet all of you. Coming to my role, I am responsible for AWS Business Unit within TCS. That means I am responsible for anything that happens on cloud, on AWS. It's a Full Stack unit. I have the global responsibility. That's whether it's a applications, data, infrastructure, transformation that happens, as well as OT at the edge. So, that's my responsibility. >> Savannah: Well, I love talking about the edge. One of my favorite. >> Transformation is a theme of what you do. We heard that the pandemic accelerated digital transformation initiatives at many companies. How did you see the pandemic affecting your business, affecting the customers you were working with? >> Pandemic definitely kind of accelerated a lot of cloud adoption, right? A lot of companies initially focused on resiliency, coming back to handling the pandemic, the situation. But, it also drove a lot of innovation in the business models. They had to think on their feet, re-look at their business models, change the channels and that continued. Pandemic is thankfully gone by but, the transformation actually continued. The way that we actually see on cloud, especially transformation, it has evolved. What we call as Cloud 2.0. Now, cloud is actually more focused on future-proofing the businesses. And, the initial days it was more about future-proofing the technology and technology architecture. But, it has evolved to future-proofing businesses. That means implementing new business models, bringing in agility, measuring the business value. And, that's where we see a significant traction. >> So, it's not about technology then. It's not about infrastructure. >> It is about technology but, really delivering business value. It's about, how can I improve the customer experience? >> Well, can you give us a couple of examples of companies you work with that embody this idea? >> I can imagine in the travel and hospitality zone. Probably few communities more sensitive than when someone's having a disruption or frustration within that process. And, perhaps few time periods less chaotic than the last few years. Tell us about your experience and what you've seen. >> Absolutely. To answer your question, first of all, coming out of pandemic, right? Many customers in the travel and hospitality industry where legacy, did not modernize for the last decade or so because, there have been many ups and downs in the industry. So, during pandemic, post-pandemic, one of the the way they wanted to rebound was, can we do the transformation? First of all, cloud as a technology adoption, but, beyond that, how do customers derive value, business value? That is one of the key aspects of the old transformation. And, if you take, I can give a couple of examples. Avis Car Rental, they had monolith mainframe applications and, that was there for almost couple of decades, right? But, over a period of time, they were not able to have the availability of those applications. There were many outages. As a result, businesses could not do the bookings. Like OTAs, customers could not do the bookings, the application was not available most of the time. And, it's all legacy, right? So, that is where we all came in, TCS. How do we first of all, simplify the complexity of the landscape? That is one. Then, second is, modernize the legacy application. That's the second thing. Third is, how do you scale it? Because, everyone wants to go faster, right? How do you scale it? That is where we partnered with AWS as well, to bring in some specific solutions. One example for Avis', their Rent Shop. Because, of the lack of availability, because, it's monolith application and legacy application. It was not available. So, as a result, we partnered and we brought in our contextual knowledge of the car rental industry to kind of transform, move it to cloud. And, today, as a result of it, Avis was able to save millions of dollars from a MIB standpoint. Second, in terms of availability, that was 99.9% availability. As a result, they had a pick in their business revenue as well. So, this is one of the ways that its helped. The second example I want to quote is, United Airlines. Here again, we've been present for a long time. We have a deep industry knowledge of the airline industry. So, we brought in our airline contextual knowledge and the United landscape to bring in a TCS's solution that we developed. It's called the Aviana. It's an intelligent operations solution for the airline industry, which we have developed. It's on AWS as well, that is being implemented in United. As a result, the ground staff, they have to take decisions on the moment when there is a irregular operation. That could be flight delays, as a result, customers connections will be lost. >> Savannah: Baggage. >> Baggage, right? Baggage delays. >> So many variables. The complexity... >> exactly >> in this matrix is wild. >> So, leveraging the Aviana solution, the ground staff were able to take decisions based on exceptions. They were able to take decisions quickly so that, they improved the customer experience. I think that was one of the key successes for United in the recent times. So, those two are the examples that I would call where customers have the right business value. So, cloud was not just for technology. They all are deriving a lot of business value as well. I would say. >> How important do you think it is for companies facing these unique challenges and scaling to work with partners like TCS? And, I'm sure you would say very important, but, tell me a little bit more why it's so important and those core benefits that they're going to get. Krishna, let's start off with you. Yeah, let me take again the AWS cloud transformation, right? TCS has formed AWS Business Unit two years back. So, we are a covid baby in a way. We have been working with the AWS for more than a decade but, we formed a dedicated Full-Stack Unit to drive cloud transformation on AWS. In these last two years, we've grown three X and customers we have added 400 new customers we have added. >> Nicely done. Just want to see you there. That's huge. Especially during these times. Congratulations. >> So, it's basically about the scale that we bring in. What we have done as a differentiation is, if you look at the entire cloud journey, right from taking a decision which cloud is, right, all the way to the cloud migration modernization and running operations. So, we have built complete platform. AML based platforms, where we have taken our delivery wisdom and codified it onto these platforms. So, we support around thousand plus customers on AWS in varying capacity. All of that knowledge is codified and, that is what we bring to the table, to the customers. And, so, customers obviously appreciate that value that best practices that are coming. And, coupled with that, the industry knowledge that we have on banking, life sciences, healthcare, automotive. So, it's partly the IT, it is the industry transformation as well. Because, we are working on connected cars, for example, in automotive. We are working on accelerated drug development platforms. We're working on complete banks as a platform that we have. TCS has built on AWS. So, 400 customers are there. It's the complete banking and insurance platform. So, this is the combination of the technical expertize that is digitized using platforms, as well as the industry knowledge, is the reason why customers work with us on the cloud transformation. >> So, we're seeing you talk about the vertical industry knowledge. AWS also has its own vertical industry plays. How do you, I guess, coordinate with them or, do you compete with them or, do you stay out of each other's way? >> No, we actually collaborate aggressively. >> Savannah: I like that (laughs) >> Right, so, it's not.. >> Savannah: With vigor. >> With vigor. TCS supports approximately 14 verticals. With AWS, we went with the focused industry play. We said we look at financial services, travel, transportation, hospitality, healthcare, life sciences and automotive, to start with. And, we have Go Big plans with AWS. very focused. The collaboration is actually at the industry solutions because, AWS is a great platform, ever evolving, keeps you on on your toes to really adapt it. But, that is always going on, the collaboration. But, the industry, I'm actually glad AWS last year took a pivot on focusing on industries. Now, we talk the same language when we go in front of a board or a CEO or COO. Present it. We are talking about the future of the industry not just the future of the technology. So, it's a win-win. >> You are also developing products on top of AWS that are not industry verticals, that build on the platform. What kinds of products are those? >> For cloud transformation, for example, consulting. We have a product called Cloud Counsell. We have a decision engine on the data side. We have something called Cloud Foundation, Mason. CloudMason. It's just the foundation, right? And, entire migration and modernization factory. And, the last one on cloud operations is actually Cloud Exponence. So, these are time tested. You have Fortune 500 customers using this regularly actively leveraging that. And, these are all AWS in a well architecture framework certified. So, they work well and they're designed to work on cloud, not only in the native environment, but, also legacy environment. Because, enterprises is not just only native, cloud-native. There is a lot of legacy. Sowmya spoke about the mainframe model... >> So much legacy, we were talking about it. >> So, you have to have a combination of solutions. So, the platforms that we're building, the products we're building, work in both the environments. >> Yeah, and that agility and ability to help customers navigate that prioritization. I mean, there's so many options. We talk about how many new companies there are every year. New solutions. Our adoption of technology is accelerating. As, McKinsey said, we went through 10 years of technological evolution and workplace evolution over the first six months of the pandemic. So, really everything's moving at unprecedented velocity unlike ever before. We have a new game here on theCUBE specifically for this show. And, we are challenging our guests, prompting our guests, to give us a 30 second sizzly sound bite with your hot take on the most important themes of this year's show. Think of it as a thought leadership moment. Opportunity to plug if you really want it. Krishna, you've just given me the nod. I'm going to start with you first and then we'll then we'll pass it along, yeah >> Sure. I think on thought leadership, the way that on cloud, business value is the focus, not the technology. Technology is important, but business value is the focus. And, the way that I see it evolving is with quantum computing coming out more and more, becoming relevant, and Edge is actually becoming quite active as well. All this while on cloud, we focused on business value at the centralized place at the corporate. But, I think the real value of cloud is when you deliver the results, business results, where the customers consume it, that is at the edge. I think that's basically the combination of centralized and the edge is where the real value of cloud is, right. And, I also loud, I know you said 30 seconds but, give me 30 more seconds. >> I like your answer right now. So, I'm going to give you a little more time. Yeah, thank you. >> You've earned more time. (laughs) >> So, I like the way Adam said in the keynote, if you look at it broadly, I categorizes two things. There are a lot of offerings that are becoming comprehensive, like AWS Connect, bringing in workforce management into it, making it a complete end to end product. Similarly, Security Lake, all bringing in the entire security and compliance under one, similarly data. So, there are lot of things that he announced where it is an end to end comprehensiveness of the thing. But, what I love about is, what Amazon is known for, supply chain. So, they rolled out AWS Supply Chain offering. Walk Out technology. So, the Amazon proposition is actually being brought to AWS as a core proposition. I think that's very futuristic and I think we can see more and more customers, enterprise customers, adopting AWS more to drive transformation >> Badly needed right now. Supply chain resiliency. >> Supply chain really having its moment the last two years. File under two words. No one knew, many of us did who worked in it before this. And, here we are, soon as we lost our toilet paper, everyone's freaked out. I love that you talked about business value and also that the end customer is on the edge and, everyone kind of forgets we are essentially the edge device. This is the edge device, it's all around us. And, all the technology that we're all using that you're even talking about is built right inside here from my airlines app to my car rentals to all of it. All right Sowmya, give us your 30 second hot take, roughly. >> Taking the cue from Krishna, right? Today, things are available on AWS Marketplace. So, tomorrow, somebody wants to start an airline, they just have to come and plug and play the apps that are available in the marketplace. Especially your supply chain. The Amazon is known for that. And, a small and medium business they want to start something, right, a .com. It's very easy. So, that's something that we are all looking for. The future is going to be very, very bright and great for the businesses, is what I would say because, most of it could be plug and play with all the solutions. >> Paul: It's already been built. >> On the cloud, so, we are looking forward to it. The second thing I would talk about is, we have to take it to scale. How more and more people can leverage AWS, right? The talent is very important and, that is where partners like us focus on re-scaling our talent. We have 600,000 people, right? We are not just... >> 600,000 people! That's basically as many people live in the San Francisco Bay area for contexts for our listeners. It's how many people work for Walmart? >> It's 1.2 million in Walmart? >> Is it really? >> It is, yes, yes. That's work for Walmart, sidebar. >> So from that standpoint, as the company, we are focusing on re-skilling, up-skilling our talent in order to work AWS cloud and so on, so, that they can go and support our customers. That is something that is very important and that's going to be the future as well. Bring it to scale, go faster. >> I love that you just touched on the fact that you essentially have to practice what you preach because, you've got to think about those 600,000 people in a 100 locations across 40 plus different countries. I love it. Sowmya, I'm going to close on that note. The future is bright, just like your fabulous blazer. >> Thank you so much. Krishna, Sowmya, thank you so much for being here with us. We can't wait to see what happens next, who you help next, and how Tata continues to transform. Thank all of you for tuning in today. A full jam packed day of coverage live here from Las Vegas, Nevada. We are at AWS re:Invent with Paul Gillin. I'm Savannah Peterson. We're theCUBE, the leader in High-Tech Coverage. (corporate electronic xylophone jingle outro)

>>Hello. And welcome back to the cubes live coverage here in Seattle for the cubes coverage of AWS marketplace seller conference. Now part of really big move and news, Amazon partner network combines with AWS marketplace to form one organization, the Amazon partner organization, APO where the efficiencies, the next iteration, as they say in Amazon language, where they make things better, simpler, faster, and, and for customers is happening. We're here with Chris Cruz, who's the general manager, worldwide leader of ISV alliances and marketplace, which includes all the channel partners and the buyer and seller relationships all now under one partner organization, bringing together years of work. Yes. If you work with AWS and are a partner and, or sell with them, all kind of coming together, kind of in a new way for the next generation, Chris, congratulations on the new role and the reor. >>Thank you. Yeah, it's very exciting. We're we think it invent, simplifies the process on how we work with our partners and we're really optimistic so far. The feedback's been great. And I think it's just gonna get even better as we kind of work out the final details. >>This is huge news because one, we've been very close to the partner that we've been working with and we talking to, we cover them. We cover the news, the startups from startups, channel partners, big ISVs, big and small from the dorm room to the board room. You guys have great relationships. So check marketplace, the future of procurement, how software will be bought, implemented and deployed is also changed. So you've got the confluence of two worlds coming together, growth in the ecosystem. Yep. NextGen cloud on the horizon for AWS and the customers as digital transformation goes from lift and shift to refactoring businesses. Yep. This is really a seminal moment. Can you share what you talked about on the keynote stage here, around why this is happening now? Yeah. What's the guiding principle. What's the north star where, why what's what's the big news. >>Yeah. And so, you know, a lot of reasons on why we kind of, we pulled the two teams together, but you know, a lot of it kind gets centered around co-sell. And so if you take a look at marketplace where we started off, where it was really a machine image business, and it was a great self-service model and we were working with ISVs that wanted to have this new delivery mechanism on how to bring in at the time was Amazon machine images and you fast forward, we started adding more product types like SAS and containers. And the experience that we saw was that customers would use marketplace for kind of up to a certain limit on a self-service perspective. But then invariably, they wanted by a quantity discount, they wanted to get an enterprise discount and we couldn't do that through marketplace. And so they would exit us and go do a direct deal with a, an ISV. >>And, and so to remedy that we launched private offers, you know, four years ago. And private offers now allowed ISVs to do these larger deals, but do 'em all through marketplace. And so they could start off doing self-service business. And then as a customer graduated up to buying for a full department or an organization, they can now use private offers to execute that larger agreement. And it, we started to do more and more private offers, really kind of coincided with a lot of the initiatives that were going on within Amazon partner network at the time around co-sell. And, and so we started to launch programs like ISV accelerate that really kind of focused on our co-sell relationship with ISVs. And what we found was that marketplace private offers became this awesome way to automate how we co-sell with ISV. And so we kinda had these two organizations that were parallel. We said, you know what, this is gonna be better together. If we put together, it's gonna invent simplify and we can use marketplace private offers as part of that co-sell experience and really feed that automation layer for all of our ISVs as they interacted with native >>Discussions. Well, I gotta give you props, you and Mona work on stage. You guys did a great job and it reminds me of the humble nature of AWS and Amazon. I used to talk to Andy jazzy about this all the time. That reminds me of 2013 here right now, because you're in that mode where Amazon reinvent was in 2013. Yeah. Where you knew it was breaking out. Yeah. Everyone's it was kind of small, but we haven't made it yet. Yeah. But you guys are doing billions of vows in transactions. Yeah. But this event is really, I think the beginning of what we're seeing as the change over from securing and deploying applications in the cloud, because there's a lot of nuanced things I want to get your reaction on one. I heard making your part product as an ISV, more native to AWS's stack. That was one major call out. I heard the other one was, Hey, if you're a channel partner, you can play too. And by the way, there's more choice. There's a lot going on here. That's about to kind of explode in a good way for customers. Yeah. Buyers get more access to assemble their solutions. Yeah. And you got all kinds of like business logic, compensation, integration, and scale. Yeah. This is like unprecedented. >>Yeah. It's, it's exciting to see what's going on. I mean, I think we kind of saw the tipping point probably about two years ago, which, you know, prior to that, you know, we would be working with ISVs and customers and it was really much more of an evangelism role where we were just getting people to try it. Just, just list a product. We think this is gonna be a good idea. And if you're a buyer, it's like just try out a private offer, try out a self, you know, service subscription. And, and what's happened now is there's no longer a lot of that convincing that needs to happen. It's really become accepted. And so a lot of the conversations I have now with ISVs, it's not about, should I do marketplace it's how do I do it better? And how do I really leverage marketplace as part of my co-sell initiatives as, as part of my go to market strategy. >>And so you've, you've really kind of passed this tipping point where marketplaces are now becoming very accepted ways to buy third party software. And so that's really exciting. And, and we see that we, you know, we can really enhance that experience, you know, and what we saw on the machine image side is we had this awesome integrated experience where you would buy it. It was tied right into the EC two control plane. And you could go from buying to deploying in one single motion. SAS is a little bit different, you know, we can do all the buying in a very simple motion, but then deploying it. There's a whole bunch of other stuff that our customers have to do. And so we see all kinds of ways that we can simplify that. You know, recently we launched the ability to put third party solutions outta marketplace, into control tower, which is how we deploy all of our landing zones for AWS. And now it's like, instead of having to go wire that up as you're adding new AWS environments, why not just use that third party solution that you've already integrated to you and have it there as you're span those landing zones through >>Control towers, again, back to humble nature, you guys have dominated the infrastructure as a service layer. You kind of mentioned it. You didn't really kind of highlight it other than saying you're doing pretty good. Yeah. On the IAS or the technology partners as you call or infrastructure as you guys call it. Okay. I can see how the, the, the pan, the control panel is great for those customers. But outside that, when you get into like CRM, you mentioned E R P these business apps, these horizontal and verticals have data they're gonna have SageMaker, they're gonna have edge. They might have, you know, other services that are coming online from Amazon. How do I, as an ISV, get my stuff in there. Yeah. And how do I succeed? And what are you doing to make that better? Cause I know it's kind of new, but not new. Yeah, >>No, it's not. I mean, that's one of the things that we've really invested on is how do we make it really easy to list marketplace? And, you know, again, when we first start started, it was a big, huge spreadsheet that you had to fill out. It was very cumbersome and we've really automated all those aspects. So now we've exposed an API as an example. So you can go straight out of your own build process and you might have your own C I CD pipeline. And then you have a build step at the end. And now you can have that execute marketplace update from your build script, right across that API all the way over to AWS marketplace. So it's taking that effectively, a C CD pipeline from an ISV and extending it all the way to AWS and then eventually to a customer, because now it's just an automated supply chain for that software coming into their environment. And we see that being super powerful. There's nowhere manual steps >>Along. Yeah. I wanna dig into that because you made a comment and I want you to clarify it here in the cube. Some have said, even us on the cube. Oh, marketplace. Just the website's a catalog. Yeah. Feels old school. Yeah. Feels like 1995 database. I'm kind of just, you know, saying no offense sake. And now you're saying, you're now looking at this and, and implementing more of a API based. Why is that relevant? I'm I know the answer. You already set up with APIs, but explain the transition from the mindset of it's a website. Yeah. Buy stuff on a catalog to full blown API layer. Yeah. Services. >>Absolutely. Well, when you look at all AWS services, you know, our customers will interface, you know, they'll interface them through a console initially, but when they're using them in production, they're, it's all about APIs and marketplace, as you mentioned, did start off as a website. And so we've kind of taken the opposite approach. We've got this great website experience, which is great for demand gen and, you know, highlighting those listings. But what we want to do is really have this API service layer that you're interfacing with so that an ISV effectively is not even in our marketplace. They interfacing over APIs to do a variety of their high, you know, value functions, whether it's listing soy, private offers. We don't have that all available through APIs and the same thing on the buyer side. So it's integrating directly into their AWS environment and then they can view all their third party spend within things like our cost management suites. They can look at things like cost Explorer, see third party software, right next to first party software, and have that all integrated this nice as seamless >>For the customer. That's a nice cloud native kind of native experience. I think that's a huge advantage. I'm gonna track that closer. We're we're gonna follow that. I think that's gonna be the killer killer feature. All right. Now let's get to the killer feature and the business logic. Okay. Yeah. All partners all wanna know what's in it for me. Yeah. How do I make more cash? Yeah. How do I compensate my sales people? Yeah. What do you guys don't compete with me? Give me leads. Yeah. Can I get MDF market development funds? Yeah. So take me through the, how you're thinking about supporting the partners that are leaning in that, you know, the parachute will open when they jump outta the plane. Yeah. It's gonna be, they're gonna land safely with you. Yeah. MDF marketing to leads. What are you doing to support the partners to help them serve their >>Customers? It's interesting. Market marketplace has become much more of an accepted way to buy, you know, our customers are, are really defaulting to that as the way to go get that third party software. So we've had some industry analysts do some studies and in what they found, they interviewed a whole cohort of ISVs across various categories within marketplace, whether it was security or network or even line of business software. And what they've found is that on average, our ISVs will see a 24% increased close rate by using marketplace. Right. So when I go talk to a CRO and say, do you want to close, you know, more deals? Yes. Right. And we've got data to show that we're also finding that customers on average, when an ISV sales marketplace, they're seeing an 80% uplift in the actual deal size. And so if your ASP is a hundred K 180 K has a heck of a lot better, right? >>So we're seeing increased deal sizes by going through marketplace. And then the third thing that we've seen, that's a value prop for ISVs is speed of closure. And so on average, what we're finding is that our ISVs are closing deals 40% faster by using marketplace. So if you've got a 10 month sales cycle, shaving four months off of a sales cycle means you're bringing deals in, in an earlier calendar year, earlier quarter. And for ISVs getting that cash flow early is very important. So those are great metrics that we're seeing. And, and, you know, we think that they're only >>Gonna improve and from startups who also want, they don't have a lot of cash ISVs that are rich and doing well. Yeah. They have good, good, good, good, good to market funding. Yeah. You got the range of partners and you know, the next startup could be the next Figma could be in that batch startups. Exactly. Yeah. You don't know the game is changing. Yeah. The next brand could be one of those batch of startups. Yeah. What's the message to the startup community. Yeah. >>I mean, marketplace in a lot of ways becomes a level in effect, right. Because, you know, if, if you look at pre marketplace, if you were a startup, you were having to go generate sales, have a sales force, go compete, you know, kind of hand to hand with these largest ISVs marketplace is really kind of leveling that because now you can both list in marketplace. You have the same advantage of putting that directly in the AWS bill, taking advantage of all the management go features that we offer all the automation that we bring to the table. And so >>A lot of us joint selling >>And joint selling, right? When it goes through marketplace, you know, it's gonna feed into a number of our APN programs like ISV accelerate, our sales teams are gonna get recognized for those deals. And so, you know, it brings nice co-sell behavior to how we work with our, our field sales teams together. It brings nice automation that, you know, pre marketplaces, they would have to go build all that. And that was a heavy lift that really now becomes just kind of table stakes for any kind of ISV selling to an, any of >>Customer. Well, you know, I'm a big fan of the marketplace. I've always have been, even from the early days, I saw this as a procurement game changer. It makes total sense. It's so obvious. Yeah. Not obvious to everyone, but there's a lot of moving parts behind the scenes behind the curtain. So to speak that you're handling. Yeah. What's your message to the audience out there, both the buyers and the sellers. Yeah. About what your mission is, what you're you wake up every day thinking about. Yeah. And what's your promise to them and what you're gonna work on. Cause it's not easy. You're building a, an operating model. That's not a website. It's a full on cloud service. Yeah. What's your promise. And what's >>Your goals. No. And like, you know, ultimately we're trying to do from an Aus market perspective is, is provide that selection experience to the ABUS customer, right? There's the infamous flywheel that Jeff put together that had the concepts of why Amazon is successful. And one are the concepts he points to is the concept of selection. And, and what we mean by that is if you come to Amazon it's is effectively that everything stored. And when you come across, AWS marketplace becomes that selection experience. And so that's what we're trying to do is provide whatever our AWS customers wanna buy, whatever form factor, whatever software type, whatever data type it's gonna be available in AWS marketplace for consumption. And that ultimately helps our customers because now they can get whatever technologies that they need to use alongside Avis. >>And I want, wanna give you props too. You answered the hard question on stage. I've asked Andy EY this on the cube when he was the CEO, Adam Celski last year, I asked him the same question and the answer has been consistent. We have some solutions that people want a AWS end to end, but your ecosystem, you want people to compete yes. And build a product and mostly point to things like snowflake, new Relic. Yeah. Other people that compete with Amazon services. Yeah. You guys want that. You encourage that. Yeah. You're ratifying that same statement. >>Absolutely. Right. Again, it feeds into that selection experience. Right. If a customer wants something, we wanna make sure it's gonna be a great experience. Right. And so a lot of these ISVs are building on top of AWS. We wanna make sure that they're successful. And, you know, while we have a number of our first party services, we have a variety of third party technologies that run very well in a AWS. And ultimately the customer's gonna make their decision. We're customer obsessed. And if they want to go with a third party product, we're absolutely gonna support them in every way shape we can and make sure that's a successful experience for our customers. >>I, I know you referenced two studies check out the website's got buyer and seller surveys on there for Boer. Yeah. I don't want to get into that. I want to just end on one. Yeah. Kind of final note, you got a lot of successful buyers and a lot of successful sellers. The word billions, yes. With an S was and the slide. Can you say the number, how much, how many billions are sold yeah. Through the marketplace. Yeah. And the buyer experience future what's those two things. >>Yeah. So we went on record at reinvent last year, so it's approaching it birthday, but it was the first year that we've in our 10 year history announced how much was actually being sold to the marketplace. And, you know, we are now selling billions of dollars to our marketplace and that's with an S so you can assume, at least it's two, but it's, it's a, it's a large number and it's going >>Very quickly. Yeah. Can't disclose, you know, >>But it's a, it's been a very healthy part of our business. And you know, we look at this, the experience that we >>Saw, there's a lot of headroom. I mean, oh yeah, you have infrastructure nailed down. That's long, you get better, but you have basically growth up upside with these categor other categories. What's the hot categories. You >>Know, we, we started off with infrastructure related products and we've kind of hit critical mass there. Right? We've, there's very few ISVs left that are in that infrastructure related space that are not in our marketplace. And what's happened now is our customers are saying, well, I've been buying infrastructure products for years. I'm gonna buy everything. I wanna buy my line of business software. I wanna buy my vertical solutions. I wanna buy my data and I wanna buy all my services alongside of that. And so there's tons of upside. We're seeing all of these either horizontal business applications coming to our marketplace or vertical specific solutions. Yeah. Which, you know, when we first designed our marketplace, we weren't sure if that would ever happen. We're starting to see that actually really accelerate because customers are now just defaulting to buying everything through their marketplace. >>Chris, thanks for coming on the queue. I know we went a little extra long. There wanted to get that clarification on the new role. Yeah. New organization. Great, great reorg. It makes a lot of sense. Next level NextGen. Thanks for coming on the cube. Okay. >>Thank you for the opportunity. >>All right here, covering the new big news here of AWS marketplace and the AWS partner network coming together under one coherent organization, serving fires and sellers, billions sold the future of how people are gonna be buying software, deploying it, managing it, operating it. It's all happening in the marketplace. This is the big trend. It's the cue here in Seattle with more coverage here at Davis marketplace sellers conference. After the short break.

>>Welcome back everyone to the cubes coverage here in Seattle, Washington for the Avis marketplace seller conference, part of the APN partner network merging with the marketplace to form the Amazon partner organization. I'm John furrier, host of the cube Walter Wall coverage today, Christian Gor cash, who is the VP of alliances at Kong Inc. Welcome to the cube. Thanks for coming on. >>Thank you. Thank you, John. Really glad to be here. Corke exactly. Yeah. It's awesome. >>So Kong we've been following you guys for while Docker Kong cube. You've been part of our cube conversation. Also part of our, our startup showcase fast growing startup, you know, working on stuff that everyone loves APIs. I mean, APIs are so popular now that they now a security concern, right? Yeah. So like it gets squat there everywhere. I won't say API sprawl, but APIs are the connections and that are, is the web. That is the cloud. Okay. Now with cloud native developers who are now in the front lines have taken over it, everyone knows DevOps dev SecOps is now the new it and it's the developers security and data they're below they're the new ops, right? So, so this is where microservices come in, open source service MES new automation is coming down the pike. That's super valuable to businesses as they look at cloud native architecture, what are you guys doing in there? Take a minute to explain Kong's value proposition, the hot products, and then why you're here. >>Yeah. So, you know, I joined Kong now or three years ago, you know, we were still just reaching our hundred employees, mark, which is very important, very startup, but even back then, you know, Kong was relatively well known in industry, you know, so we have one of the most, well the most popular open source project in API gateway area. So con API gateway, you know, we cross now 300 million downloads, even more important is just the scale it, which the product's been used. So between our open source community and enterprise customers, we are now crossing like 11 trillion transactions per month. Now just give you comparison. Like this is like 18, 19 times more than Netflix per month. You know? So for any company that has a technology that operates it at scale, you need to hit few things outta the park. You know, as he mentions cloud data developers, they want simplicity. You know, they want automation. They also want performance and scale and security, which are all critical, you know, to how Kong, you know, start as opensource project. Now, of course we have the whole suite of enterprise products. We also have our con service mesh offering as well as our cloud offerings. >>Yeah. And this is how open source is doing it now, obviously, you know, I, I still remember, I still tell the story to the young startups. Hey, I, there was proprietary software when I was in college. Open source is now everything. Now you've got, got cloud scale. So the dynamic between open source, which has become the software industry open source success doesn't mean it's it's game over. It's the beginning. The commercialization that you guys have gone through is super important. Trillions of transactions. Now you have enterprises working with you. What's the big advantage of the seller relationship that you have with Amazon? Why are customers using it? What are they buying it for? Give the pitch of con for the marketplace customer. >>Yeah, it's actually, we are relatively new in AWS marketplace. You know, so our first transaction that we ever done was actually in July and 2021. So we are just over a year, you know, that journey, you know, when I look what Chris gross talked today, he was talking about, you know, Hey, just publishing marketplace, not enough. You know, you need to understand what's your value proposition. You need to make sure your operations already, your sales is ready. Everything is, is set. And we kind of did this for the first year and a half is spend a lot of time improving our integration with AWS overall, all the first party services relevant to con we also understood, well, what does it take to kind of fine tune our value proposition? We have like three specific sales place. And you know, when we launch our flagship product con connect enterprise and got our first transaction, that was great milestone for, for star like Kong. But then what we've seen is just that work that we've done before really paid off. I mean right now, >>Like what we'll give example. >>Yeah. So, you know, we are focusing on as measure three sales place. Money is we are focused, specific on helping customers who are modernizing and, and their application going to the cloud. And you have a lot of these, you know, lifting shift and are rearchitect and modernized, but most of the attentions on the workloads, what about the connections? You know, so a monolith application had to authentic all the users understand wheres the network and so on. When you build those, when you now decouple this built like 1,000 thousand microservices, you don't want to repeat this for every microservice. So that's where K brings the whole suite from, you know, service match to the API gate to help manage the journey and really support this environment. And we spend a lot of time to just fine tune that message. So that customers understood where, you know, how can we help them on their journey beyond what, for instance, cloud native or AWS API gateway offers them. So we can really help them from day one on the journey and accelerate. And >>I think I it's a no, it's a no braining for a customer to buyer or to come into the marketplace and say, click, I'm gonna buy some data analytics services. I'm gonna buy gateway through Kong. But when they start getting into these microservices, this automation opportunity there, there's more behind the curtain for them with Kong. So I have to ask you with the keynote we heard from Chris, the leader of the marketplace. Now he said that he wants the ISVs to be more native in the cloud. That probably resonates with you. You, >>You guys well with con's relatively simple because we were built at cloud native, you know, so very briefly the whole story of Congo. This is before Ajo, our founders were actually running the, the very popular API exchange col mesh shape. And they had to build their own gateway just to handle the scale and was built on cloud native technologies. And then when everybody's calling you, what are you using to running? This are using PGS. And so else, no, we built ourselves, oh, how can we get our hands on? That's how con actually >>Came to. And that's how the big winners usually happen too. They start build their own, solve their own problem because it's a big scale problem. Exactly. No one's had that problem. >>Yeah. And what we have seen, especially what was very, you know, through, through the pandemic, what we have seen. And it's interesting, you know, being in a startup doing pandemic is like, whoa, will the life just shut down or what we're doing? You know? But actually what we have seen customers prioritize the new business capability. For instance, you have a large parental companies that overnight, they have to understand where the assets are. Yeah. Or banks who are like 45 days of, you know, approving process for the loans. They need to reduce it for a day or two. >>Yeah. And they're adding more developers, too, exactly. To build the modern application. So they need to have that infrastructure as code aspect. Correct. >>And they >>Need in place. >>Yeah. I need to like you have, you know, I don't think that many customers still have waterfall cycles, but they have, have pre pretty long developers development cycles. And now you need to, you know, do this multiple times a day. That's >>Interesting. We talked to a lot of cloud architects and C CIO C says, and you know, the executive just hire more developers take that hill, build. It just don't build a new app. It's not that easy boss. When, when the cloud architect says we have to be fully operationally ready with cloud native infrastructure's code. So with that, you're seeing a lot more enterprises come in now that are more savvy. They getting better. We're seeing Kubernetes more and more. You're seeing containerization. You're seeing that cloud native enterprise acceptance. What does that mean for you guys in the marketplace, as you look at the value proposition, how are you guys working with the marketplace today and where do you see customers buying in the future? >>Yeah, so we as mentioned, you know, we, we are now a year into that journey. We already seen tremendous benefits just in terms of reducing the friction. You know, the whole procurement, you know, you come as a startup with some, some of the largest companies in the world, they used to buy five, 10 billion in software and they have all these processes and you're like, well, but we only have like two people in finance. Sorry. How can you, and where marketplace can really, really helps us is, you know, improve this experience, both sides because they understand like we are fast moving company. They, they want us because of our speed and, and innovation that we, the product's strong. Yeah. They don't want us to get bogged down in all these pro procurement processes either. And so, so that's the first benefit. We also are working very hard to make sure that the customers can provision Kong in AWS and automate across the board. So essentially reducing their time to value dramatically. Yeah. And another thing that we found tremendously beneficial for us is a startup is the whole concept of a standard marketplace contract. Yeah. So instead of us coming with our little MSA or come like 50 page MSA from companies, we now have a middle ground. So we can just agree. You know, there's some differences, some specifics to qu software and it's tremendously reduced costs on both sides. >>Great. For you guys great for the buyers. Yeah. You get deployed services. They're not just buying, they're managing and deploying. Yeah, >>Exactly. Great. >>Quick, final question. Put a plugin for the company. What are you working on now? What's the big news. What's the con update? >>Well, that's an interesting part because I can't tell you because next week we have our con summit. Oh right. In San Francisco. The cubes not so 28, 20 ninth. Yeah. We, we we'll, I think we are gonna fix that in the future. But anyway, this is the first time after pandemic to do this in person, we have number of very exciting announcement, our Kong products, as well as you may hear some news about our AWS partnership, >>We like con we believe that DevOps has happened. Dev sec ops, whatever you gonna call it, dev is now the developers they're in the front lines. They're in the C I CD pipeline. They're shifting left. That's the new they took over it. That's what DevOps does. It's not a title. Now you have security and data ops behind the scenes. That's gonna be middleware. That's gonna have tons of microservices. So more, more, more action coming, all API based. >>Exactly. And the more, you know, the more complexity we can take away from that, the better we, you know, the >>Whole community. Thank you. Spending the time to come on the cube here at the, a us marketplace seller conference. What do you think about the APN merging with the marketplace formed the P the Amazon partner organization. Thumbs up, thumbs down. What's your heard? >>It's excellent. We have a great friend in AP, a great friend, us marketplace. Now both of them work together with huge. >>Fantastic. Yes. Thanks for okay. Cube coverage here in Seattle. I'm John furier APN marketplace together. APOs the new organization making it easier. Of course, we got all the coverage here. Thanks for watching.

>>Okay, welcome back. Everyone's cubes live coverage of eight of us reinforced 22. I'm John furrier, my host David Lon. We've got a great guest from Cisco, Eric Costin, technical marketing engineer, Cisco systems. Great to have you on. Thanks with >>The all right. Thanks for having, >>Of course we've doing a lot of Cisco laws, Cisco events, Barcelona us know a lot of folks over there. A lot of great momentum supply chain challenges, but you got the cloud with a lot of networking there too. A lot of security conversations, dev sec ops, the trend we're hearing here is operations security and operations. What are some of the business realities that you guys are looking at right now focused on from a Cisco perspective and a landscape perspective? >>Well, the transition to the cloud is accelerating and it's really changed the way we're doing business and what we do now, this combined with the more and more remote work by remote users and also the consumption of cloud-based tools to perform your business functions has dramatically changed the contour of the business environment. The traditional trust boundary has evaporated or at least transformed dramatically, but you still have those requirements for trust for micro segmentation. So what we've seen is a dramatic change in how we do business and what we do. And this is essential because the value proposition is enormous and companies are able to pursue more and more ambitious objectives. But from a security point of view, it's quite challenging because on one hand, what we call the attack surface has increased and the stakes are much higher. So you have more sophisticated malicious actors taking advantage of a broader security target in order to conduct your business in order to maintain business continuity and achieve your objectives. You need to protect this environment. And one, one of the, >>Sorry, just to, just to clarify, sure. You said the value proposition is enormous. You mean the value proposition of the cloud is enormous. Exactly. So the business is leaning in big time and there are security consequences to >>That precisely. And so, and one thing that we've seen happen in the industry is as these components of the business environment have change, the industry has sort of bolted on more and more security solutions. But the problem with that is that's led to enormous complexity in administering security for the company, which is very expensive to find people with those expertise. And also the complexity itself is a vulnerability. >>And, and that traditional trust boundary that you talked about, it hasn't been vaporized has it, it's still there. So are you connecting into that? Is there an interoperability challenge? Does that create more security issues or are people kind of redoing? We talk about security as a do over, how are customers approaching it? >>It is a challenge because although the concept of a trust boundary still exists, the nature of the hybrid multi-cloud environment makes it very difficult to define furthermore, the traditional solutions such as simply having a, a, a firewall and, and an on-premise network is now much more complex because the on-premise network has to connect to the cloud infrastructure and parts of the cloud infrastructure have to be exposed to the public. Other parts have to be protected. So it's not that the, the concept of trusted versus untrusted has gone away. It's just become fundamentally more complex. >>So Eric, I wanna get your thoughts on this higher level abstraction trend, because you're seeing the complexity being pushed to the customers and they want to buy cloud or cloud operations from partners platforms that take the heavy lifting from there, and best of breed products that handle the complexity. What's your reaction to that, that statement? Do you think that's happening or that will happen because either the complexity is gonna be solved by the customer, or they're gonna buy a platform or SA product. >>Now the, the it's it's unreasonable to expect the customers to constantly adapt to this changing environment. From the point of view of, of security, they have to be able to focus on their business objectives, which is to actually sell their products and pursue their ambitions. And it's a distraction that they really can't afford if they have to be focused on security. So the solutions have to take that challenge that distraction away from them, and that has to be integral to the solution. >>So you're saying that the, the vendors, the provi supplier has to deal the underlying complexities on behalf of the customer. >>Exactly. The vendor can't do this without a robust partnership with the cloud provider, working together, the both at the engineering level to develop the products together and in the implementation, as well as standing side by side with the customer, as they expand their business into the >>Cloud, this is super cloud it's super cloud. Right? Exactly. So give us the specifics. What are you doing? What's Cisco doing? How are you working with AWS? What solutions are you talking about? >>Well, Cisco has a wide variety, quite an expansive portfolio because there's a large number of components to the solution. This spans both the, the workload protection, as well as the infrastructure protection. And these are integrated and in partnership with AWS not only integrated together, but integrated into the cloud components. And this is what allows comprehensive protection across the hybrid cloud environment. >>So are we talking about solutions that are embedded into switches? We're talking about software layers, maybe give, describe, add a little color, paint, a picture of the portfolio. >>And, and it's really all of those things. So the most of the solutions historically could say evolved from solutions that were utilized in the physical infrastructure, in the firewalls, in the switches, in the routers. And some of these technologies are still basically confined to those, to those form factors. But some of the most important technologies we use such as snort three, which is a best of breed intrusion protection system that we have adopted is, is applicable as well to the virtual environment, so that we, we push into the cloud in a way that's seamless. So that if you're, if you've developed those policies for your on-prem solutions, you can extend them into the cloud effortlessly. Another example of something that adapts quite well to the cloud is security intelligence. Cisco has talus. Talus is the world's leading security intelligence operation. This is fundamental for addressing threats day zero attacks and Taos updates are products approximately once every hour with the new, with information about these emerging attacks, as well as informing the community as a whole of this. And now that that architecture is very easily extensible into the cloud because you can inform a virtual device just as easily as you can inform a physical device of an emergent threat, >>But technically, how do you do that integration? That's just through AWS primitives. How do you, how does Cisco work with AWS at an engineering level to make that happen? >>So, part of it is that we, we, we have taken certain of our products and we virtualized them. So you could say the, the, the simplest or more straightforward approach is to take our firewalls and, and our other products and simply make virtual machines out of them. But that's really not sort of the most exciting thing. The most exciting thing is that working with them, with integration, with their components and doing such things as having our management platforms, like our Cisco defense orchestrator, be able to discover the virtual environment and utilize that discovery to, to manipulate the security components of that environment. Yeah. >>Kurt, this is where I think you, you, onto something big here management is kind of like, oh yeah, we have software management software kind of always a thing. When you talk about large scale, multiple data point billions and billions of things happening a month. Quantum, we mentioned that in the keynote, we heard Kurt who's VP of platform. So about reasoning. This is kind of a whole nother level of technology. Next level reasoning, knowing things mentioned micro segmentation. So we're seeing a new era of not just policies, reasoning around the networks, around the software stuff that needs to be better than just machine learning, doing predictive and, you know, analysis. Can you share your reaction to that? Because I see this dots connecting at a whole nother level. >>Yes. Now, as we understand artificial intelligence machine learning, I think we appreciate that one of the key components there, we think about it as data science, as data management. But when you think about data, you suddenly recognize where's it coming from data requires visibility. And when we talk about the transition to the cloud and the dispersion of the workforce, visibility is one of the great challenges and visibility even prior to these transitions has been one of the primary focuses of Cisco systems. So as we transition to the cloud and we recognize the need to be able to interpret what we're seeing, we have expanded our capacity to visualize what's happening. And I think there's a, a significant contribution yeah. To the >>Dave and I were talking about this in context to our thesis about super cloud, how that's going evolving building on top of the hyperscalers CapEx investment, doing things, customer data control flows are a huge thing going across multiple geographies. It's global, you got regions, you got network, some trusted, some not. And you have now applications that are global. So you got data flows. >>Yes. >>I mean, data's gotta move across multiple environments. So that's a challenge >>And it has to move secure securely. And furthermore, there's a real challenge here with confidence, with confidence of the company that it's data flow is secure in this new environment that is frankly, can be a little bit uncomfortable. And also the customer and the partners of that business have to be confident that their intellectual property, that their security and identity is protected. >>Yeah. Dave and I were talking also, we're kind of old and seen some seen the movie before. Remember the old days of multi-vendor and OSI models and, you know, interoperability, we're kind of at a new inflection point where teamwork, not just ecosystem partners, companies working together to make sure things are secure. This is a whole nother data problem, opportunity. Amazon sees things that other people don't seek and contribute that back. How does this whole next level multi-vendor partnerships, the open source is a big part of the software piece of it. You got it's custom Silicon. You mentioned. How do you view that whole team oriented approach in security? >>Now this is absolutely essential. The community, the industry has to work together. Fortunately, it's in the DNA of Cisco to interate, I've sat next to competitors at customer sites working to solve the customer's problem. It's just how we function. So it's not just our partnerships, but it's our relationship with industry because industry has common purpose in solving these problems. We have to be confident in order to pursue our objectives. >>You see, you see this industry at a flash point right now, everyone has to partner. >>Exactly. >>Okay. How would you summarize that? We, we are out of time, but so give us your leadership about the >>Part of you, of business leadership. A business needs business continuity, its contributors have to be able to access resources to perform their job. And the customers and partners need confidence to deal with that business. You need the continuity, you demand flexibility to adapt to the changing environment and to take advantage of emerging opportunities. And you expect security. The security has to be resilient. It has to be robust. The security has to be simple to implement Cisco in partnership with AWS provides the security. You need to succeed. >>Eric, thanks coming for so much for coming on the cube. Really appreciate your insights and your experience and, and candid commentary and appreciate your time. Thank >>You. Thank you very much for the >>Opportunity. Okay. We're here. Live on the floor and expo hall at reinforce Avis reinforced 22 in Boston, Massachusetts. I'm John ante. We'll be right back with more coverage after this short break.

>>Hey, welcome back everyone to the cubes coverage of Avis reinvent 2021 here in Las Vegas. Um, John, for your host, the Q with my coach, Dave Nicholson cloud analyst here with SiliconANGLE in the queue. We've got a great guest Rez, the honor, man, SVP cloud hyperscalers transformation TD. Synnex welcome to the cube. Thanks for coming on resident. Hey, >>Good morning. Good >>Morning to you guys. You guys just had this big acquisition with billions and billions of dollars in revenue. Take us through, what are you guys do for set the table for the, for the company? Right. >>Okay. Yeah, it is a pretty big one. Uh, we're now foot number 60 on the fortune 100, um, worldwide revenues around just under $60 billion. Uh, we represent somewhere in the region of, uh, 1500 vendors and OEMs and uh, in over a hundred countries. And, uh, we serve over a hundred thousand parts, 150,000 partners now worldwide. So you got everything from the, uh, end points, style products, uh, all the way up to, uh, data center cloud, serving from the retail to SMB, to VARs going go all the way to enterprise specialists, NSIs. So DD >>And X, big company, you won't global reach. You hit everybody. Basically you T you sell a lot of products, software, hardware, you name it. Cloud is here. What is the big trend that you guys are seeing with cloud? Because you you're innate. You're, you're talking to all the customers, you have a lot of services and you have products. You represent a lot of different brands. How are people rolling them together? Are they composing cloud what's? What are you seeing in the global landscape? >>Um, we specialize in cloud. They've been doing that for a number of years and actually depending on where partners are within the journey, uh, they will have different levels of specialization. And, um, the way we like to look at it is a matrix, um, in terms of where is the complexity of the product that they're trying to take to market, um, versus what is the size and their own maturity. So we, uh, tune our services and our support for those partners to help them better understand and onboard all of that technology and address it towards their partners. Um, so if you can imagine, um, you got many, many announcements that were made here, right? And our partners have to consume all of that information, all of that technology and learn how to use it. And that's where we come in. We, we, we effectively act as the bridge to help them get up there, running and lower the barrier of entry for them to execute >>On those products and they want to add services to it all. Good. Cloud's perfect for that. So what's the relationship with AWS? I'm sure they're obviously enabling a lot of value. What is the relationship with AWS partner network? How do you guys, what are you guys enabled? What are you guys enabled with Amazon? >>So, um, if I give you the, uh, picture of our cloud practice builder, that's a good place to start. Our cloud practice builder program starts with, um, looking at the partner, understanding what is their maturity in that path specifically related to the technologies that they want to work on with AWS. And, um, we look at them in terms of have they got the sales capability, have they got the operational capability, the financial setup, and, um, really helped them then on that journey. So, um, so yeah, we, um, can go very, very deep, uh, where we have our own cohorts who help those partners get up to speed with, >>Do a little, you gotta do a little vetting, you gotta make sure people have the right capabilities. And certain people have certain orientation to certain things, maybe levels of certification. Yep. Is there a swim lanes developing in the partner network that you guys are working with? Big trends, they specializing more in application modernization. Is it more infrastructure or what are you guys seeing in terms of the trends? >>There are multiple, uh, uh trend-setter. So as you say, we have one lane specifically for our ifs. Um, one lane for our, um, uh, people who host with infrastructure. We are, um, you know, obviously data centers, one of our biggest focus areas. Um, and, um, so each of our partners goes into a specific lane specifically related to where they want to focus on. So if you consider for instance, um, somewhere in the area of, uh, ISV ISBNs, um, the primary thing that many of the ISV is out there don't have is the ability to understand all of the AWS programs. So we help them understand that, understand how they can get the most optimal, uh, cost and program with AWS. And then you get into, you get into the next level, which is around, um, uh, their cloud operations, how they actually transact with us. Uh, and you can, you can build a stack, you get into security and then you get a well architected frameworks. So this is just one of the swim lanes that you could effectively go, and we can help, help build them, build that out for them. >>Yeah. So, so Raza draw a little map for me, a sort of a mental map from the perspective of an end user customer say, I'm a very large organization, I've got a large it footprint. I'm looking towards modernizing in the future. How am I engaging with what TD Synnex is actually delivering to the market? We've been talking about partners. So give us a hypothetical again, I'm the customer who is, who's the sales rep. Who's calling on me initially, how am I interacting with you versus the partner? And I know that there are a variety of ways, but give me, give us an example. I want to make sure that people watching this understand cause we use the term partner to me in a whole variety of different things. >>Yeah. Very, very good question. Cause, uh, he is index is one of the biggest companies that the vast majority of the consumers out there have inherited, right? Yeah. We are for number 600 fortune 100. Now most organization deal with a local. It trusted it partner that trusted it partner, um, then is who they would go to, whether it is their infrastructure, whether there is there, uh, um, security that we work with that partner, um, to help them manage it. Now, what we do is really support the partner to have the knowledge they need to have the expertise. They need to have the services that they need to have the solutions that they need to have to deploy those technologies. Um, with that customer. Now, in majority of the cases, the customer will never come in contact with us because we are behind the scenes supporting our partners. >>However, increasingly we are seeing three motions that we work with. One is with our partners, we do sell to right partner, knows what they want. They've worked with the customer, they've established a need. Um, they come to us and we help them deliver that technology. We do a cell width. So this is the part where you're talking about more of the newer technologies, where the partner may be lacking some of that expertise. So this is where are our experts and give you an idea. We have over 300 certifications just in the last year with AWS, um, where our experts would then help the partner actually land that technology with the customer. And then the ultimate level is a sell for you're talking about longer sales cycles, very complex, where they really need to get deep. So we have our own, um, experience centers, uh, customer immersion, uh, uh, programs where the customer actually comes to us with a partner where we then help them actually get through that process. >>So you're a multi-tiered distribution system. You provide service layer to the frontline partners before the end-users provide support and it software technology and, and executive services for them to serve their customer because they're probably not staffed up. They don't have the resources, they have a good business model and they want to make a lot of money. They >>Do, they do. And, um, they have good gross >>Profit margins. >>I hope so. I hope we, we, we help them actually deliver better profit margins and as they move to services and recurring revenues with cloud that becomes more predictable and sustainable for them as well. >>Well, just, I was kidding, but I'm, I'm serious. I want to get into this gross margin because think one of the things that you're bringing up with this question is if I'm a re a partner and I'm talking to an end-user, I might, I want to make a lot of profits. So services are naturally important. I make more gross profit on services. So if you have volume discounts on things that I might not have that volume discount, if I'm going direct to the manufacturer or a platform you provide that, is that right? Like getting that right, that you guys get, provide that discount pass through. >>We do. Um, we laid up, yes, we get a lot of support through their programs. They announced many programs this week, for instance, and as the partner gains more specializations and they gain access to more support through us, they also gain access to some preferred, um, uh, pricing. So to an extent it's about volume. It's also about how deep they go, how, how, how much they invest in their own expertise. So really is a, uh, not just a volume game, but it's a quality game as well. >>Operational value that you provide because you guys must have a lot of programs that pass through to the partner, uh, software systems. What kind of examples can you give if I'm the partner and I have an end-user and I have a boutique, let's just say I specialize in data analytics and whatever unique thing you're providing me services. Is there like certain software systems that you guys have? What operational support do you give to your customers? >>So in terms of the, um, technology that the consumer consumes, um, there is a whole range of technologies around data management and data analytics. Um, then if you're talking about, in terms of the support, operational support that we give to the partner, again, there's the bigger the partner, the more transactions, the more volume they do, they need to have that operational optimization as well. Again, that's where we come in and give them the tools and the technologies. They need to optimize that. >>It's going to ask you the re-invent now that we're in person again, been a year and two years since we've been to reinvent. What's the, what, what are you, what's your assessment of the show this year? What's the big takeaway, um, that you see this year, uh, that that's gonna be relevant for you? >>I, I love the way these guys, um, land some incredibly new technologies. Uh, and I love the theme of Pathfinders from yesterday. Um, so when I look at the, uh, 5g, I mean, that sounds like a game changer to me. And I think there should be a lot of partners out there thinking, hold on a minute, this is a massive opportunity for us. Um, yeah, I mean, so >>The serverless stuff is getting better and better. I mean, like >>It's, they do a good job on their announcements. There is a reason why their technologies so highly rated, uh, these guys know how to do technology. >>And I think if, if I'm, uh, I think of the services that you could roll on top of this, I mean, if you're in front of a customer big, medium or large, I mean, if I'm a developer, a service provider, I can make so much more profit by building more of these services because that pathfind opens up these net new things, 5g AI as a service, kind of the anything. >>Yeah. Um, I mean partners with they, they have their business models. They, the ones who have figured out how to wrap the services around the solutions that are out there. Um, typically we find that they are the most successful with the fastest growth rates and they kind of get themselves into very, uh, positive virtual cycle. Um, the more they can wrap around those services, the higher their value, the more margin they tend to make, the more profitable they are. And actually then they continue to invest and expand their footprint. So >>Quick advice pretend that I am about to become essentially a local trusted value added reseller partner for my end user customers. And I'm going to become a partner of your company. What would your counsel be to me about what I should focus, focus on? What's hot. What's the hottest tip of the spear right now. Yes, right now I need to go out and hire these people, >>Data, data, data, and analytics data. I would absolutely zoom in on that. Um, it is the new oil and every organization needs to have insights. And if businesses out there do not have those insights, they are at a disadvantage partners who can figure out how to build services around data. They're the guys who are really winning. >>Awesome. Great insight. Thanks for coming on the cube here at re-invent great conversation with gradients. I thanks for coming on. Appreciate it. Pleasure. Okay. Cube covers. You're watching the cube, the leader in worldwide tech coverage here in Raven. I'm Jeffrey with Dave Nicholson, host of the cube. Thanks for watching. We'll be right back.

>>Hi, everyone. Welcome to the cubes coverage of Avis reinvent 2021 we're onsite in person. It's a virtual event, also hybrid events. I'm Jennifer and my host, David Dante ninth year, Dave, we've been doing Avis reinvent the cube and it's 11th season. We've seen a lot. Yeah, I'll say. >>And the show is pretty packed, John. I mean, I think it's surprised some folks over 25,000 people here. I mean, obviously a lot of sponsors, but >>Customers to a bad event for AWS in terms of attendance is like record-breaking for any other company, people are standing in line for sessions. It's definitely happening. People are here to learn. They're not just all employees. So definitely a successful event in person as well in the live stream. But so much news to talk about. Andy Jassy is now the CEO of Amazon. That's the top story Adam's Lipsky's taking over as CEO of AWS time, Amazonian who left Amazon to take the CEO job of Tableau sold that company to Salesforce under mark Benioff. Now back to take the helm from Andy Jassy and quite the pressure cooker here as he takes the stage, a lot of people are asking, is will he do well? Will he fumble on stage? Will he do the right things? And does he have what it takes to take the cloud to the next generation with AWS as their number one clear far and away, then the second competitor in Microsoft and then a look distant third and Google. So Amazon's are under a ton of competitive pressure. At least from an industry standpoint, everyone's still trying to catch up. It's the same theme, Dave, every year Amazon is out front and the lead just gets extended and extended. And again, here, no exception. Well, the Uber >>Of course there's you mentioned is Andy Jassy is now taking over a CEO of Amazon. And you know, history would suggest that a lot of times that companies falter when there's a CEO transition, but it feels like it's different this time. Andy Jassy was here since the beginning launched AWS versus a profit engine of Amazon brought back Adam sill Lipski who has a deep understand. He's not as technical as Andy, but obviously as a deep understanding of the business, yeah, he was comfortable up in the keynote. It wasn't John, a typical firehose of announcements. Even those, a lot of announcements, they didn't shove them down our throat and they didn't in the analyst session as well. Usually in the analyst session, it's hours and hours and hours of firehose Kool-Aid injection, not this year. Why do you think that is, is that a COVID thing? Is that a change in now? >>I think Adam's Leschi wants to be his own guy. As, as leader here, a lot of things were eliminated from the keynote that Andy Jasmine did, for instance, Andy Jesse loves music. So we always had the music walk up music like you see in sports, uh, which is very cool. That's an Andy Jassy kind of tweak. Andy is all about announcements and he was just, uh, pushing the envelope. Adam was much more laid back. He sees, I think, more of a holistic picture being more of an app guy being more of a data guy, less of a, I would say under the covers nerd like Jassy was, Andy was very deep on, on a lot of the tech stuff as is Adam. But I think Andy a little bit more proactive on that. So Adam was very much more about the impact of 80 of us culturally, as a society, as a company and kind of brought in this kind of think different apple vibe, which is, you know, the people who are Pathfinders, um, as he takes that Jassy kind of, um, approach of leaders, but be a builder, be a change agent, be a game changer. >>Adam took it to another level by saying, Hey, it's okay to be a Pathfinder because it's net new disruption with the cloud. And I think that's the story that I see coming out of this where, uh, in talking to Adam one-on-one Amazon absolutely has a secret weapon in it's chips, custom Silicon. They're absolutely crushing it with how they're thinking about SAS and platforms and they have a huge ecosystem. And I think at the end of the day, and we talked about this in our story on Silicon angle, Amazon could actually wipe out Microsoft. And I think Microsoft's core competitive advantage has always been their ecosystem and their developers. I think right now in the next few years, if Microsoft doesn't match Amazon, they will be decimated anyway, you know? >>Yeah, hold on. Okay. Amazon's not going to wipe out Microsoft. Microsoft has too much of a cash cow. Look at the hanging on to windows. Couldn't, you know, the mistake and missing mobile event initially missing the cloud. Didn't wipe out Microsoft. So they've just got too much of a software cashflow. That's not gonna happen maybe a little bit over the top. >>I thought, but Microsoft has done a great job and it's not going to tell it to kind of stay in the game and do more. But if you look at the major inflection points, Dave where's digital equipment corporation, where's prime computer. Well, >>I think this is the point is again, history would show that those companies, when they handed the reigns over to a new CEO failed, they faltered, it was self-inflicted wounds. It almost happened. You thought it would happen with Microsoft, whether it became irrelevant under bomber, but when Nadella came in, he reinvigorated because specifically they had the cashflow to be able to do that. Now. So the big question is, okay, w what's going to happen. We ran a survey to our community to see what could disrupt Amazon. You know, that the us government wants to break them apart or wants to regulate them. But our survey respondents said there's a 60% plus probability that Amazon will be disrupted by other factors. And that's what I was self-inflicted wound that's Jesse's that's right. And that's, Jessie's big challenge is how to not make those disruptions, how to fight those disruptions. >>The number one, uh, reason why they could be disrupted was self-inflicted wounds, which again, history would show what happened. But one of the things we talked about is that normally happens when companies stop innovating when they rest on their laurels. Right. And you kind of saw that with those companies that you mentioned, but you mentioned their secret weapon. We wrote about that in our article, the chips. So we heard no secret. Everybody knew graviton three was coming, right? And so that is Amazon secret up. And you know, I've been thinking about this. John Amazon makes a lot of money on x86 instances that they've deployed years ago and they charge a lot for, I was wondering, you know, is the, or the old X 86 instances actually more profitable than graviton, maybe at this point in time, but long-term graviton. They control their own destiny because they control the hardware and software stack. And I bet you allows them to get better negotiating leverage with >>M D and it's of course, I mean, pat, Kelsey, we should talk about this all the time, but as bad as Jason Intel, you, if you're not out in the next wave, your driftwood, I think Intel and AMD and others, they have purpose-built general purpose chips. They're probably going to be for the lift and shift stuff when you, but if you're actually seriously writing software as an owner on the cloud, and you want specific advantages of speed and performance, you're going to want the custom Silicon that's purpose-built for your application and write code to that stack. So, so I think there's a whole nother level of platform as a service. Dave, that's kind of coming out of this re-invent that I think could be a multi generational trend, which is, Hey, the cloud is of super cloud or platform. Look at the riser, snowflake and Databricks. Those guys are on Amazon. Like they're super clouds in and of themselves they're platforms. They're not appoint SAS solution. I think Microsoft in my, my analysis is, yeah, they got office 365, okay. Word processing stuff. But what other SAS apps do they have besides SQL server and other things that are actually being built on there? And if, if I'm a developer you're going to want to go to the platform. That's the highest performance for office 365. It's a cash cow. But how long is that going to last >>A long time? I mean, major momentum. We argue about that later, but I wanna, I want to touch on graviton three because I think that was the big announcement of the day 25% faster than graviton to at least twice the floating point performance twice the crypto graphic performance in three times for machine learning, learning workloads, and very importantly, 60% less power. So at Amazon scale, uh, Adam said this in our meeting, he said, the economics really favor us because of our scale. And so, and they've also announced new training them instances and, and, and what, what having custom Silicon allows Amazon to do is release on a much, much faster cadence than traditional x86. And they could do, and they could do really cool things. Nitro is there, Nick they're smart NEC, which it says the basis, their new hypervisor, if you will. So it allows them to bring in x86, uh, Nvidia NPUs some of their own or Nvidia GPU, some of their own Silicon. So optionality is really the key there. You heard them announce, uh, an SAP instance. So that's a memory intensive instance. They can dial things up, dial things down. They've got full control of the stack. And by the way, copying them Google's copy of Microsoft is copying them. And who's leading this charge in custom Silicon, AWS, obviously Tesla, apple. I mean, these are leading companies that I don't think they all got it wrong. I think >>The Silicon angle is to have your own custom Silicon. And that's the, that is the clearly the advantage as it's vertically integrated. But the other thing that's coming out of this reinvents, the purpose built software concept where, you know, they're not copying Microsoft playbook as the wall street journal was saying, and some are saying Microsoft copying Amazon, Amazon has always been this horizontally scalable resource that's cloud, but with machine learning and AI, you now have this purpose-built kind of capability from software into the app itself where data has to be addressable. And I think the people in the data business kind of know this, but as the rest of the world comes out, architecturally having that horizontal observation space and data that's vertically tied to machine learning is a huge architectural shift. This is a complete rethinking of how software is built and that's going to be a game changer. I think Amazon's well out on front of that. And I think that's going to be a huge architectural shift. >>Well, let's quantify this a little bit because you know, you're, you're making the point that Amazon is the number one cloud, which I would agree with. We're talking here about IAS infrastructure as a service in the past layer that sits on top of that. Microsoft defines the cloud is we'll put in an office 365, Google we'll put in its Google apps, Amazon pure infrastructure as a service. And if you just look at that space, that's about $120 billion business. When you add up AWS, Azure, Alibaba and GCP, which I would contend are the only four hyperscalers out there. I don't include Oracle as a hyperscale. I don't include IBM. I get a lot of crap for that sometimes. Yeah, but we're talking big scaler, $120 billion. So actually relatively small compared to the trillion dollar opportunity that they have, but it's growing at 35% a year. Amazon will do more than 60 billion this year, 62 billion, just to quantify it in that ISS space. Microsoft will be about 38, 30 9 billion. Okay. So pretty substantial. Those two are far ahead of the others. Everybody else's, you know, Google is still in, you know, under 10 billion, Alibaba is right around there. So those two, it's really a two horse race. And I asked Microsoft using its software estate. Amazon's gotta be the innovator and has to have the best cloud to win. And it does well >>Also a platform. Let's go back to the little history lesson for the younger folks out there. When Microsoft was had a monopoly, they had windows operating system, which has had DAS under the covers, but windows was the operating system. And office was a suite of applications. They encourage software developers to build on top of windows and they had other servers off SQL server all came out of that small history. So their bread and butter was to have developers build on top of windows. Hence the monopoly, of course they had the application and the system software, hence the monopoly, hence the Microsoft breakup by the government in 1997. Now today cloud is essentially one big kind of PC concept. It's like windows, it's windows equivalent. So cloud is essentially an environment platform that has apps that run on top of it. Okay. In that world, Amazon by far is the number one windows model at Amazon's. >>I mean, Microsoft is used to is okay, I got Azure and I got office 365 that keeps them in business that keeps them from losing. So it's a placeholder. So that what I'm looking at is what is Amazon? I mean, Amazon versus Azure, doing relative to ISV and uptake for developers. And I'm suggesting that this trend of Amazon will go, if it goes uncontested by Azure, they'll wipe the table on ISV and suffer developers. If you're an owner of a software, you're not gonna write software, that's gonna be sub-optimized for a platform. That's not going to be before, >>Unless you're, unless you're a Microsoft developer, nearly all.net days. And there are a lot of those. And that's what, that's what Microsoft is doing. They're they're, they're, they've, they've shifted to cloud, they've gone everything into cloud. So Azure is their platform for innovation and acceleration. >>So those developers are going to build a sub application versus going over here on AWS. >>Well, that's the, that's the story with Microsoft. Good enough. I know >>Again, this is we're speculating, but we're going to watch that, but that is, to me, will be the battlefield of what will determine Azure versus AWS. And I think everything else is smoke and mirrors Amazon Webster way ahead of Azure, but the TeleSign is going to be does 80 bus attract those developers on their cloud with the custom Silicon, with the integrated stack and with the purpose-built software. I mean, it's looking really good. I think they've got a really compelling story. >>I think it's less about Azure versus AWS. I mean, that's an interesting storyline and I love to talk about it, but I think they'll go back to 120 billion out of 4 trillion. That's really the, the larger opportunity for, for both Microsoft and AWS to continue to grow. Because you look at, you look at Dell with apex, you look at HPE with GreenLake, Lenovo, Cisco, they've all got their own clouds. One of the things that didn't get into our article, but Adam Lipski when, when you asked him about hybrid is that hybrid cloud. When we were talking about some of the stuff they're doing, he S he said, look, that's not cloud what those guys are doing. That's not what we did. And he talked today about edge has to be AWS, not like AWS. That was the quote to use. Talk about, you know, private 5g, bringing out posts. And he gave some examples of that. The point is they, AWS is bringing its system, its architecture to the edge it's programming model infrastructure as code to the edge. Now, Kubernetes, Kubernetes does moderate that a little bit, but his point was, that's not AWS. That's not the cloud. >>Yeah. I think in summary, Dave had to wrap up what's the big trend this week is that Amazon web services is a, is a heaven environment for a developer, for the elite people who want to roll their own for the folks in it. In these other environments, you can have prefabricated purpose-built software platform to build on top of. And I think that isn't going to address the whole ease of ease of rollout. So if I'm a SAS developer, I don't, I want, I don't want to rebuild that over again. I don't want to roll my own. I'll take what you got and connects a good example. If you want to call shedder, you can take it and use it and then build on top of it and iterate on it. So I think it's more of here's a platform for you and take it. So I think that to me is the big story and that's not and think about it. How many people out there, a role in their own Amazon, you've got to be pretty strong at Amazon, uh, familiar ups to roll your own gut >>Of other quick points that he barely emphasized the primitives, the API APIs, that multiple databases, right tool for the right job, took a shot at Oracle without mentioning Oracle because they had sort of one database, but I will say this is mission critical. Oracle still owns that. Uh, they talked about a mainframe migration, tooling and runtime from mainframe compatible runtime. That's going to allow them to nip at the edges of those mainframe workloads and Oracle workloads. It, they're not going to get to the core anytime soon. They also talked about role level and cell level security. We think that's the squirrel acquisition from years ago. And then he made a statement. We have three X with Redshift price performance better than any cloud data warehouse sort of interesting shot at, at, at, at a snowflake and Databricks Databricks. So, um, anyway, yeah, >>I mean, I think, I think overall, I thought Adam did a good job. I think he didn't, uh, he didn't disappoint. Okay. But that's comfortable. I think his goal was to get through this and not have people go well, it's not Andy Jassy. I thought he did an awesome job and he did a good job. And he, he got, he got what he needed to do >>Comfortable. And he obviously leaned on some of his Pathfinder customers. NASDAQ, I thought was very impressive. United airlines dish. So, >>Okay. Cutie coverage, ninth year of the cube here at ADP reinvent, uh, 2021 is the cube. You're watching the leader in high-tech coverage. The cube.

>>From around the globe. It's the cube with digital coverage of AWS reinvent 2020, sponsored by Intel and AWS. >>Welcome back to the queue. It's virtual coverage of Avis reinvent 2020 I'm John furry, your host. Um, this is a cute virtual we're here. Not in, in remote. We're not in person this year, so we're doing the remote interviews. And then this segment is going to build on the quantum conversation we had last year, Richard moles, general manager of Amazon bracket and aid was quantum computing and Fernando Brandao head of quantum algorithms at AWS and Brent professor of theoretical physics at Caltech. Fernando, thanks for coming on, Richard. Thanks for joining us. >>You're welcome to be here. >>So, Fernando, first of all, love your title, quantum algorithms. That's the coolest title I've heard so far and you're pretty smart because you're a theoretical professor of physics at Caltech. So, um, which I'd never be able to get into, but I wish I could get into there someday, but, uh, thanks for coming on. Um, quantum has been quite the rage and you know, there's a lot of people talking about it. Um, it's not ready for prime time. Some say it's moving faster than others, but where are we on quantum right now? What are, what are you, what are you seeing Fernanda where the quantum, where are peg us in the evolution of, of, uh, where we are? >>Um, yeah, what quantum, uh, it's an emerging and rapidly developing fields. Uh, but we are see where are you on, uh, both in terms of, uh, hardware development and in terms of identifying the most impactful use cases of one company. Uh, so, so it's, it's, it's early days for everyone and, and we have like, uh, different players and different technologies that are being sport. And I think it's, it's, it's early, but it's exciting time to be doing quantum computing. And, uh, and it's very interesting to see the interest in industry growing and, and customers. Uh, for example, Casa from AWS, uh, being, uh, being willing to take part in this journey with us in developmental technology. >>Awesome. Richard, last year we talked to bill Vass about this and he was, you know, he set expectations really well, I thought, but it was pretty much in classic Amazonian way. You know, it makes the announcement a lot of progress then makes me give us the update on your end. You guys now are shipping brackets available. What's the update on your end and Verner mentioned in his keynote this week >> as well. Yeah, it was a, it was great until I was really looking at your interview with bill. It was, uh, that was when we launched the launch the service a year ago, almost exactly a year ago this week. And we've come a long way. So as you mentioned, we've, uh, we've, uh, we've gone to general availability with the service now that that happened in August. So now a customer can kind of look into the, uh, to the bracket console and, uh, installed programming concept computers. You know, there's, uh, there's tremendous excitement obviously, as, as you mentioned, and Fernando mentioned, you know, quantum computers, uh, we think >>Have the potential to solve problems that are currently, uh, uh, unsolvable. Um, the goal of bracket is to fundamentally give customers the ability to, uh, to go test, uh, some of those notions to explore the technology and to just start planning for the future. You know, our goal was always to try and solve some of the problems that customers have had for, you know, gee, a decade or so now, you know, they tell us from a variety of different industries, whether it's drug discovery or financial services, whether it's energy or there's chemical engineering, machine learning, you know, th the potential for quantum computer impacts may industries could potentially be disruptive to those industries. And, uh, it's, it's essential that customers can can plan for the future, you know, build their own internal resources, become experts, hire the right staff, figure out where it might impact their business and, uh, and potentially disrupt. >>So, uh, you know, in the past they're finding it hard to, to get involved. You know, these machines are very different, different technologies building in different ways of different characteristics. Uh, the tooling is very disparate, very fragmented. Historically, it's hard for companies to get access to the machines. These tend to be, you know, owned by startups or in, you know, physics labs or universities, very difficult to get access to these things, very different commercial models. Um, and, uh, as you, as you suggested, a lot of interests, a lot of hype, a lot of claims in the industry, customers want to cut through all that. They want to understand what's real, uh, what they can do today, uh, how they can experiment and, uh, and get started. So, you know, we see bracket as a catalyst for innovation. We want to bring together end-users, um, consultants, uh, software developers, um, providers that want to host services on top of bracket, try and get the industry, you know, rubbing along them. You spoke to lots of Amazonians. I'm sure you've heard the phrase innovation flywheel, plenty of times. Um, we see the same approach that we've used successfully in IOT and robotics and machine learning and apply that same approach to content, machine learning software, to quantum computing, and to learn, to bring it together. And, uh, if we get the tooling right, and we make it easy, um, then we don't see any reason why we can't, uh, you know, rapidly try and move this industry forward. And >>It was fun areas where there's a lot of, you know, intellectual computer science, um, technology science involved in super exciting. And Amazon's supposed to some of that undifferentiated heavy. >>That's what I am, you know, it's like, >>There's a Maslow hierarchy of needs in the tech industry. You know, people say, Oh, why five people freak out when there's no wifi? You know, you can't get enough compute. Right. So, you know, um, compute is one of those things with machine learning is seeing the benefits and quantum there's so much benefits there. Um, and you guys made some announcements at, at re-invent, uh, around BRACA. Can you share just quickly share some of those updates, Richard? >>Sure. I mean, it's the way we innovate at AWS. You know, we, we start simple and we, and we build up features. We listen to customers and we learn as we go along, we try and move as quickly as possible. So since going public in, uh, in, in August, we've actually had a string of releases, uh, pretty consistent, um, delivering new features. So we try to tie not the integration with the platform. Customers have told us really very early on that they, they don't just want to play with the technology. They want to figure out how to, how to envisage a production quantum computing service, how it might look, you know, in the context of a broad cloud platform with AWS. So we've, uh, we launched some integration with, uh, other AWS capabilities around security, managing limits, quotas, tagging resources, that type of thing, things that are familiar to, uh, to, to, to current AWS users. >>Uh, we launched some new hardware. Uh, all of our partners D-Wave launched some, uh, uh, you know, a 5,000 cubit machine, uh, just in September. Uh, so we made that available on bracket the same day that they launched that hardware, which was very cool. Um, you know, we've made it, uh, we've, we've made it easier for researchers. We've been, you know, impressed how many academics and researchers have used the service, not just large corporations. Um, they want to have really deep access to these machines. They want to program these things at a low level. So we launched some features, uh, to enable them to do their research, but reinvent, we were really focused on two things, um, simulators and making it much easier to use, uh, hybrid systems systems that, uh, incorporate classical compute, traditional digital computing with quantum machinery, um, in the vein that follow some of the liens that we've seen, uh, in machine learning. >>So, uh, simulators are important. They're a very important part of, uh, learning how to use concepts, computers. They're always available 24, seven they're super convenient to use. And of course they're critical in verifying the accuracy of the results that we get from quantum hardware. When we launched the service behind free simulator for customers to help debug their circuits and experiments quickly, um, but simulating large experiments and large systems is a real challenge on classical computers. You know, it, wasn't hard on classical. Uh, then you wouldn't need a quantum computer. That's the whole point. So running large simulations, you know, is expensive in terms of resources. It's complicated. Uh, we launched a pretty powerful simulator, uh, back in August, which we thought at the time was always powerful managed. Quantum stimulates circuit handled 34 cubits, and it reinvented last week, we launched a new simulator, which actually the first managed simulator to use tensor network technology. >>And it can run up to 50 cubits. So we think is, we think is probably the most powerful, uh, managed quantum simulator on the market today. And customers can flip easily between either using real quantum hardware or either of our, uh, stimulators just by changing a line of code. Um, the other thing we launched was the ability to run these hybrid systems. You know, quantum computers will get more, no don't get onto in a moment is, uh, today's computers are very imperfect, you know, lots of errors. Um, we working, obviously the industry towards fault-tolerant machines and Fernando can talk about some research papers that were published in that area, but right now the machines are far from perfect. And, uh, and the way that we can try to squeeze as much value out of these devices today is to run them in tandem with classical systems. >>We think of the notion of a self-learning quantum algorithm, where you use a classical optimization techniques, such as we see machine learning to tweak and tune the parameters of a quantum algorithm to try and iterate and converge on the best answer and try and overcome some of these issues surrounding errors. That's a lot of moving parts to orchestrate for customers, a lot of different systems, a lot of different programming techniques. And we wanted to make that much easier. We've been impressed with a, a, an open projects, been around for a couple of years, uh, called penny lane after the Beatles song. And, um, so we wanted to double down on that. We were getting a lot of positive feedback from customers about the penny lane talk it, so we decided to, uh, uh, make it a first class citizen on bracket, make it available as a native feature, uh, in our, uh, in our Jupiter notebooks and our tutorials learning examples, um, that open source project has very similar, um, guiding principles that we do, you know, it's open, it's cross platform, it's technology agnostic, and we thought he was a great fit to the service. >>So we, uh, we announced that and made it available to customers and, uh, and, and, uh, already getting great feedback. So, uh, you know, finishing the finishing the year strongly, I think, um, looking forward to 2021, you know, looking forward to some really cool technology it's on the horizon, uh, from a hardware point of view, making it easy to use, um, you know, and always, obviously trying to work back from customer problems. And so congratulations on the success. I'm sure it's not hard to hire people interested, at least finding qualified people it'd be different, but, you know, sign me up. I love quantum great people, Fernando real quick, understanding the relationship with Caltech unique to Amazon. Um, tell us how that fits into the, into this, >>Uh, right. John S no, as I was saying, it's it's early days, uh, for, for quantum computing, uh, and to make progress, uh, in abreast, uh, put together a team of experts, right. To work both on, on find new use cases of quantum computing and also, uh, building more powerful, uh, quantum hardware. Uh, so the AWS center for quantum computing is based at Caltech. Uh, and, and this comes from the belief of AWS that, uh, in quantum computing is key to, uh, to keep close, to stay close of like fresh ideas and to the latest scientific developments. Right. And Caltech is if you're near one computing. So what's the ideal place for doing that? Uh, so in the center, we, we put together researchers and engineers, uh, from computer science, physics, and other subjects, uh, from Amazon, but also from all the academic institutions, uh, of course some context, but we also have Stanford and university of Chicago, uh, among others. So we broke wrongs, uh, in the beauty for AWS and for quantum computer in the summer, uh, and under construction right now. Uh, but, uh, as we speak, John, the team is busy, uh, uh, you know, getting stuff in, in temporary lab space that we have at cottage. >>Awesome. Great. And real quick, I know we've got some time pressure here, but you published some new research, give a quick a plug for the new research. Tell us about that. >>Um, right. So, so, you know, as part of the effort or the integration for one company, uh, we are developing a new cubix, uh, which we choose a combination of acoustic and electric components. So this kind of hybrid Aquacel execute, it has the promise for a much smaller footprint, think about like a few microliters and much longer storage times, like up to settlements, uh, which, which is a big improvement over the scale of the arts sort of writing all export based cubits, but that's not the whole story, right? On six, if you have a good security should make good use of it. Uh, so what we did in this paper, they were just put out, uh, is, is a proposal for an architecture of how to build a scalable quantum computer using these cubits. So we found from our analysis that we can get more than a 10 X overheads in the resources required from URI, a universal thought around quantum computer. >>Uh, so what are these resources? This is like a smaller number of physical cubits. Uh, this is a smaller footprint is, uh, fewer control lines in like a smaller approach and a consistent, right. And, and these are all like, uh, I think this is a solid contribution. Uh, no, it's a theoretical analysis, right? So, so the, uh, the experimental development has to come, but I think this is a solid contribution in the big challenge of scaling up this quantum systems. Uh, so, so, so John, as we speak like, uh, data blessed in the, for quantum computing is, uh, working on the experimental development of this, uh, a highly adequacy architecture, but we also keep exploring other promising ways of doing scalable quantum computers and eventually, uh, to bring a more powerful computer resources to AWS customers. >>It's kind of like machine learning and data science, the smartest people work on it. Then you democratize that. I can see where this is going. Um, Richard real quick, um, for people who want to get involved and participate or consume, what do they do? Give us the playbook real quick. Uh, so simple, just go to the AWS console and kind of log onto the, to the bracket, uh, bracket console, jump in, you know, uh, create, um, create a Jupiter notebook, pull down some of our sample, uh, applications run through the notebook and program a quantum computer. It's literally that simple. There's plenty of tutorials. It's easy to get started, you know, classic cloud style right now from commitment. Jump in, start simple, get going. We want you to go quantum. You can't go back, go quantum. You can't go back to regular computing. I think people will be running concert classical systems in parallel for quite some time. So yeah, this is the, this is definitely not a one way door. You know, you go explore quantum computing and see how it fits into, uh, >>You know, into the, into solving some of the problems that you wanted to solve in the future. But definitely this is not a replacement technology. This is a complimentary technology. >>It's great. It's a great innovation. It's kind of intoxicating technically to get, think about the benefits Fernando, Richard, thanks for coming on. It's really exciting. I'm looking forward to keeping up keeping track of the progress. Thanks for coming on the cube coverage of reinvent, quantum computing going the next level coexisting building on top of the shoulders of other giant technologies. This is where the computing wave is going. It's different. It's impacting people's lives. This is the cube coverage of re-invent. Thanks for watching.

>>From around the globe. It's the cube with digital coverage of AWS reinvent executive summit 2020, sponsored by Accenture and AWS. >>Okay. Welcome back to the cubes coverage of 80 us. Re-invent 2020 virtual ecentric executive summit. The two great guests here to break down the analysis of the relationship with cloud and essential. Brian bowhead director ahead of Accenture. 80 was a business group at Amazon web services. And Andy T a B G the M is essentially Amazon business group lead managing director at Accenture. Uh, I'm sure you're super busy and dealing with all the action, Brian. Great to see you. Thanks for coming on. So thank you. You guys essentially has been in the spotlight this week and all through the conference around this whole digital transformation, essentially as business group is celebrating its 50th anniversary. What's new, obviously the emphasis of next gen post COVID generation, highly accelerated digital transformation, a lot happening. You got your five-year anniversary, what's new. >>Yeah, it, you know, so if you look back it's exciting. Um, you know, so it was five years ago. Uh, it was actually October where we, where we launched the Accenture AWS business group. And if we think back five years, I think we're still at the point where a lot of customers were making that transition from, you know, should I move to cloud to how do I move to cloud? Right? And so that was one of the reasons why we launched the business group. And since, since then, certainly we've seen that transition, right? Our conversations today are very much around how do I move to cloud, help me move, help me figure out the business case and then pull together all the different pieces so I can move more quickly, uh, you know, with less risk and really achieve my business outcomes. And I would say, you know, one of the things too, that's, that's really changed over the five years. >>And what we're seeing now is when we started, right, we were focused on migration data and IOT as the big three pillars that we launched with. And those are still incredibly important to us, but just the breadth of capability and frankly, the, the, the breadth of need that we're seeing from customers. And obviously as AWS has matured over the years and launched our new capabilities, we're Eva with Accenture. Um, and in the business group, we've broadened our capabilities and deepened our capabilities over the, over the last five years as well. For instance, this year with, with COVID, especially, it's really forced our customers to think differently about their own customers or their citizens, and how do they serve as those citizens. So we've seen a huge acceleration around customer engagement, right? And we powered that with Accenture customer engagement platform powered by ADA, Amazon connect. And so that's been a really big trend this year. And then, you know, that broadens our capability from just a technical discussion to one where we're now really reaching out and, and, um, and helping transform and modernize that customer and citizen experience as well, which has been exciting to say, Andy want to get your thoughts here. We've >>Been reporting and covering essential for years. It's not like it's new to you guys. I mean, five years is a great anniversary. You know, check is good relationship, but you guys have been doing the work you've been on the trend line. And then this hits and Andy said on his keynote, and I thought he said it beautifully. And he even said it to me, my one-on-one interview with them was it's on full display right now, the whole digital transformation, everything about it is on full display and you're either were prepared for it or you kind of word, and you can see who's there. You guys have been prepared. This is not new. So give us the update from your perspective, how you're taking advantage of this, of this massive shift, highly accelerated digital transformation. >>Well, I think, I think you can be prepared, but you've also got to be prepared to always sort of, I think what we're seeing in, in, um, in, in, in, in recent times and particularly in two 20, what, what is it I think today there are, um, 4% of the enterprise workloads sits at the cloud. Um, you know, that leaves 96% out there on prem. Um, and I think over the next four to five years, um, we're going to see that sort of, uh, acceleration to the, to the cloud pick up, um, this year as Andy touched on, I think, uh, uh, on Tuesday in his, I think the pandemic is a forcing function, uh, for companies to, to, to really pause and think about everything from, from, you know, how they, um, manage that technology, their infrastructure, to, to clarity to where that data sets to what insights and intelligence that getting from that data. >>And then eventually even to, to the talent, the talent they have in the organization and how they can be competitive, um, that culture, that culture of innovation, of invention and reinvention. And so I think, I think, you know, when you, when you think of companies out there faced with these challenges, it forces us, it forces AWS's forces, AEG to come together and think through how can we help create value for them? How can we help help them move from sort of just causing and rethinking to having real plans in action and that taking them, uh, into, into implementation. And so that's, that's what we're working on. Um, I think over the next five years, we're looking to just continue to come together and, and help these companies get to the cloud and get the value from the cloud. Cause it's, it's beyond just getting to the cloud attached to me and living in the cloud and getting the value from it. >>It's interesting. Andy was saying, don't just put your toe in the water. You've got to go beyond the toe in the water kind of approach. Um, I want to get to that large scale cause that's the big pickup this week that I kind of walked away with was it's large scale. Acceleration's not just toe in the water experimentation. Can you guys share, what's causing this large scale end to end enterprise transformation and what are some of the success criteria have you seen for the folks who have done that? Yeah. And I'll, I'll start in the end. >>You can buy a lawn. So you, it's interesting if I look >>Back a year ago at reinvent and when I did the cube interview, then we were talking about how ABG we're >>Starting to see that shift of customers. You know, we've been working with customers for years on a single of what I call a single-threaded programs, right? We can do a migration, we can do SAP, we can do a data program. And then even last year we were really starting to see customers ask. The question is like, what kind of synergies and what kind of economies of scale do I get when I start bringing these different threads together and also realizing that it's, you know, to innovate for the business and build new applications, new capabilities, well, that, that is going to inform what data you need to, to hydrate those applications, right? Which then informs your data strategy while a lot of that data is then also embedded in your underlying applications that sit on premises. So you should be thinking through how do you get those applications into the cloud? >>So you need to draw that line through all of those layers. And that was already starting last year. And so last year we launched the joint transformation program with AEG. And then, so we were ready when this year happened and then it was just an acceleration. So things have been happening faster than we anticipated, but we knew this was going to be happening. And luckily we've been in a really good position to help some of our customers really think through all those different layers of kind of the pyramid as we've been calling it along with the talent and change pieces, which are also so important as you make this transformation to cloud >>Andy, what's the success factors. Andy Jassy came on stage during the partner day, a surprise fireside chat with Doug Hume and talking about this is really an opportunity for partners to, to change the business landscape with enablement from Amazon. You guys are in a pole position to do that in the marketplace. What's the success factors that you see, >>Um, really from three, three fronts, I'd say, um, w you know, one is the, the people. Um, and, and I, I, again, I think Andy touched on sort of a, uh, success factors, uh, early in the week. And for me, it's these three areas that it sort of boils down to, to these three areas. Um, one is the, the, the, the people, uh, from the leaders that it's really important to set those big, bold visions point the way. And then, and then, you know, set top down goals. How are we going to measure you almost do get what you measure, um, to be, you know, beyond the leaders, to, to the right people in the right position across the company. We're finding a key success factor for these end to end transformations is not just the leaders, but you haven't poached across the company, working in a, in a collaborative, shared, shared success model, um, and people who are not afraid to, to invent and fail. >>And so that takes me to perhaps the second point, which is the culture. Um, it's important, uh, with finding food for the right conditions to be set in the company, not enable people to move at pace, move at speed, be able to fail fast, um, keep things very, very simple, and just keep iterating and that sort of culture of iteration, um, and improvement versus seeking perfection is, is super important for, for success. And then the third part of maybe touch on is, is partners. Um, I think, you know, as we move forward over the next five years, we're going to see an increasing number of players in the ecosystem in the enterprises state. Um, you're going to see more and more SAS providers. And so it's important for companies and our joint clients out there to pick partners like, um, like AWS or, or Accenture or others, but to pick partners who have all worked together and built solutions together. And that allows them to get speed to value quicker. It allows them to bring in pre-assembled solutions, um, and really just drive that transformation in a quicker, it sorts of manner. >>Yeah, that's a great point worth calling out, having that partnership model that's additive and has synergy in the cloud, because one of the things that came out of this this week, this year is reinvented, is there's new things going on in the public cloud, even though hybrid is an operating model, outpost and super relevant. There, there are benefits for being in the cloud and you've got partners, APIs, for instance, and have microservices working together. This is all new, but I got, I got to ask that on that thread, Andy, where did you see your customers going? Because I think, you know, as you work backwards from the customers, you guys do, what's their needs, how do you see them? You know, where's the puck going? Where can they skate to where the puck's going? Because you can almost look forward and say, okay, I've got to build modern apps. I got to do the digital transformation. Everything is a service. I get that, but what do they, what, what solutions are you building for them right now to get there? >>Yeah. And, and of course, with, with, you know, industries blurring and multiple companies, it's always hard to boil down to the exact situations, but you can probably look at it from a sort of a thematic lens. And what we're seeing is as the cloud transformation journey picks up from us perspective, we've seen a material shift in the solutions and problems that we're trying to address with clients that they are asking for us, uh, to, to help, uh, address is no longer just the back office where you're sort of looking at cost and efficiency and, um, uh, driving gains from that perspective. It's beyond that, it's now materially the top line. It's, how'd you get the driving to the, you know, speed to insights, how'd you get them decomposing, uh, their application set in order to derive those insights. Um, how'd you get them, um, to, to, um, uh, sort of adopt leading edge industry solutions that give them that jump start, uh, and that accelerant to winning the customers, winning the eyeballs. >>Um, and then, and then how'd you help drive the customer experience. We're seeing a lot of push from clients, um, or ask for help on how do I optimize my customer experience in order to retain my eyeballs. And then how do I make sure I've got a soft self-learning ecosystem at play, um, where I, you know, it's not just a practical experience, but I can sort of keep learning and iterating, um, how treat my, eat, my customers, um, and a lot of that, um, that's still self-learning that comes from, you know, putting in, uh, intelligence into your, into your systems, getting an AI and ML, uh, in that. And so as a result of that, where it was seeing a lot of push and a lot of what we're doing, uh, is pouring investments into those areas. And then finally, maybe beyond the bottom line and the top line is how do you harden that and protect that with, um, security and resilience? Uh, so I'll probably say those are the three areas. John >>Brian on the business model side, obviously the enablement is what Amazon has. Um, we see things like SAS factory coming on board and the partner network I've see a, is a big, huge partner of you guys. Um, the business models there. You've got I, as, as doing great with chips, you have this data modeling this data opportunity to enable these modern apps. We heard about the partner strategy from Andy. I'm talking about yesterday now about how can partners within even a center. What's the business model side on your side that you're enabling this. Can you just share your thoughts on that? >>Yeah. And so it's, it's interesting. And again, I'm kind of build it in a build a little bit on some of the things that Andy really talked about there, right? And that we, if you think of that from the partnership, we are absolutely helping our customers with kind of that it modernization piece and we're investing a lot and that there's hard work that needs to get done there. And we're investing a lot as a partnership around the tools, the assets and the methodology. So in AWS and Accenture show up together as AEG, we are executing off a single blueprint with a single set of assets so we can move fast. So we're going to continue to do that with all the hybrid announcements from this past week, those get baked into that, that migration modernization theme, but the other really important piece here as we go up the stack, Andy mentioned it, right? >>The data piece, like so much of what we're talking about here is around data and insights. Right? I did a cube interview last week with, uh, Carl hick. Um, who's the CIO from Takeda. And if you hear Christophe Weber from Takeda talk, he talks about Takeda being a data company, data and insights company. So how do we, as a partnership, again, build the capabilities and the platforms like with Accenture's applied insights platform so that we can bootstrap and really accelerate our client's journey. And then finally, on the innovation on the business front, and Andy was touching on some of these, we are investing in industry solutions and accelerators, right? Because we know that at the end of the day, a lot of these are very similar. We're talking about ingesting data, using machine learning to provide insights and then taking action. So for instance, the cognitive insurance platform that we're working together on with Accenture, if they get about property and casualty claims and think about how do we enable touchless claims using machine learning and computer vision that can assess based on an image damage, and then be able to triage that and process it accordingly, right? >>Using all the latest machine learning capabilities from AWS >>With that deep, um, AI machine learning data science capability from Accenture, who knows all those algorithms that need to get built and build that library by doing that, we can really help these insurance companies accelerate their transformation around how they think about claims and how they can speed those claims on behalf of their policy holder. So that's, what's an example of a, kind of like a bottom to top view of what we're doing in the partnership to address these new needs. >>That's awesome. Andy, I want to get back to your point about culture. You mentioned it twice now. Um, challenge is a big part of the game here. Andy Jassy referenced Lambda. Next generation developers were using Lambda. He talked about CIO stories around, they didn't move fast enough. They lost three years. A new person came in and made it go faster. This is a new, this is a time for a certain kind of, um, uh, professional and individual, um, to, to be part of, um, this next generation. What's the talent strategy you guys have to attract and attain the best and retain the best people. How do you do it? >>Um, you know, it's, it's, um, it's an interesting one. It's, it's, it's oftentimes a, it's, it's a significant point and often overlooked. Um, you know, people, people really matter and getting the right people, um, in not just in AWS or, but then on our customers is super important. We often find that much of our discussions with, with our clients is centered around that. And it's really a key ingredient. As you touched on, you need people who are willing to embrace change, but also people who are willing to create new, um, to invent new, to reinvent, um, and to keep it very simple. Um, w we're we're we're seeing increasingly that you need people who have a sort of deep learning and a deep, uh, or deep desire to keep learning and to be very curious as, as they go along. Most of all, though, I find that, um, having people who are not willing or not afraid to fail is critical, absolutely critical. Um, and I think that that's, that's, uh, a necessary ingredient that we're seeing, um, our clients needing more off, um, because if you can't start and, and, and you can't iterate, um, you know, for fear of failure, you're in trouble. And I think Andy touched on that you, you know, where that CIO, that you referred to last three years, um, and so you really do need people who are willing to start not afraid to start, um, and, uh, and not afraid to lead. Yeah. >>It takes a gut-check there. I just said, you guys have a great team over there. Everyone at the center I've interviewed strong, talented, and not afraid to lean in and, and into the trends. Um, I got to ask on that front cloud first was something that was a big strategic focus for Accenture. How does that fit into your business group? That's, uh, Amazon focus, obviously their cloud, and now hybrid everywhere, as I say, um, how does that all work it out? >>We're super excited about our cloud first initiative, and I think it fits it, um, really, uh, perfectly it's it's, it's what we needed. It's, it's, it's a, it's another accelerant. Um, if you think of first, what we're doing is we're, we're putting together, um, a capability set that will help enable him to and translations as Brian touched on your help companies move, you know, from just, you know, migrating to, to, to modernizing, to driving insights, to bringing in change, um, and, and, and helping on that, on that talent. So that's sort of component number one is how does Accenture bring the best, uh, end to end transformation capabilities to our clients? Number two is perhaps, you know, how do we, um, uh, bring together pre-assembled as Brian touched on preassembled industry offerings to help as an accelerant, uh, for our, for our customers three, as, as we touched on earlier, is, is that sort of partnership with the ecosystem. >>We're going to see an increasing number of SAS providers in an estate in the enterprises States out there. And so, you know, parts of our cloud first and our AEG strategy is to increase our touchpoints and our integrations and our solutions and our offerings where the ecosystem partners out there, the ISV partners out there, and the SAS providers out there. And then number four is really about, you know, how do we, um, extend the definition of the cloud? I think oftentimes people thought of the cloud just as sort of on-prem and prem. Um, but, but as Andy touched on earlier this week, you know, you've, you've got this, the concept of hybrid cloud and that in itself, um, uh, is, is, is, uh, you know, being redefined as well, you know, where you've got the intelligent edge and you've got various forms of the edge. Um, so that's the fourth part of, of our, of our cloud first strategy. And, and, and for us was super excited because all of that is highly relevant for ABG, as we look to build those capabilities as industry solutions and others, and as we look to enable our customers, but also how we, you know, as we, as we look to extend how we go to market, uh, I joined tally PS, uh, in, uh, in our respective skews and products. >>Well, what's clear now is that people now realize that if you contain that complexity, the upside is massive. And that's great opportunity for you guys. We got to get to the final question for you guys to weigh in on, as we wrap up next five years, Brian, Andy weigh in, how do you see that playing out? What do you see this exciting, um, for the partnership and the cloud first cloud, everywhere cloud opportunities share some perspective. >>Yeah, I, I, they, you know, just kinda building on that cloud first, right? What cloud first. And we were super excited when cloud first was announced and you know, what it signals to the market and what we're seeing in our customers, which is cloud really permeates everything that we're doing now. Um, and, and so all aspects of the business will get infused with cloud in some ways, you know, it, it touches on all pieces. And I think what we're going to see is just a continued acceleration and getting much more efficient about pulling together the disparate, what had been disparate pieces of these transformations, and then using automation using machine learning to go faster. Right? And so, as we start thinking about the stack, right, well, we're going to get, I know we are, as a partnership is we're already investing there and getting better and more efficient every day as the migration pieces and the moving assets, the cloud are just going to continue to get more automated, more efficient, and those will become the economic engines that allow us to fund the differentiated, innovative app activities up the stack. >>So I'm excited to see us, you know, kind of invest to make those, those, um, those bits accelerated for customers so that we can free up capital and resources to invest where it's going to drive the most outcome for their end customers. Um, and I think that's going to be a big focus and that's going to have the industry, um, you know, focus. It's going to be making sure that we can consume the latest and greatest of AWS has capabilities and, you know, in the areas of machine learning and analytics, but then Andy's also touched on it bringing in ecosystem partners, right? I mean, one of the most exciting wins we had this year, and this year of COVID is looking at the universe, uh, looking at Massachusetts, the COVID track and trace solution that we put in place is a partnership between Accenture, AWS, and Salesforce, right? So again, bringing together three really leading partners who can deliver value for our customers. I think we're going to see a lot more of that. As customers look to partnerships like this, to help them figure out how to bring together the best of the ecosystem to drive solutions. So I think we're going to see more of that as well. >>All right, Andy final word, your take >>Of innovation is, is picking up. Um, the split things are just going faster and faster. I'm just super excited and looking forward to the next five years as, as you know, the technology invention, um, comes out and continues to sort of set new standards from AWS. Um, and as we, as Accenture bringing our industry capabilities, we marry the two, we, we go and help our customers super exciting times. >>Well, congratulations on the partnership. I want to say thank you to you guys, because I've reported a few times some stories around real successes around this COVID pandemic that you guys worked together on with Amazon that really changed people's lives. Uh, so congratulations on that too as well. I want to call that out. Thanks for coming >>Up. Thank you. Thanks for coming on. >>Okay. This is the cubes coverage, Accenture AWS partnership, part of the center's executive summit at Avis reinvent 2020. I'm John for your host. Thanks for watching.

>>from Santa Clara, California. In the heart of Silicon Valley, it's the queue covering altitude 2020. Brought to you by aviatrix. >>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 Informatica Stacy Linear from terror data. And Jennifer read with Victor Davis to the stage. >>So we're gonna show you a jacket. Yeah, I get it. >>I was just gonna I was just gonna really rib you guys. See? Where's your jackets? And Jen's got the jacket on. Okay. >>Good. Love. The aviators. Aces, Pilot gear. They're above the clouds. Storage to new heights. So guys, aviatrix pace is love the name. I think it's great. Certified. This is all about getting things engineered. So that level of certification I want to get into that. But first take us through the day in the life on a SAS. And just to point out, Stacy's a squad leader. So he's He's like Squadron leader, quadrant leader, quadrant leader. So it's got a bunch of pieces underneath him, but share your perspective day in the life. 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 U. S. 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 critical gaps that we found is people having the networking background. Because there you graduate from college and you have a lot of computer science background. You can program. We've got python, but now working and packets they just don't get. And so just taking them through all of the processes that it's really necessary to understand when you're troubleshooting is really critical. And, um, because you're going to get an issue where you need to figure out where, exactly is that happening on the network, you know, is by my issue just in a vpc is on the instant side is a security group or is it going on prim? And is this something actually embedded within Amazon itself? I mean, I trouble shot an issue for about six months going back and forth with Amazon, and it was the VW 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 OK, it's fixed and actually actually help 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, but 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 >>just so he just write some software that takes care of itself, but we'll come back to that. I want to come back to that problem solve with Amazon, but I think the only thing I have to >>add to that is that it's always the network as long as I've been in. Networking has always been the network's fault. If you're in the I'm even to this day, you know, still, networks 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 100 different things. Make that >>And now you got a full stack. Dev Ops, you know, a lot more time. Another 100 times are changing your squadron leader. I get that right. What is? What is the squadron leader first? Could you describe what it is? I think probably just leading off with network components of it. But they from my perspective when you think about what you asked them was it's about no issues and the escalations off my days like that. That's a good outcome. That's a good day. Is a good day's a good day for you. Mention the Amazon. 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 point against that guy's problem that girls problems. So what? How do you solve that? And how do you get the young guns up to speed? Is there training is that this with a certification comes in, >>whatever the certification is really going to come in I know when we, uh, we got together at reinvent one of the questions that that we had with with Steven 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 was like, No, no, no, no, that's going a little too high. We need to get really low because the better someone can get 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, you know, because everything is abstracted in Amazon and a Net and Azure and Google, it's abstracted in there. These virtual gateways they have VPN is that you just don't have the logs on is 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 I built it, you know, and there's like each one of those little things that well, if they 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 the teaching them how to read act. Even >>so, we were talking before we came on up on stage about your career. You've been networking all your time, and then, you know, you're no 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 talk about, You know, it's never fall. I walk in bare feet in the snow when I was your age, 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 network is in high school level now where I didn't learn that until 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 submit, and they don't understand why you can break it down. Smaller. What? 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 helps. But when you got into networking, how what was it like that? And compare it now? Almost like we heard earlier. Static versus Dynamic. Don't be static. And then you just set the network. You got a perimeter? >>Yeah. No, there was no such thing. Yeah, no. So, back in the day, I mean, yeah, I mean, we had banyan vines for email, 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. And I got a great polish this thing and actually shoot like to see if it works. I mean, that was the network crypt. Five cat, five cables to run an Ethernet, you know? And then from that to set 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. It was a software product manager for a while, So I've gone all the way up the stack. And then, ah, two and 1/2 3 years ago, I came across, too, to work with NTT 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 >>dio. And then with this with program ability is 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 certifications? >>I think some of the importance is that its 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 solve it in a general. That's true in Multi Cloud as well. You can't learn how cloud networking works without understanding how AWS and Measure and GC P r. 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 outside of the business issues. What does it mean to do? That code is that networking is the configurations that aviatrix what is the state matrix is a certification, but what is it about the multi cloud that makes it multi networking and multi vendor? But the >>easy answer is yes, >>yes, it's >>all got to be a general. Let's get your hands and you have to be >>right. And it takes experience because it's every every cloud vendor has their own certification. Um, whether that stops and, um, advanced networking and events, 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 in 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 OK 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, 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 and seeing it and going through it. And >>I have a question. So, you know, I just see it. We started this program maybe six months ago. We're seeing a huge amount of interest. I mean, where oversubscribed on all the training sessions, we've got people flying from around the country, even with Corona virus flying to go to Seattle to go to these events were over >>subscribed. Good is that originally they would put their Yeah. Is >>that something that you see in your organizations? Are you recommending that two 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. Is there really isn't anything like that? Is that something you guys could comment on? That do you see the same things in your organization I see from >>my side Because we operate in a multi cloud environments that really helps. It's beneficial. Yeah, >>I think I would add that, um, 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. I p addresses are I know how the network works and a couple little check marks. Our little letters by your 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 and enough of the understandings that you have the tools necessary, >>right? So I guess my final question for you guys is why and a certification is relevant. And then second part is share with Livestream folks who aren't yet a certified or might want to jump in to be aviator certified engineers. Why is it important? So why is it relevant? And why should someone want to be a certified engineer? >>I think my V is a little different. I think certification comes from proving that you have the knowledge not proving that you get a certification to get. I mean, they're backwards. So when you've got the training and the understanding in 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 >>that. So that who is the right person that look at this and saying I'm qualified is a network engineer. Is that a Dev ops person? What your view? 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 develop some security lots and lots of security. Because network is so involved in so many of them, that's just the next progression. >>You want to add something there, I would say expand that to more automation engineers because we have those now, so I'm probably extended >>Well, I think the training classes themselves are helpful, especially the entry level ones for people who maybe quote unquote cloud architects. But I've never done anything in networking for them to understand why we need those things to really work, Whether or not they go through it. Eventually get a certification is something different. But I really think fundamentally understanding how these things work. It makes them a better architect. Make 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 have tradition down on Prem networking. They can understand how that's gonna work in the cloud. >>I know we've got just under 30 seconds left. I want to get one more question than just one more for the folks watching that are maybe younger than I don't have. The networking training from your experience is, 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 and why they should go with the deeper and networking space we'll start with. You know, I would say it's probably fundamental right after delivery 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, um, is a fundamental change is something that starts from the base and work your way up. >>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 built something and your overlapping eyepiece space. Not that that doesn't happen. But how can I actually make that still operate without having to re? I re platform? It's like those challenges, like those younger developers or Cisco engineers can really start to get their hands around and understand those complexities and bring that forward in their careers. >>And, you know, the pipes are working plumbing. >>That's right. >>And they know how it works. How to code it. >>That's right. >>Awesome. Thank you, guys for great insights. Ace certified engineers, also known as aces, give a round of applause. >>Yeah, Yeah, that's great. Thank you. Okay, alright, that >>concludes my portion. Thank you, Steve. Thanks for having >>on. Thank you very much. That was fantastic. Everybody >>running with John Furrier. Yeah. So Great event. Great event. I'm >>not gonna take along with that. We got lunch outside for the people here. Just a couple of things. I just called action, right? So we saw the aces. You know, for those of you out of the stream here, become a certified. It's great for your career. Is great for not knowledge is is fantastic. It's not just an aviatrix thing. It's going to teach you about cloud networking, multi cloud networking with a little bit of aviatrix, exactly what the Cisco CC IE program was for I p Network. That type of the thing that's number one second thing is, is is learn, right? So there's a There's a link up there for the for to join the community, get like I started this. This is a community. This is the kickoff to this community, and it's a movement. So go to what may be community dot IBM dot com. Starting a community of multi cloud. So you get trained learn. I'd say the next thing is we're doing over 100 seminars in 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 you know, on the live stream 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 is 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 gnome or and schedule get with us and schedule a multi our architecture workshop sessions. So we 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, compute storage, everything and everything you've heard. Today. Every panel kept talking about architecture, talking about operations. Those are the types of things that we saw. We help. You could 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 our network architecture, and they put it on the whiteboard that's what we and that's the most valuable thing they get from us. So this becomes there 20 year network architecture, drawing that. They don't do anything without talking 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 waas and join the movement. And for those of you here, join us for lunch and thank you very much. >>Yeah, >>yeah, yeah.

(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

absolutely build on some of Ben's comments because I think what he articulated is one of the killer use cases of VMware cloud on a to us that I think is driving that momentum right which is we think it's one of the best solutions in the marketplace and customers have told us this to enable them to migrate and modernize right so let's talk about the migrate piece first right you have customers that have these tremendous enterprise class applications running on vSphere and their data centers they're built on top of that platform they depend upon it for performance availability everything else with VMware Club a native us we can migrate those applications with zero downtime no refactoring no additional cost in a matter of weeks or months as opposed to if you had to refactor everything to take years and millions of dollars right so that cloud migration use case I would say is that is the killer for us and that's you know exactly what Ben was we're definitely seeing that and I think that's the thing that really got me excited about a year ago was watching enterprises make that transition and say you know what the center of gravity has gone from architectures inside the on-prem data center is now moved to in the cloud I mean that shift has happened it happened to people talked about it five years ago but they didn't mean it and now when you talk to enterprises they are actually moving into the cloud not just talking about it and they're saying where that is the center of gravity and what's interesting to me was I think even just the tone of Andy Jesse today and what he was talking about was it's once you define what your architecture is you push it everywhere so cloud 1.0 and 2.0 was really more about taking my architecture that was on prem and pushing it into the cloud so let me take virtual appliance a virtual router basically my hardware router packaged it up put it on the cloud that's not cloud native it's cloud naive as we talk right and so what's the chase has happened is now everybody realizes the center of gravity is in the cloud and you start seeing things like outposts you see things like wavelength you see things like you know tgw network manager things getting pushed out the architecture of the cloud now actually pushing out and extending out into on-premises I've been at it for a couple of decades so in the beginning there was a lot of evangelism that this is safe it's consumable by the enterprise it's not some kind of crazy idea to bring open-source you're not going to lose your intellectual property or things like that those days I mean I I'm sure you can find an exception but those days are largely over in this in the sense that open-source has gone mainstream so I would say open-source is one most large enterprises have an open-source strategy they consider open source as critical to not only how they source software from vendors but also how they build their own applications so the world has really really evolved and now it's really a question of where are you partnering with vendors to build infrastructure that's critical to your business but not your differentiator and where are you leveraging open-source internally for your to differentiate your business I think that's a more sophisticated view it's not the safety question it's not is it is it legally you know that you're bringing legal concerns into the picture it's really a much different conversation and people in the enterprise are looking how can we contribute to these projects so that's really it's pretty exciting actually both are a great place for startups right they're not meters cluesive so I think if you go horizontal the amount of data being created by your applications your infrastructure your sensors time series data ridiculously large amount right and that's not going away anytime soon I recent did investment ain't chronosphere did you guys covered over at coupon a few weeks ago that's talking about metrics and absorbedly data time series data so they're gonna handle that horizontal amount of data petabytes and petabytes how can it query this quickly deeply with a lot of insight that's one play right cheaper better faster at scale the next play like you said is vertical it's how do I own data or slice the data the more contacts they know as can have we talked about like the virtual cycle of data right this the system of the tile well bye own set of da to be healthcare government or self-driving car data that no one else has I can build a solution and to end and go deep and so either pick a lane or pick a geography you can go either way it's hard to do both though it's hard for start-up any big company it's very few companies can do two things well starves especially succeed by doing one thing very well I'm impressed they got two CEOs the CEO of goldman sachs david solomon the CEO of Cerner coming to the show that's kind of rare that the CEO of your customer comes to the show I guess the second thing I'd say is you know Amazon is not a rinse and repeat company at these shows although they are when it comes to shock and awe so they ticked the Box on shock and awe but you're right John they're talking a lot about transformation I would sort of think of it as a disruption here's what I would say to that Amazon has a dual disruption agenda one is its disrupting the horizontal technology stack and two it's disrupting industries it wants to be the platform of which startups in particular but also incumbents can disrupt industries and it's in their DNA because it's in Amazon's DNA and I think it's the last thing I'll say as Amazon is the retai Amazon retail is the you can buy anything here store and now to your point Justin Amazon Web Services is you can get AWS anywhere at the edge and a little mini data centers that they're built on outpost and of course in the cloud absolutely you know I'd say primarily were most kind of pleased with the variety of workloads and these cases the customers are bringing us into you know I think when we started out on this journey we saw a tremendous promise for the technology to really improve the aw psycho system and customer experience for people that wanted to consume block storage in the cloud what we learned as we started working with customers is that because of the way we've architected the product brought a lot of the same capabilities we deliver on our flash arrays today into AWS it's a lot of customers to take us into all the same types of workloads that they put flush arrays into right so that's their Tier one you know mission-critical environments there VMware workloads their Oracle workloads or safety workloads they're also looking at us from everything from you know to do lifts and shifts test and dev in the cloud as well as dr right and and that again i think you know speaks to a couple things it speaks to the durability the higher level of service that were able to deliver in AWS but also the compatibility with which we're able to deliver the same sets of features and you know have it operate in exactly the same way on prime in the cloud because it's look if you're gonna dr the last time you know the last point in time you want to discover that there's a caveat hey this feature doesn't quite work the way you expect is when you have a dr failover and so the fact that we set out with this mission in mind to create that exact level of sameness you know it's really paying dividends in the types of use cases the customers are bringing us into I think we're delighted you know Mike obviously and I've been friends for years he's had some connections with VMware in his past that that that certainly helped in setting up this partnership so we're grateful to Mike and Andy and the team for that and it's you know two and a half to three years now since we announced it tremendous amount of customer interest listen you know we said at the beginning of this when you take sort of the king of the public cloud and the king the private cloud together and don't force customers to say these have to be separate doors you can do them both together customers like that message and what we've been really doing over the course the last 12 18 months is perfecting use cases for this platform I think to us the key word is migrations cloud migrations when people are moving their workloads of an app off vmware vsphere or our cloud foundation we want this to be the best place for it to land we are more cloud and AWS for migration opportunity and anything short of that refactoring app would be you know not something that would be a good use of people's time and money because they should be then modernizing with all the wonderful services that Amazon's built once they've migrated so we've really perfected our message in the course the last six 12 months to two ms migrated and modernized migrated modernized so we could migrate you into this avenue and then modernized with a set of container and other services so that mess is working we put on stage at VMware and there are many of them here too big Amazon customers VMware cloud and Amazon Freddie Mac and IHS market and they were telling are tens of thousands customers at those shows and similarly many of them here that that's the best option to be able to do things yeah so if you know public sector public sector actually has a lot of Windows or Microsoft workloads in it and so we're seeing a lot of public sector customers looking to modernize their Windows workloads in fact we made several announcements just yesterday around helping more public sector customers modernize for example one is Windows Server 2003 and 2008 will go out of support and so we have a great new offering with technology that can help them to not refactor but actually abstract those layers and move quickly to 2016 and 2019 because both of those will go out of support in January and Dave mentioned you know cloud first strategies but we're also seeing a lot of movement around data you know data is really powerful Andy mentioned this as well yesterday but for example in our partner keynote where I just came from we had on stage Avis yeah hey this not public sector customer but what they're doing is the the gentleman said you know your car can now talk to you and that data is now being given to local state officials local city officials they can use it for emergency response systems so that public and private use of data coming together is also a big trend that we're seeing it's all about breaking down I mean if devops is all about breaking down silos between Devon operations and in other parts of the business Deb sack ops or secure dev ops or whatever we want to call it is just bringing more people into the fold and helping security join that party and get at things earlier in the cycle so we can catch it before it you know before before there's a breach that's in the news so you know I think there's going to continue to be convergence between Amazon business in AWS over time and in the marketplace we offer kind of a goods marketplace they offer a software marketplace and a services marketplace and so I think we're still working on how do we harmonize that experience better and we've got a lot of work to do there we have a saying at Amazon that it's always day one and that's a great example where we still have a lot of work to do but one of the things that is another one of our partners Koopa which is a procure-to-pay a platform and a longtime Amazon business partner we've done some pretty creative things to improve the user experience and make it easier for customers use both Koopa and Amazon business and in concert together Koopa announced a couple months ago they've built an integration to the AWS marketplace and so that's a pretty exciting opportunity where people who are provisioning services via AWS be a Dobis marketplace can have that that transaction flows seamlessly into their prepare to pay solution and let you know the user who's provisioning that focus on what they want to do which is developing new solutions to serve customers I mean the spectrum is massive so the our biggest challenge is keeping up with everything and continuing to innovate with all the things that are happening but again the benefits of the platform that we have enables us to do that and the enhancements we weight made this year this year now that our platform is is more open we can connect a collect data from multiple entities not just the New Relic agents that we've that we were built on so the concept of observability and being able to observe the entire application environment it is built on the fact that data's got to come from all these different places then we need to turn that around and curate it into the right experience in the right use case that the customer is looking for so all I can say is that our company's built on innovation we try and stay on the cutting edge of all that trying to stay current with that and meet the customers needs as as everyone here is innovating like crazy at scale well I mean there's a lot of a lot of the technology we build comes from things that we're doing ourselves you know and that we're learning ourselves it's kind of how we started thinking about microservices serverless - we saw the need we know we would have we would build all these functions that when some kind of object came into an object store we would spin up compute all those tasks would take like three or four hundred milliseconds then we spin it back down and yet we'd have to keep a cluster up in multiple availability zones because we needed that fault tolerance and it was we just said this is wasteful and that's part of how we came up with lambda and you know when we were thinking about land that people understandably said well if we build lambda and we build this serverless event-driven computing a lot of people were keeping clusters of instances aren't going to use them anymore it's going to lead to less absolute revenue for us but we we have learned this lesson over the last 20 years at Amazon which is if it's something it's good for customers you're much better off cannibalizing yourself and doing the right thing for customers and being part of shaping something and I think if you look at the history of technology you always build things and people say well that's going to cannibalize this and people are gonna spend less money what really ends up happening is they spend spend less money per unit of compute but it allows them to do so much more that they ultimately long-term end up being you know more significant customer look I mean the the SHA this show estate Volante says amazon always delivers with the shock and awe you know broadest and deepest so many pieces here you know I took a selfie with many people and the biggest celebrity of the show AWS outpost the rack it's over in the corner there and people asking me about all the gear inside I said you should stop asking about that because you will never touch it only AWS will so put a curtain around it it's managed as a service and that's what I think people are still trying to understand we've been talking about cloud for what 15 years now but Amazon's positioning on cloud is still different than everyone else's when I think back to some of the waves there's that buzzword and there's one or two that really architectural er different in deliver and Amazon laid out their strategy even more and through the geeky pieces and transformation was the theme you [Music]

(upbeat music) >> Hi, and welcome to theCUBE, the leading source for insights into the world of technology and innovation. I'm your host Donald Klein, and today's topic is the market for autonomous vehicles and the ecosystem suppliers looking to tap into this brave new world of autonomous capabilities in our daily commute. To have this conversation I'm joined by Rudy Burger, managing partner at Woodside Capital. Rudy, welcome to the show. >> Thanks Don, it's great to be here. >> Great, so look, why don't we start off Rudy, why don't you tell us a little bit about Woodside Capital and your role there? >> Great, so I founded Woodside Capital about 20 years ago having started five different companies of my own, one of which I took public. We are a specialist M&A advisor. We work with so-called growth stage often venture-backed companies and help them find buyers that are usually much larger public companies. Our clients are usually US or European companies and we find buyers in the US, Europe, or Asia. >> Excellent, excellent, okay. And why don't you talk a little bit about your kind of specialty areas? >> So I focused my career, and certainly the work at Woodside Capital, on imaging technologies and as an enabling technology, and the products and markets that are enabled by imaging and increasingly computer vision. So nowadays that is autonomous vehicles, consumer technology, security surveillance, and digital health. So enabling technologies, the computer vision is the theme that binds those together. >> Okay, well, the thing that's on everybody's mind these days is autonomous vehicles, when are we going to get them? Very high profile for sure. Before the show we talking about the kind of two key ingredients to making this happen, the AI software which is kind of the brains of the operation and then also the sensors which enable all of the AI. So why don't we talk about the sensor world first, okay? Lot of discussion about there, so sort of does the brave new world of vehicles need lidar? Does it not need lidar? Are there other types of sensors coming along? What's your sense of that market and how it's looking for all of the different players in it? >> So, Don, I look at it from a sort of fairly basic standpoint. Humans have two very capable image sensors and a very powerful processor, and the degree to which the automotive manufacturers and so-called Robo-Taxi developers have decided it's necessary to sprinkle every sensor known to man, and I'm talking lidar, radar, ultrasound, thermal, and of course cameras, is to some extent a degree to which, you know, image sensors are not as good as our eyes today. Now, there are some areas in which we will probably always have technology as a help. For example, humans are not very good at seeing in the dark whereas a thermal technology can do that very well. But my overall belief is that it's never a good idea to bet against an incumbent technology, and in this case I'm talking about so-called CMOS image sensors which are the sensor that goes into pretty much every camera in the world now. It's never a good idea to bet against the incumbent technology being able to scale into a new market. Every time people have done that, they've been wrong. Back in the early days the debate was whether CMOS image sensors would ever be good enough to replace CCDs as the sensor technology, and of course now, you know, everything uses CMOS image sensors. In other markets there was a long period of time in which people were thinking that LCD panels would never be large enough to replace, you know, for television, for example, 50 inch and so forth. It was never going to happen, so we needed plasma TVs, we needed rear-projection TVs. But slowly but surely the incumbent technology, LCDs, expanded to that market. So my belief is that CMOS image sensors will evolve to a point at which they will replace the need for lidar in most applications. >> Interesting, so that's a very controversial statement, right? Because you've certainly seen a lot of emphasis on the development of new generation lidar capability. >> Over 100 lidar companies started over the last three, four years, and of course many of them will not be happy to hear me say that. There are two distinct markets and one is the so-called Robo-Taxi market, and the other is more of the consumer vehicle ADAS market, and I think we need to think about those separately because the economics behind both are very different. If you look at the Robo-Taxi market, those vehicles tend to be much more expensive and are relatively price-insensitive. So if they can improve safety a little bit by putting a lidar on there, you know, great, let's do it, multiple lidars because these vehicles will be in operation 24 by seven, and if each vehicle costs 200,000, $250,000, fine. When we talk about the mass market for automobiles, type of car that you and I might go down and buy, very different thing. And, you know, auto makers sweat the pennies, and so putting a one or $200 lidar in a vehicle, big decision. And to the extent that they can replace the need for that lidar with a much less expensive camera system, that's what they'll do. Bear in mind that Mobileye, which has been the biggest success story, acquired by Intel for $13.5 billion, second largest acquisition Intel ever made, they for the most part still run on one camera, forward-looking camera. That's it, no radar, no lidar, no thermal, one camera. So the clever use of image processing, computer vision, and one image sensor can do a great deal. >> Interesting, okay. Well, so I want to talk about the software in just a second, but just to kind of finish this point, so if you were advising a sensor company that's developing some next gen capabilities, whether lidar or other related technologies, is the point you're making here that there are certain segments of this industry which are going to be more attractive to your technology than others? >> Absolutely, yes. I mean, the first thing to recognize is that the automotive industry has never really been a particularly comfortable fit with the economics and timeline of venture capital. VCs need to invest and recoup and redeploy back to their LPs on an eight-year cycle. But the automotive industry moves quite slowly, perhaps Tesla are excepted, and what the first piece of advice I would give these companies is it's probably going to be three, four, five years before, even if you have the right technology, before that technology really starts generating any significant volume and revenue. So for many venture-backed companies, that's too long. So the first piece of advice is find pockets of revenue, right, beachheads if you will, where you can land your technology and start generating revenue before you get to the automotive market. And many of these lidar companies we just talked about are not going to last long enough to get to the automotive market because not only does the automotive market move slowly but the autonomous vehicle market keeps on getting pushed out to the right as the industry realizes that this is a big, hairy problem. And so I would say, what is it that your technology can do an order of magnitude better than any other technology? Focus on that and find some opportunities for revenue outside the automotive industry that will sustain the company on its way to the holy grail. >> Interesting, yeah, so find that alternative revenue source to get you to base camp, and then when the market's ready, climb that Everest to-- >> I've seen so many companies basically go out of business because they've set their sights on either the automotive market, and it's go for broke. We're not interested in, all these other things are distractions. You know, entrepreneurs don't have a plan B. Or this. We're going to get our technology into a smartphone, that's it. And there are possibly some other opportunities but it takes so long and it's so difficult to get your technology into a smartphone that they go out of business before they ever get to that point. >> Interesting, okay. So good advice for people looking to kind of apply their technology in this kind of a very difficult market, right, very complicated market. All right, well, then let's switch to the other side of it. So we were kind of talking about the key ingredients, right? Sensors but also AI and the software around that, okay, and there are some very big players developing the software. Tesla's had their Autonomy Day where they've showcased their technology. You've obviously got Google with their capabilities developing software. How do you make sense of this overall landscape because we do see a lot of smaller providers also trying to develop software here. >> So the first thing that I find fascinating about the automotive industry is that for the most part there is no software market. There's perhaps one exception of any scale, that's BlackBerry that sells the QNX software. They found a point within the entertainment console where they can license their software. But for all of the development and capital invested into automotive software, nobody is actually generating revenue, making a living, by licensing software. And one of the main reasons for that is that, you know, the automotive market, really since inception, has been a hardware business. This is a business of bending sheet metal, internal combustion engines, and software has really not played that big a role up until relatively recently. So even those companies that do have software technology have ended up selling it into the automotive supply chain as a piece of silicon, embedded on a piece of silicon, not as, you know, here's my software on a USB stick, right? I think that the whole software licensing model hasn't so far fit well, fit comfortably, with the automotive industry. And the other reason is that there's no standard platform. If I were to develop a piece of software, I can, in the PC industry, I can develop for Windows, I can develop for Mac, I can develop for an iPhone. There's no such thing in the automotive industry, and particularly in this new world of autonomous vehicles there is no standard platform. There are many different processors, Nvidia has staked an early claim there. And the reason that most of the companies developing autonomous vehicle technology have developed the so-called full-stack solution, everything from code running on the processor, integrated through the sensors and so forth, is for that reason, there is no standard platform. So each company has developed the whole solution for themselves, and there are many of them around here that have raised hundreds of millions of dollars, some cases billions of dollars, for that purpose. So there is, today, no software market for automotive in the same way that we think about it in other industries. >> Understood, understood. But in terms of the companies that are actually pushing the envelope on these kind of capabilities, right, so we're taking the best of AI, we're applying it to big data sets, and then hopefully being able to extract that to create capabilities for these vehicles, right? What's your sense of how far that's come along in-- >> Well, it's come a long way but, here I'm going to push the boat out a little bit. I don't believe that the so-called deep learning technology, which is the current state of the art for AI, it's the technology that has allowed computers to beat humans at chess, at Go, I don't think that that flavor of AI, that approach to AI, is ever going to get us to safe enough autonomous vehicles. And that's because it works extremely well in fairly well-bounded rules, rule-bounded games or any scenario like that, but can you imagine trying to teach your 16-year-old how to drive by showing them images of every situation that they might encounter, right? Impossible. It's an infinite, it's not a well-bounded set. And that's so difficult because we really haven't developed the technology to allow computers to learn, to have things like common sense, to infer, you know, well, this happened, so this is likely to happen. So I think we are going to need a whole new breakthrough in AI before we get to what is generally considered safe enough vehicles. >> Interesting, well then, maybe if we kind of apply your previous thought about sort of Robo-Taxis as maybe being the segment where you're going to see the most use of these newer sensor technologies. >> Rudy: Near term, yes. >> Exactly, what about maybe, is that sort of the same rules apply there for maybe the AI providers, that they're-- >> I think so and that's why they're all focused on that. I mean, from Uber to Waymo, they've all made the same calculation which is if you're running a fleet of vehicles, and so for example in Uber's case, the driver takes 80% of the fare and only 20% goes back to Uber, but if you can replace the driver with a computer, you can keep that vehicle on the road 24 by seven and you can keep 100% of the revenue. You don't need to pay the computer. So that's the calculus that they're all going through. But I think that many of them are making a fundamental mistake and I predicted recently that I think Uber, my prediction for 2020 is that Uber is going to divest its autonomous vehicle business and get back to the business that it should be focused on. Uber generates about $14 billion a year in gross revenue, so 20% of that, which is the piece that Uber keeps after the drivers take their 80, is what, 2.8 billion. Uber should be able to be an extremely profitable business on 2.8 billion of net revenue, but they're spending a huge chunk of money every year on R&D. Now, I would argue that Hertz and Avis have successful businesses. They're in the service, they're in the transportation business, but they didn't decide that they had to build their own cars in order to be in that business. My view, personal view, is that what Uber should be doing is saying, that's not our business, right? We are the world's best at managing this sort of peer-to-peer network crowdsourced transportation, if you will. And when some company, some Silicon Valley startup, comes out with safe enough technology, great, we'll use it, but we don't have to develop that ourselves. >> Well then, maybe just to play devil's advocate here for a second, what about it's a Robo-Taxi-type technologies being applied in bounded areas within metropolitan areas where the rules-- >> That's where it will start. >> Could be more-- >> I think that's where it will start, but I think part of the problem is that we have, perhaps in part due to all of the media hype around autonomous vehicles, we've been misdirected to thinking about autonomous vehicles as a replacement for the car we drive to work every day and I think that's the wrong way to think about it. I think that autonomous vehicles are going to show up in the market as an extension of public transportation. Right, you know, I get off the train and there's an autonomous vehicle waiting to take me for the last couple of miles to my office. >> And those last couple of miles would be sort of a regulated space. >> Rudy: May well be. >> Where the AI is more than capable of functioning. >> Right, and that, you know, yes. And so it's better to think about autonomous vehicles as not being a revolutionary technology but much more of an evolutionary technology. And in fact, most of these technologies are showing up in so-called ADAS technologies which are designed to make driving your regular car safer, lane assist, keeping you a safe distance. >> Donald: Maybe just explain that word, ADAS, and what that means. >> So ADAS stands for automated driver-assistance systems. So one of the first was cruise control, right, everybody's familiar with cruise control. And so to some extent ADAS is just building on cruise control. In addition to maintaining a constant speed, you can now stay in the lane. In addition to maintaining a constant speed, it will now automatically slow down if you get too close to the car in front. And so you can see ADAS as, you know, collision avoidance and so forth, not full autonomy, still have to have a driver in the driver's seat, but evolving year by year until one year we wake up and, yep, my car will actually drive me all the way from home to work without me intervening. Right, it's going to happen in that way. >> So incremental improvements. >> Incremental improvement. >> To ADAS as opposed to kind of revolution of autonomy. >> An overnight sensation. >> Yeah, right, coming from nowhere. Okay, understood. Well then, let's pivot from that then, okay. So let's talk about the automotive industry as a whole and sort of your thoughts on how this is all going to play out. >> Yeah, so there are some very interesting dynamics playing out in the automotive industry. Firstly, as good news, as a result of all of this money and innovation in the automotive industry, Detroit's actually coming back. I go there once or twice a year and you can feel the economy coming back in Detroit, but it's not going to come back around, you know, bending sheet metal. And the challenge that the automotive companies have is so much of their infrastructure and expertise has been built on construction, building a car, production lines to bend the metal, install the engine, and the internal combustion engine itself. And by complete coincidence, to some extent, we've got this confluence of all of these autonomous technologies and electric vehicles happening at the same time. Electric vehicles are much easier to make than internal combustion engines. Far fewer parts. It's one of the reasons that China has spun up about 20 different electric vehicle companies recently. So I think that long term, my prediction is that the automobile industry will go the same way that the personal computer industry went. When the PC first, you know, it was born by IBM, or Apple in some sense before that. There were dozens of companies producing different PCs and it was very much, they were expensive products, and, you know, relatively unusual. As the industry matured, the supply chains matured, and it became apparent there were really only two companies that were making a lot of money out of the PC industry. The companies that developed the software, operating system, and the companies that developed the processor, and all of the manufacturing went over to, in the PC's case, in Taiwan, right? And I think that exactly the same thing is going to happen with the automotive industry. Tesla today still actually makes cars, but I don't see them long term being in the car business because they're really a technology company. It's the reason I don't think Apple is ever going to get into the car industry. They make fantastic margins selling computer products. The gross margin selling a car, it's miserable. It can be single digits or teens. That would completely tank Apple's blended gross margin. So my prediction for the industry is there will be a few small pockets of very profitable businesses, particularly around the operating system, by which I mean the intelligence or the AI intelligence, and then the processor, whether it's a Qualcomm processor or a Nvidia processor or an Intel processor. And as with the PC industry, most of the profit will go there and most of the manufacturing will end up getting outsourced because that's not the value-add, you know, bending metal and so forth. >> Interesting, well, so in the kind of compute market today, right, we have this notion of sort of cloud-native, right, okay, and that many of the companies that are developing apps as relying on cloud-native infrastructure have a kind of technology lead that's going to be hard for some of the legacy providers to actually catch up on. Now, other people say that that's not necessarily the case and et cetera, right? Can you make the same argument for the electric car market, that some of the electric-natives might have a kind of sustainable advantage here? >> I should've added, today the cloud infrastructure companies, cloud services, SaaS companies, in the PC world, you know, very profitable, and I can see a similar cloud services model developing for the automotive industry. However, other than Tesla, it's very difficult to change the automotive channel to support that. I'll give you one example. Everyone that owns a Tesla is very used to the idea that, sometimes on a daily basis, a new bunch of software, operating system software, is downloaded overnight to your vehicle. You wake up in the morning and some new feature's been turned on, right? Tesla can do that because they bypass the entire dealership channel that has a complete lock on the rest of the industry. So for example, if GM wants to do the same thing as Tesla and do sort of what's called over-the-air, OTA, updates, software updates, they can't do that because their contract with the dealership network states that if there is service to be done on the vehicle, the vehicle has to be brought back to the dealership, and the dealerships consider updating the software on the vehicle as service. So their contract with the dealers actually prevent them from doing something that basic. So it's not just a technology issue. The whole channel and way vehicles get sold is going to have to change. >> Interesting, so that's the advantage that some of the new generation of vehicle manufacturers-- >> I would say that Tesla has a five year lead, technology lead, because they, like Apple, are vertically integrated. They're doing everything from user interface, fit and function, all the way down to the semiconductor. They're developing their own semiconductors now. So they have become a fearsome competitor in the electronic vehicle space because they've been doing it for longer than the other major auto companies. They've figured out a lot of the, you know, tricks and techniques of how to extend mileage and so forth. And so they have a substantial lead in the industry at this point, despite the fact that over the next 12, 18 months, every automotive company is going to be coming out with their own flavor of electronic vehicle. >> So then it's more than just about having electric drivetrains, et cetera, right? It's about the whole suite of capabilities. >> It's a systems engineering challenge. >> Interesting, okay. All right, well Rudy, we're going to have to leave it there, okay, but I think everything you've told us is, it sounds like some good news for some of the Tesla stock holders at the moment. >> I think so. >> Okay, well. (laughs) We'll pass on making an opinion about that, but great conversation, thank you for your insights. Okay, this is Donald Klein, host of theCUBE, here with Rudy Burger, managing partner at Woodside Capital. >> Rudy: Great, thank you, Don. (upbeat music)

(upbeat music) >> Hi, and welcome to theCUBE, the leading source for insights into the world of technology and innovation. I'm your host Donald Klein, and today's topic is the market for autonomous vehicles and the ecosystem suppliers looking to tap into this brave new world of autonomous capabilities in our daily commute. To have this conversation I'm joined by Rudy Burger, managing partner at Woodside Capital. Rudy, welcome to the show. >> Thanks Don, it's great to be here. >> Great, so look, why don't we start off Rudy, why don't you tell us a little bit about Woodside Capital and your role there? >> Great, so I founded Woodside Capital about 20 years ago having started five different companies of my own, one of which I took public. We are a specialist M&A advisor. We work with so-called growth stage often venture-backed companies and help them find buyers that are usually much larger public companies. Our clients are usually US or European companies and we find buyers in the US, Europe, or Asia. >> Excellent, excellent, okay. And why don't you talk a little bit about your kind of specialty areas? >> So I focused my career, and certainly the work at Woodside Capital, on imaging technologies and as an enabling technology, and the products and markets that are enabled by imaging and increasingly computer vision. So nowadays that is autonomous vehicles, consumer technology, security surveillance, and digital health. So enabling technologies, the computer vision is the theme that binds those together. >> Okay, well, the thing that's on everybody's mind these days is autonomous vehicles, when are we going to get them? Very high profile for sure. Before the show we talking about the kind of two key ingredients to making this happen, the AI software which is kind of the brains of the operation and then also the sensors which enable all of the AI. So why don't we talk about the sensor world first, okay? Lot of discussion about there, so sort of does the brave new world of vehicles need lidar? Does it not need lidar? Are there other types of sensors coming along? What's your sense of that market and how it's looking for all of the different players in it? >> So, Don, I look at it from a sort of fairly basic standpoint. Humans have two very capable image sensors and a very powerful processor, and the degree to which the automotive manufacturers and so-called Robo-Taxi developers have decided it's necessary to sprinkle every sensor known to man, and I'm talking lidar, radar, ultrasound, thermal, and of course cameras, is to some extent a degree to which, you know, image sensors are not as good as our eyes today. Now, there are some areas in which we will probably always have technology as a help. For example, humans are not very good at seeing in the dark whereas a thermal technology can do that very well. But my overall belief is that it's never a good idea to bet against an incumbent technology, and in this case I'm talking about so-called CMOS image sensors which are the sensor that goes into pretty much every camera in the world now. It's never a good idea to bet against the incumbent technology being able to scale into a new market. Every time people have done that, they've been wrong. Back in the early days the debate was whether CMOS image sensors would ever be good enough to replace CCDs as the sensor technology, and of course now, you know, everything uses CMOS image sensors. In other markets there was a long period of time in which people were thinking that LCD panels would never be large enough to replace, you know, for television, for example, 50 inch and so forth. It was never going to happen, so we needed plasma TVs, we needed rear-projection TVs. But slowly but surely the incumbent technology, LCDs, expanded to that market. So my belief is that CMOS image sensors will evolve to a point at which they will replace the need for lidar in most applications. >> Interesting, so that's a very controversial statement, right? Because you've certainly seen a lot of emphasis on the development of new generation lidar capability. >> Over 100 lidar companies started over the last three, four years, and of course many of them will not be happy to hear me say that. There are two distinct markets and one is the so-called Robo-Taxi market, and the other is more of the consumer vehicle ADAS market, and I think we need to think about those separately because the economics behind both are very different. If you look at the Robo-Taxi market, those vehicles tend to be much more expensive and are relatively price-insensitive. So if they can improve safety a little bit by putting a lidar on there, you know, great, let's do it, multiple lidars because these vehicles will be in operation 24 by seven, and if each vehicle costs 200,000, $250,000, fine. When we talk about the mass market for automobiles, type of car that you and I might go down and buy, very different thing. And, you know, auto makers sweat the pennies, and so putting a one or $200 lidar in a vehicle, big decision. And to the extent that they can replace the need for that lidar with a much less expensive camera system, that's what they'll do. Bear in mind that Mobileye, which has been the biggest success story, acquired by Intel for $13.5 billion, second largest acquisition Intel ever made, they for the most part still run on one camera, forward-looking camera. That's it, no radar, no lidar, no thermal, one camera. So the clever use of image processing, computer vision, and one image sensor can do a great deal. >> Interesting, okay. Well, so I want to talk about the software in just a second, but just to kind of finish this point, so if you were advising a sensor company that's developing some next gen capabilities, whether lidar or other related technologies, is the point you're making here that there are certain segments of this industry which are going to be more attractive to your technology than others? >> Absolutely, yes. I mean, the first thing to recognize is that the automotive industry has never really been a particularly comfortable fit with the economics and timeline of venture capital. VCs need to invest and recoup and redeploy back to their LPs on an eight-year cycle. But the automotive industry moves quite slowly, perhaps Tesla are excepted, and what the first piece of advice I would give these companies is it's probably going to be three, four, five years before, even if you have the right technology, before that technology really starts generating any significant volume and revenue. So for many venture-backed companies, that's too long. So the first piece of advice is find pockets of revenue, right, beachheads if you will, where you can land your technology and start generating revenue before you get to the automotive market. And many of these lidar companies we just talked about are not going to last long enough to get to the automotive market because not only does the automotive market move slowly but the autonomous vehicle market keeps on getting pushed out to the right as the industry realizes that this is a big, hairy problem. And so I would say, what is it that your technology can do an order of magnitude better than any other technology? Focus on that and find some opportunities for revenue outside the automotive industry that will sustain the company on its way to the holy grail. >> Interesting, yeah, so find that alternative revenue source to get you to base camp, and then when the market's ready, climb that Everest to-- >> I've seen so many companies basically go out of business because they've set their sights on either the automotive market, and it's go for broke. We're not interested in, all these other things are distractions. You know, entrepreneurs don't have a plan B. Or this. We're going to get our technology into a smartphone, that's it. And there are possibly some other opportunities but it takes so long and it's so difficult to get your technology into a smartphone that they go out of business before they ever get to that point. >> Interesting, okay. So good advice for people looking to kind of apply their technology in this kind of a very difficult market, right, very complicated market. All right, well, then let's switch to the other side of it. So we were kind of talking about the key ingredients, right? Sensors but also AI and the software around that, okay, and there are some very big players developing the software. Tesla's had their Autonomy Day where they've showcased their technology. You've obviously got Google with their capabilities developing software. How do you make sense of this overall landscape because we do see a lot of smaller providers also trying to develop software here. >> So the first thing that I find fascinating about the automotive industry is that for the most part there is no software market. There's perhaps one exception of any scale, that's BlackBerry that sells the QNX software. They found a point within the entertainment console where they can license their software. But for all of the development and capital invested into automotive software, nobody is actually generating revenue, making a living, by licensing software. And one of the main reasons for that is that, you know, the automotive market, really since inception, has been a hardware business. This is a business of bending sheet metal, internal combustion engines, and software has really not played that big a role up until relatively recently. So even those companies that do have software technology have ended up selling it into the automotive supply chain as a piece of silicon, embedded on a piece of silicon, not as, you know, here's my software on a USB stick, right? I think that the whole software licensing model hasn't so far fit well, fit comfortably, with the automotive industry. And the other reason is that there's no standard platform. If I were to develop a piece of software, I can, in the PC industry, I can develop for Windows, I can develop for Mac, I can develop for an iPhone. There's no such thing in the automotive industry, and particularly in this new world of autonomous vehicles there is no standard platform. There are many different processors, Nvidia has staked an early claim there. And the reason that most of the companies developing autonomous vehicle technology have developed the so-called full-stack solution, everything from code running on the processor, integrated through the sensors and so forth, is for that reason, there is no standard platform. So each company has developed the whole solution for themselves, and there are many of them around here that have raised hundreds of millions of dollars, some cases billions of dollars, for that purpose. So there is, today, no software market for automotive in the same way that we think about it in other industries. >> Understood, understood. But in terms of the companies that are actually pushing the envelope on these kind of capabilities, right, so we're taking the best of AI, we're applying it to big data sets, and then hopefully being able to extract that to create capabilities for these vehicles, right? What's your sense of how far that's come along in-- >> Well, it's come a long way but, here I'm going to push the boat out a little bit. I don't believe that the so-called deep learning technology, which is the current state of the art for AI, it's the technology that has allowed computers to beat humans at chess, at Go, I don't think that that flavor of AI, that approach to AI, is ever going to get us to safe enough autonomous vehicles. And that's because it works extremely well in fairly well-bounded rules, rule-bounded games or any scenario like that, but can you imagine trying to teach your 16-year-old how to drive by showing them images of every situation that they might encounter, right? Impossible. It's an infinite, it's not a well-bounded set. And that's so difficult because we really haven't developed the technology to allow computers to learn, to have things like common sense, to infer, you know, well, this happened, so this is likely to happen. So I think we are going to need a whole new breakthrough in AI before we get to what is generally considered safe enough vehicles. >> Interesting, well then, maybe if we kind of apply your previous thought about sort of Robo-Taxis as maybe being the segment where you're going to see the most use of these newer sensor technologies. >> Rudy: Near term, yes. >> Exactly, what about maybe, is that sort of the same rules apply there for maybe the AI providers, that they're-- >> I think so and that's why they're all focused on that. I mean, from Uber to Waymo, they've all made the same calculation which is if you're running a fleet of vehicles, and so for example in Uber's case, the driver takes 80% of the fare and only 20% goes back to Uber, but if you can replace the driver with a computer, you can keep that vehicle on the road 24 by seven and you can keep 100% of the revenue. You don't need to pay the computer. So that's the calculus that they're all going through. But I think that many of them are making a fundamental mistake and I predicted recently that I think Uber, my prediction for 2020 is that Uber is going to divest its autonomous vehicle business and get back to the business that it should be focused on. Uber generates about $14 billion a year in gross revenue, so 20% of that, which is the piece that Uber keeps after the drivers take their 80, is what, 2.8 billion. Uber should be able to be an extremely profitable business on 2.8 billion of net revenue, but they're spending a huge chunk of money every year on R&D. Now, I would argue that Hertz and Avis have successful businesses. They're in the service, they're in the transportation business, but they didn't decide that they had to build their own cars in order to be in that business. My view, personal view, is that what Uber should be doing is saying, that's not our business, right? We are the world's best at managing this sort of peer-to-peer network crowdsourced transportation, if you will. And when some company, some Silicon Valley startup, comes out with safe enough technology, great, we'll use it, but we don't have to develop that ourselves. >> Well then, maybe just to play devil's advocate here for a second, what about it's a Robo-Taxi-type technologies being applied in bounded areas within metropolitan areas where the rules-- >> That's where it will start. >> Could be more-- >> I think that's where it will start, but I think part of the problem is that we have, perhaps in part due to all of the media hype around autonomous vehicles, we've been misdirected to thinking about autonomous vehicles as a replacement for the car we drive to work every day and I think that's the wrong way to think about it. I think that autonomous vehicles are going to show up in the market as an extension of public transportation. Right, you know, I get off the train and there's an autonomous vehicle waiting to take me for the last couple of miles to my office. >> And those last couple of miles would be sort of a regulated space. >> Rudy: May well be. >> Where the AI is more than capable of functioning. >> Right, and that, you know, yes. And so it's better to think about autonomous vehicles as not being a revolutionary technology but much more of an evolutionary technology. And in fact, most of these technologies are showing up in so-called ADAS technologies which are designed to make driving your regular car safer, lane assist, keeping you a safe distance. >> Donald: Maybe just explain that word, ADAS, and what that means. >> So ADAS stands for automated driver-assistance systems. So one of the first was cruise control, right, everybody's familiar with cruise control. And so to some extent ADAS is just building on cruise control. In addition to maintaining a constant speed, you can now stay in the lane. In addition to maintaining a constant speed, it will now automatically slow down if you get too close to the car in front. And so you can see ADAS as, you know, collision avoidance and so forth, not full autonomy, still have to have a driver in the driver's seat, but evolving year by year until one year we wake up and, yep, my car will actually drive me all the way from home to work without me intervening. Right, it's going to happen in that way. >> So incremental improvements. >> Incremental improvement. >> To ADAS as opposed to kind of revolution of autonomy. >> An overnight sensation. >> Yeah, right, coming from nowhere. Okay, understood. Well then, let's pivot from that then, okay. So let's talk about the automotive industry as a whole and sort of your thoughts on how this is all going to play out. >> Yeah, so there are some very interesting dynamics playing out in the automotive industry. Firstly, as good news, as a result of all of this money and innovation in the automotive industry, Detroit's actually coming back. I go there once or twice a year and you can feel the economy coming back in Detroit, but it's not going to come back around, you know, bending sheet metal. And the challenge that the automotive companies have is so much of their infrastructure and expertise has been built on construction, building a car, production lines to bend the metal, install the engine, and the internal combustion engine itself. And by complete coincidence, to some extent, we've got this confluence of all of these autonomous technologies and electric vehicles happening at the same time. Electric vehicles are much easier to make than internal combustion engines. Far fewer parts. It's one of the reasons that China has spun up about 20 different electric vehicle companies recently. So I think that long term, my prediction is that the automobile industry will go the same way that the personal computer industry went. When the PC first, you know, it was born by IBM, or Apple in some sense before that. There were dozens of companies producing different PCs and it was very much, they were expensive products, and, you know, relatively unusual. As the industry matured, the supply chains matured, and it became apparent there were really only two companies that were making a lot of money out of the PC industry. The companies that developed the software, operating system, and the companies that developed the processor, and all of the manufacturing went over to, in the PC's case, in Taiwan, right? And I think that exactly the same thing is going to happen with the automotive industry. Tesla today still actually makes cars, but I don't see them long term being in the car business because they're really a technology company. It's the reason I don't think Apple is ever going to get into the car industry. They make fantastic margins selling computer products. The gross margin selling a car, it's miserable. It can be single digits or teens. That would completely tank Apple's blended gross margin. So my prediction for the industry is there will be a few small pockets of very profitable businesses, particularly around the operating system, by which I mean the intelligence or the AI intelligence, and then the processor, whether it's a Qualcomm processor or a Nvidia processor or an Intel processor. And as with the PC industry, most of the profit will go there and most of the manufacturing will end up getting outsourced because that's not the value-add, you know, bending metal and so forth. >> Interesting, well, so in the kind of compute market today, right, we have this notion of sort of cloud-native, right, okay, and that many of the companies that are developing apps as relying on cloud-native infrastructure have a kind of technology lead that's going to be hard for some of the legacy providers to actually catch up on. Now, other people say that that's not necessarily the case and et cetera, right? Can you make the same argument for the electric car market, that some of the electric-natives might have a kind of sustainable advantage here? >> I should've added, today the cloud infrastructure companies, cloud services, SaaS companies, in the PC world, you know, very profitable, and I can see a similar cloud services model developing for the automotive industry. However, other than Tesla, it's very difficult to change the automotive channel to support that. I'll give you one example. Everyone that owns a Tesla is very used to the idea that, sometimes on a daily basis, a new bunch of software, operating system software, is downloaded overnight to your vehicle. You wake up in the morning and some new feature's been turned on, right? Tesla can do that because they bypass the entire dealership channel that has a complete lock on the rest of the industry. So for example, if GM wants to do the same thing as Tesla and do sort of what's called over-the-air, OTA, updates, software updates, they can't do that because their contract with the dealership network states that if there is service to be done on the vehicle, the vehicle has to be brought back to the dealership, and the dealerships consider updating the software on the vehicle as service. So their contract with the dealers actually prevent them from doing something that basic. So it's not just a technology issue. The whole channel and way vehicles get sold is going to have to change. >> Interesting, so that's the advantage that some of the new generation of vehicle manufacturers-- >> I would say that Tesla has a five year lead, technology lead, because they, like Apple, are vertically integrated. They're doing everything from user interface, fit and function, all the way down to the semiconductor. They're developing their own semiconductors now. So they have become a fearsome competitor in the electronic vehicle space because they've been doing it for longer than the other major auto companies. They've figured out a lot of the, you know, tricks and techniques of how to extend mileage and so forth. And so they have a substantial lead in the industry at this point, despite the fact that over the next 12, 18 months, every automotive company is going to be coming out with their own flavor of electronic vehicle. >> So then it's more than just about having electric drivetrains, et cetera, right? It's about the whole suite of capabilities. >> It's a systems engineering challenge. >> Interesting, okay. All right, well Rudy, we're going to have to leave it there, okay, but I think everything you've told us is, it sounds like some good news for some of the Tesla stock holders at the moment. >> I think so. >> Okay, well. (laughs) We'll pass on making an opinion about that, but great conversation, thank you for your insights. Okay, this is Donald Klein, host of theCUBE, here with Rudy Burger, managing partner at Woodside Capital. >> Rudy: Great, thank you, Don. (upbeat 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] [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

(upbeat music) >> Narrator: Live from Las Vegas, it's theCube. Covering AWS re:Invent 2019 brought to you by Amazon Web Services and Intel, along with it's ecosystem partners. >> Hello there and welcome back to theCube's live coverage here in Las Vegas for AWS re:Invent 2019. This is theCube's seventh year covering re:Invent. They've been doing this show for eight years, we missed the first year, I'm John Furr, and my co-host David Vellante. We're here extracting the signal from the noise, and we're here with an amazing guest, our friend, she's been here with us from the beginning of theCube, since inception. Always great to get to comment with her. Sandy Carter Vice President with Amazon Web Services. >> Thank you. >> Now in the public sector handling partners. Great to see you, thanks for coming on again and sharing your content. >> So great to see you guys, so dressed up and looking good guys, I have to say. (laughs) >> You're looking good to, but I can't help but stare at our other guest here, the IoT suitcase. >> First, tell us-- >> Yes. >> About the IoT suitcase. >> Well we, in public sector we have a partner program, and that program helps entrepreneurs. And we're really keen on especially helping female entrepreneurs. So one of our entrepreneurs created this suitcase, that's an IoT based suitcase, you can put your logo's and that sort of thing on it, but more importantly for public sectors, she created this safety ring, John. And so, if I touch it I've de-activated it, but if I touch it, it will call the police for me, if I'm being assaulted. Or if I'm having an emergency, I can touch it and have an ambulance come for me as well. And the really cool thing about it is she worked backwards from the customer, figuring out like how are most people assaulted, and if you have an emergency and you fall, what's the best way to get ahold of someone. It's not your phone, because you don't always carry it, it's for a device like this. >> Or a bigger device that you can't, or you leave on the table somewhere, but that's you know it's attractive. >> It's awesome. >> And it's boom, simple. >> And it's pink. (laughs) >> What I love fast about re:Invent as an event is that there's so much innovation going on, but one of the areas that's become modernized very rapidly is the public sector. Your now in this area, there's a lot of partners, a huge ecosystem going, and the modernization effort is real. >> It is. >> Could you share some commentary on what's going on. Give people a feel for the pace of change, what's accelerating? What are people doubling down on, what are some of the dynamics in public sector? >> Yeah, so if you know public sector, public sector actually has a lot of Windows or Microsoft workloads in it. And so we're seeing a lot of public sector customers looking to modernize their Windows workloads, in fact we made several announcements just yesterday around helping more public sector customers modernize. For example, one is Windows Servers 2003, and 2008 will go out of support, and so we have a great new offering, with technology, that can help them to not re-factor, but actually abstract those layers and move quickly to 2016 and 2019, because both of those will go out of support in January. >> A lot of people don't know, and I've learned this from talking with Andy Jassy in the keynote, as well as hearing from some other folks, is that you got, Amazon runs a lot of Windows. >> Oh, we have 57% Windows workloads on AWS in terms of market segment share. Which is 2x the next nearest cloud provider, 2x. And most customers choose to run their Windows workloads on us, because we are so innovative, we move really fast. We're more reliable. The latest public data from 2018 shows that the nearest cloud provider had seven times more downtime. So if your in public sector or even commercial, who can afford to be down that long, and then finally, we have better security. So one of the things we've been focused on for public sector is FedRamp solutions. We know have over 90 solutions that are FedRamp ready. Which is four times more than the next two cloud providers. Four times more than the two combined. >> That's interesting, so I got to ask the question that's popping up in my mind, I'm sure people are curious about. >> Yeah. >> I get the Windows working on Amazon, and that makes a lot of sense, why wouldn't you want to run on the best cloud. The question I would have is, how would the licensing work, because, that's seems to be lock-in spec, Oracle does it, Microsoft does it, does license become the lock-in. So, when something expires, what happens on the licensing side. Licensing is really tricky, and in fact, October 1st, Microsoft made some new licensing changes. And so, we have some announcement to help our customers still bring their own licenses, or what we call fondly, BYOL over to AWS, so they don't have to double invest on the license. >> So you can honor that license on AWS. >> Yeah, and you have to do it on a dedicated host. Which at midnight madness, we announced new dedicated host solution, that's very cloud-like. Makes it as easy to run a dedicated host instance as it is an EC2 instance. So, wicked easy, very cost effective if your moving those on-premises workloads over. >> I just want to point out John, something that's really important here is a lot of times, software companies will use scare tactics, to your point. They'll jack up the cost of the license, to say, ah you got to stay with us, if you run on our hardware or our platform, you pay half. And then they'll put out, "Oh, Amazon's twice as expensive." But these are all negotiable. I've talked to a number of customers, particularly on the Oracle side, and said, no, no, we just went to Oracle and said look, you got a choice, I either give us the same license price or we're migrating off your database. Okay, all right. But some of it is scare tactics, and I think you know increasingly, that's not working in the marketplace. So I just wanted to point that out. >> So what's the strategy for customers to take, I guess that's the question. Because, certainly the licensing becomes again like they get squeezed, I can see that. But what do customers do, is there a playbook? >> Well there is, and so the best one is you buy your license from Microsoft, and then using BYOL, you can bring that over to AWS. It's faster, more performance, more reliable, that sort of thing. If you do get restricted though John, like they are doing for instance with their end of support, you could run that on Azure, and get all the security fixes. We are trying to provide technical solutions, like the ability to abstract Windows Server 2003 and Server 2008 as it goes out of support. >> I mean certainly in the case of Oracle, it used to be you know 10-15 years ago, you didn't have a choice. Instead of one RDBMS, and now it's so much optionality in databases. >> And I will also tell you that we have a lot of customers today, who are migrating from SQL server, or Oracle over to Aurora. Aurora, is equally as performant, and a tenth of the cost. So we actually have this team called the database freedom team that will help you do that migration. In fact I was talking to a very large customer last night, and I was explaining some of the options. And their like, "Let's do the Aurora thing." Let's do it two-step. Let's start by migrating the database over, Oracle and SQL and then I want to go to Aurora. It's like database built for the cloud, it's faster and its cheaper. So why wouldn't you do that? >> Yeah, and I think the key is, to my question about a friction. What's frictionless? How can they get it done quickly without going through the trip-wires of the licensing. >> Certain workloads are tough, right. You know if you're running your business on high transaction volume. But a lot of the analytics stuff, the data warehouse, you know look at Amazon's own experiences. You guys are just ticking it off, moving over from Oracle to Aurora, it's been fun to watch. >> I want to get you guy's perspective Dave, you and Sandy, because I think you guys might have good insight on this, because everyone knows that I'm really passionate about public sector, I've been really enamored with Teresa's business from Day one, but when she won the CIA deal, that really got my attention. As I dug into the Jedi deal, and that all went sideways, it really jumped out at me, that public sector is probably the most transformative market, because they are modernizing at a record pace. I mean this is like a glacier moving market. They don't really have old ways, they got the beltway bandits, they got old procurement, old technology, and like literally in a short period of time, they have to modernize. So they're becoming more enterprise like, can you guys, I mean pros in the enterprise, what's your take? It just seems like a Tsunami of change in the public sector, because the technology is driving it. What do you guys think about this? Am I on or off base? What are some of the trends that are going on? >> I mean I have a perspective, but please. >> No, okay. So I'll start. So I see so much transformation regardless of what industry your looking at. If you're looking at Government for example working with SAP NS2, we just actually took 26 different flavors of SAP ERP for the Navy, and helped them to migrate to the cloud. For the US Navy, which is awesome. Arkis Global, did the same thing for the UK. We actually have Amazon Connect in there, so that's like a cool call center driven by Machine Learning, and the health care system for the UK. Or you can even look at things, like here in the U.S. there's a company that really looks at how you do monitoring for the children to keep them safe. They've partnered up with a National Police Association, and they are bringing that to the cloud. So regardless of education, non-profits, government, and it's around the world, it's not just the US. We are seeing these governments education, start-ups, non-profits, all moving to the cloud, and taking their own legacy systems to Linux, to Aurora, and moving very rapidly. >> And I think Andy hit on it yesterday, it's got to start with top-down leadership. And in the government, if you can get somebody whose a leading thinker, CIO, we're going cloud first. Mandate cloud, you know you saw that years ago, but today, I think it's becoming more mainstream. I think the one big challenge is obviously the disruption in defense and that's why you talked about Jedi, in defense it's very high risk, and it needs disruption, it's like healthcare its like certain parts of financial services are very high risk industries, so they need leadership, and they need the best platform underneath in a long term strategy. >> Well Jedi actually went different. It was actually the right call, but I reported on that. But I think that what gets me is that Cerner on stage yesterday, on Yaney's keynote highlights that it's just not inefficiencies that you can solve, there's multiple win-win-win benefits so in that health care example, lower the costs, better care, better, the providers are in better shape, so in government in public sector, there's really no excuse to take the slack out of the system. >> Yeah. >> Well, there's regulation though. >> Yeah, and Dave mentioned cloud first strategies, we're also seeing a lot of movement around data. You know data is really powerful. Andy mentioned this as well yesterday, but for example in our partner keynote where I just came from. We had on stage Avis. Now, Avis, not public sector customer, but what they're doing is, the gentleman said, was that your car can now talk to you, and that data is now being given to local state officials, local city officials, they can use it for emergency response systems. So that public and private use of data, coming together, is also a big trend that we're seeing. >> I think that's a great example, because Avis I think what he said is a 70 year old company, I think the fleet was 18 billion dollar fleet. >> 600,000 vehicles. >> 600,000 vehicles, 18 billion dollars worth of assets, this is not a born in the cloud start-up, right. That's essentially transformed the entire fleet and made it intelligent. >> Right, and using data to drive a lot of their changes. Like the way they manage fuel for 600,000 cars, and the way they exchange that with local officials is helping them to you know not just be number two, but to start to take over number one. >> But to your point, data is at the core, right. >> Yeah. >> If you are the incumbent and you want to transform, you got to start with the data. >> Sandy, I want to get your reaction to two memes that have been developing on theCube this week. One is, if you take the T out of Cloud Native, and it's Cloud Naive. (Sandy laughs) The other one is, if your born in the cloud, that's great, your winning, but at the price of becoming re-born in the cloud. This is the transformation. Some are, and they're going to not have a long shelf life. So there's a real enterprise and now public sector re-birth, re-borning in the cloud, the new awakening. This is something that is happening. You're an industry veteran, you've seen a lot of waves, what's the re-born, what's this getting back on the cloud, really happening. What is going on? >> It's really interesting, because now I'm in the partner business, and one of our most successful programs is called our partner transformation program. And what that does, is it's a hundred day transformation program to get our partners drinking our own champagne, which is to be on the cloud. And one of the things, we know we first started testing it out, we didn't have a lot of takers, but now, those partners who have gone through that transformation, they're seeing 70% year to year growth, versus other apion partners, even though they're at an advanced layer, they're only seeing 34% growth. So its 2x of revenue growth having transformed to the cloud. So I think, you know back to your question, I think some of this showing the power. Like, why do you go to the cloud, it's not just about cost, it's about agility, it's about innovation, it's about that revenue growth, right. I mean 2x, 70% growth, you can't sneeze at that. That's pretty impactful. >> And you know this really hits, something of passion for me and Dave and our team is the impact on a society. This is a real focus across all generations now, not just millennials, and born in the web, into older folks like us, who have seen before the web. There's real impact, mission driven things. This is a check for good, shaping technology for good. Educate you guys have. This is a big part of what you guys are doing. >> Absolutely, this is one of the reasons why I really wanted to come work in the public sector, because it's fun helping customers make money, and we still do that. But it's really better, when you can help them make money and do great things. So you know, making with the Mayo clinic, for example, and some of these non-profit hospitals, so they can get better data. The GE example that Andy used yesterday, that data is used in public sector. Doing things, like, I know that you guys are part of re-powered tech. You know we brought a 112 unrepresented minorities and women to the conference. And I have to tell you I got goosebumps when one person came up to me and he said, it's the first time he stayed in a hotel, and he's coming here to enhance his coding. You don't realize when I go back to my country, you will have changed my life. And that's just like, don't you get goosebumps from that, versus it's great to change a company, and we want to do that, but it's really great when you can impact people, and that form or fashion. >> And the agility makes that happen faster, its a communal activity, tech for good is here. >> Absolutely, and we just announced today, right before this in the partner's session, that we now have the public safety and disaster response competency for our partners. Because when a customer is dealing with some sort of disaster or emergency they need a disconnected environment for a long periods of time. They need a cloud solution to rally the troops. So we announced that, and we had 17 partners step up immediately to sign up for that. And again, that's all about, giving back, helping in emergency situations, whether it's Ebola in Africa or Hurricane Dorene, right. >> Well, Sandy congratulations, not only have you a senior leader for AWS doing a great job. >> Thank you. >> Just a great passion, and Women in Tech, Underabridged Minorities, you do an amazing job on Tech for Good. >> Thank you. Well it's such an honor to always be on the show. I love what you guys do. I love the memes, I'm going to steal them, okay. >> Can I ask you another question? >> Absolutely. >> Before you wrap. You've had an opportunity to work with developers, you've experienced other clouds. Now you're with AWS and a couple of different roles. Can you describe, what's different about AWS, is it cultural, is it the innovation, I mean what's tangible that you can share with our audience in terms of the difference. >> I think it's a couple of things, the first one the way they we hire. So we hire builders, and you know what it really starts from that hiring. I actually interviewed Vernor the other day, and he and I had a debate about can you transform a company where you have all the same people, or do you need to bring in some new talent as well. So I think it's the way we hire. We search for people that not only meet the leadership criteria, but also are builders, are innovators. And the second one is, you know when Andy says we're customer obsessed, we're partnered obsessed. We really are. We have the mechanisms in place, we have the product management discipline. We have the process to learn from customers. So my first service I launched at AWS, I personally talked to 141 customers and another 100 partners. So think about that, that's almost two hundred almost fifty customers and partners. And at most large companies, as a senior executive you only spend about 20% of your time with customers, I spent about 80% of my time here with customers and partners. And that's a big difference. >> Well we look forward to covering the partner network this year. >> Awesome >> Your amazing, we'll see Teresa Carson on theCube here at 3:30. We are going to ask her some tough questions. What should we ask Teresa? >> What to jest Teresa? Where did you get those red pants? (everyone laughs) >> She's amazing, and again. >> She is amazing. >> We totally believe in what you're doing, and we love the impact, not only the technology advancement for modernizing the public sector across the board. But there's real opportunity for the industry to make, shape technology for betterment. >> Yeah. >> You're doing a great job. Thank you so much. >> Thank you. I think we should start another hashtag for theCube too, is #technologyforgood. >> Awesome. >> What do you think? >> Let's do it. >> I love that. >> But Jonathan been doing a lot of work in that area. >> I know he has. >> We love that. #technologyforgood, #techforgood. This is theCube here live in Las Vegas for re:Invent. I want to thank Intel and AWS, this is the big stage. We had two stages, without sponsoring our mission we wouldn't be here. Thank you AWS and Intel. More coverage after this short break. (dramatic music)