(click) >> Welcome this special Cube conversation in the Intel Tech Lounge at the Sundance Film Festival. I'm John Furrier with The Cube. We are here with Ari Kuschnir, who is the founder and managing partner of Missing Pieces. Doing some really amazing work on the future of filmmaking. He's got a great entrepreneurial spirit. And creative desire to deliver great product. Welcome! >> Thank you, thank you. >> So, tell them about Missing Pieces and what's going on in your world. So, there's context. Take a minute to explain what you are working on. >> Well, the premise is to be at this intersection of storytelling technology. And to make stuff people actually want to watch. And VR and AR are parts of it. But not the whole. So, I know some of the conversation focus is on, is on VR, and we're just as excited about where storytelling is headed. In terms of what technology allows us to do. But the key for me is. I'm just passionate about, a new thing comes out. And I want to figure out how to make something really great. But meaningful, and powerful with that. >> We were talking before you came out about filmmaking, obviously trained in the discipline, obviously a variety of other things. But I want to get your perspective, we're on top of this new generation, what does that mean to you? When you hear that new generation, a new creative is coming? What does that mean to you? >> Yeah, I feel like I've ridden the wave of the thing as it's happened. And I mean, the company has too. So, I went to film school in the late 90s. And it was the first time you could buy like, first Final Cut, and the first wave of that. So you could make art little movies on the weekend, you no longer needed even to go to the school itself to borrow the equipment. That was revolutionary in 1999. And then 2005, when we started thinking about the company. You know, your Vimeo, YouTube, video i-Pod all come out within five months of each other. Towards the later part of the year. And it's a revolution. It's clear that with distribution, now not only can we make it and edit it in our laptops. But we can put it out, and millions of people could watch it. And that was the first time that was possible. And it was revolutionary. And I think it still is, to some degree. So, we've just, you know, as it evolves what I see is that, it's not, I've always felt like it's not enough to make the sausage as they say. You know, the directors, the talent that I sign now. Like the project we have now here at Sundance, young Jake. Jake is a great example of a creative who you can't fit in a box. He's an Internet artist, he's a rapper. He's an interactive video maker. He did an app called Emoji.Ink. And he does celebrity emoji portraits. He has a hundred thousand followers on Instagram. So, he can command his own audience. So, when a brand, or an agency comes to him. It's a very different approach than when they come for a very straight up work for hire, director's commercial kind of thing. That is the future, I mean. The future is about having a passionate audience, making things for that audience, understanding it. And being able to communicate with them on a daily basis, or a weekly basis in a powerful way, right? Through story. >> Yeah, I mean, you're riding the wave. And the waves are getting bigger. One of the things we do, we do a lot of tech coverage. And we see this in Cloud computing where software changed from Waterfall to Agile. And now the craft's coming back on the software side. But still now, software is eating the creative world. Because now a new wave is coming. So, speak to that, because you're, this is, you can almost look at the old ways. You mentioned the commercials and films. Almost like the Waterfall. You know, crafts, craft it up and you ship it. And you hope it works well. >> Ari: Yeah. >> But now, you have this new model of iteration. Where it's more Agile creative. How do you do Agile, like your artist, and not lose the craft? >> Yeah, well it's a challenge. Look, I've had so many opportunities in our 10 plus year career to kind of go in that direction of just like quantity over quality. And we could just never do it. I mean we're just not cut out for it. But at the same time, I'm not, I never ignore, how to optimize the content based on data, and based on what the landscape is looking like. So, an important thing for example that we consider in every project is context. Like what, how is this project going to be released? Oh, it turns out that, it's really a big social media push. It's not a TV thing. Or it turns out specifically it's Facebook versus Instagram. And that's a very different type of edit. And a very different type of way you start the video. 'Cause you've got a certain, even a different format, and a different way of looking at the content. So, you start to get into, and then you start to iterate, and look at the different ways in which you can repurpose, and rerelease the content, but customize it for each thing. So, you get into this really interesting place where the data is driving the story. And the feedback is driving the story. >> And the audience is part of the journey. >> Yes. And the comments, and the way in which people are taking the thing that you've made and re-interpreting it, is really interesting. And part of the story. >> You trigger a lot of emotion with me, when we're talking, because, you know, as an entrepreneur, I started media businesses turning into, and no-one has even seen this kind of media business before. But I have no media training of any kind. I did a science major. So, there's certain, and I've observed that there's dogma in the journalism business. And there's, but you know, how dare I challenge that, or others. You're doing the same thing. >> I love that by the way. >> So, I want to ask you. What is the dogma with the old world, 'cause the naysayers are usually the ones with the dogma. "Oh, it will never work!" >> Ari: Yeah. >> So, you're on the front end of this new trend. But you're going to have a visibility into what they're thinking, what is that? >> The dogma is, you know, the whole like, there's only big name directors, and you know, it's a certain caliber of work. And that craft is the ultimate thing. And that you just have to make the thing great. And it'll do the thing that is needs to do. Without any thinking in terms of context, or media buyer. How it can actually become a social, socially engaged piece. So, the thing that we're always fighting is some version of that. And then because we came from a scrappy place, but we're now, you know, a pretty legit thing, I think people, some people will still be like, well that's the kind of like, the problem solving sometimes gets interpreted as scrappy. Which is a word I really don't like. And I think-- >> It's a compliment on one hand. >> Yeah. >> But some people look at it as an insult. "Oh, he's just scrappy!" >> Well-- >> "He's not legit!" >> You never want to be the cheap solution. You want to be the solution that people call because nobody else can solve this problem for you. I think we, there's a strand of the company that's like, the kind of like, pick up the phone and we'll figure it out. And, the impossible project that nobody else can do. And then there's another strand where it's just like, you just want to make stuff people actually want to watch. How hard it that? The thing where you could just buy the media, and expect the results is trickier and trickier. >> I mean you could be different, and innovative, but that might not be good. But if you're good doing it, you're differentiated and you're innovating. >> Ari: That's right. >> What's the filmmaking track on that line. Because certainly there's a lot of innovation. And with innovation comes failure. But people are trying to be different. And being different actually is a good thing. What are some of the trends that you're seeing where people are having some success. And where people are stumbling. >> Yeah, that's a good. I mean what I see is, the things that do well take cultural context into account, and again speak to the people in that way. So, it's like a feedback loop that it's creating with its own audience. And we almost always, there's almost always a time in the process when we're dealing with an agency, or a brand where things start to go a little bit like, too, too much, and in that direction that you don't want it to take. Somebody, usually me, or someone will say, "Look, if we make these changes. "Or if we go in this direction. "We won't want to share it. "And if we don't want to share it, "nobody's going to want to share it." So, that becomes a key thing. Whereas before you could sort of away with some of that, now it's like, well, it has to pass this sort of, kind of litmus test in terms of like, are you comfortable with sharing this thing, because it speaks to you or not. >> So, I want to ask you the hard question, we're here at the Intel Tech Lounge, obviously Intel is doing a lot of tech things. They're trying to get all this new tech. And I see it on, whether you watch the NFL playoffs, with, you know, with the camera angles, the games, on basketball games. You see them using the power of technology-- >> We're actually working on an Intel Olympics VR related project that got a little tease ad, CES. So, I can just say that. >> Yeah I know, so what's the tech? What's the cool new game changer in your mind. As a tool that you need to be more successful, and other artists could use? >> Hmmm, well, you tend to, yeah I mean, I think we-- >> John: More horsepower, more compute, more-- >> No, I mean it's really the, What happened with the AR was really interesting, which was, everyone realized, oh, the phone's already in our pocket. While the headset needs to be something that really needs to be standalone. It needs to be $200. You know, like, you sort of, there's different kinds of headsets, of course. They do different kinds of things. But that's an extra hardware. The phone we already have in our pockets. So, everyone's started taking AR seriously. Including the big players. And what that allowed was a, a rethinking of what the possibilities with story would be. So, in some ways this last year has been a readjustment, and a rethinking of, well, what can you do with the phone that you've already got in your pocket. In terms of expanding the storytelling. Or placing a story in the middle of your living room, you know. A layer, using the phone as a window and a layer. But I'm equally as excited about what's coming in VR, interactive VR, room-scale VR, you know. The project that we have here is an interactive 360 project with a phone. >> What's that called? >> It's called On My Way. And the artist is young Jake. And the original conceit of it, is, it's Jake, there's four Jakes in a car. And every time you move the phone to a different Jake, it changes the Jake. So, as soon as it passes the quadrants. So, the four quadrant it kind of swaps the Jake. And that creates a really fun, and interesting thing. And he actually designed it for the phone, vertical. Because that's the way most people are going to experience it. >> John: That's awesome. >> But it's playing on a headset as well. >> Oh you're definitely a new creative. Love chatting with you. >> Thank you. >> Final, well, I have two questions, first one is, Sundance, what's the story this year? What's your report? If you had to go back and your friend asked you to give him a report, "Hey, what happened Ari, "what's going on at Sundance this year?" >> A combination of really interesting high-end VR projects. Some of them leaning into this kind of like more psychedelic less narrative driven stuff. Which I really like. Kind of like really embracing the fact that it's another world, and taking you there. And then the AR stuff. There's a thing called Tender, Ten Day R. Or Tendar. Which is a play on Tinder, by Tinder Claus. Which is, uses augmented reality, and emotion, and machine learning, everything that you could hope for in a really interesting way. So, that's kind of showing you where it's going. So, I think those two things. >> Psychedelic's interesting. I always, I mean this kind of tangent. But in, I've been seeing on The Cube interviews, I think we're going to have a digital hippy revolution. >> Ari: Definitely! >> And it's coming. I mean you can feel it. It's a different culture. >> When I was looking a lot of people, yeah, a lot of people are scared to, I mean, VR is a really great consciousness expanding way to go to get into other worlds. Without, you know-- >> And will all the crap going on in the world today you can almost look at this as a Sixties like movement in this modern era. Where it could be a major catalyst for massive change. >> Yeah, and there's a piece about, you know, this female shaman that grows through the tribe in Ecuador. And became the first ever female shaman for her tribe. And there's a piece called Chorus that, within it. Which is just super weird and trippy. And almost has no plot, but is amazing. >> All right Ari, you've got to run. Quick soundbite. What are you working on, what's exciting you these days? Share a little bit about what's happening. >> A variety of, again it's the full spectrum of storytelling, so it's not one thing. It's really pushing, experiential pushing, branded content pushing, original content that we're getting a lot more into that game. Long form series. VR series. Really, that's kind of the next wave for the company is to set foot, much stronger in the original space, and create our own original IP. Our own original content. >> Awesome, Ari Kuschnir managing partner and founder of Missing Pieces, check them out. Lot of great work. And again, it's a whole new game changing, from storytelling to the tech. The collision between technology and artistry, and creative, and it's happening. It's here at Sundance, at the Intel Tech Lounge. I'm John Furrier with The Cube conversation here at Sundance, which is part of our coverage. Was to look at the angle of Sundance 2018. Thanks for watching. (upbeat music)

>> Male: TheCUBE presents, UIPATH, Forward 5 brought to you by, UIPATH. >> Okay the party has started here at forward 5 UIPATH big customer event if you're watching the cube. We're wrapping up day one with the co-CE0 segment. Daniel Dines is here. He's the founder and Co-CEO of UIPATH and Rob Enslin, is co-CEO. Gents, great to see you. Thanks for spending some time with us. I know you're super busy. >> Thanks Dave. >> So I've been looking forward to this. Daniel you know I've followed the company for a long time. The really interesting path you took, to get to where you are today. How did you guys meet? And why did you decide to hire Rob? >> Male: (laughs) >> Rob: Well let me start. I uh, I was looking for a partner. Actually, in our work to your stand here, we are talking about how, how you feel in this job. You feel so alone. Because you are the center of all pressure points. And having a partner, having someone that has your back, it's kind of awesome. So I was looking for a partner. And our current friend, Carl Escenbach, he introduced us to each other, and we instantly clicked. And this is the type of job where it's uh either work well or it doesn't. It cannot be anything in the middle. >> Right, okay with Carl, we know Carl well. Awesome operator. Knows the business super well. So Rob, what attracted you to UIPATH? You had a great situation at google. You guys were growing like crazy. Why did you decide to come here? What did you see that attracted you? >> Yeah you know when I, when I went to google, I went to google because I really believed that data and AI was necessary for companies. And business is to be competitive in the future. And we did some great stuff at google cloud in the 3 years. But I knew UIPATH from a couple of years ago when they were mainly a RPA space. And I just felt that there was a place in time when automation was going expand. And as I sat down with Carl a couple of times, spoke to carl. And then I sat down with Daniel, I knew that there was something special with UIPATH, that could be a generational opportunity. Not any for myself but for the company in the future. And then I, you know I got to know Daniel. And at this stage of my career I was like, I'm pretty fussy about what I want to do and what I want and where I want to go. First of all, I want to go to a company that had great product, had a great culture, and I wanted to work with somebody that we could shake the future together and you know, Daniel and I just hit it off from the very first time we met. He got to meet my family, my dogs and we did the whole, we did the whole courting thing before we actually decided this was going to be a good thing for both of us. >> Dave: That's good. >> Rob: Yeah. >> Dave: You got to meet the family. That's very good. >> We just had, John Furrier and I just had, Mohit Aron and Sanjay Poonen into out studio. Cause Mohit, you know, formal google. Long time. And they decided to kind of split duties. Mohit's going into product, he didn't keep his CEO title. He walked. How are you guys splitting you time? What are each of you going to, responsible for? >> Daniel: Well its, its kind of similar. On a day by day operation I, I rely heavily on Rob. We do it together. Strategic decisions about the company's destiny. I'm doing mostly the product these days. Which is a big relief for me. And I think we also split a bit of customers visit. Which is great. I still enjoy meeting customers. I need, customers are food for my cause. >> Dave: (laughs) yeah and your awesome product visionary. You've been there since day one. Now Rob, you said in the key note today that you've seen around about a hundred customers. You've transverse the world. What did you learn from them that informed you? That gave you confidence that the the move to the internet platform, even though you had already started that. >> Male: Yeah. >> But you're really doubling down on that >> Rob: You know when I... >> from a stand point. >> Rob: You know Dave, when you think about it, like I was, I was so impressed that Daniel had the vision to create a platform 3 years ago. >> Dave: Yeah. >> All right. And as we went around the world. As I went around the world, and it was one of the very first things I've seen. I've got to understand how customers see UIPATH, from their advantage point. What are they looking for from us? Why is this company, why doe customers like this company so much? And as I went around the world. I went to Asia a couple, I went to Asia, Australia, Singapore, Japan. I was in Europe twice. We did the trip together. We went to visit customers. And it was very much the same thing. Helps us expand automation faster. And we are so surprise, at the break of your platform. We never knew that. And so it kind of just had, for me, it was conviction. It's like, this walls is the right decision you've made. There's so much opportunity there. And that's, you know that's kind of what I've learned through the last four five months. >> Dave: Now as you know Daniel, I've written a lot about your company. One of the things I've said is that, that start ups, if I can call you that back pre-IPO, typically don't have as much international exposure as UIPATH had. I mean you sort of, you sort of started as an international company and became more US centric. You said, in the, in the key note today, you're talking to Ray Wong about people may don't understand that challenges of FX. Point being, when you convert international dollars into US dollars there are less of them cause the dollars stronger. But still, I've always felt like that international footprint is an advantage. Rob you came from SAP, you know, again European based company. I don't, (stutters), do you regret that? Now? I mean I know it's technical, I'm sure you don't, but talk about that sort of international exposure? Why that's a long term benefit. >> Well, you, first of all, you expand faster. I think we expanded faster than our competition because our global footprint was larger. And we had the courage. Go in Japan, for instance. Everybody told me, it's impossible to make for such a small starter. It's impossible to make a business in Japan. But we didn't believe it. We're just crazy and we went there, and be built a very sizable business in Japan. Fifty-five percent of our revenue, even today, it's outside U.S. Now of course that has a down side. When uh, When the local currencies, you know, are losing the value compared to the dollars, we're impacted. As we go to... to investors, until now, so we are seeing like a (indistinct) in terms of ARI. It's huge. Only because (indistinct) and losing the business in Russia. But it still, it's the strength of our company. Things will come back. And then, you know, the growth engine will re-accelerate again. >> Dave: Yeah but when the dollars weakens that'll be in your favor. Rob I want to pick up on something you said today in your keynote. You went back and started, you know the cycles of ERP and you know, internet, et cetera. I kind of have a love hate with ERP. I have to be honest. >> Male: (laughing) >> But it, but but (chuckles) but if I go back to that. Late eighties nineties, you wouldn't have be able to pick SAP as the winner. And then SAP emerged. You know, very clearly. But the more interesting thing, is that the customers who are implementing ERP well. The practitioners did better than their peers, and dominated their industries. And their stocks went up. Their evaluations went up. Different worlds obviously but, do you see the same thing happening with RPA and automation? What gives you confidence that that's the case? >> I absolutely do see the same thing happening with automation and RPA being a part of, in being a part of that. The reason, the reason I believe that is speed is so critical. (stutters) And if you think about how hard it is for a CIO or a c level executive to consume the technology coming at them, plus all the changes in the world being thrown at them. It's compiling and compiling and compiling. We have an incredible solution, that can help companies. And there comes certain times, the love outcomes to the business. Like no one else gets. And when I see that, I view that as just like the beginning of what's going to happen in the future so, in many ways, and I've said this to many of my friends, it feels like 1992, 1993 to me. And it's interesting because no one really understood then why SAP would be great in 1992 and 93. And they got a couple of things right. They got the eco system right. Their new partners were important. And the knew they needed to drive business outcome for companies, in which they did. And so I feel like we are in a very similar place. Very different technology obviously. And the speed of change now is so dramatic, compared to what it was. And there's very few technology that can provide that level of speed and accomodation to their customers. >> All right, let's talk about priorities. You guys got a lot of work to do and you've, you've laid it out to the financial community. You've got to have profitable growth, because of FX, it part, you've lowered your forecast. But I think there's some conservative in their as well. Um, but you got to do that balance. You've given some guidance on gross margins. Cloud maybe brings that down a little bit. RnD I saw wide range. Thirteen to seventeen percent. I hope you keep spending on RnD. Big fan of that. You know stock buybacks and, RnD if in your position are going to be better. And the product priorities, continue to build that out. But question, let's start with the product. So you've got an on-prem stack and you've got a cloud stack that's emerging, how do you balance those out? How do you do the integration? You've done a great job with the integration. Does it, are you concerned about your ability to continue to work at that speed with two code bases? I wonder if you could address that? >> Daniel: We've become a cloud first company. We deliver all of our products first in the cloud. We've deliver on the two week (indistinct) in the cloud. So that helps us integrate quite fast. I think we made a very good business decision to build our cloud team in Seattle. In Bellevue to be specific. And we have access to great talent that knows how to build serious cloud service. Which is hard to find dollar. And uh, so, and also we, we have, we benef- one of our only benefits was, we have the really good architecture. We have an architecture that work easily on-prem and on the cloud. And even today, our work flow foundation, our local designers, were easy to modernize. So right now we are launching studio weapon. But behind the scene, it's the same workflow engine. Our customers don't have to rewrite anything. It just works. And it does the same to take our own brand product and brand it in the multicloud. So, it's, there is no friction at all. Actually cloud is just helping us accelerate. But we benefit then again of a really solid architectural foundation. >> Daniel: Architecture matters. We've seen that in this industry. We got the B52s rocking out in the background, I love it, but I've got so many questions for you guys. I want to talk about the go to market. Because Rob, it's obviously a strength of yours. You've come in. You've communicated to the street, that you're reshaping the sales floors. Are they lowering the ratios of sales? People, the customers at the high end, mid range as well, using digital. I mean the numbers are one to ten now. At the top. One to maybe fifty at the mid range. Where are you in terms of that journey? You've got to find people, you got to train them, how do you get the productivity out of those guys? Take us through your thinking there? >> Rob: Yeah firstly, I think we have enough resources. Having resources is not an issue. Um, we have an incredible vehicle to acquire customers inside the company. Our digital sales motion, it's probably the best I've seen. And so we have the ability to acquire customers really fast. And we get the first workload in really fast. The challenge is we need to, we need to be able to drive a (indistinct) model and we graduate customs when we acquire them into the direct sales floors. And then direct sales floors, we're not going to go one to thirty, we're talking one to ten for the direct sales floor. And even the high up in the pyramid, we want to have an even denser model than that. And the whole purpose is to drive the time to consumption much quicker, much faster. So we know exactly if we acquire a customer, will they spend? Do they have a (indistinct) spend? On what level do they have a (indistinct) spend? And therefore when we capture them, we can immediately surround them, and put the right resources so we can grow faster. We think this will have a significant impact on the organization. We'll start to implement certain pieces in the next quarter. Um, things like packaging solutions. Putting them in, enabling the sales organization. And buy the beginning of next year, we'll be ready to actually go full board, globally. We already put some pieces in place when I joined. Chris Weber, my chief business officer, did a great job doing some of those pieces. So we're on the journey already. >> Dave: Yeah and even before you guys were public and you weren't publishing your NRR numbers. Our ETR survey partner, we, we always thought you had very low churn. And I think you broke out just yesterday. The, the NRR for overseas vs U.S, U.S I think was 140 plus percent. >> Male: Yeah >> Very very strong. A little, a little less overseas but the churn is still very low. >> Male: Yep. >> Okay so that's super positive. Customer affinity, I was wanted to code these events. I listen to the key notes very carefully, and then interview customers on the cube, and I try to identify, is there alignment there? And I see very strong alignment, I have to say, and strong customer affinity. So that's in your favor. I have, Daniel, I got another question for you on product. What is Symantec automation? What the heck is that? Can you explain that? I don't understand >> Dave, have you seen the demo in my (indistinct)? >> Dave: You know, I had to leave and do interviews, so I, uh, I missed it. >> I think, I think that demo answer complete your question. So in the s-, you know there saying that great, you can not distinguish great technology by magic. I think technology should be simple. And we, we show today, one of the simplest demo that you can imagine. But it's so, such a complex technology behind the scene, that you also can not imagine. So what was demo? We show how one business user, without any technical skills, can build any type of document. Can be a passport, can be an invoice, can be a legal (indistinct), and just go, "I want to copy data from here, and I want to paste data there". Can be a spreadsheet, can be another obligation, and like a human user, without understanding, without having prior knowledge about data, document layout, about screens, screens layouts, nothing, we analyze real time. Document. We discover, we discover the meaning of the information. We analyze the screen. We understand the screen but we understand the meaning of the screen. And we understand how the information in one side relate to the other side. And we just connects the dots and we copy the information and we paste it. A job that you'll do as a human user, maybe three minutes, is done in ten seconds. This is powerful. >> Yeah that is powerful. Thank you for that. I mean, and you take the date, whether it's transaction data or unstructured data and and and bring meaning out of it. That's powerful. Last question and I'll let you guys go. Rob, you got traders, and you've got long term investors. All right traders going to be defensive, today. I get that. Make the case for UIPATH, for long term investors. >> Rob: I think we're going to be a multi-gern- multi-billion company and we're going to be a generational company of our time. And we will define enterprise automation. And it's going to be a long term game and we feel like really strong that we'll be the lead in that game. >> Dave: Guys, thanks so much for coming to the cube. Great show. Always fun at UiPath Forward. Really appreciate your time. Thank you. >> Thanks dave. >> Appreciate it as well. >> Okay wrap it up, day one, we're here tomorrow, first thing, Dave Vellante and Dave Nicholson. Thanks for watching, forward 5, Uipath big customer event, we'll see you tomorrow. (music)

>>Welcome back everyone to the cubes live coverage here in San Francisco for VMware Explorer. I'm John farer, Dave LAN two days of Wal three days of Wal Walker. Two sets live events got PERA, had Metabo, senior vice president and general manager of cloud management at VMware. I got it. Right. Thanks for coming on the queue. >>You got it right. Good to >>Be here. We're all smiles. Cause we were talking about your history. You once worked at loud cloud and we were reminiscent about how cloud was before cloud was even cloud. Exactly. And how, how hard it was. >>And >>It's still hard. Complexity is a big deal. And one of the segments we want to talk to you about is the announcement around aria and you see cloud manage a big part of this direction to multi-cloud yes. To tame the complexity. And you know, we were quoting Andy Grove on the cube, let chaos rain, and then rain in the chaos. Exactly. Okay. A very famous quote in tech and the theme here is cloud chaos. Yes. And so we're starting to see signs of raining in that chaos or solving complexity. And every major inflection point has this moment where yes, it gets so hard and then it kicks up to the right and grows and link gets solved. So we feel like we're in that moment. >>I couldn't agree more. And in fact, the way I say is our, our, our tagline is we make the complexity of managing cloud invisible so that you can focus on building your business apps. And you're right about the inflection point. Every time a new technology hits, you have some point of adoption and then it becomes insanely successful. And that's when the complexity hits, then you go and tame the complexity till the next technology hits. Right? That's what happens. It's happened with virtualization. Then it has happened with cloud then with containerization and now the next one will hit. And so with aria, we said, we have to fundamentally change the problem, right? We are constantly running a race of TAing, this complexity. So very excited about this announcement with which we're doing with aria. And we said, imagine if I could have a view of my environment and all the dependencies, I don't need to know everything, just the environment and its dependencies. Then I can now start solving problems and answering questions that I was unable to before. And newer technologies can keep coming and piling on, but I'll always be able to answer that, help >>Our audience understand Ari, a great name and, and what's new. Your Heka what's new from, you know, it's not just V V realize with a new name what's what's new specifically. >>Yeah. Please. No. >>Explain some people. Well, >>There's some commentary on snarky comments, but it's a product it's not a rebrand of something >>Else. It's right. It's not explain that. It's not a, yeah. So what we did is let, let me start off. Why, why we started aria? So we said, okay, native public managing environments, native public cloud environments and cloud native applications is a different ballgame, more Emeral workloads, very large scale, highly fragmented data. So we looked at that problem rounds up and said, we need to have a management solution that solves that problem focused on native public cloud and cloud native apps and the core to solving that problem was you can't just solve it for one cloud or you can't solve it for one discipline. When I say discipline, when you think about management, what do you manage? You're managing to optimize cost. You're managing to optimize performance. You're managing to optimize your security and you're managing to speed up the delivery. That is it. And so we said, we'll have a new look to this management. And what we have done with aria is we have introduced a brand new platform, which we call aria hub powered by aria graph, which allows you to deliver this man on this management challenges, by creating a map of your environment, a near real time map of your environment. And then we are able to, once we know what an application looks like and how it maps to the infrastructure, we can go and query other subsystems to tell you, what is the cost of an application? What is the performance of an application? Creating a common understanding >>This now it's a new architecture. >>I just wanted to get that out there. It's federated >>New graph database. >>Yes. It's a new architecture federated, a platform that not only gives you a map of your environment, but it federates into other sources to pull that data together. Right now, one of the data sources that it federates into is of course also we realize, yeah, yeah. Cloud health, >>You plug and >>Cloud observability. You plug everything into it. Yeah. And as part of the announcement, we didn't just announce a platform. We also announced a set of crosscutting solutions cuz we said, okay, what is the power of the platform? The big thing is it removes the swivel share management. It allows you to answer questions you couldn't answer before. And so >>Swivel share meaning going from one app to another one app logging in exactly >>Credentials in credentials. And you don't have a common understanding of app across those. So now you hire people who do integration buses, right? All kinds of cloud. So the three new end to end solutions we are announcing also in, along with the platform, these are brand new. One is something called aria guardrails. So when I have development environments today, for example, my, I do development on public cloud as well as private cloud. I have thousands of accounts, each one with its own security rules, each one with its own policies. After I initially deploy the account, it becomes a nightmare to manage that. So what aria guardrails allows you to do is set up these multi-cloud environments with the right policies. And not only is it about one time provisioning, but it is maintaining them on >>A run basis. And those credentials are also risk. Cuz you have a password on the dark web, that's exposed on one and you've got to change it. And, and there's so many things going on exactly on security, which brings me up to the point of, you know, we were talking, we're gonna see Tom later on security. We heard earlier, why wasn't security in the keynote? Oh, it's table stakes. That's what Z has said. But we're like, okay, I get that. So let's just say that security is table stakes. There's a big trend towards security as a state of something at a, at a given time. And that CSOs and CSOs are going to defensible. Yes. Meaning being defensible all the time. Yes. As an ongoing thing, which is not just running a pen test once a week. Yes. Like multiple testing, real testing. Not simulation. Yes. To be secure. Yes. So it's not about being secure. It's about having security, but defense ability is the action now not yeah. Yeah. >>Can >>You does that, how does that fit into this? Because this seems to like be in this wheelhouse of management. >>No, I think you're bringing a very important point, which is the security as a post. The fact item is no longer. Right? Right. You want to bake in security. This is a shift left of security that we talk about when you're building an application and you are deploying code in your test, you wanna say, Hey, what is the security? Is it secure? Is it meeting my guardrail? Then when you deploy it from an operations perspective, also it is a security concern. It's not just a security team's concern now. So is my configuration right? Is my configuration secure? Has, is it drifting? It's never a snapshot in time. It's constantly, you have to look at it. Is it drifting? And that is exactly what we are doing also with aria. So >>That's part of the solution you're talking about in the guardrails within being >>Able to maintain the secure configuration right now, as I said, there's always a security discipline. Yeah. Which is you are done by security teams, but you also want operations teams and development teams to enforce security in their respective practices. And that's what Ari allows you to do. >>So the question on multi-cloud comes in, okay. So this is all good. By the way, we love that shift left again, very developer. And I would argue actually we are argue on the cube. That dev ops is the development environment for cloud native. So the it operational once called ops is now in dev just saying he is, and then data ops and security ops are now the new it because that's where the hard problems are. So how do you look at the data side of it as well as security in your view of multi-cloud because you know, hybrid cloud, I can see the steady state between, you know, on premises and cloud, if it's operating cloudlike but now you're starting to look at spanning clouds. Yes. Yes. Not full spanning workloads. That's not there yet, but certainly people have multiple clouds. Yeah. But when you data seems to be the first thing spanning not necessarily the app itself, but how do you guys view that multi-cloud aspect of what you're managing? I mean, how you look at that? >>I think there are different angles to it. Right? You can look at it from the data angle and you look at it on how the, how protected a data is for us. When you look at management discipline, it is all from the perspective of configurations. Okay. If I have configured my environment correctly, then you should not be able to do something that destroys or the data. Right. So getting the configuration right. When you're developing that, getting the configuration right. When you're provisioning the app and then getting the configuration, right. Even when you're doing day two and ongoing operations, that is what we bring to the table. And to some extent, that aria visibility, that I was talking about an Ary graph, a near real time view of the configuration state and its dependencies is very critical. So now I can ask questions. Is there a misconfiguration, by the way, the answer is yes, they, yeah. >>That is a lot by the way, too, right? Yeah. >>Which, which exposes me. And then you can say, Hey, is there user activity associated with that misconfigured? Good object. Now suddenly you have go, go to a red alert. So not only something misconfigured, but there is user activity associated with the misconfigured data. You know, this is something that I have. This >>Is where AI sings beautifully because beautifully, once you have the configuration baseline done, yes. It's like securing the S3 bucket, which is like a knee has to be a like brushing your teeth. It's gotta be a habit. Exactly. It's like, you just don't even think about, you just don't leave an S3 bucket. >>It's gotta be simplified because you're, we're asking the devs now to be security pros, correct. Secure the run time, secure the paths, you know, secure the containers. And so they need help. This is not what they wake up in the morning passionate about. Right. >>But that is where the guardrails comes in. Totally. Yeah. So a a developer, why should they care? They should just say, look, I'm developing for the credit card industry. I need a PCI compliant environment. And then let us take care of defining that environment, deploying that environment, managing that environment on an ongoing basis, they should be building code. Yeah. Right. But there is a change also, which is in the past, these were like two different islands and two different views with aria graft. We also have created this unified API that a developer could query or an ops could query to create a common understanding of the environment. So you're not looking at, you know, the elephant won the trunk and the other one, the tail you're looking at it in a common way. >>Can you talk about the collaboration between tan zoo and aria portfolios? Because obviously the VMware customers are investing in tan zoo. A lot of stuff's coming outta the oven. We heard some Dave heard some stuff from Chris Wolf and he's gonna come on tomorrow. And Raghu was hinting at some other stuff. That's not yet public, but you know, this things happening, >>Things happening, lot of >>Things, you know, you know, announcements happened years ago last year. Now some fruit's coming off the tree, this is a hot product aria. It makes a lot of sense for the customers. Where's the cloud native stuff, kicking, connecting in. What's the give us the overview what's connection >>Is lots and lots of connections. So you have a beautiful Kubernetes environment and a cloud native platform. You have accelerated app development. Now you're building more apps, more microservices based apps, more fragmented data, more information. So think of aria as an envelope around all of this. So wherever you are, whether you are building an application, deploying an application, managing an application, retiring an application through that life cycle, we can bring that management. So what we are doing with Tansu is with the platform, develop and platform. Now we can hook in management with a common perspective earlier in the life cycle. I don't have to wait for it to go to production to start saying, is it secure? Is it configured? How is it performing? What is my cost trade off as a developer, I've decided to, to fix a latency issue, I'm gonna add a new region or I'm gonna scale out a particular tier. Do I know how much it'll cost me? Can I give you that right at your fingertips, potentially even within the development platform and within the ID, that's the power, right? So bringing Ary, >>Not a lot of heavy lifting on the develop. So it's pretty much almost like a query to a database or >>As simple API that they can just query as part of their development process. Yeah. So by bringing aria and Tansu and really aria en developing Tansu right. You're able to bring that power >>Developer. I just always smile because you, I remember we, we have a group called the cloud. AATI the early OG found cloud. >>AATI >>The early days of cloud. When we were talking about infrastructure as code yes. Way back when, and finally it's actually happening. So what you're describing is infrastructure's code because now there's more complexity happening under the hard and top and you know, service are being turned on and off automatically. Yes. And sometimes you might not even know what's going on. Exactly. If you have guard rail, >>But you have to discover the state, know something has turned on, understand the implication and then synthesize, synthesize it down to the insight for the user. >>You know, a lot of people have been complaining about other older companies. Like Splunks the world who have great logging technology for gen one cloud, but now these new logging logging becomes a problem. Can you talk about how you guys are handling that? Give confidence or yeah. Explain that there's everything's gonna be logged properly. Yeah. >>So, so really look, there are three disciplines that we have management. Discipl like, ultimately there are thousands of names, but it boils down to you're managing the cost. You're managing the security, you're managing the performance of your applications. That is it. Right. So what we found is when you think of these disciplines as siloed load solutions, you can't ask a simple question as what is my cost performance trade off. You can't ask a simple question as, Hey, I'm improving performance. How, what is the implication of security? And that's when you start building complex solutions that say, okay, let me collect log from here. Let me collect this from here. Then let me correlate and normalize an application definition and tell you something and then put it in a spreadsheet and put it in a spreadsheet finally for manual work. Exactly. So one of the pillars is about managing performance. >>We have very powerful capabilities today in our portfolio. Tansu observability, which is part of aria portfolio. We realize log, which is part of aria portfolio, networks, insights, and operations. So with the common, when you, when you have a common language, we have a common language. We understand each other. Similarly with Ary graph and aria hub, we have creating this common language. So once we create a common language, all the various observability and log solutions have a meaning. They have relevance. And so we are able to take the noise from all these systems and synthesize it down to what we call business insights. And that's what is one of the big announcement as part of aria, awesome take data, which we have lots of and convert it to information. >>Give us the bumper sticker on why VMware. >>Well, I I'll tell you, when you talk about various public clouds, each public cloud has their native solutions. I've got control tower, I've got cloud wash, cloud trail, different solutions, and some of the hyperscalers are also expanding their solutions to other cloud. I think VMware in a way, from a multi-cloud perspective, we are in a wonderfully neutral position. Not only do we have a wealth of technology and assets that we can bring to the game, but we can also do it evenly across all clouds. So, so look at something like cost. Do you trust one of the hyperscalers to tell you that what is the cost comparison between them and another hyperscaler? That is where the VMware value comes in? >>I think people just try to hear what the cost of one cloud. Exactly, exactly. That is often people make money doing that is a job. No, >>No, definitely. Even a single cloud. What is the cost? >>It's a cloud economist out there and we know who he is. Corey Corey, a friend of the cube. He does it for his living. So help people figure out their bill. Exactly. Just on one cloud. >>Exactly. It's one cloud. So being able, we have the unique position where, and the right sets of technologies and experiences to bring that solution to bear across multicloud. Right. Great. >>What's your vision real quick. One minute left. What's your vision for the group? What are you investing in? What's your goals? What are you trying to do? Ask you the products. New. Gonna roll that out. What's what's the plan. I >>Really, again, the biggest one, the, the, the tagline I talked about, right. I, I, I want to, you know, I'm telling customers, managing stuff is boring. Don't waste your time on it. Let us take care of it. Right? So make the cloud complexity invisible so that you can focus on building your applications and everything that we do in the business unit is targeted towards that one goal. It is not about doing more features, more capabilities. It's are you solving customers questions? And we start from question down, >>Be thank you for spending your valuable time here in the cube, explaining the new news. Appreciate it. All right. Get lunch. After the short breaks, stay more with the cube live here in San Francisco for VMware Explorer, 22. I'm John that's. Dave. >>Thank you.

>>Okay. We're back with Ari Basu, who is Cisco's resident philosopher, who also holds a master's in computer science. We're gonna have to unpack that a little bit and Najati chair he who's technical lead at Cisco. Welcome guys. Thanks for coming on the cube. >>Happy to be here. Thanks a >>Lot. All right, let's get into it. We want you to explain how Cisco validated the SBRI technology and the proof points that, that you have, that it actually works as advertised. So first Outre tell first, tell us about Cisco tech. What does Cisco tech do? >>So T is otherwise it's an acronym for technical assistance center is Cisco's support arm, the support organization, and, you know, the risk of sounding like I'm spotting a corporate line. The, the easiest way to summarize what tag does is provide world class support to Cisco customers. What that means is we have about 8,000 engineers worldwide, and any of our Cisco customers can either go on our web portal or call us to open a support request. And we get about 2.2 million of these support requests a year. And what these support requests are, are essentially the customer will describe something that they need done some networking goal that they have, that they wanna accomplish. And then it's tax job to make sure that that goal does get accomplished. Now, it could be something like they're having trouble with an existing network solution, and it's not working as expected, or it could be that they're integrating with a new solution. >>They're, you know, upgrading devices, maybe there's a hardware failure, anything really to do with networking support and, you know, the customer's network goals. If they open up a case for request for help, then tax job is to, is to respond and make sure the customer's, you know, questions and requirements are met about 44% of these support requests are usually trivial and, you know, can be solved within a call or within a day. But the rest of tax cases really involve getting into the network device, looking at logs. It's a very technical role. It's a very technical job. You're look you're, you need to be conversing with network solutions, their designs protocols, et cetera. >>Wow. So 56% non-trivial. And so I would imagine you spend a lot of time digging through through logs. Is that, is that true? Can you quantify that like, you know, every month, how much time you spend digging through logs and is that a pain point? >>Yeah, it's interesting. You asked that because when we started this on this journey to augment our support engineers workflow with zebra solution, one of the things that we did was we went out and asked our engineers what their experience was like doing log analysis. And the anecdotal evidence was that on average, an engineer will spend three out of their eight hours reviewing logs, either online or offline. So what that means is either with the customer live on a WebEx, they're going to be going over logs, network, state information, et cetera, or they're gonna do it offline, where the customer sends them the logs, it's attached to a, you know, a service request and they review it and try to figure out what's going on and provide the customer with information. So it's a very large chunk of our day. You know, I said 8,000 plus engineers, and so three hours a day, that's 24,000 man hours a day spent on long analysis. >>Now the struggle with logs or analyzing logs is there by out of necessity. Logs are very contr contr. They try to pack a lot of information in a very little space. And this is for performance reasons, storage reasons, et cetera, BEC, but the side effect of that is they're very esoteric. So they're hard to read if you're not conversant, if you're not the developer who wrote these logs or you or you, aren't doing code deep dives. And you're looking at where this logs getting printed and things like that, it may not be immediately obvious or even after a low while it may not be obvious what that log line means or how it correlates to whatever problem you're troubleshooting. So it requires tenure. It requires, you know, like I was saying before, it requires a lot of knowledge about the protocol what's expected because when you're doing log analysis, what you're really looking for is a needle in a haystack. You're looking for that one anomalous event, that single thing that tells you this shouldn't have happened. And this was a problem right now doing that kind of anomaly detection requires you to know what is normal. It requires, you know, what the baseline is. And that requires a very in-depth understanding of, you know, the state changes for that network solution or product. So it requires time, tenure and expertise to do well. And it takes a lot of time even when you have that kind of expertise. >>Wow. So thank you, archery. And Najati, that's, that's about, that's almost two days a week for, for a technical resource. That's that's not inexpensive. So what was Cisco looking for to sort of help with this and, and how'd you stumble upon zebra? >>Yeah, so, I mean, we have our internal automation system, which has been running more than a decade now. And what happens is when a customer attaches a log bundle or diagnostic bundle into the service request, we take that from the Sr we analyze it and we represent some kind of information. You know, it can be alert or some tables, some graph to the engineer, so they can, you know, troubleshoot this particular issue. This is an incredible system, but it comes with its own challenges around maintenance to keep it up to date and relevant with Cisco's new products or new version of the product, new defects, new issues, and all kind of things. And when I, what I mean with those challenges are, let's say Cisco comes up with a product today. We need to come together with those engineers. We need to figure out how this bundle works, how it's structured out. >>We need to select individual logs, which are relevant and then start modeling these logs and get some values out of those logs, using pars or some rag access to come to a level that we can consume the logs. And then people start writing rules on top of that abstraction. So people can say in this log, I'm seeing this value together with this other value in another log, maybe I'm hitting this particular defect. So that's how it works. And if you look at it, the abstraction, it can fail the next time. And the next release when the development or the engineer decides to change that log line, which you write that rag X, or we can come up with a new version, which we completely change the services or processes, then whatever you have wrote needs to be re written for that new service. And we see that a lot with products, like for instance, WebEx, where you have a very short release cycle that things can change maybe the next week with a new release. >>So whatever you are writing, especially for that abstraction and for those rules are maybe not relevant with that new release. With that being sake, we have a incredible rule creation process and governance process around it, which starts with maybe a defect. And then it takes it to a level where we have an automation in place. But if you look at it, this really ties to human bandwidth. And our engineers are really busy working on, you know, customer facing, working on issues daily and sometimes creating these rules or these pars are not their biggest priorities, so they can be delayed a bit. So we have this delay between a new issue being identified to a level where we have the automation to detect it next time that some customer faces it. So with all these questions and with all challenges in mind, we start looking into ways of actually how we can automate these automations. >>So these things that we are doing manually, how we can move it a bit further and automate. And we had actually a couple of things in mind that we were looking for and this being one of them being, this has to be product agnostic. Like if Cisco comes up with a product tomorrow, I should be able to take it logs without writing, you know, complex regs, pars, whatever, and deploy it into this system. So it can embrace our logs and make sense of it. And we wanted this platform to be unsupervised. So none of the engineers need to create rules, you know, label logs. This is bad. This is good. Or train the system like which requires a lot of computational power. And the other most important thing for us was we wanted this to be not noisy at all, because what happens with noises when your level of false PE positives really high your engineers start ignoring the good things between that noise. >>So they start the next time, you know, thinking that this thing will not be relevant. So we want something with a lot or less noise. And ultimately we wanted this new platform or new framework to be easily adaptable to our existing workflows. So this is where we started. We start looking into the, you know, first of all, internally, if we can build this thing and also start researching it, and we came up to Zeum actually Larry, one of the co co-founders of Zeum. We came upon his presentation where he clearly explained why this is different, how this works, and it immediately clicked in. And we said, okay, this is exactly what we were looking for. We dived deeper. We checked the block posts where SBRI guys really explained everything very clearly there, they are really open about it. And most importantly, there is a button in their system. >>So what happens usually with AI ML vendors is they have this button where you fill in your details and sales guys call you back. And, you know, we explain the system here. They were like, this is our trial system. We believe in the system, you can just sign up and try it yourself. And that's what we did. We took our, one of our Cisco live DNA center, wireless platforms. We start streaming logs out of it. And then we synthetically, you know, introduce errors, like we broke things. And then we realized that zebra was really catching the errors perfectly. And on top of that, it was really quiet unless you are really breaking something. And the other thing we realized was during that first trial is zebra was actually bringing a lot of context on top of the logs. During those failures, we work with couple of technical leaders and they said, okay, if this failure happens, I I'm expecting this individual log to be there. And we found out with zebra, apart from that individual log, there were a lot of other things which gives a bit more context around the root columns, which was great. And that's where we wanted to take it to the next level. Yeah. >>Okay. So, you know, a couple things to unpack there. I mean, you have the dart board behind you, which is kind of interesting, cuz a lot of times it's like throwing darts at the board to try to figure this stuff out. But to your other point, Cisco actually has some pretty rich tools with AppD and doing observability and you've made acquisitions like thousand eyes. And like you said, I'm, I'm presuming you gotta eat your own dog food or drink your own champagne. And so you've gotta be tools agnostic. And when I first heard about Z zebra, I was like, wait a minute. Really? I was kind of skeptical. I've heard this before. You're telling me all I need is plain text and, and a timestamp. And you got my problem solved. So, and I, I understand that you guys said, okay, let's run a POC. Let's see if we can cut that from, let's say two days a week down to one day, a week. In other words, 50%, let's see if we can automate 50% of the root cause analysis. And, and so you funded a POC. How, how did you test it? You, you put, you know, synthetic, you know, errors and problems in there, but how did you test that? It actually works Najati >>Yeah. So we, we wanted to take it to the next level, which is meaning that we wanted to back test is with existing SARS. And we decided, you know, we, we chose four different products from four different verticals, data center, security, collaboration, and enterprise networking. And we find out SARS where the engineer put some kind of log in the resolution summary. So they closed the case. And in the summary of the Sr, they put, I identified these log lines and they led me to the roots and we, we ingested those log bundles. And we, we tried to see if Zeum can surface that exact same log line in their analysis. So we initially did it with archery ourself and after 50 tests or so we were really happy with the results. I mean, almost most of them, we saw the log line that we were looking for, but that was not enough. >>And we brought it of course, to our management and they said, okay, let's, let's try this with real users because the log being there is one thing, but the engineer reaching to that log is another take. So we wanted to make sure that when we put it in front of our users, our engineers, they can actually come to that log themselves because, you know, we, we know this platform so we can, you know, make searches and find whatever we are looking for, but we wanted to do that. So we extended our pilots to some selected engineers and they tested with their own SRSS. Also do some back testing for some SARS, which are closed in the past or recently. And with, with a sample set of, I guess, close to 200 SARS, we find out like majority of the time, almost 95% of the time the engineer could find the log they were looking for in zebra analysis. >>Yeah. Okay. So you were looking for 50%, you got to 95%. And my understanding is you actually did it with four pretty well known Cisco products, WebEx client DNA center, identity services, engine ISE, and then, then UCS. Yes. Unified pursuit. So you use actual real data and, and that was kind of your proof proof point, but Ari. So that's sounds pretty impressive. And, and you've have you put this into production now and what have you found? >>Well, yes, we're, we've launched this with the four products that you mentioned. We're providing our tech engineers with the ability, whenever a, whenever a support bundle for that product gets attached to the support request. We are processing it, using sense and then providing that sense analysis to the tech engineer for their review. >>So are you seeing the results in production? I mean, are you actually able to, to, to reclaim that time that people are spending? I mean, it was literally almost two days a week down to, you know, a part of a day, is that what you're seeing in production and what are you able to do with that extra time and people getting their weekends back? Are you putting 'em on more strategic tasks? How are you handling that? >>Yeah. So, so what we're seeing is, and I can tell you from my own personal experience using this tool, that troubleshooting any one of the cases, I don't take more than 15 to 20 minutes to go through the zebra report. And I know within that time either what the root causes or I know that zebra doesn't have the information that I need to solve this particular case. So we've definitely seen, well, it's been very hard to measure exactly how much time we've saved per engineer, right? What we, again, anecdotally, what we've heard from our users is that out of those three hours that they were spending per day, we're definitely able to reclaim at least one of those hours and, and what, even more importantly, you know, what the kind of feedback that we've gotten in terms of, I think one statement that really summarizes how Zebra's impacted our workflow was from one of our users. >>And they said, well, you know, until you provide us with this tool, log analysis was a very black and white affair, but now it's become really colorful. And I mean, if you think about it, log analysis is indeed black and white. You're looking at it on a terminal screen where the background is black and the text is white, or you're looking at it as a text where the background is white and the text is black, but what's what they're really trying to say. Is there hardly any visual cues that help you navigate these logs, which are so esoteric, so dense, et cetera. But what XRM does is it provides a lot of color and context to the whole process. So now you're able to quickly get to, you know, using their word cloud, using their interactive histogram, using the summaries of every incident. You're very quickly able to summarize what might be happening and what you need to look into. >>Like, what are the important aspects of this particular log bundle that might be relevant to you? So we've definitely seen that a really great use case that kind of encapsulates all of this was very early on in our experiment. There was, there was this support request that had been escalated to the business unit or the development team. And the tech engineer had really, they, they had an intuition about what was going wrong because of their experience because of, you know, the symptoms that they'd seen. They kind of had an idea, but they weren't able to convince the development team because they weren't able to find any evidence to back up what they thought was happening. And we, it was entirely happenstance that I happened to pick up that case and did an analysis using Seebri. And then I sat down with the attack engineer and we were very quickly within 15 minutes, we were able to get down to the exact sequence of events that highlighted what the customer thought was happening, evidence of what the, so not the customer, what the attack engineer thought was the, was a root cause. It was a rude pause. And then we were able to share that evidence with our business unit and, you know, redirect their resources so that we could change down what the problem was. And that really has been, that that really shows you how that color and context helps in log analysis. >>Interesting. You know, we do a fair amount of work in the cube in the RPA space, the robotic process automation and the narrative in the press when our RPA first started taking off was, oh, it's, you know, machines replacing humans, or we're gonna lose jobs. And, and what actually happened was people were just eliminating mundane tasks and, and the, the employee's actually very happy about it. But my question to you is, was there ever a reticence amongst your team? Like, oh, wow, I'm gonna, I'm gonna lose my job if the machine's gonna replace me, or have you found that people were excited about this and what what's been the reaction amongst the team? >>Well, I think, you know, every automation and AI project has that immediate gut reaction of you're automating away our jobs and so forth. And there is initially there's a little bit of reticence, but I mean, it's like you said, once you start using the tool, you realize that it's not your job, that's getting automated away. It's just that your job's becoming a little easier to do, and it's faster and more efficient. And you're able to get more done in less time. That's really what we're trying to accomplish here at the end of the day, rim will identify these incidents. They'll do the correlation, et cetera. But if you don't understand what you're reading, then that information's useless to you. So you need the human, you need the network expert to actually look at these incidents, but what we are able to skin away or get rid of is all of the fat that's involved in our, you know, in our process, like without having to download the bundle, which, you know, when it's many gigabytes in size, and now we're working from home with the pandemic and everything, you're, you know, pulling massive amounts of logs from the corporate network onto your local device that takes time and then opening it up, loading it in a text editor that takes time. >>All of these things are we're trying to get rid of. And instead we're trying to make it easier and quicker for you to find what you're looking for. So it's like you said, you take away the mundane, you take away the, the difficulties and the slog, but you don't really take away the work, the work still needs to be done. >>Yeah. Great guys. Thanks so much. Appreciate you sharing your story. It's quite, quite fascinating. Really. Thank you for coming on. >>Thanks for having us. >>You're very welcome. Okay. In a moment, I'll be back to wrap up with some final thoughts. This is Dave Valante and you're watching the, >>So today we talked about the need, not only to gain end to end visibility, but why there's a need to automate the identification of root cause problems and doing so with modern technology and machine intelligence can dramatically speed up the process and identify the vast majority of issues right out of the box. If you will. And this technology, it can work with log bundles in batches, or with real time data, as long as there's plain text and a timestamp, it seems Zebra's technology will get you the outcome of automating root cause analysis with very high degrees of accuracy. Zebra is available on Preem or in the cloud. Now this is important for some companies on Preem because there's really some sensitive data inside logs that for compliance and governance reasons, companies have to keep inside their four walls. Now SBRI has a free trial. Of course they better, right? So check it out@zebra.com. You can book a live demo and sign up for a free trial. Thanks for watching this special presentation on the cube, the leader in enterprise and emerging tech coverage on Dave Valante and.

>>Hi, I'm Branch Ari >>and I'm the global Portfolio, part of marketing manager for IBM Data Integration. I'm through to invite you today, your data offs crowdchat event where we will learn about how IBM data integration is one of the white well building blocks for data ops and delivers a multi cloud data >>integration solution >>to accelerate our >>client's journey to AI. Join us on May 27 where IBM and find leaders who follow the data ops methodology and are implementing this technology supported really an interactive session. >>How did you can do today?

from the cube studios in Palo Alto in Boston connecting with thought leaders all around the world this is a cube conversation hello everyone welcome to the cube conversation here in Palo Alto our studios of the cube I'm showing for your host we're here during the crisis of Cove in nineteen doing remote interviews I come into the studio we've got a quarantine crew or here getting the interviews getting the stories out there and of course the story we continue to talk about is the impact of Kovan 19 and how we're all getting back to work either working at home or working remotely and virtually certainly but as things start to change we can start to see events mostly digital events and we're here to talk about an event that's coming up called the failover conference from gremlin which is now gone digital because it's April 21st but I think what's important about this conversation that I want to get into is not only talk about the event that's coming up but talk about these scale problems that are being highlighted by this change in work environment working at home we've been talking about the at scale problems that we're seeing whether it's a flood of surge of traffic and the chaos that's ensuing across the world with this pandemic so I'm excited have two great guests Alberto Ferran auto senior vice president marketing gremlin and Tammy Bhutto principal site reliability engineer or SRE guys thanks for coming on appreciate it thank you Thank You Alberto I want to get to you first you know we've known each other before you've been in this industry we all we've been all been talking about the cloud native cloud scale for some time it's kind of inside the ropes it's inside baseball Tami your site reliability engineer everyone knows Google knows how well cloud works this is large-scale stuff now with The Cove in 19 we're starting to see the average person my brother my sister our family members and people around the world go oh my god this is really a high impact this change of behavior the surge of you know whether whether it's traffic on the internet or work at home tools that are inadequate you start to see these statistical things that were planned for not working well and this actually Maps the things that we've been talking about it in our industry Alberto you've been on this how you guys doing and what's your what's your take on this situation we're in right now yeah yeah we're we're doing pretty well as a company we were born as a distributed organization to begin with so for us working in a distributed environment from all over the world is is common practice day-to-day personally you know I'm originally from Italy my parents my family is Milan and Bergen audible places so I have to follow the news with extra care and so much in me it becomes so much clearer nowadays that technology is not just a powerful tool to enable our businesses but it also is so critical for our day-to-day life and thanks to you know video calls I can easily talk to my family back there every day Wow so that's that's really important so yes we've been talking for a long time as you mentioned about complex systems at scale and reliability often in the context of mission-critical applications but more and more these systems need to be reliable also when it comes to back office systems that enable people to continue to work on a daily basis yeah well our hearts go out to your family and your friends in Italy and hope everyone's stay safe there no that was a tough situation continues to be a challenge Tammy I want to get your thoughts how is life going for you you're a sight reliable engineer what you deal with on the tech side is now happening in the real world it's it's almost it's mind-blowing and to me that we're seeing these these things happen it's it's a paradigm that needs attention and whew look at it as a sre dealing a most from a tech side now seeing it play out in real life it's such an interesting situation really terrible so one of the things that I specialize in as a site reliability engineer is incident management and so for example I previously worked at Dropbox where I was you know the incident manager on call for 500 million customers you know it's like 24/7 and these large-scale incidents you really need to be able to act fast there are two very important metrics that we track and care about as a site reliability engineer the first one is mean time to detection how fast can you detect what something is happening obviously if you detect an issue faster and you've got a better chance of making the impact lower so you can contain the blast radius I like to explain it to people like if you have a fire in your sauce bin in your kitchen and you put it out that's way better than waiting until your entire house is on fire and the other metric is mean time to resolution so how long does it take you to recover from the situation so yeah this is a large-scale global incident right now that we're in yeah I know you guys do a lot of talk about chaos theory and that applies a lot of math involved we all know that but I think when you go look at the real world this is gonna be table stakes and you know there's now a line in the sand here you know pre-pandemic post pandemic and i think you guys have an interesting company gremlin in the sense that this is this is a complex system and if you think about the world we're going to be living in whether it's digital events that you guys are have one coming up or how to work at home or tools that humans are going to be using it's going to be working with systems right so you have this new paradigm gonna be upon us pretty quickly and it's not just buying software mechanisms or software it's a complex system it's distributed computing and operating so I mean this is kind of the world can you guys talk about the gremlin situation of how you guys are attacking these new problems and these new opportunities that are emerging one of the things that I've always specialized in over the last 10 years is chaos engineering and so the idea of chaos engineering is that you're injecting failure on purpose to uncover weaknesses so that's really important in distributed systems with distributed you know cloud computing all these different services that you're kind of putting together but the idea is if you can inject failure you can actually figure out what happens when I inject that small failure and then you can actually go ahead and fix it one of the things I like to say to people is you know focus on what your top 5 critical systems are let's fix those first don't go for low-hanging fruit fix the biggest problems first get rid of the biggest amount of pain that you have as a company and then you can go ahead and like actually if you think about Pareto principle the 80/20 rule if you fix 20% of your biggest problems you actually solve 80% of your issues that always works something that I've done while working at National Australia Bank doing chaos engineering also what gremlin at Dropbox and I help a lot of our customers do that to albariño talk about the mindset involved it's almost counterintuitive whoa-oh-oh risk the biggest system and I don't want to touch those there working fine right now and then these problems just gestate they kind of hang around to the bin in the kitchen fire you know mist okay I don't want to touch it the house is still working so this is kind of a new mindset could you talk about what your take is on that is the industry there I mean oh it was a kind of a corner case you know you had Netflix you had the chaos monkey those days and then now it's the DevOps practice for a lot of folks you guys are involved in that what's the what's the appetite what's the progress of chaos engineering and mainstream yeah it's interesting that you mentioned DevOps and you know recently Gartner came up with a new revisited devil scream work that has chaos engineering in the middle of the lifecycle of your application and the reality is that systems have become so complex in infrastructure so many layers of abstractions you have hundreds of services if you're doing micro services but even if you're not doing micro services you have so many applications connected to each other build really complex workflows and automation flows it's impossible for traditional QA to really understand well the vulnerability are in terms of resiliency in terms of quality too often the production environment is also too different from the staging environment and so you need a fundamentally different approach to go and find where your weaknesses are and find them before they happen before you end up finding yourself in a situation like the one we're in today and you're not prepared and so much of what we talk about is giving it >> and the methodology for people to go and find these vulnerabilities not so much about creating cause chaos but it's about managing sales that is built into our current system and exposing those vulnerabilities before they create problem and so that's a very scientific methodology and and and tooling that we would bring to market and we help customers with Tammy I want to get your thoughts on so you know we used to riff a lot of to our 10th you know cube we've had a lot of conversation we've ripped over the over the years but you know when the surge of Amazon Web Services came out as pretty obvious the clouds amazing and look at the startups that were born you mentioned Dropbox you work there these comings and all these born in the cloud these hyper scale comes built from scratch great way to scale up and we used to joke about Google people say I would like a cloud like Google but no one has Google's use cases and Google really pioneered the sre concept and you gotta give them a lot of props for that but now we're kind of getting to a world where it's becoming Google like there's more scale now than ever before it's not a corner case it's becoming more popular and more of a preferred architecture this large scale what's your assessment of the of the mainstream enterprises how far are they did in your mind our way are they there with Castle they clothed how they doing it how does someone take how does someone develop an SRE practice to get the Google like scale because Google has an amazing network they got large-scale cloud they have sres they've been doing it for years how does a company that's transforming their IT have expertise it's a great question I get asked this a lot as well one of our goals at Bremen is to help make Internet more reliable for everybody everyone using the Internet all of the engineers who are trying to build reliable services and so I'm often asked by you know companies all over the world how do we create an SRE practice and how do we practice chaos engineering and so actually how you can get started actually rolling out your sre program based on my experiences I've done it so when I worked at Dropbox I worked with a lot of people who had been at Google they've been at YouTube they were there when was rolled out across those companies and then they brought those learnings to Dropbox and I learned from them but also the interesting thing is if you look at enterprise companies so large banks say for example I worked at a National Australia Bank for six years we actually did a lot of work that I would consider chaos engineering and sre practices so for example we would do large-scale disaster recovery and that's where you fail over an entire data center to a secret data center in an unknown location and the reason is because you're checking to make sure that everything operates okay if there's a nuclear blast that's actually what you have to do and you have to do that practice every quarter so but but if you think about it it's not very good to only do it once a quarter you really want to be practicing chaos engineering and injecting failure on this I think actually my I prefer to do it three times a week do I do it a lot but I'm also someone who likes to work out a lot and be fit all the time so I know that do something regularly you get great results so that's what I always tell us yeah I get the reps in as we say you know get get stronger at the muscle memory guys talk about the event that's coming up you got an event that was schedules physical event and then you were right in the planning mode and then the crisis hits you going digital going virtual it's really digital but it's digital that's on the internet so how are you guys thinking about this I know I it's out there it's April 21st can you share some specifics around the event well who should be attending and how they get involved online yeah yeah they vent really came about about together about a month ago when we started to see all the cancellations happening across the industry because of code 19 and we are extremely engaged with in the community and we have a lot of talks and we are seeing a lot of conferences just dropping and so speakers losing their opportunity to share their knowledge with respect to how you do reliability and topics that we focus on and so we quickly people it as a company and created a new online event to give everyone in the community the opportunity to you know they'll over to a new event as the president as a as the conference name says and and have those speakers will have lost their speaking slots have a new opportunity to go share their knowledge and so that came together really quickly we share the idea with a dozen of our partners and everyone liked it and all the sudden this thing took off like crazy in just a month where we are approaching you know four thousand registrations we have over 30 partners signed up and supporting the initiative a lot of a lot of past partners as well covering the event so it was impressive to see the amount of interest that that we were able to generate in such a short amount of time and really this is a conference for anybody who is interested in resilience and if you want to know from the best on how to build business continuity of persistence people and processes this is a great opportunity at no cost we need some free conference and the target persona and the audience you want to have a ten is what Sree Zoar folks doing architectural work and what's that that's the target yes and to attend our cadets s Ari's developers business leaders who care about the quality and reliability of their applications who need to help create a framework and a mindset for their organization that speaks to what Tammy was saying a minute ago having that constant crap is on a daily basis about who and finding how to improve things you know Tammy we've been doing going to physical events with the cube and extracting the signal of the noise and distributing it digitally for ten years and I got to ask you because now that those are those events have gone away you talk about chaos and injecting failure these doing these digital events is not as easy it's just live streaming it's it's hard to replicate the value of a physical event years of experience and standards roles and responsibilities to digital different consumption environments a synchronous you're trying to create a synchronous environment it's its own complex system so I think a lot of people are experimenting and learning from these events because it's pretty chaotic so I'd love to get your thoughts on how you look at these digital events as a chaos engineer how should people be looking at these events how are you I was looking at it you know I also want to get the program going get people out there get the content but you have to iterate on this how do you view this it is really different so I actually like to compare it to fire drills in SRA so often what you do there is you actually create a fake incident or a fake issue so you just you know you're saying let's have a fire drill similar to like you know when you're in a building and you have a fire drill that goes off you have wardens and everything and you all have to go outside so we can do that in this new world that we're all in all of a sudden you know a lot of people have never run an online event and now all of a sudden they have to so what I would say is like do a fire drill um run up you know a baked one before you do the actual on one to make sure that everything does work okay my other tip is make sure that you have backup plans backup plans on backup plans on backup plans like as in SRA I always have at least three to five backup plans like I'm not just saying plan a and Plan B but there's also a C D and E and I think that's very important and you know even when you're considering technology one of the things we say with chaos engineering is you know if you're using one service inject failure and make sure that you can fail over to a different alternative service in case something goes wrong yeah hence the failover conference which is the name of the conference yeah yeah well we certainly are gonna be sending a digital reporter there virtually if you need any backup plans obviously we have the remote interviews here if you need any help let us know really appreciate it I'll great to see you guys and thanks for sharing any final thoughts on the conference how what what happens when we get through the other side of this I'll give you guys a final word we'll start with Alberto with you first yeah I think one when we are on the other side of this will will understand even more the importance of effective resilience architecting and and and testing I think you know as a provider of tools and methodologies for that we we think we will be able to help customers do we do a significant leap forward on that side and the conference is just super exciting I think it's going to be a great I encourage everyone to participate we have tremendous lineup of speakers that have incredible reputation in their fields so I'm really happy and and excited about the work that the team has being able to do with our partners put together this type of event okay Tammy yes ma'am I'm actually going to be doing the opening keynote for the conference and the topic that I'm speaking about is that reliability matters more now than ever and I'll be sharing some you know bizarre weird incidents that I've worked on myself that I've experienced you know really critical strange issues that have come up but yeah I just I'm really looking forward to sharing that with everybody else so please come along it's free you can join from your own home and we can all be there together to support each other you got a great community support and there's a lot of partners press media and an ecosystem and customers so congratulations gremlin having a conference on April 21st called the failover conference the qubits look at angle we'll have a digital reporter there we covering the news thanks for coming on and sharing and appreciate the time I'm Jeff we're here in the Palo Alto series with remote interview with gremlin around there failover conference April 21st it's really demonstrating in my opinion the at scale problems that we've been working on the industry now more applicable than ever before as we get post pandemic with kovin 19 thanks for watching be back [Music]

>>live from Stanford University. It's the queue covering Stanford women in data science 2020. Brought to you by Silicon Angle Media. >>Yeah, yeah. Hi. And welcome to the Cube. I'm your host, Sonia Atari. And we're live at Stanford University, covering the fifth annual Woods Women in Data Science Conference. Joining us today is Lillian Kearse. Keo, who's the Insights manager at Spotify. Slowly and welcome to the Cube. Thank you so much for having me. So tell us a little bit about your role at a Spotify. >>Yeah, So I'm actually one of the few insights managers in the personalization team. Um, and within my little group, we think about data and algorithms that help power the larger personalization experiences throughout Spotify. So, from your limits to discover weekly to your year and wrap stories to your experience on home and the search results, that's >>awesome. Can you tell us a little bit more about the personalization? Um, team? >>Yes. We actually have a variety of different product areas that come together to form the personalization mission, which is the mission is like the term that we use for a big department at Spotify, and we collaborate across different product areas to understand what are the foundational data sets and the foundational machine learning tools that are needed to be able to create features that a user can actually experience in the app? >>Great. Um, and so you're going to be on the career panel today? How do you feel about that? I'm >>really excited. Yeah, Yeah, the would seem is in a great job of bringing together Diverse is very, uh, it's overused term. Sometimes they're a very diverse group of people with lots of different types of experiences, which I think is core. So how I think about data science, it's a wide definition. And so I think it's great to show younger and mid career women all of the different career paths that we can all take. >>And what advice would you would you give to? Women were coming out of college right now about data science. >>Yeah, so my my big advice is to follow your interests. So there's so many different types of data science problems. You don't have to just go into a title that says data scientists or a team that says Data scientist, You can follow your interest into your data science. Use your data science skills in ways that might require a lot of collaboration or mixed methods, or work within a team where there are different types of different different types of expertise coming together to work on problems. >>And speaking of mixed methods, insights is a team that's a mixed methods research groups. So tell us more about that. Yes, I >>personally manage a data scientist, Um, user researcher and the three of us collaborate highly together across their disciplines. We also collaborate across research science, the research science team right into the product and engineering teams that are actually delivering the different products that users get to see. So it's highly collaborative, and the idea is to understand the problem. Space deeply together, be able to understand. What is it that we're trying to even just form in our head is like the need that a user work and human and user human has, um, in bringing in research from research scientists and the product side to be able to understand those needs and then actually have insights that another human, you know, a product owner you can really think through and understand the current space and like the product opportunities >>and to understand that user insight do use a B testing. >>We use a lot of >>a B testing, so that's core to how we think about our users at Spotify. So we use a lot of a B testing. We do a lot of offline experiments to understand the potential consequences or impact that certain interventions can have. But I think a B testing, you know, there's so much to learn about best practices there and where you're talking about a team that does foundational data and foundational features. You also have to think about unintended or second order effects of algorithmic a B test. So it's been just like a huge area of learning in a huge area of just very interesting outcomes. And like every test that we run, we learn a lot about not just the individual thing. We're testing with just the process overall. >>And, um, what are some features of Spotify that customers really love anything? Anything >>that's like we know use a daily mix people absolutely love every time that I make a new friend and I saw them what they work on there like I was just listening to my daily makes this morning discover weekly for people who really want >>to stay, >>you know, open to new music is also very popular. But I think the one that really takes it is any of the end of year wrapped campaigns that we have just the nostalgia that people have, even just for the last year. But in 2019 we were actually able to do 10 years, and that amount of nostalgia just went through the roof like people were just like, Oh my goodness, you captured the time that I broke up with that, you >>know, the 1st 5 years ago, or just like when I discovered that I love Taylor Swift, even though I didn't think I like their or something like that, you know? >>Are there any surprises or interesting stories that you have about, um, interesting user experiences? Yeah. >>I mean, I could give I >>can give you an example from my experience. So recently, A few a few months ago, I was scrolling through my home feed, and I noticed that one of the highly rated things for me was women in >>country, and I was like, Oh, that's kind of weird. I don't consider >>myself a country fan, right? And I was like having this moment where I went through this path of Wait, That's weird. Why would Why would this recommend? Why would the home screen recommend women in country, country music to me? And then when I click through it, um, it would show you a little bit of information about it because it had, you know, Dolly Parton. It had Margo Price and it had the high women and those were all artistes. And I've been listening to a lot, but I just had not formed an identity as a country music. And then I click through It was like, Oh, this is a great play list and I listen to it and it got me to the point where I was realizing I really actually do like country music when the stories were centered around women, that it was really fun to discover other artists that I wouldn't have otherwise jumped into as well. Based on the fact that I love the story writing and the song, writing these other country acts that >>so quickly discovered that so you have a degree in industrial mathematics, went to a liberal arts college on purpose because you want to try out different classes. So how is that diversity of education really helped >>you in your Yes, in my undergrad is from Smith College, which is a liberal arts school, very strong liberal arts foundation. And when I went to visit, one of the math professors that I met told me that he, you know, he considers studying math, not just to make you better at math, but that it makes you a better thinker. And you can take in much more information and sort of question assumptions and try to build a foundation for what? The problem that you're trying to think through is. And I just found that extremely interesting. And I also, you know, I haven't undeclared major in Latin American studies, and I studied like neuroscience and quantum physics for non experts and film class and all of these other things that I don't know if I would have had the same opportunity at a more technical school, and I just found it really challenging and satisfying to be able to push myself to think in different ways. I even took a poetry writing class I did not write good poetry, but the experience really stuck with me because it was about pushing myself outside of my own boundaries. >>And would you recommend having this kind of like diverse education to young women now who are looking >>and I absolutely love it? I mean, I think, you know, there's some people believe that instead of thinking about steam, we should be talking instead of thinking about stem. Rather, we should be talking about steam, which adds the arts education in there, and liberal arts is one of them. And I think that now, in these conversations that we have about biases in data and ML and AI and understanding, fairness and accountability, accountability bitterly, it's a hardware. Apparently, I think that a strong, uh, cross disciplinary collaborative and even on an individual level, cross disciplinary education is really the only way that we're gonna be able to make those connections to understand what kind of second order effects for having based on the decisions of parameters for a model. In a local sense, we're optimizing and doing a great job. But what are the global consequences of those decisions? And I think that that kind of interdisciplinary approach to education as an individual and collaboration as a team is really the only way. >>And speaking about bias. Earlier, we heard that diversity is great because it brings out new perspectives, and it also helps to reduce that unfair bias. So how it Spotify have you managed? Or has Spotify managed to create a more diverse team? >>Yeah, so I mean, it starts with recruiting. It starts with what kind of messaging we put out there, and there's a great team that thinks about that exclusively. And they're really pushing all of us as managers. As I seizes leaders to really think about the decisions in the way that we talk about things and all of these micro decisions that we make and how that creates an inclusive environments, it's not just about diversity. It's also about making people feel like this is where they should be. On a personal level, you know, I talk a lot with younger folks and people who are trying to just figure out what their place is in technology, whether it be because they come from a different culture, >>there are, >>you know, they might be gender, non binary. They might be women who feel like there is in a place for them. It's really about, You know, the things that I think about is because you're different. Your voice is needed even more. You know, like your voice matters and we need to figure out. And I always ask, How can I highlight your voice more? You know, how can I help? I have a tiny, tiny bit of power and influence. You know, more than some other folks. How can I help other people acquire that as well? >>Lilian, thank you so much for your insight. Thank you for being on the Cube. Thank you. I'm your host, Sonia today. Ari. Thank you for watching and stay tuned for more. Yeah, yeah.

>>live from Stanford University. It's the queue covering Stanford women in data Science 2020. Brought to you by Silicon Angle Media. >>Hi, and welcome to the Cube. I'm your host, Sonia today, Ari. And we're live at Stanford University covering wigs, Women in Data Science Conference 2020 And this is the fifth annual one. Joining us today is John Hoegger, who is the principal data scientist manager at Microsoft. John. Welcome to the Cube. Thanks. So tell us a little bit about your role at Microsoft. >>I manage a central data science team for myself. 3 65 >>And tell us more about what you do on a daily basis. >>Yeah, so we look at it across all the different myself. 365 products Office Windows security products has really try and drive growth, whether it's trying to provide recommendations to customers to end uses to drive more engagement with the products that they use every day. >>And you're also on the Weeds Conference Planning Committee. So tell us about how you joined and how that experience has been like, >>Yeah, actually, I was at Stanford about a week after the very first conference on. I got talking to Karen, one of this co organizers of that that conference and I found out there was only one sponsor very first year, which was WalMart Labs >>on. >>The more that she talked about it, the more that I wanted to be involved on. I thought that makes it really should be a sponsor, this initiative. And so I got details. I went back and my assessment sponsor. Ever since I've been on the committee trying it help with. I didn't find speakers on and review and the different speakers that we have each year. And it's it's amazing just to see how this event has grown over the four years. >>Yeah, that's awesome. So when you first started, how many people attended in the beginning? >>So it started off as we're in this conference with 400 people and just a few other regional events, and so was live streamed but just ready to a few universities. And ever since then it's gone with the words ambassadors and people around the world. >>Yes, and outwits has is over 60 countries on every continent except Antarctica has told them in the Kino a swell as has 400 plus attendees here and his life stream. So how do you think would has evolved over the years? >>Uh, it's it's term from just a conference to a movement. Now it's Ah, there's all these new Our regional events have been set up every year and just people coming together, I'm working together. So, Mike, self hosting different events. We had events in Redmond. I had office and also in New York and Boston and other places as well. >>So as a as a data scientist manager for many years at Microsoft, I'm I'm sure you've seen it increase in women taking technical roles. Tell us a little bit about that. >>Yeah, And for any sort of company you have to try and provide that environment. And part of that is even from recruiting and ensuring that you've got a diverse into s. So we make sure that we have women on every set of interviews to be able to really answer the question. What's it like to be a woman on this team and your old men contents of that question on? So you know that helps as faras we try, encourage more were parented some of these things demos on. I've now got a team of 30 data scientists, and half of them are women, which is great. >>That's also, um So, uh, um, what advice would you give to young professional women who are just coming out of college or who just starting college or interested in a stem field? But maybe think, Oh, I don't know if they'll be anyone like me in the room. >>Uh, you ask the questions when you interview I go for those interviews and asked, like Like, say, What's it like to be a woman on the team? All right. You're really ensuring that the teams that you're joining the companies you joined in a inclusive on and really value diversity in the workforce >>and talking about that as we heard in the opening address that diversity brings more perspectives, and it also helps take away bias from data science. How have you noticed that that bias becoming more fair, especially at your time at Microsoft? >>Yeah, and that's what the rest is about. Is just having those diverse set of perspectives on opinions in heaven. More people just looking like a data and thinking through your holiday to come. Views on and ensure has been used in the right way. >>Right. Um and so, um, what do you going forward? Do you plan to still be on the woods committee? What do you see with is going how DC woods in five years? >>Ah, yeah. I live in for this conference I've been on the committee on. I just expected to continue to grow. I think it's just going right beyond a conference. Dossevi in the podcasts on all the other initiatives that occurring from that. >>Great. >>John, Thank you so much for being on the Cube. It was great having >>you here. Thank you. >>Thanks for watching the Cube. I'm your host, Sonia, to worry and stay tuned for more. Yeah.

>>Hi and welcome to another Cube conversation today were BMC Felix's Immersion Days and the Senate Clara Marry on Santa Clara, California We're having a great series of conversations about the convergence of digital service's and operations management on one of the most important features of that is How do you realise Analytics Analytics is on? The tip of everybody's tongue is these days, but it's being applied marketing and sales >>kind of the >>surely cobbler's children that aren't getting the same treatment or, in fact, the IittIe organization. So what we're gonna do in this next few conversation is learn more about how I t analytics is beginning to transform I t. And facilitating this convergence of digital service is in operations management. And to do that, we've got Gore over Bari. Who's the president's or co founder on CEO of numeric fi. Welcome to the Cube. >>Thank you, Peter. Pleasure to be here. >>So, Gaurav, tell us a little about new verify. Let's start there. >>Sure. Yeah, I know. I liked, you know, in your opening statement, he talked about I t in terms of its own use of analytics being a little like, you know, a situation where the cobbler's children don't have any shoes because I t stood up pretty powerful analytical applications for the CMO, the CFO, VP of sales, et cetera, but not for writing itself. And so we think. Yes, it's ironic, but it's also untenable. And it's untenable because in the age of digital transformation, where you're opening up digital channels for revenue generation and the like and customer engagement, I t. Is really moving up from the basement to the boardroom, right? So you have CEOs who worry now about things like availability, about sort of a speed of innovation with quality and things like that. And so to be able to have a decision support system ah, system of intelligence, if you will, that across rank and file off i t across the plan bill run life cycle across the entire idea. State from infrastructure to ABS to Business Service's gives you recommendations and intelligent insights on how to, you know, improve the quality of your work, the health of your systems to reduce the risk of your systems that we felt it was an idea whose time had come on. So that's why we got started with the Mer if I and we rolled out a bunch of targeted analytical applications across areas like Project Analytics develops analytic service and lyrics, Asset Analytics and the like. And so it's sort of a string of purse that you can deploy across your I T organization and its interconnected s so you can ask cross getting questions as well. So that's in a nutshell. The story in America, Fi in its vision. >>So, Garv, I've been within a proximate to i t You're in I t for a long time now. And it's not that we didn't have reporting because I t was always doing reporting. We have poured on no stop lights projects wherever they were. But I think what you're saying is something a little bit more fundamental. It's really Can we do a better job of really capturing the resources that are creating value for the business, understand how to deploy them or successfully We're not just talking about the infrastructure. We're talking a lot about people. I got that right. >>You hit that nail on the head there. Ultimately, you know it is a business, and you have to if you want to face sort of the epic challenges and opportunities off tomorrow that I t alone can really take on. You have to understand the people process, project and product dimensions of the I t business. And so what that means is, if you want to drive down your iron oh, costs from, you know, roughly 72% of I t budget, which is what it was. The average today to 50% is the gold standard. That's half a trillion dollars for the G two K, right? And you want to take that savings and reinvest it in agility in foster app. David. Higher quality, right? How do you do that without tapping into things like automation and the use of analytics to drive down your ire no cost rationally and increase your dev your development velocity intelligently? Right? So that's where analytics has a huge role to play. >>But also it's got to be fucking interrupt you. It's gotta be that you have to have. You have to start with visibility. Yep, into what resource is are generating the greatest return? Yeah. Why air they generating that return? Why are other resources not generating return? Yeah, and seeing how all that gets connected across the range of activities that a nightie organization is performing on behalf of the business. >>Yeah, I know exactly. I think the how is really about getting that visibility across sources, and it's a non trivial problem to do that when you have a plethora of sources that were never built to talk to one another. You may want to, for example, with an I t. Understand. You know, the total open work on each person's plate, right? So they may have a bunch of incident resolution work that they're doing, and the data and the signal from that comes from a B, M, C or a service now and yet they may be pulled into apt of work, which the signal is coming from Ajira or a C A. How do you pull that together into a single dashboard that gives you that view of what everyone's working on? And then you can make decisions like goodness with so much unplanned work that's gone Fred's way, there is no way that the epic that he's involved with is going to, you know, be completed on time. So I have Project Chris. I have released risk as a result, I may even have attrition risk. And so the ability to pull together data into a single model answer the visibility question, too. You're to the point you make and then go the next step off predicting likely outcomes. That's the magic. And that's the use of analytics to sort of trance for my tea into, um, you know, operating in a far more intelligent paradigm than it has thus far. >>Other tools have attempted to do this, but they attempted to basically be the soup to nuts tool. So they forced users Thio install agents everywhere that there was a single process model that was expected to be employed to administer all kinds of different resources. There are very significant limits on how you considered application development application management, For example, Why is numeric five different? >>Yeah, what we've tried to do is really take ah leaf from the page on books of those who have set up succeeded in this endeavor before. So if you look at you know the solutions that a CMO might have it at her fingertips or a CFO might have right fundamentally, it's about pulling data into existing systems, not requiring a change of behavior but pulling data from existing systems into a canonical model into a standard sort of analytical data model that runs on surfing. Ah, a dedicated stack on. Then you basically have this layer off descriptive, prescriptive and predictive analytics sort of folded in on. That's the approach we've taken where we say, Hey, look, we want There is such a thing as a change management system that doesn't go away. We would like to mind the accumulated history of all the changes you've ever put into production by tapping into your service management system and then your upstream Devon test system. Because change is often a piece of court, it began its life somewhere in a in a death cycle. So how many times was that piece of court rollback tested? How many times that it failed the testing cycle? Who worked on it? What's been their success rate thus far? And then, with respect to the change itself in the past, how often has a change like this failed? You know, if changes were done on a weekend through a combination of an unsure in offshore team, is that implicated in a failed changes in the past and then downstream of the change in the past, you know, Was it a decline in performance or usage availability as gleaned from your monitoring tools? So we pull all data from all these sources without requiring you to re instrument them into a standard model. And then, for every upcoming change, we tell you Hey, this one is a risky change. Go look at it. Send it back for further testing. Hey, this one is a lower exchange pusher to production directly and so inherently thehe bility toe pull data from multiple existing sources into a standard data model and have best practice reports and insights sort of layer on top. That's the approach taken. >>Well, look, I really like this. Uh, let me let me see if I can summarize something you just said So Numeric fei is not immediately antagonistic to anything that anybody has with the shop. That it starts from a proposition. That look what you're doing is working or not, But let's start from across from a premise. It you're doing something now. Let's learn more about it. Let's then asked Can we do it better? Yes or no? You have the intelligence to do that. And if it should be replaced, can you actually get to the point of that? You can actually indicate or suggest how and when to replace something. >>Yeah, that's a fabulous question. I think you know, increasingly what we're seeing is that our customers are pulling us in the direction off, making active recommendations on decisions that they could potentially make such as, you know, you may want to consider consolidating a certain class of applications because, you know, given its revenue and usage, the amount of support button associated with it is too high here. You might want to take a more refined and data driven, inside driven approach to asset retirement because you know this whole, >>you know, >>everything that Lenovo, in five years old Moscow is too blunt an instrument, you know, retired those assets that are the most error prone and keep alive those assets that still have useful life >>And that process, maybe itself be extremely expensive, very limited returns >>precisely precisely. So the ability to transcend now from just visibility on dashboards to providing active recommendations for every action along the way, you know, project race release risk, patrician risk, change, risk service quality risk, et cetera. We see that as as the as the vision for us. You know, it's the use of a I not just for automation, you know, sort of Ah, which clearly the ops field is investing in, but also the use of a i for decision support for providing you with intelligent recommendations across the full sphere of activities that I t undertakes. >>Grove Ari from the from the verify. Thanks very much for being on the Cube. >>My pleasure. Thank you. >>Once again, this has been a cute conversation from BMC. Helix is immersion days and the we look forward to seeing you again. Thanks for listening.

>> Announcer: Live, from San Francisco, celebrating 10 years of high-tech coverage, it's theCUBE. Covering VMworld 2019. Bought to you by VMware and its ecosystem partners. >> Welcome back to theCUBE's live coverage here at Vmworld 2019, San Francisco, California. We're in Moscone North Lobby. I'm John Furrier, with my co-host Dave Vellante. Dave, 10 years of covering VMworld. This is our 10th year. Pat, you've been on every year since 2010. We have photos. >> That's sort of scary. >> You had a goatee back then. (Pat laughs) We've heard your rap going way back. Welcome back, good to see you. >> Oh man, scary. You guys probably got some dirt on me. Boy, I better be careful. >> John: Pat Gelsinger, the CEO of VMware on theCUBE. Thanks for coming on this evening. >> Oh, always a pleasure to be on with you guys, love it. >> Don't end up as driftwood. Security is a do over. We're going to talk about all that. >> We're going to spend the entire segment just talking about Pat Gelsinger's predictions. We'll recycle some of them, but let's get into the core news here, VMworld. You've done such an amazing job. We've given you a lot of props on theCUBE over the years, but still continuing, even in the market climate that's swinging up and down right now, VMware still producing great results. The team is executing. Their transition since October 2016 when you kind of made that move, cloud is it, clear vision, a lot's been falling into place. Pivotal has dropped on your lap, and you got the engineering stuff coming out on top of vSphere and a bunch of other things. Great stuff, I mean, you must be geeking out. >> Well, thank you. At the US gymnastics finals, Simone Biles did a triple double. First time ever in competition. And I think of our last week as a triple double, right, two major acquisitions, an earnings call, and now VMworld and all the announcements as part of it. It's like wow. >> John: You stick the landing, you stick the landing. >> That's right, we did yesterday morning. We stuck the landing and Ray did that today as well. So super proud of the team in bringing these across the line. And I think certainly meeting with many of the customers and the partners here everybody's sort of going wow. And I was excited about VMware before I got here. Now I'm just euphoric, and it's really-- >> I'm told Ray did an exceptional job. I'm going to talk to him later today on theCUBE. Today in his keynote he was great. He repeated the messages over and over again, but he nailed the tech piece. I got to ask you, as the engine of VMware is continuing to be put together and expand it's like a new turbo engine gets pulled in here. There's a lot of really good engineering going on. What are you most excited about? How would you describe all the action going on? If someone says, "Pat, what's the underlying engine here?" What's being built? What's going to be the outcome of all this? >> Well, I think it sort of boils down to, right, these two phrases that you heard from me yesterday. We're going to engineer for good, the tech for good stuff, we're going to do good engineering. And doing both of those is just okay. And you sort of say, "Hmm, we got vSAN," right? We're not being able to optimize the performance because big blocks, little blocks, latency, buffer size, all this other kind of stuff, so now we're doing Magna, right? And when you see that demonstration there, it's like we're going to do it automatically for you to be a fine-grain optimizing your storage. Wow, that's pretty cool, and it's intelligence, right? It's sort of saying, "Wow, this is really cool." So let's go automatically produce an understanding of the underlying network, understand what's going on, give you the rules that we recommend, and allow you to simulate them, which is super cool, right? Within minutes, we will give the network engineer more understanding of what's really going on in our applications, and then allow them to see it in real time and then apply it. Every one of these, and it's just 10 or 15 tremendous engineers who are doing these little innovations that are fundamentally changing the industries that they're in, in addition to the big stuff. It's just thrilling. >> Dave did a survey before coming into VMworld with customers with a panel. 41% said they're not going to change their spending habits with VMware so creating the-- >> Dave: They said they're going to increase-- >> Increase. >> In the second half, only 7% said they're going to decrease. >> So great customer loyalty, and remember, VMware's moving so fast and transit. Customers aren't moving as fast as you guys are, and you've talked about that before. What are you hearing from customers as they look at it and say, "Wow, is it too much new stuff?" 'Cause they want to continue to operate, but they also want to enable the developer piece. Because remember, DevOps means dev and ops. You guys got the ops piece down. You're adding stuff to it. There's always concerns there making sure it's smooth and you guys work on that. The dev piece becomes super critical. That's where Amazon really shined with public cloud. So hybrid cloud's here. What is the DevOps equation for hybrid? I mean Kubernetes is a good start. Where do you see it going? >> Yeah, and that's really the center. To me, that is the most important news of VMworld this year is the entire Tanzu message, the coming together of Pivotal, the coming together of Pacific, coming together with Mission Control, so really leveraging VMware in the run layer, leveraging Pivotal in the build, and Heptio in the manage, right, and those coming together into Tanzu. I think that's the most important thing that we're doing. And I think for operators, which is really the center of our audience here at VMworld, they've always struggled with those crazy developers. They do this cool new stuff. It's not operational, it's not secure. But in bringing those together, the magic formula for that is Kubernetes. And that's why we're making these big bets. The move with Pivotal, obviously the Heptio guys, I mean Joe Beda and Craig, they're just the rock stars of that community because they really are solving in an industry-consensual standard way. That's really the magic of Kubernetes. This ain't a VMware thing, this is an industry thing. >> Is Kubernetes the technology enabler? I mean, TCP/IP was that in the old networking days. It enabled a lot of shifts in the industry. You were part of that wave. Is Kubernetes that disruptive enabler? >> Yeah, I really see it as one of those key transition points in the industry. And as I sort of joked, if my name was Scott, and we were 20 years ago, I'd be banging the table calling it Java. And Java defined enterprise software development for two decades. By the way, Scott's my neighbor. He's down the hill, so I look down on Mr. McNealy. I always sort of like that. (everybody laughs) >> He looks up to you. >> But it changed how people did enterprise software development for the last two decades. And Kubernetes has that same kind of transformative effect, but maybe even more important, it's not just development but also operations. And I think that's what we're uniquely bringing together with Project Pacific, really being able to bridge those two worlds together. And if we deliver on this, I think the next decade or two will be the center of innovation for us, how we bridge those two roles together and really give developers what they need and make it operator friendly out of the box, cross the history to the future. This is pretty powerful. >> So that does lead to the big question. You just mentioned developers. And when you look out the VMworld audience, it's not comprised of huge developers. I know you're thinking about this, so what's your plan to attract those developers? You're giving them platform now, and the technologies. but those builders, what are you going to do for them? Is it build community, more events, more training? What's the plan there? >> Yeah, and I'd say I think about it in a couple of different context. One is if we were here six years ago, and you would have asked me about open source, right? I mean, VMware's reputation in the open source community wasn't good, right? We hired Dirk, we started to build momentum, make contributions. One of the litmus tests for Joe and Craig on Heptio, 'cause remember, a lot of people could have bought Heptio. Because some was who's going to be the buyer, but also will they be a willing seller. And their litmus test was are you really serious about open source, right? Are you really committed to the open source, Kubernetes tree and development and cloud-native computing foundation? Are you really there? 'Cause they were also looking do I want to be bought by you? Do I want to be part of the VMware family? And we passed the test. That's why Heptio's part of the team. Clearly, this has been central to Pivotal and their views. So we have to be open-source credible. We also have to be developer credible, and those two are tightly linked. And that's why we noted on stage Pivotal, particularly the Java community, is three-plus million developers. Bitnami is two million-ish developers. We now have high volume connections to the developer community, and you're going to see us show up in dramatically more profound ways at places like Kubicon and SpringOne is coming up, just start to be in the developer spaces. And ultimately, you got to do stuff that they care about. At the end of the day, winning developers has nothing to do with great marketing, even though that's important. You have to do great code, right, and bring them value to their development assignments. And we think with the assets that we're lining up, that's why we did Pivotal, Bitnami, Heptio, some of our organic things, Dirk's leadership here. I believe that a year or two from now VMware could be seen as the most developer and open source enterprise company in the industry. And that's the goal that I'm on. >> Well, I have an idea for you. Allocate 1,000 engineers to open source and start having them build new applications, new workloads, give it away to the open source community, and then sell your products and services to them. That would get you in fast. >> Well, by the way, we now have hundreds of engineers who are committed to open source, who their full-time job is open source contributions. So I'm not to 1,000 yet, but I'm now several hundred that their day job, night job, weekend job is open source contribution. So we're becoming very credible, and as you heard me say in the keynote, we are now top three contributor to Kubernetes. This is big, and some areas like the networking area we're clearly the leader in a number of the key networking open source technologies, and you'll see us do more of those kind of projects. >> One of the things you mentioned, I mean you mentioned about open source six years ago, you might have rolled your eyes, or you might not have had an opinion on it 'cause the timing of where VMware was. But one thing you've been banging the drum on since 2012 is hybrid cloud. And so you see certain things early. You see those waves. That's what you're known for, in my opinion. You're really good about it. You see blockchain as a great wave, but as a headline I'm reading on Fortune it says, "VMware CEO Pat Gelsinger, "Bitcoin is bad for humanity." >> Sold all my bitcoin (laughs). >> Okay, so now are you implying then, and blockchain is a lot of open source components there. It's evolving, you've a lot of blockchain projects. So is that an indictment on the unregulated currency market or is it the underlying infrastructure? And are you excited about blockchain as an underlying? Is it one of those hybrid cloud moments for you, or is it more of we'll see how it develops? What's your thoughts? And explain the bitcoin comment too. >> Yeah, the idea of distributed ledger technology, immutable distributed trust, I've said I think of that and blockchain as the underlying technology as almost like public private key encryption, right? If we go back 40 years before RSA or Vashumi and Ari, it's that important. This is breakthrough, innovative technology in how you do distributed secure trust. That's powerful, so we are huge believers, strongly committed to blockchain and distributed leverager technology. Now, why do I make my comments like I do on bitcoin? So bitcoin, as it's implemented, and implementation of blockchain and distributed ledger, I assert is bad. It's bad for two reasons. One is it's an environmental crisis, right? A single ledger, if you and I transacted a penny, right, I would consume enough energy to power your house for half a day. I mean, it's incredible, and I mean, that's why you have these crazy bitfarms being built and people finding GPUs. >> So you think from a sustainability standpoint. >> Absolutely. >> That's where you came from. >> Climate sustainability, right, this is a terrible implementation of blockchain. Secondly, the way it's also done as well in this totally unregulated environment, almost all of its uses are for illicit and criminal purposes. That's who's trading in bitcoin as well. So its purpose is almost all illicit, right, and it's environmental crisis. I say bad. Now, I'm not saying that blockchain is bad. I think this is revolutionizing. >> I want to make sure we clarify that because obviously unregulated outside the United States has been a big problem. We see it in the SEC crackdown, and results are-- >> Studies have shown over 95% of the use of bitcoin is criminal, so say bad. Let's go make it good, and that's what I mean these two phrases, do good engineering, and engineer for good. How do we make blockchain, and this is part of the reason, we had just announced on Sunday a partnership with Australian Stock Exchange and Data Asset, that they're leveraging the VMware distributed ledger technology, right, as part of their go-forward strategy for the stock exchange of Australia. Well, that's good, right? We're making it suitable for enterprises, meeting the regulatory requirements and-- >> John: Are you happy with the progress of where the blockchain is for you guys? >> Absolutely, and we're order-plus magnitude better in terms of performance and energy consumption. So yeah, and we're just getting started. >> And it's consensus-based, which is great. A quick question for you on multicloud. So hybrid cloud you said in 2012, I challenged you on it, and you've been banging the drum since 2012. It's a couple years into it, and hybrid cloud is pretty much standard. People see it, recognize it as the cloud 2.0. Multicloud is all the buzz and all the rage. I hear it everywhere. What does it actually mean is a different debate, so I want to get your thoughts on defining what multicloud is and is it going to have that same gestation period of the same kind of years? 'Cause if it's seven years to get or six years to get hybrid cloud mainstream, is multicloud going to have a similar trajectory? >> Yeah, so let's try to be very crisp with the definition. Multicloud is simply that. Customers using multiple clouds for different business purposes. And what we said is is that we're going to help them manage. That's the center point of cloud health, right? Help customers manage, cost optimize, secure in a multicloud environment where the underlying infrastructure is dissimilar, not compatible, right? And in that sense, you sort of say you can have consistent operations if we do our job well with cloud health, but you're not going to have consistent infrastructure, meaning I can't VMotion between these things, I can't have higher these things. So that's the multicloud. Now a proper subset of multicloud is hybrid cloud. And hybrid cloud is where you have both consistent operations and consistent infrastructure. And that's when we can do things like you saw on the demo today, right? We're running a VMware stack on Azure. We're moving Azure running workloads in real time, right, without stunning them, pausing them, to an Amazon VMC instead of moving workloads from Amazon VMC onto an Azure instance. That's the hybrid cloud, and that's the power at work, from private data centers to multiple different targets in the public cloud where you can be optimizing the location of work nodes based on the proper business requirements. And that might be governance. That might be performance. It might be latency. It might be the time of the day of the week when you have capacity available, right? And that's really what we're saying. Consistent operations and consistent infrastructure, proper subset of multicloud. >> I have a question on something you said yesterday. You said, "Strength lies in differences not similarities." True, I buy that. There's a number of difference between you and your preferred public cloud partner. AWS doesn't use the term multicloud. They say you shouldn't say security's not broken. And there are a number. You want to be the best infrastructure and developer software company. They want to be that platform. They want to be the security cloud, on and on and on. So I see this impending collision course, maybe not tomorrow, but what are your thoughts on the differences and the good or bad that does for the industry? >> Yeah, well, we appreciate Amazon, the investments that we're making. We've both bet big with each other, and they've been a great partner. And in fact, I'm going to talk to Andy before the end of the week, update some of the announcements and some of the things. Great partner, we have regular cadence of our activities with each other. And as we said, they're our preferred public cloud partner. And with it, it's preferred in two senses. It's a go to market and how we position that, but it's also an R&D statement, right? This is where we're doing a lot of core engineering, and that will flow into private cloud embodiments, flow into our other public cloud and our cloud-verified partners. But that's the point of the arrow in terms of the innovations, the go to market, and the R&D aspects of the partnership. And I expect we're going to be here five years from now and we're going to have this conversation, and I'm going to answer it exactly the same way. >> That'll be our CUBE's 15th anniversary, and so we'll be excited for that. It's our 10 year, so I want to last question put you on the spot, looking back over 10 years, pick the moments that you think were key inflection points. What were key notable good things that happened, bad things that happened, or things that didn't happen, right? And then going forward 10 years, you laid out a few of them with Kubernetes. Just past 10 years, could be CUBE memories, but in VMware's world, you were at EMC first, then became CEO, a lot's changed. Paul Maritz laid out the original vision. And where we are today, what's your key moments? >> Yeah, well, I think if you go all the way back, obviously, hey when the first WSX, right, people could run Linux and Windows on their client. Wow, right? The first VMotion, right, oh my gosh, and that sort of ushered in ESX. Obviously the transition from Diane to Paul, the public offering, boy, that was a pretty tumultuous time. And from Paul to Pat was very much we lay it out pretty much this any cloud vision, and that model, it was formative and we're sort of bringing it together. It was get rid of some assets, bring together, so sort of that transition was challenging for the company. But then we've started to sort of systematically say build from the core. What do we have? What do we need as we started to build these layers in the concentric circles? The Nicira acquisition, boom, that was the shot that changed the world of networking. And obviously, that doesn't change quickly, but we have a multibillion dollar networking business, Avi Networks, VeloCloud, we're building that set of assets. >> Software-defined data centers. The Core engine, that was a key point. >> Dave: That was a total game changer. >> You cannot build a software-defined data center if you don't address the networking. It's just that simple, and that's why I was so passionate about that. Obviously, the HCI move with vSAN. Joe Tucci was so pissed off at me, right? (everybody laugh) What are you doing? It's operative. It's part of the ingredients of the data center, Joe. I got to do it, wait. >> John: Just being a software company. >> Yeah, yeah, right, so that was a pretty tense moment. The period of the Dell EMC merger, a tough period, right, as well, and just where the company's going to go. And within a week, right, I'm going to be fired. I'm going to be spun out, right? I'm going to be the new CEO of Dell, right? I mean, it was going to be HP. >> John: All the rumor. >> Stock is 40, obviously the Amazon moment, when we did that partnership. vCloud Air, hey, we had the right idea. We didn't implement it properly, and then we did it right with the Amazon partnership, and that just changed the cloud industry. And I think we're going to look at today, this week, and the moves with Heptio, Kubernetes, Pivotal, those pieces coming together, and to this audience Project Pacific, right, it's just like okay, wow, everyone of them will become Kubernetes enabled. 20,000 selfies with Joe Beda, right, have now been ushered because it is that game changing, we believe. This is the biggest free architecture of the Core platform in a decade, so. >> My favorite quote from you was if you're not out on that next wave, you're driftwood. You said that on the QA, I forget which year it was. >> And mine's security's the do over. (Pat laughs) >> You're doing it over, you're doing it, Mr. Gelsinger. >> Next 10 years, what's the big wave everyone should be on? What's the wave that you identify? You've seen many waves, you've created waves, you've been part of waves. What's the wave for the next 10 years that people should pay attention to, that they need to be on? >> Well, if they're not on the networking wave, get on it, right? They got to be on this multicloud hybrid wave. Could it be louder? The Kubernetes one is the one, right? That's the one I'm going to put at the front of the list. And this move in security, I am just passionate about this, and as I've said to my team, if this is the last thing I do in my career is I want to change security. We just not are satisfying our customers. They shouldn't put more stuff on our platforms if they can't-- >> John: National defense issues, huge problems. >> It was just terrible. And I said if it kills me, right, I'm going to get this done. And they says, "It might kill you, Pat." >> Mount Kilimanjaro right there. Pat, thank you for all your commentary, and great look back 10 years. You've been one of our favorite guests coming on theCUBE, bringing A game, you're bringing the tech chops, the historian aspect, also you're running one of the most valuable open source companies in the cloud. (Pat and John laugh) >> Love you guys, thanks so much. >> Thanks, Pat. Pat Gelsinger here inside theCUBE. Our 10th year, VM's looking good off the tee right now, middle of the fairway, as they say, for the next 10 years. I'm John Furrier, Dave Vallante, thanks for watching. (upbeat music)

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum, World 2019 brought to you by VM Wear and its ecosystem partners. >> Welcome back. We're here! Mosconi North for VM World 2019 10th Year of the Cube covering VM World. I'm stupid and my co host is John Troyer. And welcome to the program to guest from Del Technologies. Sitting to my right is Tender, my Mondal, who's the director of storage solutions and sitting to his right is David when the senior director of server, product planning and management also with Dell. Gentlemen, thanks so much for joining us. All right, so we've got server and storage and talk about something that we've been talking about for a while on the server side been delivered for a bit and on the storage side is now rolling out. So everybody's favorite topic. Nonviolent till memory express or envy me as it rolls off the tongue storage class memory, or SCM and lots of other things, you know, down there, really helping a big, transformational wave that, you know, we really changes how our applications interact with the infrastructure channel, you know, bring us up to date on the latest. >> Sure on, let's start where you ended. We're seeing explosion off applications, right? And in fact, in mornings, keynote. Bad girl singer had a stocky speaks. There are 352 million enterprise applications today. On it will be 792 million in three years. Now, as the applications are growing exponentially, we cannot keep growing the infrastructure at that rate, So N v m e is the way we can consolidate it. Ah, lot off the infrastructure. If we can think about in tow and envy, Emmy starting from the server in fear me off our fabric through the stories area down, toe the back end with envy Emmy necessities. This actually can put together a great platform where you can consulate it. Ah, lot off the applications and delivering the high performance low latency that will need while meeting video surfaced level objectives so we can go over a little bit off the details, but I think it all starts from envy me over fabric coming from the server to the story, Ari. So probably like that's the fourth step we need to consider >> David. Do You know, I love this discussion when we get to talk at the application later because, you know, Flash changed the market a lot. You know, it's like, you know, much better energy, and it's much faster, Anything. But you know, this inflection point that we're talking about for application modernization, you know, envy me is one of those enablers there and something they know your team's been working on >> for a while. Yeah, actually, on the power each side we've been, You know, we've been embracing the benefits of enemy for quite some so many years now, right? We start out by introducing enemy in our 12 generations servers, you know, frontloaded hot, serviceable drives. And then, of course, we branch out from there on in today, you know, Ah, a lot of the servers from a Polish family all support enemy devices. So the benefit there is really giving customer choices in terms of what kind of storage kind of cheering they wanted, you know, for the applications needs. Right now, one of things that's great about, you know, enemy over fabric is it's more than just a flash storage itself. It's about enabling the standards, you know, across the host across the data fire Break down to the storage really to deliver on the overall performance that you know the applications of needs and buy, you know, improving I ops and lower late, Easy overall, from a server perspective, this just means that we're releasing more CPU cycles back into the application so that they can run different types of workloads. And for us, this is this is a great story from power. Just was from Power Macs and coming together to enable this Emmy, Emmy or fabric. >> You know, I'm I'm I'm kind of slow about some of these things, but if you kind of squint at the history and, you know, we went from the PC revolution and then we had, you know, we had Sands and raise right and we had we had centralized toward shared storage last couple of years, a lot of interest and stale right hyper converged. And you had a You had a lot of pizza boxes with the storage right there. It's I mean, I now think right and I'm following the threat, I think which is now that where we now can have ah, Iraq with again a fabric and and again, now we can We can focus on our envy me storage over our envy me over fabric driven, solid state storage somewhere below my servers that are that are doing handling compute somewhere else. Is that that the future we're headed towards now >> Yes. I mean, everything has its place. But to give you the perspective, right? It's not just, I mean coming down to the storage area, but how This is enough bling, the future storage as well. And the storage class memory is the perfect example. And as Defeat said, let's take power, Max, as an example, right. Eso in power Max, you can It is like entrant, envy me ready like you get envy emi over Fabrica de front end But then we have n v m E s s trees in the back end. The thing is now it is also the N v m e is enabling technologies like stories class memory which is bringing in very high performance, very less latency Latency is going down in the order off like tents off microseconds. Now this is as close as you can get. Tow the like Dedham with persistent story. However, you need a balance. This is like order of magnitude are costlier. Now you got bar Max. What we're doing in terms of first, it's envy me. Done right? What do you mean by that? You have, like, Marty controller architectures that can actually do this level of parallel processing and our concurrency. And then we have bought, like, ECM for storage, class, memory and envy, Emmy essences. And we're doing intelligent tearing best on the built in mission learning engine that we have. And it is looking at 40 million data sets. Really time to decide. Like which sort of walk lords should go on this same drives which should go on and the M. E s estates. And on top of it, you add quality of service. So this platform gives you are service level objectives. You can choose from diamond, platinum, gold, silver or bronze, and you can consulate it. Ah, lot off those 352 million different types of applications on this area guaranteeing you are going to meet all off your SL s, no matter what type of applications they were consolidated into. >> Okay, I'm wonder if you could boast. You know bring us into what this means for VM wear customers and break it into two pieces. One is kind of a traditional virtualized shop. And secondly, you know, spend a lot of time in the keynote this morning talking about the cloud native containerized, you know, type of environment. Will there be any difference from from both of your world? >> Yeah, absolutely. I'm glad you brought that up because, you know, from from our perspective, right, what we've seen with the enablement of enemy platforms. You know, John, you brought up a very interesting point, right? It seems like you know, past couple years, we went from moving storage onto the host and now would envy me with fabric. We're actually taking the storage away from the host again. Right? And that's exactly true, because, you know, the first, the first statement you brought up stew. It's about how flash enabled different applications to run better on the host. What? We see that still right? And so what enemy? You know, we see the lower response time enabling our customers Thio run more jobs and more v ems per server. That's one aspect of it. You know, we've seen his benefit a lot of our platform today or using various different applications and solutions, and you talk about the ex rail that's a visa and story for Del. You Talk about Visa and ready notes for customers who want to build it themselves. Right platforms enabled would envy me back playing enemies. Storage allows them to use enemy or SAS sata whatever they want. But the point is, here is that when they're using every me flash, for instance, and I'll talk a little bit about the power climaxed with this all flash, uh, me back plane in a case in the study that we did with V San application running, oh ltp type of workload, we saw the response time with every me over traditional SAS, you know, from our competitors improved by 56% right, which means that from that same particular solution build out, we were able to add 44% more of'em on the platform. Now, at the same time, we increase the overall orders per minute by roughly over 600,000. Oh, pm's for that type of, uh, benchmark over our nearest competitors so that right there is the benefit that we see from my virtual eyes from, Ah, being where perspective >> on. I'll add from the storage perspective in two ways. In fact, in last vehement in a MIA, we demonstrated in tow and envy, EMI over five break up with special build off this fear supporting Envy me over fabric and stories. Class memory with envy Me drives what it gives you a regular like this fear best environment is that you have the ability to move your PM's around like the applications where the highest performance and Latin's is critical. It will be on those special service levels and special like de testers. In fact, that demonstration was like ECM did a store, and in P m E Sense media does so in the same fabric with in Bar Mexican moved things around, whether it's like regular Fibre Channel or CNN and then the other part. I want to add in the morning like we saw the announcement that now communities is built in or will be built in with the years Excite platform, right and you're sexy is bread and butter off all the storage customers that we have now with like when you consider those, uh, those things built in under this fear black from Think about, like how many applications? How many actualized workloads you can run, where that it's on premise or humor. Cloud on AWS. All of those consolidation, as well as like the performance needs while reducing your footprint does the benefit of the V M R R shops. But the PM admits are going to see from the storage site >> again. I'm not following the parts, but what kind of we're not talking about a couple of megabytes here anymore, Right? What size of parts are shipping these days? So >> So, from our perspective, up to 77 gigabyte actually start. Seven terabytes drives are available on the markets today for Envy Me Now, whether customer by those drives, you know, it depends on economic factor. But yeah, it's something that's in this available from Dell >> so on. I'll act to what David said so far in CM drives 750 gig to 1.5. Articulate a C M drives on Dwell ported often drives that will be available in the power Max Acela's 15 terabyte envy EMI assistants. So this is the capacity we're talking about. And again the Latin's is at the application level, like from the storage like you're going to see, like, less than 300 microsecond. That's the power we are bringing in with this technology to the market. >> Give >> us a >> little look forward we talked about, you know, envy me has been shipping for a bit on the servers now, really rolling out on the storage side, I saw there's a lot of started from the space. You know, one recent acquisition got guts and people talking. What? What should we be looking for from both of you over kind of the next 6 to 12 months. >> So over next to a next 6 to 12 months, he will see a lot of innovation in this case from the storage site where wth e order of magnitude. I mean, the one single Ari, I mean, today it supports, say, like, 10 million I offs less than 500 microsecond latency. Ah, I cannot give you the exact details, but within like, a short time, these numbers are going to go up by more than, like, 50%. Latency is goingto get reduced. The troop would will be driving will actually like more than double s o. You see, like a lot of these innovations and kind of like evolution in terms off the drive capacities both from the CME, drives perspective. Envy me, assess these. Those will continue to expand, leading to foster performance. Better consolidation, Uh, for all the workloads. >> Yeah, from our perspective, I mean, you know, data growth is gonna continue. We all know that, And for us, it's like designing systems based on what the customers need, what the applications needs, right. And that's why we have different types of storage available today. So for us, you know, while we're doing a lot of things from a direct attached storage perspective, customers continue to have a need for share storage. EMI over fabric just provides a better know intense story for us, really from a Power edge and Power Macs perspective. But in the future, you asked what we're going to do. Well, we see the need to probably decouple stories, class memory from the host again. And really, what's preventing us from doing today? It's really having the right fabric in place to be able to deliver to that performance level that applications needs. MM evil fabrics, fibre Channel Ethernet ice, scuzzy or I'm sorry, Infinite Band, whatever. These are some of the things that you know we're looking forward to in the future to make that that lead. All >> right, well, it's really been great to see technology that I know the people that build your products have been excited about for many years. But rolling out into the real world deployment for customers that will transform what they're doing. So for John Troyer, I'm still Minuteman back with lots more coverage here from Be enrolled 2019. Thanks for watching the Cube.

>> from the Cosmopolitan Hotel in Las Vegas, Nevada. It's the Cube covering Cooper inspired 2019. >> Brought to You by Cooper. >> Welcome to the Cube from Cooper inspired 99 Lisa Martin in The Cosmopolitan of Las Vegas. And guess who I have with me from the main stage CEO. Rob Bernstein. Welcome to the Cube. >> You so much. Thank you for having me >> exciting start today. One of Inspire really enjoyed the general session this morning. I learned three things more than three, but there's three that really stick out. One. You like pizza >> I do >> to you like kittens and kittens. And three, since 2016 there has been a five X increase and the spend going through the coop a platform with rocket ship. >> That's right. Huge momentum were well over 1.2 trillion dollars and spend that's gone through the platform. It's accelerating, and our customers are getting a lot of value and visualizing that spending, routing it to prefer contract saving money doing in smart, compliant ways. It's a really exciting time for us. >> It is, and this is across every industry manufacturing, healthcare, retail, et cetera. Every industry has the opportunity to leverage this wealth of data absolute. Cooper has to be able to get that visibility and control of all their spent. That's really revolutionary for any business. >> Well, we're really excited about it. Our community of customers is very excited about it, where building something very special here. I'll tell you one of the most exciting things. When you see that data being used in a way that drives intelligence for each individual customers, you know, we're helping them understand Where is their potential fraud with their expenses, where their suppliers maybe sending them duplicate invoices by accident? But Ari, I picks that up. So we are taking the space to a completely new level, and it's it could be more exciting. Honestly, >> well, the amount. You know, we go 1,000,000 shows a year, maybe a little bit less, But we always hear data is oil data is gold. It is. If you have access to it, you can extract insights from it really quickly and be able to act on it faster than your competition. >> Absolutely. You have to be able to normalize the data first informal, so you need a I capabilities. To do that, you have to access a massive data store you have to anonymous. The data obviously needs to be very, very secure, and then you have to draw insights out of that data. And one of things I share this morning is that we've given our customers just in 2019 more than 18,000 prescriptions of things they should consider, for example, putting some suppliers on hold if we think there's some risk with those suppliers. So absolutely, it's a I, but it's a I as the underlying element that brings out what we call community intelligence. And that's what's what's so powerful >> and the community as well, another really kind of under town that I felt and heard this morning from us. It's a community of collaboration, thes air, other businesses benefiting from what others have learned suppliers as well. So the customer centric city, the supplier central city, is there. >> Absolutely. It's all about this community concept, and we have well over 1000 companies that we've helped spend smarter, effectively and their community because these customers air sharing both in person and online, best practices, ideas for doing things differently, ideas for stretching this space beyond where it's ever been before, and that's really rewarding and every individual customers getting the benefit from that. Eso This community is developing very, very nicely, and it's serving the purposes of establishing this category, this new category of businessmen management, that world driving toward >> talk about that because that's something that's pretty innovative for Cooper. Business SPEND MANAGEMENT The role of procurement has changed. The role of finance has changed. They have the opportunity to become very strategic and really drive top line value. Talk to us about business, spend management What it means, how Coop is defining it >> absolutely well. First of all, any person I am in the world, and I've been asked this question for well over a decade. Now, do you think your company is doing a great job in managing its spending on older business needs that the company has, and you never get a resounding positive answer that, yes, we're doing a great job. And if you ask them, are you applying information technology to that problem in an effective way? The the answers or even worse? So we are attacking this full on with our customers in establishing the space, and that means everything from procurement expense reporting to invoice processing, two payments strategic sourcing, spend analytics supplier management contract lifecycle management. All of these application areas working together in concert help companies get their arms around spending and manage it in a much more smart way. And that's what this is. This is all about. >> One of the biggest challenges is you think about poor I t. Because every every line of business, whether your marketing, finance or engineering anything. Oh, engineering. I want to use lock. Start using flack. Marketing wants to use salesforce market Whatever these tools are in, suddenly this proliferation of shadowing T that's right and challenging to manage. But you can imagine how many supplier contracts are being duplicated triplicate, ID and even within the same organization, not getting the ideal price. So one of the great things big announcement today is the expansion of the relationship with Amazon in the AWS marketplace and wow, c I ose I t folks are gonna be able to do >> a lot >> through the Cupid platform. Tell us >> girls, that's right. Well, first of all, it's powered by an open by technology that we've developed, which allows you to have a very seamless experience. It's a purchasing experience that feels just like you're out on the Web, looking for any kind of item that you'd like to buy. But now you'll be able to subscribe to Service Is Cloud based. Service is through the Amazon AWS marketplace, and these Air service is that obviously would be approved by your CEO be approved by the folks involved in checking that it's secure, approved by legal and also approved by procurement So you can procure these cloud based service is very, very seamlessly right out of Cooper into AWS marketplace and back. And we think it's going to allow for obviously more volume of controlled spend, but also visibility into that spends. So it's properly matters >> that visibility is. You know, it's a word that we use in so many different applications. We don't want better visibility in our lives. In general, that is not easy to achieve. You talked about kind of these four core categories. You actually mentioned Maur that Cooper delivers its procurement, its invoices, expenses that can imagine travel management contingent workers getting an organization, whether it's a big organization like a staples or a smaller organization, that visibility is massively game changing. >> Yes, I think so. And I think one of the things that allows us to view that is we've really empowered the central hub organizations. Many the ones you described to roll out platforms to the end users all over the country, all over the world, wherever these people have employees to take control over spend. But have that Spence still routed to preferred, contractually righteous kind of spend categories that give them the results that they want. So this is a platform that is getting wide, wide adoption. And I'll tell you one of our application areas. We've seen more than a three x acceleration in the number of users over the last one year simply because of the adoption is so broadly accepted. And that has to do with our design and technology. Make it very, very usable. Our design concept of the best, you wise. No, you are right. So that's really how we're getting to where we're getting with a customer committee >> Adoptions challenging, you know. And there's if you look at the number of applications that an organization has a gonna work our list of sites, there's a lot and they're only effective if they're being utilized effectively by all of the folks that need to be doing that talk a little bit more. I love how you in your general session this morning shared with the audience. What c o u P a. Each acronym means. But and I saw that on the website best. Do I know you? I know what are some of the things that you think Cooper is doing really well that are really facilitating that adoption. That's again, that's hard to achieve. >> Well, it's in each of the letters in Cooper. So first, a comprehensive approach. That's what the C stands for. So cover every area of spend in one platform. We've never seen that before in the history of enterprise software, about a lot of siloed solutions all over the place, people trying to integrate them. We've put this all on one comprehensive platform. Secondly, doing it openly. That's what the old stands for. So being able to integrate to any ear piece system integrates a whole host of systems you mentioned slack earlier. We integrate into slack you could approve or reject spent purchased directly and slack. You have to get out to Cooper to do it, but you're doing it. The date is captured in Cooper. You is the user centrist city, so putting all the weight on the application itself and less of the weight on the employees themselves. Right now, we support guided buying with support all these capabilities, but our focus is on. You don't need any guidance in the future. Should require in the gun she should be. It should be so intuitive. The P stands for prescriptive, and this is using this community. Data we were discussing earlier to give real prescriptive advice. Teach customer, but how they should be spending or best practices, expenditures or benchmarks of how they could approve in the A stands for accelerated. It's the time of deployment. We're getting our customers live in a matter of months. They're accelerating their business process internally. I shared a stat that our customers in the last 12 months have improved the speed of their approvals by 30%. That's an aggregate. That's millions of millions, hundreds of billions of dollars in spend buying. So these five there is really differentiate us and they're really the vision areas that we focus on is a company with our with our community of customers. >> I was looking at some of the numbers from Cooper. You guys have consistently managed to grow revenues over 40% your rear in your fiscal year. 20 Q one earnings, which was just what last month or so. So revenue up 44% year over. You're crushing Wall Street's estimates by more than a 10 point gap. Lot of moment in, As you mentioned, let's talk about customers because at the end of the day, that's what you're all working towards. I know some of your proudest moments are when you get to talk with customers whose businesses have been transformed and you're giving them that the ah ha moments all the time. I love this morning how there >> was a lot >> of the voice of the customer covered there from so many different industries. The impact that you guys are making it Rolls Royce, for example, and MasterCard massive. Tell me some of your favorite stories that really articulate the breadth and depth of the value that delivers. I >> love it when the story begins in a situation where the CEO or CFO of the company don't necessarily get it, but somebody within our community steps up and shows them the business case of what we could achieve together. And then we, as a team is a collective unit delivered on achieving. Looking at was on themselves. I mean, they're processing more than $2,000,000,000 a month >> through our platform. I >> mentioned Procter Gamble. It process more than $50,000,000,000. Star Platform. Now >> these air, >> not initials. These were early adopter customers. They didn't have to go in our direction. There was some individual in that company that saw the spark of opportunity seized it, got it approved and worked with us hand in hand to drive it. And that's the stories that I love the most. And I shared so many of them this morning, but there are literally hundreds of them. All over the world in this community were cultivated. >> There are, and it's that's I think there's no bread or brand value that you can get Van it being articulated from the voice of a successful customer who it's not just normal, agile. We're saving money. It's no, we're driving shareholder value. There are significant business imperatives that are being driven because procurement is changing. We got to react to pricing pressures and forces like consumer ization. You know, we think of way have these expectations as consumers private lives, of getting anything that we want within a day when it shows up, you forgot what you ordered. It was that fast. That's right, what you guys are doing to enable the business buyers to have that same capability in their business lives. But to get that visibility, that 360 is really interesting. >> And the key also is to handle all the complexity on the back end for them. I could tell you so many companies I know that a really proud of crossing their paper based invoices very, very quickly, but they may not even know whether or not they got the goods of service is for which they're paying the invoice. So we do all of that heavy lifting on the back end on the platform itself, alleviating then users from that complexity and allowing them to have the experience that's similar to the one that that you just described >> can imagine how much money is being wasted on paper. They probably have absolutely no idea, absolutely no idea where you guys launched an Index. The Cooper Business Spend Index Just, I think, a month or two ago this is behavioral based data that you're bleeding from your community. Talk to us about the coupe of business spent index and some of the insights that you're already uncovering about the economy. >> Absolutely so. One of the things about this business spending nexus. It's something I've been thinking about frankly for over a decade. Can we collect enough data that's statistically significant enough actually be a leading indicator to future economic sentiment. You think about the data. We're looking at an aggregate. We know the average spend companies have per employee. We know how long approval cycles are, and we know the changes in those approval cycles. We know what percentage of spend is actually being rejected. Verse accepted at a moments notice aggregated those air in combination are leading in the Kidder's to the sentiment that companies have about the future of the economy. So we backwards tested this index that takes an account, these three elements that just described back to 2016 and it's proven to show pretty strong correlation with the way the economy actually played out for many of those quarters that many of those quarters. So last quarter we released our first verse, our first data set of the business spending. Next. And it showed that future economic economic sentiment for the next 3 to 4 months is actually very positive now, in some industries, more than others. But now, with three months later and clearly, the last three months have been pretty strong. So we're gonna be soon releasing our next quarterly Businessmen index. And we're gonna be doing this every quarter. Try to provide the business community with insights about where things are going. That's what everyone of business wants to know, where things are going, not where things have been. And we think we're in a unique position to share that and also, you know, sort of unfairly build awareness for brand out there so that people understand >> what we're all about. >> But that's that's critical. I'm gonna be talking to China tomorrow. You think of awareness Acquisition? Yes, Yes. Advocacy. Yes. Check, Check. Check. Old three. Those are critical last question robbery. As we look at the impact that procurement and getting this visibility of all of the distances spend can have on the business. Where is it as it relates to enabling businesses to digitally transformed >> to be competitive? Well, look, underlying all of this is the digital transformation that's happening for every company in every industry, without a doubt. But the use cases we support us so quantifiable. That's so clear not only in terms of cost savings that only in terms of compliance only in terms of visibility and getting your arms around spent actually drive revenue as well. If you do spend management effectively, you can change the way consumers experience your brand. And I shared a number of those stories. MGM resorts to Lulu Lemon to the Leukemia and Lymphoma Society and others. If you can get your arms around the spent and get people in the company, the goods and service is they need in record time. They're better position to express the company's vision to help them push towards an incredible iconic customer experiences. And we're just so proud to be ableto power that for this fast growing community of customers around the world, >> such an exciting time. Rob, thank you for having to queue, but inspired 19. It's been great. It's for looking forward to talking with lots more of your of your folks as well as amazing innovators and thinkers like Susie Orman and Deepak Chopra. Wow. Awesome stuff. Thank you. Well, thanks for having us. Thank you. All right. For Rob Bernstein. I'm Lisa Martin. You're watching the Cube from Cooper Inspired 19. Thanks for watching.

>> Live from San Diego, California It's the queue covering Sisqo live US 2019 Tio by Cisco and its ecosystem barters >> Welcome back to the cubes coverage of Day one of Sisqo Live from Sunny San Diego on Lisa Martin, my co hostess student. A man and Stuart are pleased to welcome a couple of guests from this Cisco platform and Solutions Group. We've got Barbara Half Li, senior director of Business development Barbeque. Great to have you nice to be here. And Matt Ferguson, director of product development. Matt, Welcome. >> Thank you. Nice to be here. >> So we appreciate you guys being here right at the start of happy hour here in San Diego. Thank you. Some our drinking water. Right wing quick. Just getting so, Barbara. So here we are at this's the 30th year Cisco's partner and customer, then a lot. A lot happens in 30 years. A lot of change here we are customers in every industry, living in this multi cloud hybrid world for many reasons. >> What are some >> of the things from the business perspective that you're hearing from customers? What are they looking to Sisko to do to help them traverse this new multi cloud world successfully. >> Yeah, well, one of the things that we hear customers tell us often is how doe I manage this landscape. Many people think of the cloud is just Oh, I've got a public cloud or oh, I'm gonna have my cloud on primp. But really, with the explosion of devices and I ot right, people want to know. How do we take that data from the edge from the edge? What do I do with that data? Do I put it up in a public cloud immediately? Do I bring it back to do some kind of analysis on that data? Is it goto a polo? Does it come to the branch doesn't go to the headquarters and that landscapes Very complex. So you look across that landscape and as customers of either proactively adopted the public cloud or had to adopt multiple clouds because of acquisitions they've made, this landscape just gets incredibly complex very, very quickly. So when people come to Cisco, they basically looking for a couple of things. Number one security. Because putting the security wrapper around all of that right, it becomes paramount. People lose their jobs if they're data isn't protected, so they want help with their security. They also want to know what's the best cost mix, right? How do I have the right options available to me? But the other thing they really want is speed of innovation. I mean, we hear this over and over and over. Uh, I talked to a bank the other day. 100 year old bank, right? You think 100 year old bank, um, speed of innovation may not be top of their priority, but absolutely. I walked in and they held up the phone and they said, Our competitors Aire delivering capabilities faster for the mobile user. And every time our competitors releases a new application or a new feature, I lose market share. So it isn't about cost savings anymore. It's about speed of innovation, even for 100 year old bank. When they come to Cisco, they want to know. Can you help secure this landscape? Can you give me speed of innovation? And then, of course, every cloud started the networking layer as well, Right? So what innovations is Cisco doing on the networking side? So these are some of the things that's customers come to Cisco and they ask us, what can you do for us and the help that they want? It comes back to innovation every time. >> Barbara. Actually, I've talked to some of those 100 year old Cos they need it more than ever, because that five year old bank doesn't have all the legacy and they're already moving is fast. But it's an interesting point. Matt. You know, we've been tracking community since the early days. This year, it finally feels like it's gotten to a certain maturity level, such that I've talked to a number of customers talking about how that is a lever for their digital transformation, how they're modernizing their application, pork portfolio and not just, you know, the, you know, making of the sausage of how this, you know, container orchestration, layers going toe, you know, do something that most people won't understand. It's that connection with the business kind of building up. What what robber says They're bring us inside a little bit more. You know the community's piece of that, >> Yeah, it's absolutely been tremendous to see the CNC F and Kume con absolutely just take off on the number of people that are attending. I think you been at ease as as a technology is really starting to hit its stride in the mainstream. It's a combination. I think of a number of factors. You have the developer community that's starting to really sort of embrace containers as they sort of re fact to their applications. So you have that going on, and then you have the ops persona or the people that actually have to manage and deploy the Cuban in these clusters that are starting to dive in and go waken. Take this on. We know what it means to actually manage a Cuban aunties cluster. The thing that what we're bringing, I think at Cisco is, ah, a curated staff. The opinionated stack, the ability to manage those clusters ability to actually deploy those clusters, whether it's on prime in the private in the private cloud, or leveraging the AP eyes that eight of us or Google or sure would publicly provide so that you can manage those clusters in the in the actual public's places. Well, so you have a combination of factors that are starting to come together. They're really sort of said, This is the opportunity that we're starting to see it happen right now. >> How would container ization looking at that example that Barber gave of the 100 year old bank needing to transform quickly? Otherwise, there there's so much competition, but not from your perspective. How what are some of the biggest advantage is that a legacy organization like 100 year old make is going to get by adopting containers. >> Yeah, so containers is one thing. So speed of innovation where they actually have to take their application. Asians, let's, for example, as a developer, you're have taken your monolithic applications re factor than into micro services. Now you have one piece of code turning into multiple different pieces of code in containers. Now what you have to do is you have to manage those containers, and that's where Cuban aunties comes in to be ableto orchestrate. Those containers in Google has really sort of offered this technology to the community, and that's where I think you know. You have the history of Google's, you know, operational sort of expertise, the open source ability to take uber Netease and then Sisko to sort of wrap around the lifecycle management of those containers so that you can not think about how, like the note operating system, the doctor run time, all the pieces that make up that stack and let the developers just focus on their code. And that's really what we're trying to do is enable the developers to focus on their code and not have, you know, on entire team of folks managing the cluster itself. >> So, Barbara, it's an open source community. There's a lot of partners involved. So what leads customers? Teo, turn to Sisko for these type of solutions. What differentiates them >> when you when you look at a company trying to do it on their own, I'm going to go do it is a service I'm gonna offer. Containers is a service right to do it on their own. Could take a year or more. I talked to a entertainment company the other day, and they had been working on trying to just define the requirements to do a container platform for a year. So if they could come to a company like Cisco and they can buy the container platform, we have as a sass offering, have it up and running in a matter of hours, which we have presidents of it running up in a couple of couple of hours and then delivering containers is a service to their constituents. It makes the team you're oh, right when you also look at how much it takes to curate that and then maintain it over time, the ability for us to actually consume the changes from the open source community curate that and release it is very fast. So from a nightie perspective, a nightie administrators perspective, you're able to take that offer it to the community, allow them to do development wherever they want to develop, whether it's in the public cloud, whether it's on from but maintain that, control it within the community, then you've got something right, and I mean, Matt could talk about that, too. But But then he'll agree. When we go to all the customers what our container pop firm does, how it leverages Coover Netease. How fast we give the updates out to our customers, and at the price point they are why we're talking about a month, two months. It is a pretty phenomenal opportunity for administrators to get something up and running an offering to their community very, very quickly. >> Yeah, No, you bring up some great points. They remember a couple of years ago when I talk to most customers, it's like, Well, what's your stack? Well, I pull these 35 different tools and I build all this stuff and I'm like, and I'm sorry, Don't you remember when we went to Cloud? It's about getting rid of that undifferentiated heavy lifting. Exactly why is this mission critical for your business to build and maintain this stack? And of course, the interest is for most customers out there. I want to consume it in platforms and from vendors that I trust so that I can focus on what's important in my business and drive the those business drivers. So it was a maturity thing for some of those early customers. So that Ari there, I mean, because Sisko, you've got your Cisco Container platform. You partner with the aid of Lewis's Googles. The world. Yeah, you know, Are we getting that point where customers shouldn't need to even think about that? That there's that communities and service measures and all that stuff in the >> middle of the number one goal is simplicity. And and what I would say with the container platform is that we are leveraging the speed of innovation that's occurring at the public cloud. So we're not taking a a curated stack from Cisco and putting it on the public cloud. We're leveraging the speed of innovation that that the public cloud provides. But at the same time, we're also taking that that cluster and we're putting it on crime into a private cloud. And I say Right now you're the point you're making is spot on, You know you don't necessarily in an ice tea shop with developers managing that entire stack from top to bottom. You know, why would you want to do that? And a recent quote that I heard recently was you either purchase or buy the product or you are the product, and I think that's a fascinating way to look at it because, you know, you could do that, you could curate it. You could absolutely, from top to bond curate the entire stock. But what typically happens that we're seeing from customers is well, um, organizations move on. They might not necessarily know what was built. They might be code that goes, gets older and expires, or you know gets out of dates. And so now you get stuck in an environment where your not terrified. But there's a nervousness, trepidation of going. I don't know, Let's not break it. If it ain't broke, don't fix it. And that's a lot of times what happens in these stacks. So I think we're absolutely with the CCP and the public how we're starting to actually get to that. >> So, Barbara, last question for you talking about the speed of innovation and when you were describing the massive fast R A Y customers can get by working with you guys from a container solution perspective, it's It's a no brainer as we look at some of the things that we know were coming. The wave of connectivity changes. Five. G WiFi sex. What excites you about how Cisco's story from a container platform perspective is going to change? Change as you start building and crisis that continued building technologies for these networks that are primarily wireless and incredibly fast. >> I think that's exciting for me is the way we approach the architecture, er way we're looking at certainly being more open, everything we do, building it with open AP eyes uh, and and looking across that Cisco stack knowing that at this moment in time, if you would've asked us five years ago Where are you? In cloud, Right? If you would've asked us 10 years ago, what are you going to do in Cloud? But at this moment in time to look at how we differentiate ourselves like I mentioned, every cloud started to the network. You've got to secure the entire infrastructure. You've gotta have connectivity between the clouds. Hence the CCP, the container platform, right. You have to have cloud management. You have to have cloud analytics way. Bring all of that together. So if a company has made investments and Cisco in the past, those those investments are going to come forward in this new multi cloud, multi tool man's domain landscape. And they can leverage those investments while they continue to invest with Cisco in innovations. And and that's what that's what really excites me. I think also just the world of a I and ML and big data And how when excites me is that developers Khun develop anywhere they can use all the great tools that are available. And I love the idea that the control is back in the hands of the I t administrator. From a compliance standpoint from a governance stand like we're bringing that control back into developers hands while giving the speed of innovation and the ability to develop anywhere back to the line of business in the developers. That combination is just really exciting at this moment in time. >> Awesome. And here we are in the definite zone. This is a massive community of over nearly 600,000. Strong, definite. So can you imagine all the innovation going on in this room behind us on day one? We'll we thank you both so much, Barbara, and not for joining stew and me on the A kid this afternoon. Lots of exciting things to come. Francisco or just the as I think, Chuck said this morning, were just getting started. >> We are just getting started. >> Absolutely. >> Guys are pleasure. Forced to mint a man, I'm Lisa Martin and you're watching The Cube from Cisco Live 2019

>> Live from San Diego, California It's the queue covering Sisqo Live US 2019 Tio by Cisco and its ecosystem barkers. >> Welcome back to the cubes Coverage of Day One of Sisqo Live from Sunny San Diego on Lisa Martin, my co hostess, student, a Man and Stewart Air. Pleased to welcome a couple of guests from this Cisco platform in Solutions Group, We've got Barbara Half Li, senior director of Business development Barbeque. Great to Have You Iced Beer and Matt Ferguson, director of product development. Matt, Welcome. >> Thank you. Nice to be here. >> So we appreciate you guys being here right at the start of happy hour here in San Diego. Thank you. Some our drinking water. Right wing quick. Just getting so, Barbara. So here we are at this's the 30th year Cisco's partner and customer, then a lot. A lot happens in 30 years. A lot of change here we are customers in every industry, living in this multi cloud hybrid world for many reasons. >> What are some >> of the things from the business perspective that you're hearing from customers? What are they looking to Sisko to do to help them traverse this new multi cloud world successfully. >> Yeah, well, one of the things that we hear customers tell us often is how doe I manage this landscape. Many people think of the cloud is just Oh, I've got a public cloud or oh, I'm gonna have my cloud on primp. But really, with the explosion of devices and I ot right, people want to know. How do we take that data from the edge from the edge? What do I do with that data? Do I put it up in a public cloud immediately? Do I bring it back to do some kind of analysis on that data? Is it goto a polo? Does it come to the branch doesn't go to the headquarters and that lance games very complex. So you look across that landscape and as customers of either proactively adopted the public cloud or had to adopt multiple clouds because of acquisitions, they've made this lands. Skip just gets incredibly complex very, very quickly. So when people come to Cisco, they basically looking for a couple of things. Number one security. Because putting the security wrapper around all of that right, it becomes paramount. People lose their jobs if they're data isn't protected, so they want help with their security. They also want to know what's the best cost mix, right? How do I have the right options available to me? But the other thing they really want is speed of innovation. I mean, we hear this over and over and over. I talked to a bank the other day. 100 year old bank, right? You think 100 year old bank, um, speed of innovation may not be top of their priority, but absolutely. I walked in and they held up the phone and they said, Our competitors Aire delivering capabilities faster for the mobile user. And every time our competitors releases a new application or a new feature, I lose market share. So it isn't about cost savings anymore. It's about speed of innovation, even for 100 year old bank. When they come to Cisco, they want to know, Can you help secure this landscape? Can you give me speed of innovation? And then, of course, every cloud started the networking layer as well, right? So what innovation Cisco doing on the networking site? So these are some of the things that's customers come to Cisco and they ask us, what can you do for us and the help that they want? It comes back to innovation every time. >> Barbara. Actually, I've talked to some of those homes year old cos they need it more than ever, because that five year old bank doesn't have all the legacy and they're already moving is fast. But it's an interesting point. Matt. You know, we've been tracking community since the early days. This year, it finally feels like it's gotten to a certain maturity level, such that I've talked to a number of customers talking about how that is a lever for their digital transformation, how they're modernizing their application for portfolio and not just, you know, the, you know, making of the sausage of how this, you know, container orchestration, layers going toe, you know, do something that most people won't understand. It's that connection with the business kind of building up. What what? Barber says. They're bring us inside a little bit more. You know the community's piece of that, >> Yeah, it's absolutely been tremendous to see the CNC F and Kume con absolutely just take off on the number of people that are attending. I think humanity's as as a technology is really starting to hit its stride in the mainstream. It's a combination. I think of a number of factors. You have the developer community that's starting to really sort of embrace containers as they sort of re fact to their applications. So you have that going on, and then you have the ops persona or the people that actually have to manage and deploy the Cuban in these clusters that are starting to dive in and go waken. Take this on. We know what it means to actually manage a Cuban aunties cluster. The thing that what we're bringing, I think at Cisco is, ah, a curated staff. The opinionated stack, the ability to manage those clusters ability to actually deploy those clusters, whether it's on prime in the private in the private cloud, or leveraging the AP eyes that eight of us or Google or azure would publicly provide so that you can manage those clusters in the in the actual public's places. Well, so you have a combination of factors that are starting to come together. They're really sort of said, This is the opportunity, and we're starting to see it happen right now, >> how would container ization looking at that example, that Barber gave up 100 year old bank needing to transform quickly. Otherwise, there there's so much competition, but not from your perspective. How what are some of the biggest advantage is that a legacy organization like 100 year old make is going to get by adopting containers. >> Yeah, so containers is one thing. So speed of innovation where they actually have to take their application. Shins. Let's, for example, as a developer, you're have taken your monolithic applications re factor than into micro services. Now you have one piece of code turning into multiple different pieces of code in containers. Now what you have to do is you have to manage those containers, and that's where Cuban aunties comes in to be ableto orchestrate. Those containers in Google has really sort of offered this technology to the community, and that's where I think you know. You have the history of Google's, you know, operational sort of expertise, the open source ability to take uber Netease and then Sisko to sort of wrap around the lifecycle management of those containers so that you can not think about how, like note operating system, the doctor run time, all the pieces that make up that stack and let the developers just focus on their code. And that's really what we're trying to do is enable the developers to focus on their code and not have, you know, on entire team of folks managing the cluster itself. >> So, Barbara, it's an open source community. There's a lot of partners involved. So what leads customers? Teo, turn to Sisko for these type of solutions. What differentiates them >> when you when you look at a company trying to do it on their own, I'm going to go do it is a service I'm gonna offer. Containers is a service right to do it on their own. Could take a year or more. I talked to a entertainment company the other day, and they had been working on trying to just define the requirements to do a container platform for a year. So if they could come to a company like Cisco and they can buy the container platform, we have as a sass offering, have it up and running in a matter of hours, which we have presidents of it running up in a couple of couple of dollars and then delivering containers is a service to their constituents. It makes the team a hero, right when you also look at how much it takes to curate that and then maintain it over time, the ability for us to actually consume the changes from the open source community curate that and release it is very fast. So from a nightie perspective, a nightie administrators perspective, you're able to take that offer it to the community, allow them to do development wherever they want to develop, whether it's in the public cloud, whether it's on from but maintain that, control it within the community, then you've got something right, and I mean, that could talk about that, too. But but then he'll agree. When we go to all the customers what our container pop firm does, how it leverages Cooper Netease. How fast we give the updates out to our customers and at the price point, the r o. Why we're talking about a month, two months. It is a pretty phenomenal opportunity for administrators to get something up and running an offering to their community very, very quickly. >> Yeah, no, you bring up some great points. They remember a couple of years ago. When I talk to most customers, it's like, Well, what's your stack? Well, I pull these 35 different tools and I build all this stuff down like and I'm sorry, Don't you remember when we went to Cloud? It's about getting rid of that undifferentiated heavy lifting. Exactly why is this mission critical for your business to build and maintain this stack? And of course, the interest is for most customers out there. I want to consume it in platforms and from vendors that I trust so that I can focus on what's important in my business and drive the those business drivers. So it was a maturity thing for some of those early customers. So that Ari there, I mean, because Sisko, you've got your Cisco Container platform. You partner with the aid of Lewis's Googles. The world. Yeah, you know, Are we getting that point where customers shouldn't need to even think about that? That there's that communities and service measures and all that stuff in the >> middle of the number one goal is simplicity. And and what I would say with the container platform is that we are leveraging the speed of innovation that's occurring at the public cloud. So we're not taking a a curated stack from Cisco and putting it on the public cloud. We're leveraging the speed of innovation that that the public cloud provides. But at the same time, we're also taking that that cluster and we're putting it on prime into a private cloud. And I say Right now you're the point you're making is spot on, You know you don't necessarily in an ice tea shop with developers managing that entire stack from top to bottom, you know, why would you want to do that? And a recent quote that I heard recently was your either purchase or buy the product or you are the product, and I think that's a fascinating way to look at it because, you know, you could do that, you could curate it. You could absolutely, from top to bond curate the entire stock. But what typically happens that we're seeing from customers is well, organisations move on. They might not necessarily know what was built. They might be code that goes, gets older and expires or, you know, gets out of dates. And so now you get stuck in an environment where your not terrified. But there's a nervousness, trepidation of going. I don't know, Let's not break it. If it ain't broke, don't fix it. And that's a lot of times what happens in these stacks. So I think we're absolutely with The CCP and the public file were starting to actually get to that >> barber last question for you talking about the speed of innovation and when you were describing the massively fast R a y that customers can get by working with you guys from the container solution perspective, it's It's a no brainer because we look at some of the things that we know were coming. The wave of connectivity changes. Five. G. WiFi sex. What excites you about how Cisco's story from a container platform perspective is gonna change? Change as you start building and crisis that continued building technologies for these networks that are primarily wireless and incredibly fast. >> I think that's exciting for me is the way we approach the architecture, er way we're looking at certainly being more open. Everything we do, building it with open AP eyes, uh, and and looking across that Francisco stack knowing that at this moment in time, If you would've asked us five years ago Where are you? In cloud, right? If you would've asked us 10 years ago, what are you going to do in cloud? But at this moment in time to look at how we differentiate ourselves Like I mentioned, every cloud started to the network. You've got to secure the entire infrastructure. You've gotta have connectivity between the clouds. Hence the CCP, the container platform, right. You have to have cloud management. You have to have cloud analytics way. Bring all of that together. So if a company has made investments and Cisco in the past, those those investments are going to come forward in this new multi cloud, multi tool man domain landscape. And they can leverage those investments while they continue to invest with Cisco in innovations. And And that's what That's what really excites me. I think also just the world of a I and ML and big data. And how when excites me is that developers Khun develop anywhere they can use all the great tools that are available. And I love the idea that the control is back in the hands of the I T administrator from a compliance standpoint from a governance stand like we're bringing that control back into developers hands while giving the speed of innovation and the ability to develop anywhere back to the line of business in the developers. That combination is just really exciting at this moment in time. >> Awesome. And here we are in the definite zone. This is a massive community of over nearly 600,000. Strong, definite. So imagine all the innovation going on in this room behind us on day one. We'll we thank you both so much, Barbara, and not for joining stew and me on the kid this afternoon. Lots of exciting things to come. Francisco or just the as I think, Chuck said this morning, were just getting started. >> We are just getting started. >> Absolutely. >> Guys are pleasure. Forced to mint a man, I'm Lisa Martin and you're watching The Cube from Cisco Live 2019

>> from our studios in the heart of Silicon Valley. HOLLOWAY ALTO, California It is a cube conversation. >> Hi, Welcome to the Cube Studios. From the Cube conversation, we go in depth with thought leaders driving innovation across the tech industry. I'm today's host. Beauty burst. One of the biggest challenges at every enterprise faces, especially those that are considering a serious move to the cloud, goes way beyond any questions about compute. Wait beyond any questions about storage. Perhaps the most important question will be, What do I do with my network? How does my network transform? How does my security profile transform in response to a movement to the cloud? Now there are a lot of reasons why, but one of the chief wants the cod really isn't a strategy for centralising your I t and your applications in your data, it's better thought of his cloud from more broadly distributing that function, getting it close to the action. Where is going to generate the most value? Big challenge for enterprise is in tow. Have that conversation. We've got Matt Carter, who's the CEO of Ari, aka >> not welcome to the Cube. >> Thanks for having me >> so before we get into this important question. Give us the update on Hari, aka >> So recently we were got investment. Goldman Sachs, Siri's F $50,000,000 that capital is going to really be deployed towards helping us to expand our global footprint, put money into marketing more sales. People build out processes internally as a company. So we're well capitalized and a really great position to take advantage of the enormous growth that we see in this space. >> So I mentioned upfront this notion that the cloud is a strategy for distributing your work and with controls and with certainty and with greater security, perhaps even more so than it should be thought of as a way of centralizing things that's puts enormous pressure on networks. What are you hearing from your customers as they think about some of these challenges? >> Well, one of the big challenges for a lot of our customers is complexity. Many of them have worked with a number of different providers to be able to stitch together a reliable, secure network. What makes Hari Aku is so differentiated is that we're able to manage that as one single source provider. We have a global network. We have a secure network, and so we make it easy. We take out the complexity for our customers and even more importantly, what we also do. We help out customers to accelerate their digital transformation. Many of them are going through various stages of digital transformation, able to do that by work with one single provide, like Harry, AKA who could help accelerate that in state for them much faster than others in the marketplace today. >> So you're trying to remove the network from the transformational or from the from the side of uncertainty when we start talking about digital transformation. But what is the Ariake, the Ariake Network? This this notion that you have a full stack from the actual network all the way up to the software to find services? What's the How does that manifest itself as different apologies or different approaches to your customers? >> Yes, so think of it this way, Peter. So for a customer to put together a holistic network, they're different component pot. So one component part is to say, last smile. So being able to get that circuitry broadband circuitry someplace around the world, they have to deal with a number of different vendors around that we were able to be the single source provided provided for the customers. Secondly, they have to then figure how to connect to the cloud. And they're working with a number of different telco providers to help them to stitch together that piece again. We have our own global pops around the world were able to provide the local the last mile, plus that sort of middle stage there for the customer as one single source provider. So again, complexity is the thing that's actually driving a lot of the challenges for our customers. Way able to sort of do that as one single source provided for our customers. >> But it sounds like you're also in a position to say we can reduce complexity, but we can also increase the flexibility that the network has. So I was talking with large customer large client earlier this week on one of the things that they observed is they're trying to reduce the amount of traffic disassociate with back haul back to the corporate network before close to some sass provider. How our customers ultimately starting to rethink how they direct traffic because a good, solid foundation like Ari AKA should allow you greater flexibility and how you target traffic to different circuits at different times based on location, application, data and identity. >> Yeah, so part of the thing that what customers are also to build upon that face with this is that what type of traffic works works best on what network, right? And so if you're dealing with a variety of different networks, it creates a lot of monitoring. Ah, lot of flexibility and lack of reliability for the customer. So with us again, we're able to provide them insight to application performance and use a state performance because it's all one single network, and we've become, quite frankly, an early detector. If there are problems with particular types of applications, were able to inform the customer of that and make the appropriate changes to allow for much more seamless, reliable application experience for our customers. >> So let's talk about specifically how you're helping customers. Today was one of the offers that you have and some of the approach that you have to engage in them. So one of the challenges within any large organization is to get the groupings of individuals to agree on what the problem is in the direction to take, the more shared the resources, the Mohr people participating in the conversation. Let's be honest. Is nothing more shared in an organization today than a network? How are you seeing your customers succeed? And sometimes, you know, fall victim to the challenges of tryingto build that unity around how to move forward? >> Yeah, that's a really great question. So what we have found this that it's not a single decision maker any longer in eh? In a minute with the customer. There are the lists, a willing dealing with the CTO to CEO. He or she has a constituency who have a say around the types of applications or networking that we're using to deploy that those applications. So what we have found that Ari, aka that the approach we have to take is that we have to be really good, if you will. Diplomats knowing how to go into a customer really working partner with the various constituencies, getting them in a room, making sure that they understand and help them to sort of see the end state vision and a lot of ways part of what we're trying to do with the CEO of CTO is how do we become a really good partner for them to help them help their constituents season? So what we call it our reactors no innovate grow. The no part of what we dio is actually one of the most important component parts of how we go to market. What is the problem? How does his problem impact? You know, the various constituencies inside that customer and their and their customers. So getting dimensional, dimensional izing that problem makes you were bringing the right people to the table is a really putting competency that we have, you know, manifested overtime to help that organization become successful. The thing that's important for us, we've us houses an enabler, and so you just don't see you know you enable you. You have to really work with the customer and really understand the problem that they're faced with. How do we enable the customer to really understand Dimensional is the problem and figure out how our solution helps that customer solve that problem or take advantage of that opportunity. So we call in no innovate crowd that no pa, it's really important that innovates not just invention It's really about making sure we're able to position and Taylor our solution set to the needs of the customer and grow the grow pot is really all about our customers. Success. Did we help them to become successful? Whatever that objective is. Opening up offices in China and getting their sales team productive up and running quickly. Tow, monetize, opportunity, stare. Whatever those growth objectives are, how do we help them to become successful? So everything we do is a line to the customs success, so no innovate grow. It's a real part of how we go to market. To serve the customer is comprehensive. Um, it's time consuming, but we feel is differentiating because we're not just selling you a, um you know, sort of a solution, so to speak. What was really selling you is is a a way to solve a problem or take advantage of that opportunity is a different sort of the mention of how we go to market with the others. >> So talk we'll talk a bit about how that is translating into customer success directly. You got a good product. Sounds could get a good love to go to market strategy. Really love the emphasis on on innovate. Which will you look at is how do you get your customers to successfully adopt time to value reduced uncertainty, Deeper integration? Mohr Embedded nous How is that translating success toes a little bit about how you're seeing? Are his customers be able to do things differently as a result >> so that the two pasta de so the first pot is the existing customers? So let's start with the fact that most of the existing customers who came to us came to us because they had a particular problem someplace around the world. So let us say we way. We've been able to get sort of a few sort of site locations with them. They like what they see when they come back to says, Hey, you know, you solve this problem here. Can you help us solve this problem over here? And then over time we may be able to expand, increase share. I'm with the existing customers. The second thing that we've done is that I've always said to the team, since I've been in the company with the best kept secret out there, that people don't realize that we offer this sort of into end man its service. And our customers know our customs have been good evangelist and helping us to bring in more customers. But as biggest, the market opportunity is not enough people know who we are. So part of what we're doing now, Peter is really elevating brand present. You know, if you're gonna be a company that's moving up the stack and if you're a CEO who's gonna outsource this decision, that's your connectivity. To accompany Ari aka you need to know that the person sitting across the table from you understands me gets me has thie empathy, right, sensitivities of the problems that we're dealing with, So great deal of what we're now doing is, you know, I brought in a new team. Folks have been near done that folks who've sold to these folks over the years who understand those customers problems, so elevating out brand, bringing the right level of competency into the organization and really send them make out brand muchmore wear around how we help our customers solve these problems. So a little bit of this marketing, you know, in sales. But the main thing >> is, it's just that >> we're now in a position where we need to really hone in on getting up brand much more elevated. So people understand how we solve their >> problems, engagement across entire life cycle, it's and service to success. So where is s so we could kind of see you are a good, fast growth company on the market. That's, I think, is going to become increasingly hot as people start to realize the role that network transformations going to play in this whole thing. Um, how do you see Orry, aka being a force say, in 23 years, I c e o you got to be thinking about >> well, you know, constant thinking about that. So for us, it's really, um, continue to add more innovation to our platform and a big part of that innovation. You nose around security as you're starting to, its more things going to the cloud. People want to know that isjust a secure platform. We have a very secure platform today, but we'll continue to innovate and add more layers to that. So that's one piece. The second piece is is too, you know, continue to invents, elevate our brand out into the marketplace. So we got a show about the places that give people. It's that this is a company that's going to be around for a while. That has sustainability, etcetera, so elevated and really, you know, we have a guy on our team, Ash Watt, who really is a pioneer in this space around the technology and where it's going having more thought, leadership, showing up at the right sort of conferences, making sure that we are framing and helping toe lead the thoughts around, you know, S T win and how it plays a role in the marketplace >> making that no consumable >> making that no consumable. That's exactly that's exactly right. So I think for us it's really the continuation of maturing and growing as a company. You know, we've been a Silicon Valley start up company. We've operated as a Silicon Valley start up company, but now where we are and given the complexities of managing a network right is that we have to now come across to our customers that where a company that is here for the long haul that that we have taken into account off the precautions all the necessary building blocks. Tobe able to deploy, secure global network today. We do that. Not enough people know about that. We need to continue to enhance that message healthy. >> Well, every company has its challenges, and every company has its go forward. But I could tell you, certainly our clients speak well of Ariake. So, Matt Carter, Thanks very much for being on the Cube. >> Thank you, >> Andi. Once again, we've been >> talking about Carter, CEO of Ari, aka >> Thanks for joining us for another cube conversation on Universe. See you next time.