>>Hi, we're back. We're watching, you're watching the cube coverage of Falcon 2022 live from the aria in Las Vegas, Dave Valante with Dave Nicholson and we, yes, folks, there are females in the cyber security industry. Amanda Adams is here. So the vice president of America Alliance at CrowdStrike. Thanks for coming on. >>Thank you so much for having me. >>We it's, it's fantastic to, to actually, as I was starting to wonder, but we >>Do have females in leadership. >>Wait, I'm just kidding. There are plenty of females here, but this cybersecurity industry in general, maybe if we have time, we can talk about that, but I wanna talk about the, the Alliance program, but before I do, yeah. You know, you, you got a nice career here at CrowdStrike, right? You've kind of seen the ascendancy, the rocket ship you've been on it for five years. Yep. So what's that been like? And if you had to put on the binoculars and look five years forward, what can you tell us in that 10 year span? Oh >>My goodness. What a journey it's been over the last five, six years. I've been with CrowdStrike almost six years and really starting with our first core group of partners and building out the alliances, seen obviously the transformation with our sales organization. And as we scaled, I think of our, of our technology. We started with, I think, two products at that time, we were focused on reinventing how our customers thought about NextGen AB but also endpoint detection response. From there, the evolution is really driving towards that cloud security platform, right? How our partners fit into that. And, and how we've evolved is it's not just resell. It's not just focusing on the margin and transactions. We really have focused on building the strategic relationships with our partners, but also our customers and fitting them in that better together story with that CrowdStrike platform. It's been the biggest shift. Yeah. >>And you've got that. The platform chops for that. It's just, I think you're up to 22 modules now. So you're not a point product. You guys make that, that, that point lot now in terms of the, the partners and the ecosystem, you know, it's, it's, it's good here. I mean, it's, this it's buzzing. I've said it's like service. I've said, number of times, it's like service. Now back in 2013, I was there now. They didn't have the down market, the SMB that you have that's right. And I think you you're gonna have an order. You got 20,000 customers. That's right. I predict CrowdStrike's gonna have 200,000. I, I'm not gonna predict when I need to think about that. But, but in thinking about the, the, the co your colleagues and the partners and the skill sets that have evolved, what's critical today. And, and, and what do you see as critical in the future? >>So from a skill set standpoint, if I'm a partner and engaging with CrowdStrike and our customers, if you think about, again, evolving away from just resell, we have eight routes to market. So while that may sound complicated, the way that I like to think about it is that we truly flex to our partners, go to market their business models of what works best for their organization, but also their customers. The way that they've changed, I think from a skillset standpoint is looking beyond just the technology from a platform, building a better together story with our tech Alliance partners or store, if thinking about the XDR Alliance, which we are focusing on, there's so much great value in bringing that to our customers from a skillset standpoint, beyond those services services, we've talked about every day. I know that this is gonna be a top topic for the week yesterday through our partner summit, George, our CEO, as well as Jim Cidel, that's really the opportunity as we expand in new modules. If you think about humo or log scale identity, and then cloud our partners play a critical role when it comes into the cloud migration deployment integration services, really, we're not gonna get bigger from a services organization. And that's where we need our partners to step in. >>Yeah. And, you know, we we've talked a lot about XDR yeah. Already in day one here. Yeah. With, with the X extending into other areas. That's right. I think that services be, would become even more critical at that point, you know, as you spread out into the, really the internet of things that's right. Especially all of the old things that are out there that maybe should be on the internet, but aren't yet. Yeah. But once they are security is important. So what are you doing in that arena from a services perspective to, to bolster that capability? Is it, is it, is it internally, or is it through partners generally? >>It's definitely, I think we look to our partners to extend beyond the core of what we do. We do endpoint really well, right? Our services is one of the best in the business. When you look at instant response, our proactive services, supporting our customers. If you think to XDR of integration, building out those connect air packs with our customers, building the alliances, we really do work with our partners to drive that successful outcome with our customers. But also too, I think about it with our tech alliances of building out the integration that takes a lot of effort and work. We have a great team internally, which will help guide those services to be, to be built. Right. You have to have support when you're building the integrations, which is great, but really from like a tech Alliance and store standpoint, looking to add use cases, add value to more store apps for our customers, that's where we're headed. Right. >>What about developers? Do you see that as a component of the ecosystem in the future? Yeah, >>Without a doubt. I mean, I think that as our partner program evolves right now working with our, our developers, I mean, there's different personas that we work with with our customer standpoint, but from a partner working with them to build our new codes, the integration that's gonna be pretty important. >>So we were, we sort of tongue in cheek at the beginning of this interview yeah. With women in tech. And it's a, it's a topic that, on the cube that we've been very passionate about since day one yep. On the cube. So how'd you get in to this business? H how did your, your career progress, how did you get to where you are? >>You know, I have been incredibly fortunate to have connections, and I think it's who, you know, and your network, not necessarily what, you know, to a certain extent, you have to be smart to make it long term. Right. You have to have integrity. Do what you're saying. You're gonna do. I first started at Cisco and I had a connection of, it was actually a parent of somebody I grew up with. And they're like, you would fit in very nicely to Cisco. And I started with their channel marketing team, learned a ton about the business, how to structure, how to support. And that was the first step into technology. If you would've asked me 20 years ago, what did I wanna do? I actually wanted to be a GM of an organization. And I was coming outta I come on, which is great, which I'm, it really is right up. >>If you knew me, you're like, that actually makes a lot of sense. But coming outta college, I had an opportunity. I was interviewing with the golden state warriors in California, and I was interviewing with Cisco and that I had two ops and I was living in San Jose at the time. The golden state warriors of course paid less. It was a better opportunity in sales, but it was obviously where I wanted to go from athletics. And I grew up in athletics, playing volleyball. Cisco paid me more, and it was in San Jose. And really the, the golden state warriors seemed that I was having that conversation. They said, one year community is gonna be awful. It's awful from San Jose to Oakland, but also too, like you have more money on the table. Go take that. And so I could have very much ended up in athletics, most likely in the back office, somewhere. Like I would love that. And then from there, I went from Cisco. I actually worked for a reseller for quite some time, looking at, or selling into Manhattan when I moved from California to Manhattan, went to tenable. And that was when I shifted really into channel management. I love relationships, getting snow people, building partnerships, seeing that long term, that's really where I thrive. And then from there came to CrowdStrike, which in itself has been an incredible journey. I bet. Yeah. >>Yeah. I think there's an important thread there to pull on. And that is, we, we put a lot of emphasis on stem, which people, some sometimes translate into one thing, writing code that's right. There are, but would you agree? There are many, many, many opportunities in tech that aren't just coding. >>Absolutely. >>And I think I, as a father of three daughters, it's, it's a message that I have shared with them. Yeah. They are not interested in the coding part of things, but still, they need to know that there are so many opportunities and, and it's always, sometimes it's happenstance in terms of finding the opportunity in your case, it was, you know, cosmic connection that's right. But, but that's, you know, that's something that we can foster is that idea that it's not just about the hardcore engineering and coding aspect, it's business >>That's right. So if, if there was one thing that I can walk away from today is I say that all the time, right? If you look at CrowdStrike in our mission, we really don't have a mission statement. We stop breaches every single day. When I come to work and I support our partners, I'm not super technical. I obviously know our technology and I, I enable and train our partners, but I'm not coding. Right. And I make an impact to our business, our partners, more importantly, our customers, every single day, we have folks that you can come from a marketing operations. There is legal, there's finance. I deal with folks all across the business that aren't super technical, but are making a huge impact. And I, I don't think that we talk about the opportunities outside of engineering with the broader groups. We talk about stem a lot, but within college, and I look to see like getting those early in career folks, either through an intern program could be sales, but too, if they don't like, like sales, then they shift into marketing or operations. It's a great way to get into the industry. >>Yeah. But I still think you gotta like tech to be in the tech business. Oh, you >>Do? Yeah. You do. I'm >>Not saying it's like deep down is like, not all of us, but a lot of us are kind of just, you know, well, at least you, >>At least you can't hate it. >>Right. Okay. But so women, 50% of the population, I think the stat is 17% in the technology. Yeah. Industry, maybe it's changed a little bit, but you know, 20% or, or less, why do you think that is? >>I, you know, I always go back to within technology, people hire from their network and people that they know, and usually your network are people that are very like-minded or similar to you. I have referred females into CrowdStrike. It's a priority of mine. I also have a circle that is also men, but also too, if you look at the folks that are hired into CrowdStrike, but also other technology companies, that's the first thing that I go to also too. I think it's a little bit intimidating. Right. I have a very strong personality and I'm very direct, but also too, like I can keep up with our industry when it comes to that stereotypes essentially. And some people maybe are introverted and they're not quite sure where they fit in. Right. Whether it's marketing operations, et cetera. So they, they're not sure of the opportunities or even aware of where to get started. You know what I mean? >>Yeah. I mean, I think there is a, a, a stereotype today, but I'm not sure why it's, is it unique to the, to the technology industry? No. Is it not? Right? It happens >>Thinking, I mean, there's so many industries where healthcare, >>Maybe not so much. Right. Because you know, >>You have nurses versus doctors. I feel like that is flipped. >>Yeah. That's true. Nurses versus doctors. Right. Well, I, I know a lot of women doctors though, but >>Yeah. That's kind of flipped. It's better. >>Yeah. Says >>Flipped over. Yeah. I think it's more women in medical school now, but than than men. But, >>And, and I do think in our industry, you know, when you look at companies like IBM, HPE, Cisco, Dell, and, and, and many others. Yeah. They are making a concerted effort for on round diversity. They typically have somebody who's in charge of diversity. They report, you know, maybe not directly to the CEO, but they certainly have a seat at the table. That's right. And you know, maybe you call it, oh, it's quotas. Maybe the, the old white guys feel, you know, a little slighted, whatever. It's like, nobody's crying for us. I mean, it's not like we got screwed. >>See, I know problema we can do this in Spanish. Oh, oh, >>Oh, you're not a old white guy. Sorry. We can do >>This in Spanish if you want. >>Okay. Here we go. So, no, but, but, but I, so I do think that, that the industry in general, I talked to John Chambers about this recently and he was like, look, we gotta do way better. And I don't disagree with that. But I think that, I think the industry is doing better, but I wonder if like a rocket ship company, like CrowdStrike who has so many other things going on, you know, maybe they gotta get you a certain size. I mean, you've reached escape velocity. You're doing obviously a lot of corporate, you know, good. Yeah. You know, and, and, and, and we just had earlier on we, you know, motor motor guides was very cool. Yeah. So maybe it's a maturity thing. Maybe these larger companies with you crowd size $40 billion market cap, but maybe the, the hundred plus billion dollar market cap companies. I don't know. I don't know. You guys got a bigger market cap than Dell. So >>I, I don't think it's necessarily related to market cap. I think it's the size of the organization of how many roles are open that we currently write. So we're at just over 6,000 employees. If you look at Cisco, how many thousands of employees they have there's >>Right. Maybe a hundred thousand employees. >>That's right. There's >>More opportunities. How many, what's a headcount of crowd strike >>Just over 6,000, >>6,000. So, okay. But >>If you think about the, the areas of opportunity for advancement, and we were talking about this earlier, when you look at early and career or entry level, it's actually quite, even right across the Americas of, we do have a great female population. And then as progression happens, that's where it, it tees off from a, a female in leadership. And we're doing, we're focusing on that, right? Under JC Herrera's leadership, as well as with George. One of the things that I always think is important though, is that you're mindful as, as the female within the organization and that you're out seeking somebody, who's not only a mentor, but is a direct champion for you when you're not in the room. Right. This is true of CrowdStrike. It's true of every organization. You're not gonna be aware of the opportunities as the roles are being created. And really, as the roles are being created, they probably have somebody in mind. Right. And so if you have somebody that's in that room says, you know what, Amanda Adams would be perfect for that. Let's go talk to her about it. You have to have somebody who's your champion. Yeah. >>There there's, there's, there's a saying that 80% of the most important moments in your life happen in your absence. Yeah. And that's exactly right. You know, when they're, when someone needs to be there to champion, you, >>Did that happen for you? >>Yes. I have a very strong champion. >>So I mean, I, my observation is if, if you are a woman in tech and you're in a senior leadership position, like you are, or you're a, you're a general manager or a P and L manager or a CEO, you have to be so incredibly talented because all things being equal, maybe it's changing somewhat in some of those companies I talked about, but for the last 30 years, all takes be equal. A, a, a woman is gonna lose out to a man who is as qualified. And, and I think that's maybe slowly changing. Maybe you agree with that, maybe you don't. And maybe that's, some people think that's unfair, but you know, think about people of color. Right. They, they, they, they grew up with less op opportunities for education. And this is just the statistics that's right. Right. So should society overcompensate for that? I personally think, yes, the, the answer is just, they should, there should still be some type of meritocracy that's right. You know, but society has a responsibility to, you know, rise up all ships. >>I think there's a couple ways that you can address that through Falcon funds, scholarship programs, absolutely. Looking at supporting folks that are coming outta school, our internship program, providing those opportunities, but then just being mindful right. Of whether or not you publish the stats or not. We do have somebody who's responsible for D I, within CrowdStrike. They are looking at that and at least taking that step to understand what can we do to support the advancement across minorities. But also women is really, really important. >>Did you not have a good educational opportunity when you were growing up where you're like you had to me? Yeah, no, seriously, >>No. Seriously. I went to pretty scary schools. Right. >>Okay. So you could have gone down a really bad path. >>I, a lot of people that I grew up with went down really, really bad paths. I think the inflection point at, at least for me what the inflection point was becoming aware of this entire universe. Yeah. I was, I was headed down a path where I wasn't aware that any of this existed, when I got out of college, they were advertising in the newspaper for Cisco sales engineers, $150,000 a year. We will train. I'm a smart guy. I had no idea what that meant. Right. I could have easily gone and gotten one of those jobs. It was seven or eight years before I intersected with the tech world again. And so, you know, kind of parallel with your experience with you had someone randomly, it's like, you'd be great at Cisco. Yeah. But if, if you're not around that, and so you take people in different communities who are just, this might as well be a different planet. Yes. Yeah. The idea of eating in a restaurant where someone is serving you, food is uncomfortable, right? The idea of checking into a hotel, the idea of flying somewhere on an airplane, we talk about imposter syndrome. That's right. There are deep seated discomfort levels that people have because they just, this is completely foreign, but >>You're saying you could have foreign, you could have gone down a path where selling drugs or jacking cars was, was, was lucrative. >>I had, I had, yeah. I mean, we're getting, we're getting like deep into societal things. I was, I was very lucky. My parents were very, very young, but they're still together to this day. I had loving parents. We were very, very poor. We were surrounded by really, really, really bad stuff. So. >>Okay. So, so, okay. So this, >>I, I don't, I don't compare my situation to others. >>White woman. That's I guess this is my point. Yeah. The dynamic is different than, than a kid who grew up in the inner city. Yes. Right. And, and, and they're both important to address, but yeah. I think you gotta address them in different ways. >>Yes. But if they're, but if they're both completely ignorant of this, >>They don't know it. So it's lack of >>A, they'll never be here. >>You >>Never be here. And it's such a huge, this is such a huge difference from the rest of the world and from the rest, from the rest of our economy. >>So what would you tell a young girl? My daughters, aren't interested in tech. They want to go into fashion or healthcare, whatever Dave's daughters maybe would be a young girl, preteen, maybe teen interested in, not sure which path, why tech, what would advice would you give? >>I think just understanding what you enjoy about life, right? Like which skills are you great at? What characteristics about roles and not really focusing on a specific product. Definitely not cybersecurity versus like the broader network. I mean, literally what do you enjoy doing? And then the roles of, you know, from the skillset that's needed, whether that be marketing, and then you can start to dive into, do I wanna support marketing for a corporate environment for retail, for technology like that will come and follow your passion, which I know is so easy to say, right? But if you're passionate about certain things, I love relationships. I think that holding myself from integrity standpoint, leading with integrity, but building strong relationships on trust, that's something I take really pride in and what I get enjoyment with. It's >>Obviously your superpower. >>It, >>It is. >>But >>Then it will go back to OST too, just being authentic in the process of building those relationships, being direct to the transparency of understanding, like again, knowing what you're good at and then where you can fit into an organization, awareness of technology opportunities, I think will all lend that to. But I also wouldn't worry, like when I was 17 year old, I, I thought I would be playing volleyball in college and then going to work for a professional sports team. You know, life works out very differently. Yeah. >>Right. And then, and for those of you out there, so I love that. Thank you for that great interview. Really appreciate letting us go far field for those of you might say, well, I don't know, man. I don't know what my passion is. I'll give you a line from my daughter, Alicia, you don't learn a lot for your kids. She said, well, if you don't know what your passion is, follow your curiosity. That's great. There you go. Amanda Adams. Thanks so much. It was great to have you on. Okay. Thank you. Keep it right there. We're back with George Kurtz. We're to the short break. Dave ante, Dave Nicholson. You watching the cube from Falcon 22 in Las Vegas.

(pulsing music) (digital music) >> Welcome back to the Seaport in Boston. You're watching theCUBE's coverage of Red Hat Summit 2022. A lot of bummed out Bruins fans, but a lot of happy Celtics fans. We're optimistic for tonight, Boston's crazy sports town, but we're talking tech, we're talking open source. Dr. Amanda Purnell is here. She's the director of data and analytics innovation at the US Department of Veteran Affairs, and Ben Cushing is the chief architect for federal health and life sciences at Red Hat. Folks, welcome to theCUBE, thank for coming on. >> Thank you for having us. >> So glad to be here. >> So we heard your keynote this morning, project Arches. Now you were telling us just briefly about your previous life as a clinician. >> That's right. >> That's really interesting, because you know what the outcome has to be. So talk about that project in your perspective. What the goals were and how you actually got it done. >> I could tell the long view. I'm a psychologist by training. I spent the first 10 years of my VA career providing care to veterans. So engaging in healthcare behavior change, providing training to providers and really trying to understand what is the care pathway for veterans, what's the experience of veterans along each of those touchpoints, and it became clear to me over time that there were opportunities for us to improve the transitions of care and provide better information at the right time to improve those decisions that are being made at the point of care. Ben and I were just talking before we began today, part of the core of the development of Arches was beginning with human-centered design. We wanted to interview and better understand what was the experience across the VA of many different stakeholders and trying to access meaningful information, understand in that moment what do I need to make a decision with a veteran or what do I need to make a decision with my care team and how can I improve the quality of care for veterans? And so, hundreds of interviews later, it became clear to us that we wanted to help those individuals already working for the VA to continue to improve excellence of care and one of those ways that we're trying to do that is using technology to make life easier for our veterans and for our clinicians. >> I always like to say, they say, "Follow the money." I like to follow the data. And you said something in your keynote about nurses have to have access to information and it just gets to an architectural question, because as a caregiver, you have to get insights and data and you need it fast, 'cause you're saving lives, but a lot of times, architectures are very centralized. They're monolithic and you have to beg, borrow, steal, break through blockers to get to the data that you need. How do you square that circle in today's world? Maybe you could talk about that, and then specific to Arches, how you dealt with that. >> I can dive into that a little bit. I have to say, Amanda had touched on this during the keynote, VA was one of the first, if not the first, healthcare organizations in the world to actually adopt electronic health records and because of that, they just have this incredibly rich amount of historical data and the challenge, as you pointed out, is gaining access to it. So there are a number of programs within VA designed specifically for that. And they are bringing data not just from the data warehouses, but also data from the electronic health records that are running inside of VA right now, and then also third party community data sets, as well as applications that run inside the VA. Now the value here really happens when you produce insights. Data by itself is useless. >> Lot of data out there. They're plentiful. >> You need to create knowledge and then you need that knowledge to inform your process that comes next. Those actions are really what matters. All of healthcare is process and activity and data is really just a historical record. I mean, all data that we look at is happening in the past and then as we're reading it, we're producing knowledge, again, to inform our process. Arches, the program itself, is right in that space at the knowledge layer of actually taking that data and turning it into actual insight and something that is usable and insightful for clinicians to affect the ability to deliver better care and also to actually improve their own working experience. A lot of the models that are getting built out are specifically designed to help their workflow, help them reach better outcomes for the veterans, but also for themselves, because if we can care for the providers, it'll certainly help them care for the patients even more so. >> So how does it work? I mean, from the provider's perspective, how was their life improved by Arches? >> That's a great question. We want to make it easier to access the information. So as Ben noted, the average person providing care in the field doesn't know how to code, doesn't know how to pull a unique request for an individual data point, and what we're trying to do with Arches is provide a user interface that allows for both a non-technical person and a very technical person to access information, and then what gets provisioned in front of a provider is something that is farther abstracted from the underlying data layer and more like here's a specific insight. So I use the example in my keynote of chronic kidney disease. So what's provisioned to the provider in that moment is this person is at higher risk for chronic kidney disease based on this basic information. So it's surfacing just the right amount of information to allow for that care pathway to be improved, but the physician doesn't need to see all of the layers of code underneath. They need to trust that it's worthwhile, but they don't need to know all the background abstractions. >> So it's a self-service, essentially, infrastructure in that sense. You're hiding the underlying complexities. You gave an example in your keynote of an individual who realized that they were under counting the probability of a potential disease for African Americans. >> Yes. >> I believe she just rewrote the algorithm. >> She did. >> Describe that process, because in a lot of organizations, injecting that new algorithm may have required new data sources, would take an act of the Pope to do. How did it work in Arches? >> This is what I get excited about with Arches is that we have the opportunity to empower enthusiastic people like Dr. Joshi to discover an insight and she's a talented informaticist, so she could do the technical work and provision a container for her to work in, for her to do the data analysis, the underground stuff that we're not letting the average provider have to cope with. We were able to provision the tools that she need, the environment that she needed to be able to test and develop the new insight, confirm that they're there and then begin to validate that and test it in other facilities. So our thinking is, how do we bring the resources to the users rather than saying to the users, "This is what's available. Good luck." (chuckles) >> So we've been talking a lot about, I'm sorry, go ahead. >> I want to add on to that. What we're actually experiencing inside of healthcare right now is the emergence of of learning health systems. >> Yes. >> And this is a great example of that. The terrifying number is, it takes 17 years for new knowledge that gets created with healthcare research, whether it's NIH or VA or elsewhere, it takes 17 years for those practices to make their way into practice. Generally the way that happens is through the education of new staff. And so the dissemination of that knowledge is just so freaking slow that we cannot move nimbly enough to take on that new knowledge and actually implement it in clinical space. What Amanda's describing is something that now happens in months. New knowledge getting produced and then actually getting disseminated out, both the insights, whether they are those probabilities, predictions and recommendations and the actual processes, which are getting automated, as well. So if you think about healthcare as just a process, you can automate a whole lot of that and we can move that needle really fast and actually take that 70-year number down to a couple months. >> In the early days when we were all talking about AI and getting excited about digital, I would often ask the question, will machines be able to make better diagnoses than doctors and to your point, Ben, that's not the right question. >> Exactly. >> It isn't the right question. >> The question is, how can machines compress the time to better patient outcomes- >> Yes. >> in concert with humans and that's what we're seeing now. >> That's right, it's surfacing those insights to start a conversation. >> We've been talking a lot about artificial intelligence for the last two days. As clinician or someone with a clinical background, how do you see the clinical experience changing as machines grow more intelligent? >> I think that there's a learning curve for people to feel confident in an artificial intelligence. It makes sense. So someone spent decades, perhaps, of their life obtaining medical training, doing fellowships, doing additional training that they have trust in that deep training. There are times, however, where a technology is able to surface something that we didn't know that we didn't know and it's important, as we make use of artificial intelligence, that we clearly validate it with independent means and that we clearly also bring in additional analysis to understand what are the elements and then test that new technology in an environment before we scale it widely, so that clinicians can see, yes, this was useful. If it wasn't useful, how can we make it even better? So it goes back to what we were talking about earlier that we have to bring in human-centered design to figuring out how do we make use of AI or machine learning models and make sure that there's trust in those models and that we can clearly articulate value for the clinicians and care teams on the ground. >> Is that a natural evolution of Arches? >> This is all built around it. Arches is the technology platform, but there's no magical technology that's going to change how humans interact. And so the way we think about each project is we think about what are the technological components and what are the human factors components? And we have to think about the entire care pathway. I'll go back to that example, the chronic kidney disease. She identified that we were under identifying African Americans for chronic kidney disease. So she changed the algorithm. Not only did she change the algorithm, we also had to think about who would be informed of those changes, how would that change, who would be connected to the veteran in that point of care and build out the care pathway in the care team and that's really how you actually influence an outcome. Surfacing an insight is important, but it's one part of a much larger picture. >> So what is Arches? You said it's a technology platform built on open source. At least, there's a lot of open source in there. And it's got API connectors to all the legacy technologies that you need it to. Can you describe, paint a picture of what it actually is? >> Arches is evolving as it should. So it's designed to meet the unique needs that aren't being met by other infrastructure in the VA. So we started first by identifying the need for cloud compute, so it's in the cloud, it has open source technology so that we're not stuck with any one provider and also has the ability to use containers to be able to move insights out of Arches to an enterprise solution. We're also bringing in multi-cloud strategy, which also something had been discussed quite a bit at this conference, to make sure that we're not saying only one cloud provider can be the solution for veterans' needs. Our mission is serving veterans and so we want to have access to all the technology and not just one and so we're looking at how do we expand the scope to make sure that we have the most variety possible so we can meet the needs of veterans. >> I can add a little bit to it, as well. Think of Arches as a program. It's an incubation space under the office of innovation. So it's a place where the governance allows for trying new ideas and really pushing the envelope for VA in general. There's not a lot of organizations, if any at VA, that allow for that type of incubation and so Arches is in a unique position to create new technologies and new novel approaches to solving big problems. And then the next step to that is moving the work from Arches out into the enterprise, as you called it out. So for instance, the system of engagement where the actual clinicians interact with patients, the model needs to find its way there and we can't do that in a way that disturbs the current workflow that the clinicians have. We need to be able to bring the model to where the clinician is, have those recommendations, probabilities and predictions surfaced to the clinician in a way that is precise to their existing workflow. They need it at the time they need it. Arches itself is not delivering that part of it. It's more like the place where the innovation happens and the incubation really occurs and then it's about taking this container, really, and moving out to other systems that are already deployed out to the hospitals, the edge, and in the cloud. >> And the federated governance occurs in Arches or elsewhere? >> It happens across the continuum. It's starting in Arches. the clinical validation that happens there is wickedly important, because the clinicians need to know that what they're working with is actually legit. And so when they know that the researchers and the clinicians who are involved in that incubation period have done their work, they can feel confident with the recommendations they're getting from the machine learning models that are getting deployed to one of them. >> So many questions, so little time. What's the business impact? How would you describe that? >> For me, it's an emotional impact. People have a sense of, "I have a place to develop a solution and I can get in there quick, and I can test out an idea. I could potentially partner with an external partner or if I have the talents and skills to do it myself." It's empowering all of those innovators who have great ideas to work together to test and develop and validate solutions, and they're not waiting years to get the idea off the ground. >> Amazing. >> Go ahead, bring it. >> Is Arches open source? >> Arches is a platform and it has open source component. So that the underlying infrastructure of technology is open source. >> Why was it important to you that this be built on an open source platform? >> It's important for us that we not marry ourself to any one technology and that we allow for, as much as possible, transparency and many different tools and the right tools for the right solution. So we didn't want to find ourselves connected to only one way of doing things. We want to have versatility to have the right tool for the right problem at the right time. >> I'm so sorry, we're out of time. This is so interesting and I really appreciate you here guys, coming on and sharing your insights for theCUBE audience. All right, keep it right there. This is Dave Vellante for Paul Gillin. We're in day two of Red Hat Summit 2022. You're watching theCUBE. (digital pulsing music) >> Due to the pandemic, the federal government declared a public health emergency, which created an urgency for healthcare coverage. >> One of the biggest-

>>Welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. We're here with Amanda Silver, corporate vice president, product developer division at Microsoft. Amanda, Great to see you you were on last year, Dr khan. Great to see you again a full year later were remote. Thanks for coming on. I know you're super busy with build happening this week as well. Thanks for making the time to come on the cube for Dr khan. >>Thank you so much for having me. Yeah, I'm joining you like many developers around the globe from my personal home office, >>developers really didn't skip a beat during the pandemic and again, it was not a good situation but developers, as you talked about last year on the front lines, first responders to creating value quite frankly, looking back you were pretty accurate in your prediction, developers did have an impact this year. They did create the kind of change that really changed the game for people's lives, whether it was developing solutions from a medical standpoint or even keeping systems running from call centres to making sure people got their their their goods or services and checks and and and kept sanity together. So. >>Yeah absolutely. I mean I think I think developers you know get the M. V. P. Award for this year because you know at the end of the day they are the digital first responders to the first responders and the pivot that we've had to make over the past year in terms of supporting remote telehealth, supporting you know online retail, curbside pickup. All of these things were done through developers being the ones pushing the way forward remote learning. You know my kids are learning at home right behind me right now so you might hear them during the interview that's happening because developers made that happen. >>I don't think mom please stop hogging the band with, they've got a gigabit. Stop it. Don't be streaming. My kids are all game anyway, Hey, great to have you on and you have to get the great keynote, exciting to see you guys continue the collaboration with Docker uh with GIT hub and Microsoft, A great combination, it's a 123 power punch of value. You guys are really kind of killing it. We heard from scott and dan has been on the cube. What's your thoughts on the partnership with the developer division team at Microsoft with Doctor, What's it all about this year? What's the next level? >>Well, I mean, I think, I think what's really awesome about this partnership is that we all have, we all are basically sharing a common mission. What we want to do is make sure that we're empowering developers, that we're focused on their productivity and that we're delivering value to them so they can do their job better so that they can help others. So that's really kind of what drives us day in and day out. So what we focus on is developer productivity. And I think that's a lot of what dana was talking about in her session, the developer division. Specifically, we really try to make sure that we're improving the state of the art from modern developers. So we want to make sure that every keystroke that they take, every mouse move that they make, it sounds like a song but every every one of those matter because we want to make sure that every developers writing the code that only they can write and in terms of the partnership and how that's going. You know my team and the darker team have been collaborating a ton on things like dr desktop and the Doctor Cli tool integrations. And one of the things that we do is we think about pain points and various workflows. We want to make sure that we're shaving off the edges of all of the user experience is the developers have to go through to piece all of these applications together. So one of the big pain points that we have heard from developers is that signing into the Azure cloud and especially our sovereign clouds was challenging. So we contributed back to uh back to doctor to actually make it easier to sign into these clouds. And so dr developers can now use dr desktop and the Doctor Cli to actually change the doctor context so that its Azure. So that makes it a lot easier to connect the other. Oh, sorry, go ahead. No, I was just >>going to say, I love the reference of the police song. Every breath you take, every >>mouth moving. Great, >>great line there. Uh, but I want to ask you while you're on this modern cloud um, discussion, what is I mean we have a lot of developers here at dr khan. As you know, you guys know developers in your ecosystem in core competency. From Microsoft, Kublai khan is a very operator like focus developed. This is a developer conference. You guys have build, what is the state of the art for a modern cloud developer? Could you just share your thoughts because this comes up a lot. You know, what's through the art? What's next jan new guard guard? It's his legacy. What is the state of the art for a modern cloud developer? >>Fantastic question. And extraordinarily relevant to this particular conference. You know what I think about often times it's really what is the inner loop and the outer loop look like in terms of cycle times? Because at the end of the day, what matters is the time that it takes for you to make that code change, to be able to see it in your test environment and to be able to deploy it to production and have the confidence that it's delivering the feature set that you need it to. And it's, you know, it's secure, it's reliable, it's performance, that's what a developer cares about at the end of the day. Um, at the same time, we also need to make sure that we're growing our team to meet our demand, which means we're constantly on boarding new developers. And so what I take inspiration from our, some of the tech elite who have been able to invest significant amounts in, in tuning their engineering systems, they've been able to make it so that a new developer can join a team in just a couple of minutes or less that they can actually make a code change, see that be reflected in their application in just a few seconds and deploy with confidence within hours. And so our goal is to actually be able to take that state of the art metric and democratize that actually bring it to as many of our customers as we possibly can. >>You mentioned supply chain earlier in securing that. What are you guys doing with Docker and how to make that partnership better with registries? Is there any update there in terms of the container registry on Azure? >>Yeah, I mean, you know, we, we we have definitely seen recent events and and it almost seems like a never ending attacks that that you know, increasingly are getting more and more focused on developer watering holes is how we think about it. Kind of developers being a primary target um for these malicious hackers. And so what it's more important than ever that every developer um and Microsoft especially uh really take security extraordinarily seriously. Our engineers are working around the clock to make sure that we are responding to every security incident that we hear about and partnering with our customers to make sure that we're supporting them as well. One of the things that we announced earlier this week at Microsoft build is that we've actually taken, get have actions and we've now integrated that into the Azure Security Center. And so what this means is that, you know, we can now do things like scan for vulnerabilities. Um look at things like who is logging in, where things like that and actually have that be tracked in the Azure security center so that not just your developers get that notification but also your I. T. Operations. Um In terms of the partnership with dR you know, this is actually an ongoing partnership to make sure that we can provide more guidance to developers to make sure that they are following best practices like pulling from a private registry like Docker hub or at your container registry. So I expect that as time goes on will continue to more in partnership in this space >>and that's going to give a lot of confidence. Actually, productivity wise is going to be a big help for developers. Great stuff is always good, good progress. They're moving the needle. >>Last time we >>spoke we talked about tools and setting Azure as the doctor context duty tooling updates here at dot com this year. That's notable. >>Yeah, I mean, I think, you know, there's one major thing that we've been working on which has a big dependency on docker is get help. Code space is now one of the biggest pain points that developers have is setting up a new DEV box, which they often have to do when they are on boarding a new employee or when they're starting a new project or even if they're just kicking the tires on a new technology that they want to be able to evaluate and sometimes creating a developer environment can actually take hours um and especially when you're trying to create a developer environment that matches somebody else's developer environment that can take like a half a day and you can spend all of your time just debugging the differences in environment variables, for example, um, containers actually makes that much easier. So what you can do with this, this services, you can actually create death environment spun up in the cloud and you can access it in seconds and you get from there are working coding environment and a runtime environment and this is repeatable via containers. So it means that there's no inadvertent differences introduced by each DEV. And you might be interested to know that underneath this is actually using Docker files and dr composed to orchestrate the debits and the runtime bits for a whole bunch of different stacks. And so this is something that we're actually working on in collaboration with the with the doctor team to have a common the animal format. And in fact this week we actually introduced a couple of app templates so that everybody can see this all in action. So if you check out a ca dot m s forward slash app template, you can see this in action yourself. >>You guys have always had such a strong developer community and one thing I love about cloud as it brings more agility, as we always talk about. But when you start to see the enterprise grow into, the direction is going now, it's almost like the developer communities are emerging, it's no longer about all the Lennox folks here and the dot net folks there, you've got windows, you've got cloud, >>it's almost >>the the the solidification of everyone kind of coming together. Um and visual studio, for instance, last year, I think you were talking about that to having to be interrogated dr composed, et cetera. >>How do you see >>this melting pot emerging? Because at the end of the day, you pick the language you love and you got devops, which is infrastructure as code doesn't matter. So give us your take on where we are with that whole progress of of making that happen. >>Well, I mean I definitely think that, you know, developer environments and and kind of, you know, our approach to them don't need to be as dogmatic as they've been in the past. I really think that, you know, you can pick the right tool and language and stand developer stack for your team, for your experience and you can be productive and that's really our goal. And Microsoft is to make sure that we have tools for every developer and every team so that they can build any app that they want to want to create. Even if that means that they're actually going to end up ultimately deploying that not to our cloud, they're going to end up deploying it to AWS or another another competitive cloud. And so, you know, there's a lot of things that we've been doing to make that really much easier. We have integrated container tools in visual studio and visual studio code and better cli integrations like with the doctor context that we had talked about a little bit earlier. We continue to try to make it easier to build applications that are targeting containers and then once you create those containers it's much easier to take it to another environment. One of the examples of this kind of work is now that we have WsL and the Windows subsystem for Lennox. This makes it a lot easier for developers who prefer a Windows operating system as their environment and maybe some tools like Visual Studio that run on Windows, but they can still target Lennox with as their production environment without any impedance mismatch. They can actually be as productive as they would be if they had a Linux box as their Os >>I noticed on this session, I got to call this out. I want to get your reaction to it interesting. Selection of Microsoft talks, the container based development. Visual studio code is one that's where you're going to show some some some container action going on with note and Visual Studio code. And then you get the machine learning with Azure uh containers in the V. S. Code. Interesting how you got, you know, containers with V. S. And now you've got machine learning. What does that tell the world about where Microsoft's at? Because in a way you got the cutting edge container management on one side with the doctor integration. Now you get the machine learning which everyone's talking about shifting, left more automation. Why are these sessions so important? Why should people attend? And what's the what's the bottom line? >>Well, like I said, like containers basically empower developer productivity. Um that's what creates the reputable environments, that's what allows us to make sure that, you know, we're productive as soon as we possibly can be with any text act that we want to be able to target. Um and so that's kind of almost the ecosystem play. Um it's how every developer can contribute to the success of others and we can amor ties the kinds of work that we do to set up an environment. So that's what I would say about the container based development that we're doing with both visual studio and visual studio code. Um in terms of the machine learning development, uh you know, the number of machine learning developers in the world is relatively small, but it's growing and it's obviously a very important set of developers because to train a machine learning uh to train an ml model, it actually requires a significant amount of compute resources, and so that's a perfect opportunity to bring in the research that are in a public cloud. Um What's actually really interesting about that particular develop developer stack is that it commonly runs on things like python. And for those of you who have developed in python, you know, just how difficult it is to actually set up a python environment with the right interpreter, with the right run time, with the right libraries that can actually get going super quickly, um and you can be productive as a developer. And so it's actually one of the hardest, most challenging developer stacks to actually set up. And so this allows you to become a machine learning developer without having to spend all of your time just setting up the python runtime environment. >>Yeah, it's a nice, nice little call out on python, it's a double edged sword. It's easier to sling code around on one hand, when you start getting working then you gotta it gets complicated can get well. Um Well the great, great call out there on the island, but good, good, good project. Let me get your thoughts on this other tool that you guys are talking about project tie. Uh This is interesting because this is a trend that we're seeing a lot of conversations here on the cube about around more too many control planes. Too many services. You know, I no longer have that monolithic application. I got micro micro applications with microservices. What the hell is going on with my services? >>Yeah, I mean, I think, you know, containers brought an incredible amount of productivity in terms of having repeatable environments, both for dev environments, which we talked about a lot on this interview already, but also obviously in production and test environments. Super important. Um and with that a lot of times comes the microservices architecture that we're also moving to and the way that I view it is the microservices architecture is actually accompanied by businesses being more focused on the value that they can actually deliver to customers. And so they're trying to kind of create separations of concerns in terms of the different services that they're offering, so they can actually version and and kind of, you know, actually improve each of these services independently. But what happens when you start to have many microservices working together in a SAS or in some kind of aggregate um service environment or kind of application environment is it starts to get unwieldy, it's really hard to make it so that one micro service can actually address another micro service. They can pass information back and forth. And you know what used to be maybe easy if you were just building a client server application because, you know, within the server tear all of your code was basically contained in the same runtime environment. That's no longer the case when every microservices actually running inside of its own container. So the question is, how can we improve program ability by making it easier for one micro service that's being used in an application environment, be to be able to access another another service and kind of all of that context. Um and so, you know, you want to be able to access the service is the the api endpoint, the containers, the ingress is everything, make everything work together as though it felt just as easy as as um you know, server application development. Um And so what this means as well is that you also oftentimes need to get all of these different containers running at the same time and that can actually be a challenge in the developer and test loop as well. So what project tie does is it improves the program ability and it actually allows you to just write a command like thai run so that you can actually in stan she ate all of these containers and get them up and running and basically deploy and run your application in that environment and ultimately make the dev testing or loop much faster >>than productivity gain. Right. They're making it simple to stand up. Great, great stuff. Let me ask you a question as we kind of wrap down here for the folks here at Dakar Con, are >>there any >>special things you'd like to talk about the development you think are important for the developers here within this space? It's very dynamic. A lot of change happening in a good way. Um, but >>sometimes it's hard to keep >>track of all the cool stuff happening. Could you take a minute to, to share your thoughts on what you think are the most important develops developments in this space? That that might be interesting to ducker con attendees. >>I think the most important things are to recognize that developer environments are moving to containerized uh, environments themselves so that they can be repeated, they can be shared, the work, configuring them can be amortized across many developers. That's important thing. Number one important thing. Number two is it doesn't matter as much what operating system you're running as your chrome, you know, desktop. What matters is ultimately the production environment that you're targeting. And so I think now we're in a world where all of those things can be mixed and matched together. Um and then I think the next thing is how can we actually improve microservices, uh programming development together um so that it's easier to be able to target multiple micro services that are working in aggregate uh to create a single service experience or a single application. And how do we improve the program ability for that? >>You know, you guys have been great supporters of DACA and the community and open source and software developers as they transform and become quite frankly the superheroes for the transformation, which is re factoring businesses. So this has been a big thing. I'd love to get your thoughts on how this is all coming together inside Microsoft, you've got your division, you get the developer division, you got GIT hub, got Azure. Um, and then just historically, and he put this up last year army of an ecosystem. People who have been contributing encoding with Microsoft and the partners for many, many decades. >>Yes. The >>heart Microsoft now, how's it all working? What's the news? I get Lincoln, Lincoln, but there's no yet developer model there yet, but probably is soon. >>Um Yeah, I mean, I think that's a pretty broad question, but in some ways I think it's interesting to put it in the context of Microsoft's history. You know, I think when I think back to the beginning of my career, it was kind of a one stack shop, you know, we was all about dot net and you know, of course we want to dot net to be the best developer environment that it can possibly be. We still actually want that. We still want that need to be the most productive developer environment. It could we could possibly build. Um but at the same time, I think we have to recognize that not all developers or dot net developers and we want to make sure that Azure is the most productive cloud for developers and so to do that, we have to make sure that we're building fantastic tools and platforms to host java applications, javascript applications, no Js applications, python applications, all of those things, you know, all of these developers in the world, we want to make sure it can be productive on our tools and our platforms and so, you know, I think that's really kind of the key of you know what you're speaking of because you know, when I think about the partnership that I have with the GIT hub team or with the Azure team or with the Azure Machine learning team or the Lincoln team, um A lot of it actually comes down to helping empower developers, improving their productivity, helping them find new developers to collaborate with, um making sure that they can do that securely and confidently and they can basically respond to their customers as quickly as they possibly can. Um and when, when we think about partnering inside of Microsoft with folks like linkedin or office as an example, a lot of our partnership with them actually comes down to improving their colleagues efficiency. We build the developer tools that office and lengthen are built on top of and so every once in a while we will make an improvement that has, you know, 5% here, 3% there and it turns into an incredible amount of impact in terms of operations, costs for running these services. >>It's interesting. You mentioned earlier, I think there's a time now we're living in a time where you don't have to be dogmatic anymore, you can pick what you like and go with it. Also that you also mentioned just now this idea of distributed applications, distributed computing. You know, distributed applications and microservices go really well together. Especially with doctor. >>Can you share >>your thoughts on the framework that you guys released called Dapper? >>Yeah, yeah. We recently released Dapper. It's called D A P R. You can look it up on GIT hub and it's a programming model for common microservices pattern, two common microservices patterns that make it really easy and automatic to create those kinds of microservices. So you can choose to work with your favorite state stores or databases or pub sub components and get things like cloud events for free. You can choose either http or g R B C so that you can get mesh capabilities like service discovery and re tries and you can bring your own secret store and easily be able to call it from any environment variable. It's also like I was talking about earlier, multi lingual. Um so you don't need to embrace dot net, for example, as you're programming language to be able to benefit from Dapper, it actually supports many programming languages and Dapper itself is actually written and go. Um and so, you know, all developers can benefit from something like Dapper to make it easier to create microservices applications. >>I mean, always great to have you on great update. Take a minute to give an update on what's going on with your division. I know you had to build conference this week. V. S has got the new preview title. We just talked about what are the things you want to get to plug in for? Take a minute to get to plug in for what you're working on, your goals, your objectives hiring, give us the update. >>Yeah, sure. I mean, you know, we we built integrated container tools in visual studio uh and the Doctor extension and Visual Studio code and cli extensions. Uh and you know, even in this most recent release of our Visual Studio product, Visual Studio 16 10, we added some features to make it easier to use DR composed better. So one of the examples of this is that you can actually have uh Oftentimes you need to be able to use multiple doctor composed files together so that you can actually configure various different container environments for a single single application. But it's hard sometimes to create the right Yeah. My file so that you can actually invoke it and invoke the the container and the micro services that you need. And so what this allows you to do is to actually have just a menu of the different doctor composed files so that you can select the runtime and test environment that you need for the subset of the portion of the application that you're working on at the end of the day. This is always about developer productivity. You know, like I said, every keystroke matters. Um and we want to make sure that you as a developer can focus on the code that only you can Right. >>Amanda Silver, corporate vice president product development division of Microsoft. Always great to see you and chat with you remotely soon. We'll be back in in real life with real events soon as we come out of the pandemic and thanks for sharing your insight and congratulations on your success this year and and congratulations on your announcement here at Dakar Gone. >>Thank you so much for having me. >>Okay Cube coverage for Dunkirk on 2021. I'm John for your host of the Cube. Thanks for watching. Mhm

>> Narrator: From around the globe, it's theCUBE with digital coverage of Dockercon Live 2020, brought to you by Docker and it's ecosystem partners. >> Everyone welcome back to Dockercon 2020, #Docker20. This is theCUBE and Docker's coverage of Dockercon 20. I'm John Furrier in the Palo Alto studios with our quarantine crew, we got a great interview segment here and big news around developer workflow code to cloud. We've got Amanda Silver, Corporate Vice President, product for developer tools at Microsoft and Scott Johnson, the CEO of Docker. Scott had a great Keynote talking about this relationship news has hit about the extension of the Microsoft partnership. So congratulations, Amanda, welcome to theCUBE. >> Thanks for having me. >> Amanda, tell us about what your role is at Microsoft. You guys are well known in the developer community. You had to develop a ecosystem even when I was in college going way back. Very modern now, the cloud is the key, code to cloud, that's the theme. Tell us about your role at Microsoft. >> Yeah, so I basically run the product, Product Design and User Research team that works on our developer tools at Microsoft. And so that includes the Visual Studio product as well as Visual Studio code that's become pretty popular in the last few years but it also includes things like the dotNET runtime and the TypeScript programming language, as well as all of our Azure tooling. >> What's your thoughts on the relationship with Docker? Obviously the news extension of an existing relationship, Microsoft's got a lot of tools, you got a lot of things you guys are doing, bringing the cloud to every business. Tell us about your thoughts on this relationship with Docker? >> Yeah well, we're very excited about the partnership for sure. Our goal is really to make sure that Azure is a fantastic place where all developers can kind of bring their code and they feel welcome. They feel natural. We really see a unique opportunity to make the experience really great for the Docker community by creating more integrated and seamless experience across Docker desktop, Windows and Visual Studio and we really appreciate how Docker has kind of, supported our Windows ecosystem to run in Docker as well. >> Scott, this relationship and an extension with Microsoft is really, I think, impressive and also notable because Microsoft's got so many tools out there and they have so successful with Azure. You guys have been so successful with your developer community but this also is a reflective of the new Docker. Can you share your thoughts on how this partnership with Microsoft, extending the way it is, with the growth of the cloud is a reflection of the new Docker? >> Yeah, absolutely John, it's a great question. One of the things that we've really been focused on since November is fully embracing the ecosystem and all the partnerships and all the possibilities of that ecosystem and part of that is just reality that we're a smaller company now and we can't do it all, nor should we do it all. Part of it's the reality that developers love choice and no one's going to change their minds on choice, and third is just acknowledging that there's so much creativity and so much energy outside the four walls of Docker that we'd be silly not to take advantage of that and welcome it and embrace it and provide that as a phenomenal experience for our developers. So this is a great example of that. The Snyk partnership we announced last week is a great example of that and you're going to see many more partnerships like this going forward that are reflective of exactly this point. >> You've been a visionary on the product side, interviewed before. Also deploying is more important than ever, that whole workflow simplifying, it's not getting complex, people want choice, building code, managing code, deploying code. This has been a big focus of yours. Can you just share your thoughts on where Microsoft comes in? Because they got stuff too, you've got stuff, it all works together. What's your thoughts? >> Right, so it needs to work together because developers want to focus on their app. They don't want to focus on duct taping and stringing together different siloed pools. So you can see in the demo and you'll see in demonstrations later throughout the conference, just the seamless experience that a developer gets in the Docker command line inner operating with Visual Studio Code, with the Docker command line and then deploying to Azure and what's wonderful about the partnership is that both parties put real engineering effort and design effort into making it a great experience. So a lot of the complexities around configuration, around default settings, around security, user management, all of that is abstracted out and taken away from the developers so they can focus on applications and getting those applications deployed to the cloud as quickly as possible. Getting their apps from code to cloud is the watchword or the call to action for this partnership and we think we've really hit it out of the park with the integration that you saw. >> Great validation in the critical part of the workflow you guys been part of. Amanda, we're living in a time we're doing these remote interviews. The COVID crisis has shown the productivity gains of working at home and working, sheltering in place but it also has highlighted the focus of developers, mainly who have also worked at home. They're been kind of used to this, you see the rigs. I saw at Microsoft build some amazing rigs from the studio, so these guys streaming their code demos. This is a Cambrian explosion of new kinds of productivity. You got the world's getting more complex at scale. This is what cloud does. What's your thoughts on this? 'Cause the tooling, there's more tools than ever, right? >> Yeah. >> I still got to deploy code. It's got to be more agile, it's got to be faster, it's got to be at scale. This is what you guys believe in. What's your thinking on all these tooling and abstraction layers? And the end of the day, developers still got to do their job. >> Yeah, well, absolutely. And now even more than ever, I think we've certainly seen over the past few months, a more rapid acceleration of digital transformation that has really happened in the past few years. Paper processes are now becoming digital processes all of a sudden. Everybody needs to work and learn from home and so there's just this rapid acceleration to kind of move everything to support our new remote first lifestyle. But even more so, we now have remote development teams actually working from home as well in a variety of different kinds of environments, whether they're using their own personal machine to connect to their infrastructure or they're using a work issued machine. It's more important than ever that developers are productive but they are productive as a team. Software is a team sport, we all need to be able to work together and to be able to collaborate. And one of the most important aspects of agility for developers is consistency. And what Docker really enables with containerization, is to make the infrastructure consistent and repeatable so that as developers are moving through the lifecycle from their local desktop and developing on their local desktop, to a test environment and to staging and to production, it's really, it's infrastructure for developers as well as operations. And so, that infrastructure, that's completely customizable for what the developers operating system of choice is, what their app stack is, all of those dependencies kind of running together. And so that's what really enables developers to be really agile and have a really fast iteration cycle but also to have that consistency across all of their development team. And we now need to think about things like, how are we actually going to bring on interns for the summer and make sure that they can actually set up their developer boxes in a consistent way that we can actually support them and things like Docker really help with that. >> As your container instances and Visual Studio cloud that you guys have has had great success. There's a mix and match formula here and the other day, developers want to ship the code. What's the message that you guys are sending here with this because I think productivity is one, simplification is the other but as developers, we're on the front lines and they're shipping in real time. This is a big part of the value proposition that you guys bringing to the table. >> Yeah, the core message is that any developer and their code is welcome (laughs) and that we really want to support them, empower them and increase their velocity and the impact that they can have. And so, having things like the fact that the Docker CLI is natively integrated into the Azure experience is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. And now that the Docker CLI tools that are part of Docker desktop have access to native commands that work well with Azure container instances, Azure container instances, if anybody is unfamiliar with that, is the simplest and fastest way to kind of set up containers in Azure and so we believe that developers have really been looking for a really simple way to kind of get containers on Azure and now we have that really consistent experience across our servers, services and our tools. Visual Studio code and Visual Studio extensions make full use of Docker desktop and the Docker CLI so that they can get that combination of the productivity and the power that they're looking for. And in fact, we've integrated these as a design point since very early on in our partnership when we've been partnering with Docker for quite a while. >> Amanda, I want to ask you about the tool chain. We've heard about workflows, making it simpler. Bottom line from a developer standpoint, what's the bottom line for me? What does this mean to me, everyday developer out there? >> I really think it means, your productivity on your terms. And so, Microsoft has been a developer company since the very beginning with Bill Gates and GW Basic. And it's actually similar for Docker. They really have a developer first point of view, which certainly speaks to my heart and so one of the things that we're really trying to do with Docker is to make sure that we can create a workflow that's super productive at every stage of the developer experience, no matter which stack they're actually targeting, whether there's targeting Node or Python, or dotNET and C Sharp or Java, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create Docker container images and use the Docker compose files. And then, just kind of do that consistently, as you're deploying it all the way up into your infrastructure in Azure. And the other thing that we really want to make sure is that that even post deployment, you can actually inspect and diagnose these containers and images without having to leave the tool. So we also think about the process of writing the code but also the process of kind of managing the code and remediating issues that might come up in production. And so we really want you to be able to look at containers up in the Azure, that are deployed into Azure and make sure that they're running and healthy and that if something's wrong, that you can actually open up a shell and be in an interactive mode and be able to look at the logs from those containers and even inspect one to see environment variables or other details. >> Yeah, that's awesome. Writing code, managing code and then you got to deploy, right? So what I've been loving about the past generation of Agile is deployment's been faster to play off all the time. Scott, this brings up that the ease of use but you'll want to actually leverage automation. This is the trend that you want to get into. You want to make it easy to write code, manage code but during the deployment phase, that's a big innovation. That's the last point, making that better and stronger. What's your thoughts on simplifying that? >> Well, as a big part of this partnership, John, that Docker and Microsoft embarked on, as you saw from the demo in the keynote, all within the Docker command line, the developer's able to do it in two simple commands, deploy an app, define and compose from their desktop to Azure. And there's a whole slew of automation and pre-configured smart defaults or sane defaults that have gone on behind the scenes and it a lot of hardcore engineering work on part of Docker-Microsoft together to simplify that and make that easy. And that goes exactly to your point, which is, the simpler you can make it, make an abstract way to kind of underline plumbing and infrastructure, the faster Devs can get their application from code to cloud. >> Scott, you've been a product CEO, you've been a product person now you're the CEO but you have a product back when you've been involved with a relationship with Microsoft for a long time. What's the state of the market right now? I see Microsoft has evolved because just the performance, corporate performance, the shift to the cloud has been phenomenal. Now developers getting more empowered, there's more demand for the pressure to put developers to do more and more creativity. So you've seen this evolve, this relationship, what does it mean? >> Yeah, it's honestly a wonderful question, John and I want to thank Amanda and the entire Microsoft team for being long standing partners with us on this journey. So it might not be known to everyone on today's day's event but Microsoft came to the very first Dockercon event way back in June 2014 and I had the privilege of greeting them and welcoming them and then they were full on, ready to see what all the excitement about Docker was about and really embraced it. And you mentioned kind of openness in Microsoft's growth over time in that dimension and we think Docker, together with Microsoft have really shown what an open developer community can do. That started back in 2014 and then we embarked on an open source collaboration around the Docker command line of the Docker engine, bringing that Docker engine from Linux and now moving it to Windows applications. And so all the sudden the promise of write once and use the same primitives, the same formats, the same command lines, as you can with Linux onto Windows applications, we brought that promise to the market. And it's been an ongoing journey together with Microsoft on open standards base, developer facing friendliness, ease of use, fast time to deploy and this partnership that we announced yesterday and we highlighted at the keynote is just another example of that ongoing relationship, laser-like focused on developer productivity and helping teams build great apps. >> Why do you like Azure in the cloud for Docker? Can you share why? >> Well, as Amanda has been sharing, it's super focused on, what are the needs of developers to help them continue to stay focused on their apps and not have their cognitive load burdened by other aspects of getting their apps to the cloud and Azure does a phenomenal job of simplifying and providing sane defaults out of the box. And as we've been talking about, it's also very open to partner integrations like the one we've announced yesterday and highlighted that make it just easy for development teams to choose their tools and build their apps and deploy them onto Azure as quickly as possible. So it's a phenomenal platform for developers and we're very excited and proud to partner with Microsoft on it. >> Amanda on your side, I see Docker's got millions of developers. you guys got millions of developers even more. How do you see the developers in Microsoft's side engaging with Docker desktop and Docker hub? Where does it all fit? I mentioned earlier how I see Docker context really improving the way that individuals and teams work with their environments in making sure that they're consistent but I think this really comes together as we work with Docker desktop and Docker Hub. When developers sign in to Docker Hub from Docker desktop, everything kind of lights up and so they can see all of the images in their repositories and they can also see the cloud environments that they're running them in. And so, once you sign into the Hub, you can see all the contexts that map to the logical environments they have access to, like Dev, NQA and maybe staging. And another use case that's really important is that we can access the same integration environment. So, I can have microservices that I've been working on but I can also see microservices that my teammates and their logs from the services that they've been working on, which I think is really great and certainly helps with team productivity. The other thing too, is that this also really helps with hybrid cloud deployments, where, you might have some on-premises hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things through your Docker Hub. >> Well, I got to say, I love the code to cloud tagline, I think that's very relevant and catchy. And I think, I guess to me what I'm seeing and I'd love to get your thoughts, Amanda on this is you oversee a key part of Microsoft's business that's important for developers, just the vibe and people are amped up right now. I know people are tensed, anxiety with the COVID-19 crisis but I think people are generally agreeing that this is going to be a massive inflection point for just more headroom needed for developers to accelerate their value on the front lines. What's your personal take on this? You've seen these waves before but now in this time, what are you most excited about? What are you optimistic about? What's your view on the opportunities? Can you share your thoughts, because people are going to get back to work. They're working now remotely but if we go back to hybrid world, they're going to be jamming on projects. >> Yeah, for sure but people are jamming on projects right now and I think that in a lot of ways, developers are first responders in that they are... Developers are always trying to support somebody else. We're trying to support somebody else's workflow and so we have examples of people who are creating new remote systems to be able to schedule meetings in hospitals for the doctors who are actually the first responders taking care of patients but at the end of the day, it's the developer who's actually creating that solution. And so we're being called to duty right now and so we need to make sure that we're actually there to support the needs of our users and that we're basically cranking on code as fast as we can. And to be able to do that, we have to make sure that every developer is empowered and they can move quickly but also that they can collaborate really quickly. And so I think that Docker Hub, Docker kind of helps you ensure that you have that consistency but you also have that connection to the infrastructure that's hosted by your your organization. >> I think you nailed, that's amazing insight. I think that's... The current situation in the community matters because there's a lot of frontline work being done to your point but then we got to rebuild, the modernization is happening as well coming out of this so there's going to be that. And there's a lot of camaraderie going on and massive community involvement I'm seeing more of. The empathy but also now there's going to be the building, the creation, the new creation. So, Scott, this is going to call for more simplicity and to abstract away the complexities. This is the core issue. >> Well, that's exactly right. And it is time to build and we're going to build our way out of this and it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that moory energy and give them the tools to go and identify and have an impact as quickly as possible. I referenced in the keynote, completely bottoms up organic adoption of Docker desktop and Docker Hub in racing to provide solutions against the COVID-19 virus. It's a war against this pandemic that is heavily dependent on applications and data. And there's over 200 projects, community projects on Docker Hub today, where you've got tools and containers and data analysis all in service to the COVID-19 battle that's being fought. And then as you said, John, as we get through the other side, there's entire industries that are completely rethinking their approach that were largely offline before but now see the imperative and the importance of going online. And that tectonic shift, nearly overnight of offline to online behavior and commerce and social and going down the list, that requires new application development. And I'm very pleased about this partnership is that together, we're giving developers the tools to really take advantage of that opportunity and go and build our way out of it. >> Well, Scott, congratulations on a great extended partnership with Microsoft and the Docker brand. I'm a big fan from day one. I know you guys have pivoted on a new trajectory, which is phenomenal, very community oriented, very open source, very open. So congratulations on that. Amanda, thanks for spending the time to come on. I'll give you the final word. Take a minute to talk about what's new at Microsoft for the folks that know Microsoft, know they have a developer mindset from day one. Cloud is exploding, code to cloud. What's the update? What's the new narrative? What should people know about Microsoft with developer community? Can you share some data for the folks that aren't in the community or might want to join or the folks in the community who want to get an update? >> Yeah, it's a great kind of question. Right now, I think we are all really focused on making sure that we can empower developers throughout the world and that includes both those who are building solutions for their organizations today but also, I think we're going to end up with a ton of new developers over this next period, who are really entering the workforce and learning to create digital solutions. Overall, there's a massive developer shortage across the world. There's so much opportunity for developers to kind of address a lot of the needs that we're seeing out of organizations, again, across the world. And so I think it's just a really exciting time to be a developer and my only hope is that basically we're building tools that actually enable them to solve the problem. >> Awesome insight, and thank you so much for your time. Code to cloud developers are cranking away, they're the first responders, going to take care of business and then continue to build out the modern applications. And when you have a crisis like this, people cut right through the noise and get right to the tools that matter. So thanks for sharing the Microsoft-Docker partnership and the things that you guys are working on together. Thanks for your time. >> Thank you. >> Thank you. >> Okay, this is theCUBE's coverage. We are at Dockercon 2020 Digital. This is theCUBE Virtual. I'm John Furrier, bringing all the action, more coverage. Stay with us for more Dockercon Virtual after this short break. (gentle music)

>>From around the globe. It's the view with digital coverage of Docker con live 2020 brought to you by Docker and its ecosystem partners. >>LeBron. Welcome back to DockerCon 2020 hashtag Docker 20 this is the cube and Dockers coverage of Docker con 20 I'm Sean for you and the Palo Alto studios with our quarantine crew. We've got a great interview segment here in big news around developer workflow code to cloud. We've got Amanda silver corporate vice president, product for developer tools at Microsoft and Scott Johnson, the CEO of Docker. Scott had a great keynote talking about this relationship news has hit about the extension of the Microsoft partnership. So congratulations Amanda. Welcome to the cube. >>Thanks for having me. >>Amanda, tell us a bit about what your role is at Microsoft. You guys are well known in the developer community to develop an ecosystem when even when I was in college going way back, very modern. Now cloud is, is the key code to cloud. That's the theme. Tell us about your role at Microsoft. >>Yeah. So I basically run the product, uh, product design and user research team that works on our developer tools that Microsoft and so that includes the visual studio product as well as visual studio code. Um, that's become pretty popular in the last few years, but it also includes things like the.net runtime and the TypeScript programming language as well as all of our Azure tooling. >>What's your thoughts on the relationship with Docker? I'll show you the news extension of an existing relationship. Microsoft's got a lot of tools. You've got a lot of things you guys are doing, bringing the cloud to every business. Tell us about your thoughts on this relationship with Donker. >>Yeah, well we're very excited about the partnership for sure. Um, you know, our goal is really to make sure that Azure is a fantastic place where all developers can kind of bring their code and they feel welcome. They feel natural. Uh, we really see a unique opportunity to make the experience really great for Docker, for the Docker community by creating more integrated and seamless experience across Docker, desktop windows and visual studio. And we really appreciate how, how Docker is kind of, you know, supported our windows ecosystem to run in Docker as well. >>Scott, this relationship and an extension with Microsoft is really, uh, I think impressive and also notable because Microsoft's got so many, so many tools out there and they have so successful with Azure. You guys have been so successful with your developer community, but this also is reflective of the new Docker. Uh, could you share your thoughts on how this partnership with Microsoft extending the way it is with the growth of the cloud is a reflection of the new Docker? >>Yeah, absolutely. John's great question. One of the things that we've really been focused on since November is fully embracing the ecosystem and all the partnerships and all the possibilities of that ecosystem. And part of that is just reality. That we're a smaller company now and we can't do it all, nor should we do it all. Part of us. The reality that developers love voice and no one's gonna change their minds on choice. And third is just acknowledging that there's so much creativity and so much energy. The four walls of Docker that we'd be building, not the big advantage of that and welcome it and embrace it and provide that as a phenomenal experience part of Alfred's. So this is a great example of that. The sneak partnership we announced last week is a grant to have that and you're going to see many more of uh, partnerships like this going forward that are reflective of exactly this point. >>You've been a visionary on the product side of the interviewed before. Also deploying is more important than ever. That whole workflow, simplifying, it's not getting complex. People want choice, building code, managing code, deploying code. This has been a big focus of yours. Can you just share your thoughts on where Microsoft comes in because they got stuff too. You've got stuff, it all works together. What's your thoughts? >>Right? So it needs to work together, right? Because developers want to focus on their app. They don't want to focus on duct taping and springing together different siloed pools, right? So you can see in the demo and you'll see in, uh, demonstrations later throughout the conference. Just the seamless experience that a developer gets in the document man line inter-operating with visual studio code with the Docker command line and then deploying to Azure and what's what's wonderful about the partnership is that both parties put real engineering effort and design effort into making it a great experience. So a lot of the complexities around the figuration around default settings around uh, security, user management, all of that is abstracted out and taken away from the developer so they can focus on applications and getting those applications deployed to the proudest quickly as possible. Getting their app from code to cloud is the wok word or the or the call to action for this partnership. And we think we really hit it out of the park with the integration that you saw, >>Great validation and a critical part of the workflow. You guys have been part of Amanda, we're living in a time we're doing these remote interviews. The coven crisis has shown the productivity gains of working at home and working in sheltering in place, but also as highlighted, the focus of developers mainly who have also worked at home. They've kind of used to this. Do you see the rigs? I saw her at Microsoft build some amazing rigs from the studio. So these guys streaming their code demos. This is, um, a Cambrin explosion of new kinds of productivity. And yet the world's getting more complex at scale. This is what cloud does. What's your thoughts on this? Cause the tooling is more tools than ever, right? So I still gotta deploy code. It's gotta be more agile. It's gotta be faster. It's gotta be at scale. This is what you guys believe in. What's your thinking on all these tooling and abstraction layers and the end of the day, don't you still got to do their job? >>Yeah, well, absolutely. And now, even more than ever. I mean, I think we've, we've certainly seen over the past few months, uh, uh, a more rapid acceleration of digital transformation. And it's really happened in the past few years. Uh, you know, paper processes are now becoming digit digital processes. All of a sudden, you know, everybody needs to work and learn from home. And so there's just this rapid acceleration to kind of move everything to support our new remote lifestyle. Um, but even more so, you know, we now have remote development teams actually working from home as well in a variety of different kinds of, uh, environments. Whether they're using their own personal machine to connect to their infrastructure or they're using a work issued machine. You know, it's more important than ever that developers are productive, but they are productive as a team. Right? Software is a team sport. >>We all need to be able to work together and to be able to collaborate. And one of the most important aspects of agility for developers is consistency. And, uh, what Docker really enables is, uh, with, with containerization is to make the infrastructure consistent and repeatable so that as developers are moving through the life cycle from their local, local dev desktop and developing on their local desktop to a test environment and to staging and to production, it's really, it's infrastructure of or, or developers as well as operations. And so it's that, that infrastructure that's completely customizable for what the developer's operating system of choices, what their app stack is, all of those dependencies kind of running together. And so that's what really enables developers to be really agile and have a really, really fast iteration cycle but also to have that consistency across all of their development team. And you know, we, we now need to think about things like how are we actually going to bring on interns for the summer, uh, and make sure that they can actually set up their developer boxes in a consistent way that we can actually support them. And things like Docker really helped with that >>As your container instances and a visual studio cloud that you guys have has had great success. Um, there's a mix and match formula here. At the end of the day, developers want to ship the code. What's the message that you guys are sending here with this? Because I think productivity is one, simplification is the other, but as developers on the front lines and they're shipping in real time, this is a big part of the value proposition that you guys are bringing to the table. >>Yeah, I mean the, the core message is that any developer and their code is welcome, uh, and that we really want to support them and power them and increase their velocity and the impact that they can have. Um, and so, you know, having things like the fact that the Docker CLI is natively integrated into the Azure experience, uh, is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. Um, and now that the Docker CLI tools are, that are part of Docker desktop, have access to native commands that work well with Azure container instances. Uh, Azure container instances, if anybody's on familiar with that, uh, is the simplest and fastest way to kind of set up containers and Azure. And, and so we believe that developers have really been looking for a really simple way to kind of get containers on Azure. And now we that really consistent experience across our service services and our tools and visual studio code and visual studio extensions make full use of Docker desktop and the Docker CLI so that they can get that combination of the productivity and the power that they're looking for. And in fact, we've, we've integrated these as a design point since very early on in our partnership when we've been partnering with, with Docker for quite a while. >>Amanda, I want to ask you about the, the, the, the tool chain. We've heard about workflows, making it simpler, bottom line, from a developer standpoint, what's the bottom line for me? What does this mean to me? Uh, every day developer out there? >>Um, I, I mean, I really think it means you know, your productivity on your terms. Um, and so, you know, Microsoft has been a developer company since the very, very beginning with, you know, bill Gates and, and, uh, GW basic. Um, and it's actually similar for Docker, right? They really have a developer first point of view, uh, which certainly speaks to my heart. And so one of the things that we're really trying to do with, with Docker is to make sure that we can create a workflow that's super productive at every stage of the developer experience, no matter which stack they're actually targeting, whether there's targeting node or Python or.net and C-sharp or Java. Uh, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create, you know, Docker container images and use the compose Docker compose files. >>Um, and then, you know, just kind of do that consistently as you're deploying it all the way up into your infrastructure in Azure. And the other thing that we really want to make sure is that that even post deployment, you can actually inspect and diagnose these containers and images without having to leave the tool. Um, so we, we also think about the process of writing the code, but also the process of kind of managing the code and remediating issues that might come up in production. And so, you know, we really want you to be able to look at containers up in the Azure. Uh, up that are deployed into Azure and make sure that they're running and healthy and that if there, if something's wrong, that you can actually open up a shell and be in an interactive mode and be able to look at the logs from those containers and even inspect when to see environment variables or other details. >>Yeah, that's awesome. You know, writing code, managing code, and then you've got to deploy, right? So what I've been loving about the, the past generation of agile is deployment's been fast to deploy all the time. Scott, this brings up that the ease of use, but you want to actually leverage automation. This is the trend that you want to get in. You want, you don't want, you want to make it easy to write code, manage code. But during the deployment phase, that's a big innovation. That's the last point. Making that better and stronger. What's your thoughts on simplifying that? >>So that was a big part of this partnership, John, that the Docker in Microsoft embarked on and as you saw from the demo and the keynote, um, all within the man line, the developers able to do in two simple commands, deploy an app, uh, defining compose from the desktop to Azure and there's a whole slew of automation and pre-configured smart defaults or sane defaults that have gone on behind the scenes and that took a lot of hardcore engineering work on part of Docker and Microsoft together to simplify that and make that easy and that, that goes exactly to your point. We just like the simpler you can make it more, you can abstract a way to kind of underlying plumbing and infrastructure. The faster devs can get there. Their application from code to cloud. >>Scott, you've been a product CEO, you've been a product person, a CEO, but you have a product background. You've been involved with the relationship with Microsoft for a long time. What's the state of the market right now? I mean, obviously Microsoft has evolved. Look at just the performance corporate performance. The shift to the cloud has been phenomenal. Now developers getting more empowered, there's more demand for the pressure to put on developers to do more and more, more creativity. So you've seen this evolve, this relationship, what does it mean? >>Yeah, it's honestly a wonderful question, John. And I want to thank Amanda and the entire Microsoft team for being long standing partners with us on this journey. So it's might not be known to everyone on today's, uh, day's event. But Microsoft came to the very first Docker con event, uh, way back in June, 2014 and I had the privilege of, of reading them and welcoming them and they're, they were full on ready to see what all the excitement about Docker was about and really embrace it. And you mentioned kind of openness and Microsoft's growth over that, uh, over time in that dimension. And we think kind of Docker together with Microsoft have really shown what an open developer community can do. And that started back in 2014 and then we embarked on an open source collaboration around the Docker command line of the Docker engine, bringing that Docker engine from Linux and now moving it to windows applications. And so all of a sudden the promise of right ones and use the same primitives, the same formats, the same fan lines, uh, as you can with Linux onto windows applications. We brought that promise to the market and it's been an ongoing journey together with Microsoft of open standards based, developer facing friendliness, ease of use, fast time to deploy. And this, this partnership that we announced yesterday and we highlighted at the keynote is just another example of that ongoing relationship laser like focused on developer productivity and helping teams build great apps. >>Why do you like Azure in the cloud for Docker? Can you share why? >>Well, it's as Amanda has been sharing, it's super focused on what are the needs of developers to help them continue to stay focused on their apps and not have their cognitive load burdened by other aspects of getting their apps to the cloud. And Azure, phenomenal job of simplifying and providing sane defaults out of the box. And as we've been talking about, it's also very open to partner like the one we've announced >>Yesterday and highlighted, you know, but >>Uh, make it just easy for development teams to choose their tools and build their apps and deploy them onto Azure. It's possible. So, uh, it's, it's a phenomenal plan, one for developers and we're very excited and proud of partner with Microsoft on it. >>Amanda, on your side, I see DACA has got millions of developers. You guys got millions of developers even more. How do you see the developers in Microsoft side engaging with Docker desktop and Docker hub? Where does it all fit? >>I think it's a great question. I mean, I mentioned earlier how the Docker context can help individuals and teams kind of work in their environments work. Let me try that over. I mentioned earlier how I, how I see Docker context really improving the way that individuals and teams work with their environments and making sure that they're consistent. But I think this really comes together as we work with Docker desktop and Docker hub. Uh, when developers sign into Docker hub from Docker desktop, everything kind of lights up. And so they can see all of the images in their repositories and they can also see the cloud environments they're running them in. And so, you know, once you sign into the hub, you can see all the contexts that map to the logical environments that they have access to like dev and QA and maybe staging. And another use case that's really important is that, you know, we can access the same integration environment. >>So, so I could have, you know, microservices that I've been working on, but I can also see microservices that my, my teammates and their logs, uh, from the services that they've been working on, which I think is really, really great and certainly helps with, with team productivity. The other thing too is that this also really helps with hybrid cloud deployments, right? Where, you know, you might have some on premises, uh, hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things, uh, through your Docker hub. >>Well, I got to say I love the code to cloud tagline. I think that's very relevant and, and catchy. Um, and I think, I guess to me what I'm seeing, and I'd love to get your thoughts, Amanda, on this, as you oversee a key part of Microsoft's business that's important for developers, just the vibe and people are amped up right now. I know people are tense and anxiety with the covert 19 crisis, but I think people are generally agreeing that this is going to be a massive inflection point for just more headroom needed for developers to accelerate their value on the front lines. What's your personal take on this and you've seen these ways before, but now in this time, what are you most excited about? What are you optimist about? What's your view on the opportunities? Can you share your thoughts? Because people are going to get back to work or they're working now remotely, but when we go back to hybrid world, they're going to be jamming on projects. >>Yeah, for sure. But I mean, people are jamming on projects right now. And I think that, you know, in a lot of ways, uh, developers are our first responders in, you know, in that they are, developers are always trying to support somebody else, right? We're trying to somebody else's workflow and you know, so we have examples of people who are, uh, creating new remote systems to be able to, uh, schedule meetings in hospitals or the doctors who are actually the first, first responders taking care of patients. But at the end of the day, it's the developer who's actually creating that solution, right? And so we're being called the duty right now. Um, and so we need to make sure that we're actually there to support the needs of our users and that we're, we're basically cranking on code as fast as we can. Uh, and to be able to do that, we have to make sure that every developer is empowered and they can move quickly, but also that they can collaborate freely. And so, uh, I think that, you know, Docker hub Docker kind of helps you ensure that you have that consistency, but you also have that connection to the infrastructure that's hosted by your, your organization. >>I think you nailed that amazing insight. And I think that's, you know, the current situation in the community matters because there's a lot of um, frontline work being done to your point. But then we've got to rebuild. The modernization is happening as well coming out of this. So there's going to be that and there's a lot of comradery going on and massive community involvement. I'm seeing more of, you know, the empathy, but also now there's going to be the building, the creation, the new creation. So Scott, this is going to call for more simplicity and to abstract away the complexities. This is the core issue. >>Well that's exactly right and it is time to build, right? Um, and we're going to build our way out of this. Um, and it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that, that community energy and give them the tools to go. And identify and have an impact as quickly as possible. We have referenced in the keynote, um, completely bottoms up organic adoption of Docker desktop and Docker hub in racing to provide solutions against the COBIT 19 virus. Right? It's a, it's a war against this pandemic that is heavily dependent on applications and data and there's over 200 projects, community projects on Docker hub today where you've got uh, cools and containers and data analysis all in service to the photo at 19 battle that's being fought. And then as you said, John, as we, as we get through this, the other side, there's entire industries that are completely rethinking their approach that were largely offline before that. Now see the imperative and the importance of going online and that tectonic shift nearly overnight of offline to online behavior and commerce and social and go on down the list that requires new application development. And I'm very pleased about this partnership is that together we're giving developers the tools to really take advantage of that opportunity and go and build our way out of it. >>Well, Scott, congratulations on a great extended partnership with Microsoft and the Docker brand. You know, I'm a big fan of from day one. I know you guys have pivoted on a new trajectory which is very community oriented, very open source, very open. So congratulations on that Amanda. Thanks for spending the time to come on. I'll give you the final word. Take a minute to talk about what's new at Microsoft. For the folks that know Microsoft, know they have a developer mindset from day one cloud is exploding code to cloud. What's the update? What's the new narrative? What should people know about Microsoft with developer community? Can you share from some, some, some uh, data for the folks that aren't in the community or might want to join with folks in the community who want to get an update? >>Yeah, it's a, it's a great, great kind of question. I mean, you know, right now I think we are all really focused on making sure that we can empower developers throughout the world and that includes both those who are building solutions for their organizations today. But also I think we're going to end up with a ton of new developers over this next period who are really entering the workforce and uh, and learning to create, you know, digital solutions overall. There's a massive developer shortage across the world. Um, there's so much opportunity for developers to kind of, you know, address a lot of the needs that we're seeing out of organizations again across the world. Um, and so I think it's just a really exciting time to be a developer. Uh, and you know, my, my uh, my only hope is that basically we're, we're building tools that actually enable them to solve problems. >>Awesome insight and thank you so much for your time code to cloud developers are cranking away that the first responders are going to take care of business and then continue to build out the modern applications. And when you have a crisis like this, people cut right through the noise and get right to the tools that matter. So thanks for sharing the Microsoft Docker partnership and the things that you guys are working on together. Thanks for your time. Okay. This is the cubes coverage. We are Docker con 2020 digital is the cube virtual. I'm Sean for bringing all the action. More coverage. Stay with us for more Docker con virtual. After this short break.

(upbeat music) >> Narrator: From Seattle, Washington it's theCUBE. Covering AWS Imagine. Brought to you by Amazon Web Services. >> Hey, welcome back everybody, Jeff Rick here with theCUBE. We're at AWS Imagine, it's a show all about education. That's whether it's university, K to 12, community college, post-military service. Amazon is very, very committed to education market. It's part of the public sector group underneath Teresa Carlson. This is the second year of the conference. We're excited to be back, and really some interesting conversations about how does education move forward. 'Cause it doesn't necessarily have the best reputation for being the most progressive industry out there. So we're excited to have our next guest all the way from London, she's Dr. Amanda Broderick, the Vice-Chancellor and President of the University of East London. Welcome. >> Thank you very much. Thank you, very nice to meet you. >> Absolutely, so first off before we get into it, just kind of your impressions of this event, and kind of what Amazon is doing. Teresa did the keynote today, which is not insignificant. She's a super busy lady, and kind of what does this ecosystem, these resources, this kind of focus, do for you as an educator? >> The main reason that we're working with AWS in such a significant way is actually because of our genuine values alignment. Institutionally, those core priorities are really where we want to go as an organization. And for me this conference, this summit, has been an opportunity to share best practice, to innovate, to truly explore the opportunity to disrupt for ultimately, the end goal. Which is about the education, the development of our next generation, and the support of talent development for the future. >> But unfortunately, a lot of times it feels like institutions put the institution first, and we're seeing a lot of conversations here in the US about these ridiculously crazy, large endowments that sit in piles of money. And is the investment getting back to the students? Are we keeping our eye on the ball? That it's the students that need the investment, not all the other stuff, all the other distractions, that get involved in the higher education. >> I suppose that is where the University of East London is fundamentally different. Core to our mission is driving social mobility, and as such we have to be absolutely clear what those learner outcomes are, and they are about being able to access and accelerate in their careers, and indeed in their lifelong learning to enable them to progress in portfolio careers. >> Right, so it's interesting ahead the three topics for this shows is tomorrow's workforce, which we've talked a lot about the education. The role of ML, which I think is interesting that it got its own bullet. Just because machine learning is so pervasive, and software, and doing lots of things. And the one that that struck me is the effort to have higher predictability on the success of the student, and to really make sure that you're catching problems early, if there is a problem. You're actually using a lot of science to better improve the odds of that student success. A lot of conversation here about that topic. >> Absolutely, absolutely, and that machine learning approach is one of the key dimensions in our relationship with AWS. And this is not just about the student outcomes around continuation, engagement, progression, student success, but actually for the University of East London, it's also been about the identification of students at risk. So we fundamentally believe that health gain is a precondition of learning gain. Particularly important for an institution like ours that is so socially inclusive, and therefore what we're doing, we're actually one of ten institutions that have been funded by the government and working in partnership with AWS as a pilot to share best practice across the UK as a whole, is to identify the proxies. For example, mental health issues, to be able to signpost and traffic light the sign posting to areas of support and to be able to direct prevention, intervention and postvention strategies to those students at risk. And that project is actually a key area of our partnership development with AWS. >> And how long has that been going on? We talked it a little bit about it before we turn the cameras on, and it just seems so foundational to me that without putting in that infrastructure for these kids, regardless of their age, their probability of success on top of that, without a good foundation is so much less. So when did this become a priority? How are you prioritizing it? What are some of the really key measures that you're using to make sure that you're making progress against this goal? >> Absolutely, so the university has made good progress in terms of the fundamental issues of identifying where the correlations and the causations are between both physical and mental health and well-being, and outcomes. What we haven't been able to do at this point is the scalability of this issue, and that's really where this pilot project, which has literally been announced in the last couple of weeks, that we're working very closely with AWS in order to convert that core foundational research and development into scalable solutions. Not just for my own university, but actually for the sector as a whole. >> Right, so we talked about academic institutions, maybe not necessarily have the best reputation for innovation, especially kind of old storied ones with old ivy plants growing up old old brick walls. Is this a new kind of realization of the importance of this? Is this coming from maybe some of the more vocational kind of schools, or is it coming from the top? Do they realize that there's more to this than just making sure people study, and they know what they're doing when they turn in their test and get their paper in on time? >> It's both a top-down and bottom-up approach. It's fundamental to the University of East London. It's new ten year strategy vision 2028. Health gain is that precondition of learning gain. It's fundamental to the realization of our learner's success. But also it's come from a groundswell of the research and development outcomes over a number of years. So it's absolutely been the priority for the institution from September 2018, and we've been able to accelerate this over the last few months. >> So important. Such important work. Flipping the point a little bit on to something a little lighter, a little bit more fun, it's really innovation on the engagement with the students around things like mobile. We've had a lot of conversations here about integrating Alexa, and voice, and competing with online, and competing with other institutions, and being a little bit more proactive in engaging with the customer as your students. I wonder if you can share some thoughts as to how that has evolved over time. Again, you've been in the business for a while, and really starting to cater and be innovative on that front end, versus the back end, to be more engaging and help students learn in different ways. Where they are in little micro segments. It's a very different kind of approach. >> It absolutely is and one of our four major facilitating transformation projects, it's called our digital verse project, and that is across all of our activities of an institution, in terms of business transformation, our particular priority is prospect engagement, and how we actually convert our potential learners in more effective ways. Secondly, enhancing deeper learning, and how we then produce better learner outcomes. Thirdly, how we develop access to new ways of educational provision, 24/7 global access. And fourthly, how do we connect with employers in partnership to make sure that we get those challenges around pre-selection recruitment strategies, and we're unable to get the students, our learners, into careers post graduation. >> Right, and then what's the kind of feedback from the teachers and the professors? They have so much on their plate. Right, they've got their core academic research that they're doing, they're teaching their students, they've got a passion around that area. I always tell people it's like driving in the car in the snow at night with your headlights on, right. Just like all types of new regs that are coming in and requirements and law, and this that and the other. Now we're coming in with this whole four point digital transformation. Are they excited, are they overwhelmed, are they like finally, we're getting to do something different? I mean what's the take within the academics, specifically in your school? >> I think the answer to that is all of the above. >> All of the above. >> It really reflects the classic adoption curve. So you do have the innovators, you have the early adopters, and then you also have the laggards at the other end. And an often actually, the most traditional academics that have been doing things for many, many years, who are very set in their ways, if you expose them to new opportunities, new experiences, and actually provide them with the tools to innovate, they could be some of the best advocates for the transformation and we've certainly found that to be the case. >> Good, well Amanda, thanks for taking a few minutes of your time, it sounds like they're going to start the dancing here behind us soon. So I think we'll have to leave it there, but I look forward to seeing you sometime in London. >> Thank you very much. >> Alright, she's Dr. Amanda Broderick, I'm Jeff Rick, you're watching theCUBE. We're at AWS Imagine in Seattle. Thanks for watching we'll see you next time. (upbeat music)

(upbeat music) >> Live from Orlando, Florida, it's theCUBE covering Cisco Live 2018, brought to you by Cisco, NetApp, and theCUBE's ecosystem partnership. (upbeat music) >> Hello, welcome back everyone to the live CUBE coverage here in Orlando, Florida for Cisco Live 2018. I'm John Furrier with my co-host Stu Miniman. Three days days of wall-to-wall live coverage, we have Mandy Whaley, senior director of developer experience at Cisco DevNet and Par Merat, who is the senior director of community and ecosystem for DevNet. Mandy, great to see you, CUBE alumni. Every single time we had theCUBE with DevNet team, Par, great to see you. Congratulations, first of all. >> Thank you. >> Thanks for coming on. >> Thank you, we're happy to be here. >> Congratulations, so, really kind of a proud moment for you guys, and I want to give you some mad props on the fact that you guys have built a successful developer program, DevNet and DevNet Create for Cloud Native, over a half a million registered, engaged users, of developers using it. Not just people who come to the site. >> Correct. >> Right. >> Real developers. For an infrastructure enterprise company, that's a big deal, congratulations. >> It is, thank you, thank you. We were just chatting this morning about the really early days of DevNet at Cisco Live, and the first year of DevNet Create. And it's been great to see that community grow. And see, early on we had this vision of bringing the application developers and the infrastructure engineers together, and cross-pollinating those teams, and having them learn about each other's fields, and then build these programmable infrastructure enabled apps, and that's really, that synergy is happening within the community, and it's great to see them exchanging ideas here at events like this. >> And so we love to talk about seminal moments, and obviously DevOps drove a lot of the Cloud, and Chuck Robbins, your CEO said, "Without networking, there'd be no Cloud." True statement, absolutely, but Stu and I have always talked about the role of a network engineer, and that the power that they used to have in the enterprise is still due. It used to be the top people running the networks, mission critical, obviously security, but it's not about a retraining. It's about a path, and I think what you guys have done in success is you've shown a path where it's not about pivoting and being relevant and retraining to get a new job, it's been an extension of what they already know, >> An incentive. and I think that's very refreshing, and I think that's the real discovery. >> And we've been able to grow, because I think in our foundational years, we really spent a lot of time providing the content and the skill training, and what Mandy likes to say is, "We met them where they are." So no question was too novice. Likewise, if they were a little more advanced, we could direct them and point them in that same direction. So those early years, where, Mandy, we were just reminiscing about the first DevNet-- >> Coding 101? >> Yes, exactly, she wrote it over the weekend, and we rolled that whole event out, literally, in three months. >> And what year was that, just to kind of, this is an important seminal moment. >> 2014. >> May of 2014. >> 2014. >> 2014, the seeds of we should do something, and you guys have had certifications. We're looking at CCIEs, you go back to 1993 all the way now to 2018, so it's not like you guys are new to certification and training. It's just taking the IQ of network people, and giving them some insight. So what happened in 2014? Take us through the, obviously you bootstrapped it. >> Yes. (laughs) >> What happened, what happened next? >> We did. >> Everyone's like, whoa, >> So-- >> we can't, we're not, we're staying below the stack here. >> Well, we knew there was a lot of buzz around SDN and programmability, and we both actually, I should even back up further. We were both on the DevNet team when the DevNet program was Powerpoints, so we weren't even there yet. >> Right, when we were just planning what it even could be, like the ideas of having a developer program, and like Par was saying, we knew SDN was coming. We knew Network Controllers were coming. We didn't know what they were gonna be called, we didn't know what those APIs looked like, but we said, "The network engineers are gonna need "to know how to make REST API calls. "They're gonna need to know how to operate in Python." And so we started this program building around that vision before the portfolio is where it is today. Like today, now, we have APIs across the whole portfolio, Data Center, service provider, enterprise, and then up and down from the devices, all the way to controllers, up to the analytics level. So the portfolio's really filled out, and we've been able to bring that community along with it, which has been great. >> I want to dig into the north/south, east/west and that whole, kind of the Cloud paradigm, but I got to ask you, on a personal question, although relevant to the DevNet success. Was there a moment where, actually the seminal moments of 2014, was there a moment where you were like, "Wow, this is working." and like the, you know, (laughs) pinch me moment, or was it more of, "We got to get more resources, this is not just, "this thing's flying." >> Well it's always that. That's always the challenge. >> When was the point where >> We are, >> you said, "This is actually >> We are very-- >> "the best path, it's working, double down." When was that happening? >> I mean, I think after we started teaching those very early coding coding classes, I got this, like, flood of email from people who had attended them that said, "I took this task, I automated it, "it saved my team months of work," and getting that flow of information back from the community was early signs to me, from the technical level of, there's value, this is gonna take off, and then I think we just saw that kind of grow and grow. >> Mushroom, just kept it going. >> The other thing that I heard from a network engineer, which really resonated with me, was, you were saying, the network guy or gal likes to be there and solve the problem, and they're sort of at this deep level of control. And what I heard them say about the programmability skills was that that was another tool that they added to their sort of toolbox that let them be that person in the moment, solving that problem. And they could just solve it in a new way, so hearing the network engineers say that they have adopted programmability in that fashion, that let me know that that was gonna work, I think. >> All right, so let's get into some of the meat and potatoes, because you guys have some really good announcements. We saw you have the code ecosystem that you announced at DevNet Create, which is your emerging Cloud Native worlds coming together. That's available now. >> Yes, it's fully released. >> So take a minute to, so give us the update. >> Yes, so DevNet Code Exchange is developer.cisco.com/codeexchange so you can go there, it's live, and the idea behind this was we wanted to make it easy for the community to contribute, and also to discover code written by the community. So it's on GitHub. You can go and search on GitHub, but you get back a ton of hits if you go search Cisco on GitHub, which is great, but what we wanted to have was a curated list that you can filter by product, by language. I sometimes joke that it's like Zappos for sample code cause you can go on and say, "I want black boots, "you know the two inch heel." You can say, "I want, I want code for DNA Center, "or ACI, and I want it in Python," and then see all of the repositories submitted by the community. And then the community can also share their codes. "Hey, I've been working on this project. "I'm gonna add it to Code Exchange, so that other people "can build off of it and find it." So it's really about this community contribution, which is a strategic initiative for DevNet for this year. >> Mandy, how does that tie into other networking initiatives happening in the industry? I think of OpenDaylight, a lot of stuff happening, Docker comes this week, Kubernetes, and networking's a critical piece of all of these environments. >> Yeah, so some of the projects that you'll find in Code Exchange are things that relate. So we have some really good open-source community projects around YANG models and the tooling to help you deal with YANG models. So those might be in Code Exchange, but those are also part of the OpenDaylight community, and being worked in that. So because it is all open-source, because it is freely shared, and it's really just a way to improve discoverability, we can share easily back and forth between those communities. >> The Code Exchange is designed to really help people peer-to-peer work together and reuse code, but in the classic >> Reuse code within >> open-source ethos. >> the community. Exactly. >> Okay, so Par, you have something going on with Ecosystem Exchange. >> We do. >> Okay, so it sounds like Code Exchange, ecosystem partners, matchmaking service. What is it, take a minute to explain. >> It's kinda the next level up, and what I think we have to understand is, when we've got Code Exchange and Ecosystem Exchange under the umbrella of exchange, because within our 500, half a million community of developers, where they work, what we've found is predominately at SIs, at our VARs, at our ISVs. So these are the builders, so Code Exchange will even help that persona because they can come and see what's already been built. "Is there something that can jumpstart my development?" And if there's not, then they can work with each other, right? So if I am looking for a partner, a VAR in Australia to help me roll out my application, my navigation application, which needs to know and get data from the network, I can partner through this exchange because I can go in, see everyone, and be able to make that connection digitally versus organically. And this really started, you asked earlier what was one of the pinnacle moments? Well at these DevNet Zones, what we found is that an ISV would partner and start talking to an SI or to a VAR, and they'd start doing business planning, because what this is all about is driving those business outcomes for our customer base. And we're finding more and more they're trying to work together. >> So you're enabling people to get, do some work together, but not try and be a marketplace where you're actually charging a transaction. It's really kind of a matchmaking-- >> This is all about discovery right now. >> Community-driven discovery around business. Yeah, it's interesting, a heard a story in the hallway about DevNet, cause I love to get the examples of, we love what we're doing by the way, but want to get the examples, overheard a guy saying, "We were basically "cratering a business, jumped into the DevNet program, "and turned it around," because there was deals happening. So the organic nature of the community allowed for him to get his hands dirty and leverage it, but actually build business value. >> That's exactly right. >> That's a huge, >> That's exactly right. >> at the end of the day, people love to play with code, but they're building something for business purposes or open-source projects. >> And that's what this is about. It's really transitioning from the, "I'm gonna build," to now there's business value associated with it, and that's spectacular. >> I think so much of my career you talk, the poor network administrators, like "Help, help, "I'm gonna lock myself for a month, "and I'm gonna do all this scripting," and then three months later their business comes and asks for something that, "I need to go it again," because it's not repeatable. It's what we say is that the challenge has been that undifferentiated heavy lifting that too many companies do. >> Exactly. >> Well, that's exactly it, and the interesting thing, especially around intent-based networking is that's opening up a whole new opportunity of innovation and services. And one of the things that isn't very much different with our Ecosystem Exchange is it's the whole portfolio, so we have SIs in there as well as ISVs. And most marketplaces or catalogs really look at it in a silo version. >> I have one example of kinda the two coming together that's really interesting. So, Meraki, which is the wireless network, has really great indoor location-based services you can get from the WiFi. And then there's been ISVs who have built indoor wave finding on top of it, they're really great applications. But those software companies don't necessarily know how to go install a Meraki network or sell a Meraki network to something like this. And so it's been a great way to see how some of those wave finding companies can get together with the people who actually go sell and install and admin Meraki networks, and, but come together, cause they would have a hard time finding each other otherwise. >> And the example is actually rolled out here at Cisco Live. We've, Cisco Live partnered with an ISV to embed a Cloud-based service in their app, which is navigation. So you can go into the Cisco Live app, tap on the session that you want to see. A map will come up that will navigate you from where you are here to get there, and this is, I think this is the second largest conference center in the United States, so having that map >> So you need it. >> is really important. >> I've gotten lost twice. >> We've all got the steps to prove that that is, but, yeah, and that actually brings, one of the questions I had was, is it typically some new thing, to do wireless rollouts and SD-WAN on discovery, or is it core networking, or is it kind of across the board as to when people get involved? >> It's definitely both. It's definitely both. I mean, from the Code Exchange piece, I've talked to a lot of customers this week who are saying, "We've got our core networking teams. "We want to move towards more automation. "We're trying to figure out how to get started." And so we give them all the resources to get started, like our video series and then now Code Exchange. And then I heard from some people here, they actually coded up some things and submitted it to Code Exchange while they were here because they had an idea for just a simple, quick automation piece that they needed. And they were like, "I bet somebody else "needs it too," so it was definitely in that. >> I noticed you guys also have your Cisco team I was talking to, some of the folks here have patents are being filed. So internally at Cisco, it's kind of a wind of change happening, where, >> It is exciting times. >> IoT cameras, I just saw a solution behind us here where you plug a Rasberry Pi hardware prototype to an AP, makes the camera a video. Now it looks like facial recognition, saves the metadata, never stores video, so this is kind of the new model. >> Pretty remarkable. So final question I want to ask you is, as you guys continue to build community, you're looking for feedback, the role of integrating is critical. You mentioned this Cisco example about going to market together. It used to be, "Hey, I'm an integrator of our solution, "business planning," okay, and then you gotta go to the Cisco rep, and then there's, they're dislocated. More and more it's coming together. >> It is. >> How are you guys bridging that, those two worlds? How are you tying it together? What's the plan? >> So we're, what we're finding is a lot of those partners are also sort of morphing. So they're not just one thing anymore, and so what we're doing is we're working with them, enabling them on our platforms, providing solid APIs that they can leverage, transitioning or expanding the code, the skillsets of their workers, and then we're partnering them up with our business partners and with our ISVs, and doing a lot of that matchmaking. And with Ecosystem Exchange, again, they'll now be able to take that to a digital format, so we're seeing the whole wave of the market taking them. >> So you guys see it coming. You're on that wave. >> Yes. >> All right, real quick, I know we're short on time, but I would, Mandy, if you could just talk about what Susie Wee, you're leader talked about on stage on the keynote, she mentioned DNA Center. Can you just take a quick second, describe what that is, why it's important, and impact to the community. >> Yes, so we're really excited about DNA Center platform. DNA Center is the controller, kind of at the heart of all of our new enterprise networking software. So it sits on top of the devices, and it exposes a whole library of APIs. It'll let you do Assurance, policy, get device information. It would allow you to build a kind of self-service ops models, so you could give more power to your power users to get access to network resources, on-board new devices, things like that. >> So it sets the services. >> So it's APIs, and then you can build the services on top. And part of that is also the Assurance, which Dave Geckeler showed in his keynote, which we're really excited about. So, in DevNet we've been working to build all the resources around those APIs, and we have many code samples in Code Exchange. We actually have a community contribution sprint going on right now, and that's called Code Intent with DevNet, and it's all around DNA Center. It's asking developers to take a business intent and turn it into code, and close the loop with Assurance, and submit that back to DevNet. >> That's great. It's a real business process >> We're real excited about >> improvement with code, >> that, yeah, so you're enabling that, and slinging APIs around, having fun, are you having fun? >> Definitely having fun. >> Par? >> We always have fun >> Absolutely >> on this team. >> We always have fun, yeah. >> It's a great team. >> I can say working with you guys up close has been fun to work, and congratulations. You guys have worked really hard and built a very successful, growing ecosystem of developers and partners, congratulations. >> Thank you. You guys have helped. >> Thank you. >> Thanks for supporting >> We appreciate it. theCUBE, really appreciate, this is crew of the DevNet team talking about, back in the early days, 2014, when it started, now it's booming. One of the successful developer programs in the enterprise here. Cisco's really showing the path. It's all about the community and the ecosystems, theCUBE, of course, doing our share. Broadcasting here live in Orlando at Cisco Live 2018. Stay with us for more live coverage after this short break. (upbeat music)

(upbeat music) >> Narrator: Live from the Wynn Hotel in Las Vegas, it's theCUBE, covering Magento Imagine, 2018. Brought to you by Magento. >> Welcome back to theCUBE, I'm Lisa Martin. We've had a really informative day talking all things commerce, open commerce, and digital commerce innovation at Magento Imagine 2018. I'm joined by Amanda Batista, who is the head of content marketing for Magento. Amanda, thanks so much for all your help in coordinating this. We've had a really educational day with your folks, with your customers and partners. >> Yeah, we've had a really great community. It's been wonderful to have theCUBE here, and I'm so thrilled to be able to be here with you closing out the show. >> So this is the eighth Imagine event, There's over 3000 people here. You guys had some great speakers on stage today. I'm always very excited to see female leaders on stage. >> Absolutely. >> We talked about Baked by Melissa, she was our first guest today sharing her story. You've been growing this event year over year. What is it about #LeadingTheCharge, your hashtag and message for this event, that really differentiates this eighth event from the last several? >> Well #LeadingTheCharge is a really exciting message for us because ultimately we're focused on empowering merchants and developers and really allowing them to not worry about the technology component of things. Whatever you can dream, you can do on Magento. So, #LeadingTheCharge for us here today is really about bringing people together, making connections, and really thinking about, How do you use this community? How do you tap into all these resources? How do you see people that you haven't seen in a while? It's kind of our coming out party, our big coming together. You know, #LeadingTheCharge I think means different things for different folks, but I think for us we're really aiming to empower individuals to do the work that they do really well but also come together. So I actually heard a gentleman say that part of Leading the Charge for him is a matter of making connection. It's almost stepping out as a leader and allowing other people to come together. I think #LeadingTheCharge has been a really nice message for us today and I think our speakers have really brought that to life. >> I agree and with the sentiment that we've heard. Magento started reputation-wise, helping retailers to target the online shoppers and the experiences there. We talked with Peter Sheldon today about what you guys are doing in really formalizing how you're helping businesses, B2B organizations. There's so much opportunity that's really being driven by all of us as consumers and we have this expectation that we can get anything, anywhere, anytime. >> That's right. >> And have it delivered day or night. Amazon sets the bar really high. You guys had Amazon on main stage this morning talking about the fact that there's now 100 million Prime subscribers and how half of Amazon's revenue doesn't come from products they sell, this third-party marketplace just kicks open the doors of opportunity- >> Amanda: Right. >> for businesses from small to large alike. >> Yeah, I think it's really exciting, too, because, you know we can't all compete on price. We can't all be Amazon, but I think as we're really encouraging merchants to think about, What are you offering that's special? What are you doing from a content standpoint? Obviously, content is near and dear to me, that's my bread and butter and what I've been doing for a long time, but we really think about, what are we offering people that's value-add? Is it an added catalog, is it a manual? Is it something that helps you do your job better? Is it something that helps you go back to your organization and feel celebrated and feel excited?" I think when it comes to how we're empowering people, we're really focused on, from a content perspective, enabling you to, again, not really worry about the tech component, but think about how you can innovate your business. That's really important to us. >> Well, that's one of the things that Melissa Ben-Ishay, she's product officer at Baked by Melissa Cupcakes and how- >> Amanda: Sweet it is. >> I still want, it is, and I still want a cupcake. >> Amanda: Yes! >> It was very evident when we were talking with her that she gets, because of technology, that makes things simple for folks like herself, it allows her not to just grow the business, to open more stores, to reach hundreds of thousands of people, but to do so in a way that she doesn't have to worry about the technology. >> Amanda: Right, right. >> And that really- >> That's a great example, really, for us. I think when we look at who we're looking to enable, you know, Melissa started a business ten years ago, was let go from her job and said, Let me take a passion and bring it to life with business. They had e-commerce even before they had stores. They had e-commerce before they were up and running. I think using that as a linchpin, as a springboard to really bring her business to life, delivering a hundred cupcakes on foot on the New York City subway. I'm from New York, I ride the subway, I wouldn't want to do it with a hundred cupcakes, frankly, but these are the sort of bootstrap methods that she was enabled to do not worrying about that sort of tech component, right? She's bootstraps, she only had about five founders, five people around her with her business. Really great to hear from her and I don't see any cupcakes anywhere but I'm dying for one. >> Me too! >> Or five. >> We need to get some. One of the things that you mentioned, content, earlier, in being a content marketer, look at media as an example, with Netflix and Spotify and Amazon, and what's happened to traditional media. It's now that the way a service is delivered is as important as the content >> Absolutely. >> and what we've heard a lot from your customers that have been on the program today is they have the opportunity to deliver services in a responsive way, and in a way that's really personalized, which is really key, right? As consumers, we all want to have an experience that's tailored to us, and we've heard that as sort of an enabling capability that Magento is helping. We had a gentleman from Coca-Cola on, talking about the Share a Coke experience and how that started as a program in Australia. >> Amanda: Right. >> With one bottler, then went to Europe, then became something that was focused in store, and then the consumers are going, Hey, Coca-Cola, I can't find a bottle with my name on it. And it became this really big program for them, that they had to figure out, How do we do this in the U.S. with 70 bottlers? They needed technology that would allow them to identify and have this visibility of inventory, which you guys allow them to do, but to enable their customers to have an experience with a personalized bottle of Coca-Cola. >> Right. >> Amazing how the technology opens up doors like that, and allows these businesses, whether it's something as an establishment like Coca-Cola, or a Baked by Melissa, to be able to deliver this relevant, personal experience, at the touch of a button. It's Amazing. >> Well, listen, and it's non-negotiable, right? Think about your own experiences as a consumer. Who are you shopping with? I'm shopping with brands that understand me, that know what I need, that are offering value-add. You know, you might also revolutionize the way that we view our experiences, and we really don't have patience. Like you said, we have digital, everything is very quick, and I think the experience is the differentiator. We're really focused, again, on taking the technology out of your planning equation so that you can focus on what are you offering? What are you delivering? How are you delighting? That's a big, big area of opportunity and I think what you do to delight and engage and if you're using data intelligently, and not just the nitty gritty of data, but also simple things, the way that you welcome people via email, the way you engage on Instagram. There's a number of ways to do things that don't really require a lot of planning, a lot of cost, and so in our content efforts, we're really encouraging merchants to think about that. How do you do things in a sort of home-grown way without spending a lot of time or money? We have to be agile, we have to be quick as marketers, I certainly know that, that's the world I live in, and again, it's non-negotiable. I think as a consumer, if I don't feel that you understand me, if I don't feel that you're paying attention to the things that I'm buying or not buying, I'm going somewhere else. I'm going to go to a place that makes me feel as though I'm going to be fulfilled and delighted. I think delight is such an understated thing, but we're here at the Wynn which does a wonderful job with experience and everywhere you go it's so delightful and wonderful. >> Lisa: It is delightful! >> I came back to the room last night and my computer cord was just rattled up ever so gently, and I thought, That's delightful! You know, I Instagrammed that. That's a perfect example of providing experience that is superior. >> Speaking of experience, we just had the gentleman from the Accent Group on, Mark Teperson. It was so interesting how they've taken this company down in Australia and New Zealand, with multiple, many, many, many brands of footwear. And, you know, the online and the physical world have been merging in retail for a while now, but what they're wanting to do, to click and collect, and to create this in-store experience. It was such an interesting way of thinking about and hearing from a Chief Digital Officer say, We want to be able to enable people, especially mobile first, we're sitting on the couch with these things often, but to enable them to be able to come into my store and have an experience. That word is, we heard that referenced in many different times today, the Accent Group was a great example of that, as well as when we had your V.P. of Strategy on saying, A lot of cases depending on the, whether it's B2B or B2C, it's not mobile too, it's mobile only. It's not just leveraging technology and data and analytics to understand what I want as a consumer, but it's how I want to consume it. So it's what I was saying earlier about we're seeing this level playing field of how services are delivered, equally as important as the content that you're going to deliver to me. >> Yeah, absolutely. Again, non-negotiable, right? This idea of an omni-channel experience bridging the gaps between online and in-store, like you said, we're on the couch. I almost never shop on a computer any more, right? I'm mobile, we're enabled, we have PayPal, we our credit cards saved. I think to keep that momentum going, you want it to be a seamless experience. How many times have you gone online and found that an item is supposed to be available in the store. When you go, it's not there, right? I've even done due diligence as a savvy shopper who works in retail and says, Let me call the store and make sure it's there. There's really no margin for error there, because when we talk about experience, if you do go in store, and if you do take the initiative to make that purchase and take time out of your day, right, we're all busy people. I think mobile and digital has made it easy, especially Amazon Prime revolutionized that. (mimics beeping noise) Two days, it's on your doorstep. I think as we look to see who's sort of mimicking that experience, I think an easy way to do it, is simply put, have your systems connected, ensure that things are integrated, ensure that your inventory visibility is on point. It's a non-negotiable experience, really. >> Well, Amanda, we've had a blast at Magento Imagine 2018. Our first one, looking forward to being back next year. Thank you for putting together a great array of guests. I know we've learned a ton about this. I won't look at online shopping again the same. We want to thank you for helping us have a really enlightened and delightful conversation. >> And likewise, we've loved having theCUBE. You guys have been wonderful. I've learned a great deal and it's been really nice spending this time with you. So thanks for having me, Lisa. >> Absolutely. We hope you've had a delightful experience today with us on theCUBE. We've been live at Magento Imagine 2018. Check out theCUBE.net where you can find all the replays of the segments that we filmed today. You can also find the editorial components on SiliconANGLE.com. I'm Lisa Martin for theCUBE. We'll see you next time. (upbeat music)

>> Announcer: From San Francisco, it's The Cube, covering Samsung Developer Conference 2017 brought to you by Samsung. >> Okay, welcome back and we're live here in San Francisco for the Samsung Developer Conference, SDC2017. I'm John Furrier. This is The Cube's exclusive coverage, and I'm excited to have an amazing guest, Amanda Cooloong who's a chief storyteller, Women in Tech International, Tech TV, TechZula. She's been really a storyteller in digital for a long time. Great to have you on. Been following all your Twittersphere and your content. >> Thank you. >> You did some work with Leo Laporte, Jason Calcanis, both this week in tech's kind of version of the scene. >> Mm hm. >> What are you up to now? >> Well I am working very closely with Women in Technology International, WITI. It is the largest, oldest organization for women in tech. They have a huge summit that they put on in San Jose every year, and I'm sort of the class clown for that and emcee the conference and lead the charge there. >> Well certainly you know what's interesting you have kind of a cool vibe, you're a cool person, you know tech, you know cloud computing. >> Mm hm. >> You've been in inside baseball for the tech scene. >> Mm hm. >> But now the consumer market with digital. >> Yeah. >> Pretty powerful, I mean like finally us geeks now have a national and global stage to flex our geekness, so you see nerds- >> We're suddenly cool? >> Cool to be a geek and now you see well the programmer calls us over thank god. >> (laughs) Well is it? >> Well the bad side of it. The good side of the democratization is happening. >> Right. >> So now you have an augmented reality. So it's just some cool stuff happening. What are you most impressed with? >> What am I most impressed with? Well I love Blockchain. I've been involved with some of that for three or four years now. I actually had a podcast about Blockchain and Bitcoin. And I'm really excited about what that means for investment specifically and ICOs, Initial Coin Offerings. My friend Brock Pierce is a big, big figurehead with all of that, with Blockchain Capital. And I believe that, especially for women that are looking to get into investment and get back in the earlier stage of things, I think ICOs, Initial Coin Offerings, are a huge opportunity for them to really change up the venture world. >> So when you say ICOs, which we know a lot about 'cause we're doing one at SiliconANGLE the next couple quarters. >> Yeah. >> No rush to do it but we're going to use our own cryptocurrency. But those nuances, when you say investment do you mean as an alternative to venture capital investment or actually investing in, say, the currency itself? >> Both. But I think of it as a completely new way to invest in companies. And there are so many barriers especially for women in technology... Again, that's a big platform for me. To getting into that world that ICOs just are completely changing up the entire ecosystem there. >> Well we're seen a ton of stuff. You saw Lisa Fetterman was on earlier. >> Mm hm. >> She had a huge success with her Kickstarter. Now she's got some pretty glamorous products. The cooking thing is pretty sexy, right? >> Mm hm. >> That thing could go- >> Sous vide, even the term sous vide. I mean, it's so fresh (laughs) >> I would put money to that. I mean it's just so... But that's a good example of Kickstarter. When we look at some of the ICOs, a lot of people are raising some serious capital in utility and stock or securities. >> Mm hm. >> Although the regulations are a moving train. But on the utility side it's a no-brainer. There's some significant cash being raised. In some cases, five to 50 million plus in token sales. >> Mm hm. >> That's like Kickstarter on steroids. >> It really is, and some people are afraid of it. You know, some people are saying that's completely absurd. Why would you ever do that? I personally would say don't put all of your eggs in one basket either. We know that. There's volatility anywhere. But, again, I think it's opening a lot of doors and giving certain people opportunities that they didn't have before. >> So how is your Bitcoin position these days? >> I may have been an early investor in some Bitcoin. I may obsessively look at the value every 15 minutes or so. No, I am fortunate. I listened to my mentors, and luckily I love emerging tech, so I'm doing well in that regard. >> I saw a post on Facebook: If you just bought 10 in bitcoin and smoked weed and sat on the beach and clipped coupons all day and did nothing else, you'd be worth 20 million dollars. >> Let's just say I know people that have actually bought castles with it. I'm not joking. >> What I like about the crypto Boxchain side is that there's an early community growing. So what's your analysis, because a lot of people want to know, is it Silk Road guys? Are they bad actors? Bitcoin's the underbelly of the internet. Early adopter. >> Those stories were so funny at the beginning. I mean, I live in LA. Everyone loves the sensationalized story. And of course that existed with Bitcoin too, and yes, there was some truth to it. >> Oh of course there was. >> Yes, absolutely the Silk Road story was real. >> Anonymous and encrypted transactions. >> Oh yes. >> That's going to attract some honey to the bees. >> There's a reason why certain people can't come back into the country. Let's just leave it at that. However, we've also seen major financial institutions get onboard. You know, Fintech has exploded. There's a lot of legitimacy to Blockchain and the distributed ledger technology. >> It's one of the fastest growing products in the Linux Foundation, Hyperledger project- >> Yes. >> Which is just going gangbusters. IBM's behind it. >> Yep. >> So it's got that opensource vibe, I get that. But the community, talk about the community because there are people who are leading the community. You said you know a few of them. >> What's your take on the community? How big is it? It's emerging, obviously, it's growing. What's the protocol for new entrants coming in? What's the behavior norms? >> Sure. It's grown in leaps and bounds, I can say that. I mean, from the time I did my Bitcoin podcast a few years ago to now, back then it was very much the bro culture to a degree, a lot of libertarians (laughs), a lot of folks that couldn't come back in the country, to be quite honest. But there were certain people that came out of that movement though like Brock Pierce that really thought ahead to how do we legitimize this, how do we make sure that this is white knighted, so to speak. >> Yeah, well it's a revolutionary... It's fundamental. I had the founder of Alibaba Cloud on the record. Haven't published a video yet so this is exclusive material. He said, I asked him about Blockchain. He says it's fundamental to the internet. It is the internet. >> It is, mm hm. >> Just like TCP/IP was in the stack. >> Absolutely. >> He was adamant that this is not on top of the internet. It's fundamental to... He's talking about Blockchain. >> Yep. >> Absolutely 'cause it's supply chain, it's currency, it's a zillion things. >> It's not just coins. Everyone focused in on Bitcoin Bitcoin Bitcoin. It's a distributed ledger technology. So it goes hand in hand with the internet of things. So the two have become very much married in that regard. >> You know, all these guys I interview on The Cube over the years, and certainly I lived through it, talk about the waves, the PC wave. >> Mm hm. They talk about the client server wave. Client server essentially, it's not so much about the mini computers 'cause the mini computers were not the client server wave 'cause that was proprietary operating systems and proprietary hardware. >> Mm hm. >> HP. >> Right. >> What made client server was TCP/IP. That created Threecom, Cisco, interoperability. So that really was that second wave. People are comparing Blockchain to TCP/IP. >> I can see that. >> Dr. Wang from Alibaba Cloud. Other people are saying like the dot com bubble, euphoric excitement. >> Yeah. >> So that begs the question. Who can bring functionality... This is my thesis. I want to test it with you. >> Mm hm. >> Who can bring functionality and simplicity? Because all the successes in Web 1.0, was Yahoo a directory of links, simple, easy to use. Cisco Routers, connect your networks, it works. So simplicity and functionality seems to be the norm in the Blockchain world. >> Mm hm. >> What's your thoughts on that? Can you share your reaction to that? >> Simplicity and functionality, I mean, for me it's- >> In terms of the winners versus the losers 'cause that's what people want to know with Blockchain. Where's the scams and where the legit? >> Mm hm, well the scams are the people that came from the gaming side that had no real business expanding out the way that they did and everybody loses their coin. But we won't name names there. I think more- >> It's okay to name names. >> (laughs) But with functionality, I mean again, I keep going back to its marriage with IOT, you know, the ledger based technology and just being able to do anything transactional. That's the simplicity of it for me, the fact that it's opensource, the fact that, yeah, I think that's the core of it. >> So let's talk about Samsung. We're here's at the Samsung event. >> Sure. >> How do you see these guys? We were talking about Blockchain. It's kind of the next big wave coming. Obviously a lot of things underneath that, but above that you've got software machine learning, all the goodness of open source is growing exponentially. That wave is coming to exponential growth in opensource, code shipments, meaning more people using opensource, and things like Blockchain. How does that impact a Samsung, an Apple, an Amazon? >> Well I think opensource is necessary for IOT specifically. Obviously that would be shut down without that. I've been talking with a lot of the developers here, the Samsung-specific people saying what is it that's exciting you about this forward movement, like with the keynote this morning. What do we need? How do we move this entire industry forward with IOT? And they're excited about the platform that Samsung has announced this morning in terms of just the ubiquity of everything working together in comparison to, well, a lot of other... Sorry. >> So the crypto thing is also tying into that too. >> Yes. >> I was tying that with IOT because IOT has some security issues. >> Right. >> So we can argue maybe- >> Some security issues? (laughs) >> Well the surface area. So you know, the theme in the enterprise is, you know, cloud computing. There's no moat anymore, there's no firewall. >> Yeah. >> Perimiterless security. Perimiterless problems. It means the edge is a surface area, and we've seen these attacks coming. >> Right. >> That's a problem. >> Mm hm. >> So there's no silver bullet right now. >> Yeah. >> So Samsung probably is cagey right now on the data. >> Exactly. >> They've got some security products, but smarter things is their kind of pitch. >> And then everybody keeps saying well who owns the security piece, who's responsible for the security piece. I think that's a big question we're going to see popping up a lot because the security piece is going to be a very valuable piece to all of this, especially when you're looking at edge computing too and data being passed back and forth between the edge. I would rather see everything stay with just the edge devices, personally. >> Yeah, well it's easier to manage, why do you want to move data across the network? >> Yeah, exactly. >> Move compute it's more efficient. >> Yeah. >> So final take on augmented reality VR. >> Oh, okay. >> What's imploding? What's imploded? What's growing? What's rising? What's falling? >> Sure. >> We had a comment earlier, said VR 1.0 is over. >> It really is. I personally think AR is where it's at. I've watched a lot of things on the VR front and a lot of it was marketing speak. I think we need a bigger push on the hardware side for VR to work effectively too. We also need to look at the audience there. And a lot of people are complaining, well I don't just want to go disappear into a separate world. A lot of women, actually, are complaining about that side of it. But the AR side I think has way more application. >> Yeah, crawl, walk, run in virtual space, basically. >> Yeah, yeah. VR I think will still be a place, but I think AR is going to be a bigger explosion. >> One of the things we were talking about earlier was as folks have been through many waves you and I've seen, waves of innovation, Web 1.0, the early adopters were the adult industry with banners 'cause they were about making money. We saw this wave. We're seeing the Silk Roads and Blockchain. Arbitrage comes from usually bad actors and not usually desirable actors. >> Right. >> But one big indicator of the current user experience we're seeing is the gaming culture, right. >> Mm hm. >> Gaming right now seems to be the early adopter indicator of the major trend lines 'cause it's gamification, it's a little bit analog, multiplayer. >> Look at Unity. Unity has a huge presence here at SDC and especially on the VR front if you want to look at that. Unity's a huge player there. >> What are some of the things you see coming out of the gaming world? 'Cause we've seen virtual currencies, ICO, lot of storage, lot of dynamic, realtime. >> Yeah. Gaming mechanism too across the board always play into this too, but I think the big one is ICOs for me. That's the one I've been focusing on a lot, yeah. >> I'd like to follow up more with you on the ICO thing. We're doing a whole programming on that on November second, love to have you. >> Mm hm. Look at what Crystal Rose with Sensay's been doing. >> Who? >> Crystal Rose, Sensay, she's launched her own ICO called SENSE. >> SENSE. Great, looking forward to chatting more. >> Mm hm, out of LA. >> Final question for you for the folks not here. What's the vibe here? How would you describe SDC2017? >> I love that there's a great vibe of innovation. Honestly, I've been to some other stodgier conferences lately, and this one definitely has a nice playful, creative vibe. >> B2B is boring to boring. This is not- >> I know, you were talking about E2E, everything to everything. See, I was listening. >> You were. >> Everything to everything. Exciting to exciting. >> Exciting. >> See, I listened to that too. Yeah, I would say there's a lot of creativity here. There's a lot of side conversations happening. That's important. And I see a good balance of men and women, so that makes me happy. >> Well I'm excited from Vanessa for bringing on a great lineup, you included. >> Thank you. >> Great to meet you in person. Had a great conversation here inside The Cube. I'm John Furrier here, exclusive coverage of the SDC2017. We'll be back after this short break.

>> Narrator: Live from San Francisco it's The Cube. Covering Devnet Create 2017. Brought to you by Cisco. >> Welcome back everyone. Live in San Francisco this is The Cube's exclusive coverage of Cisco Systems inaugural DevNet Create event an augmentation, extension and build upon their successful three year old DevNet Developer Program. Our next guest is Amanda Whaley who's the director of development experience at Cisco DevNet. Congratulations Amanda on one DevNet being successful for three years and now your foray into DevNet Create which is some call it the hoodie crowd, the cloud native developers, open source, completely different animal but important. >> Yes. >> From DevNet. >> Absolutely so the hoodie crowd is more my tribe that's my background is from software development and I came to Cisco because I was intrigued when they reached out and said we want to start a developer community, we want to start a developer program. I talked to Suzie Wee for a long time about it and what was interesting to me was there were new problems to solve in developer experience. So we know how to do rest APIs, there's a lot of best practices around how you make those easy for developers to use. How you make very consumable and developer friendly and there's a lot of work to do there but we do know how to do that. When you start adding in hardware so IOT, network devices, infrastructure, collaboration, video, there's a lot of new interesting developer experience problems to solve. So I was really intrigued to join Cisco bringing my software developer background and coming from more the web and startup world, coming into Cisco and trying to tackle what's this new connection of hardware plus software and how do we do the right developer experience around... >> Okay so I have to ask you what was your story, take us through the day in the life as you enter in to Cisco, you have Suzie wooed you in you got into the tractor beam 'cause she's brilliant she's awesome and then you go woah I'm in Cisco. >> Amanda: Yeah! >> You're looking around what was the reaction? >> So what was interesting was so DevNet started three years ago at Cisco live we had our first DevNet developer zone within Cisco Live. That was actually my first day at Cisco so my first day at Cisco. >> Peter: Baptism by fire. >> Yes absolutely and so that was my first day at Cisco and Suzie talked to me and she said hey there's a lot of network engineers that want to learn how to code and they want to learn about rest APIs. Could you do like a coding 101 and start to teach them about that so literally my first day at Cisco I was teaching this class on what's a rest API, how do you make the call, how do you learn about that and then how do you write some Python to do that? And I thought is anyone interested in this that's here? And I had this room packed with network engineers which I at that time I mean I knew some networking but definitely nothing compared to the CCIEs that were in the audience. >> John: Hardcore plumber networking guys. >> Yeah very very yeah. And so I taught the course and it just like caught on like wildfire they were so excited about because they saw this is actually pretty accessible and easy to do and one thing that stood out was we made our first rest call from Python and instead of getting your twitter followers or something like that it retrieved a list of network devices. You got IP addresses back and so it related to their world and so I think it was very fortunate that I had that on my first day 'cause I had an instant connection to what that community... >> They're like who is she's awesome come on! >> Co-Ost: Gimme that code! >> You're like ready to go for a walk around the block now come on kindergartners come on out. No but these network guys they're smart >> Really smart. so they can learn I mean it's not like they're wet behind the ears in terms smarts it's just new language for them. >> And that was the point of the class was like you guys are super smart you know all of this you just need some help getting tarted on this tooling. And so many of them I keep up with them on Twitter and other places and they have taken it so far beyond and they just needed that start and they were off to the races. So that's been really interesting and then the other piece of it has been working in our more app developer technologies as developer experience for DevNet I get to work across collaboration, IOT, Networking, data center like the whole spectrum of Cisco technologies. So on the other side in application we have Cisco Spark they have javascript SDKs and it's very developer friendly and so that is kind of going back to my developer tribe and bringing them in and saying to you want to sell to the enterprise, do you want to work with the enterprise, Cisco's got a lot to offer and there's a lot of interesting things to do there. >> Yeah a lot of them have Cisco networks and gear all around the place so it's important. Now talk about machine learning and AI the hottest trend on the planet right now in your tribe and in developer tribe a lot of machine learning going on and machine learning's been around data center, networking guys it's not new to them either so that's an interesting convergence point. IOT as a network device. >> Amanda: Right right. >> So you got IOT you got AI and machine learning booming, this seems like it's a perfect storm for the melting pot of... >> It really is so today in my keynote I talked a little bit about first of all why have I always liked working with the APIs and doing these integrations and I've always thought that it's what I like about it is the possibility you have a defined set of tools or Legos and then you can build them into whatever interesting thing you want to and I would say right now developers have a really interesting set of Legos, a new set of Legos because with sensors, whether that's an IOT sensor or a phone or a video camera or a piece of a switch in your data center a lot of those you can get information from them. So whatever kind of sensor it is plus easy connectivity and kind of connectivity everywhere plus could computing plus data equals like magic because now you can do now machine learning finally has enough data to do the real thing. My original background was chemical engineering and I actually did predictive model control and we did machine learning on it but we didn't have quite enough data. We couldn't store quite enough of it, we didn't have enough connectivity we couldn't really get there. And now it's like all of my grad school dreams are coming true and you can do all these amazing things that seemed possible then and so I think that's what DevNet Create has been about to me is getting the infrastructure, the engineers, the app developers together with the machine learning community and saying like now's the time there's a lot of interesting things we can build. >> And magic can come out of that. >> Magic yeah right! >> And you think about it that's chemical reaction. The chemistry of bringing multiple things together and there's experimentation sometimes it might blow up. >> Amanda: Hopefully not! >> Innovation you know has is about experimentation and Andy Jassy at Amazon web services I mean I've talked to him multiple times and him and Jeff Bezos consistently talk about do experiments try things and I think that is the ethos. >> It is and that is particularly our ethos in DevNet in fact in DevNet Create an experiment right a new conference let's get people together and start this conversation and see how it comes together. >> What's your reaction to the show here? The vibe your feeling? Feedback your getting? Observations. >> I'm so happy it's been great. I had someone tell mt today that this was the most welcome they had felt at any developer conference that they'd been to and I took that as a huge complement that they felt very comfortable, they liked the conversations they were having they were learning lots of new information so I think that's been good and then I think exactly that mix of infrastructure plus app developer that we were trying to put together is absolutely happening. I see it in the sessions I see it in the birds of a feather and there's a lot of good conversations happening around that. >> Question for you that we get all the time and it comes up on crowd chat I'd like to ask you the question just get your reaction to is what misperception of devops is out there that you would like to correct? If there could be one and you say you know it's not that what's your... >> The one that seems the most prevalent to me and I think it's starting to get some attention but it's still out there is that devops is just about about the tools. Like just pick the right devops tools. Docker docker docker or use puppet and chef and you're good you're devopsing and it's like that is not the case right? It's really a lot more about the culture and the way the teams work together so if there was anything I could, and the people right, so it's flipping the emphasis from what's the devops tool that you're using to how are you building the right culture and structure of people? That's the one I would correct. >> Suzie was on yesterday and Peter and Suzie had a little bit of a bonding moment because they recognize each other from previous lives HP and his old job and it brought up a conversation around what Peter also did at his old job at Metagroup where he talked about this notion of an infrastructure engineer and what's interesting. >> Peter: Infrastructure developer. >> I mean infrastructure developer sorry. That was normally like a network engineer. So the network engineer's now on the engineering side meeting with developers almost like there seems I can't put my finger on it just like I can feel it my knee weather patterns coming over that a new developer is emerging. And we've talked a little bit about it last night about this what is a full stack developer it doesn't stop at the database it can go all the way down to the network so you're starting to see the view a little bit of a new kind of developer. Kind of like when data science emerged from not being an analyst but to being an algorithms specialist meets data person. >> Right I think it's interesting and this shows up in a lot of different places. When I think about devops I think about this spectrum of the teams working and there's the infrastructure teams who are working on the most deepest layer of the infrastructure and you kind of build up through there into the Devops teams into the app dev teams into maybe even something sort of above the app dev team which would be like a low code solution where you're just using something like build.io or something like that. Something that we wouldn't normally think of as developers right. So that spectrum is broadening on both ends and people are moving down the stack and moving up the stack. The network engineers one of the things in DevNet we're working on is what we call the evolution of the network engineer and where is that going and network engineers have had to learn new technology before and now there's just a new set which includes automation and APIs and configuration management, infrastructures, code and so they're moving up the stack. And then developers are also starting to think I really want my application to run well on the network because if no one can use it then my application's not doing anything and so things like the optimized for business that we have with Apple where a developer can go in through an SDK and say I want to set these QOS settings so that my app gets treatment like that's a way that they're converging and I think that's really interesting. >> Peter: So one of the things that we've been working on at Wikibon I want to test this assumption by we've talked a little bit about it is the idea of a data zone. Where just as we use a security zone as a concept where everything that's in that zone and it's both the technologies there's governmental there's other types of, has this seized security characteristics and if it's going to be part of that conglomeration it must have these security characteristics. And we're no thinking you could do the same thing with data. Where you start saying so for example we talked earlier about the idea that the network is what connects places together and that developers think in terms of the places things are like the internet of things. I'm wondering if it's time for us to think in terms of the network in time or the network is time and not think in terms of where something is but think in terms of when it is. And whether or not that's going to become a very powerful way of helping developers think about the role that the network's going to play is the data available now because I have an event that I have to support now and it seems as though that could be one of those things that snaps this group, these two communities together to think it's in time that you're trying to make things happen and the network has to be able to present things in time and you have to be cognisant of in time. It's one of the reasons for example why restful is not the only way to do things. >> Right exactly. >> IOT thinks in time what do you think about that? >> Yeah I think that's really interesting and actually that's something we're diving in with our community on is so you've been a developer you've worked with rest services and now you're doing IOT well you need to learn a lot of new protocols and how to do things more in real time and that's a skill set that some developers maybe don't have they're interested in learning so we're looking at how do we help people along that way. >> John: Well data in motion is a big topic. >> Exactly yeah absolutely. And so I think and then the network, thinking about from a network provider like I need this data here at this time is very interesting concept and that starts to speak to what can be done at the edge which is obviously like an interesting concept for us. >> But also the role the network's going to play in terms of predicatively anticipating where stuff is and when it needs to be there. >> Yeah yeah I think that's a really interesting space. >> But it's programmable if you think about what' Cisco's always been good at and most network and ops guys is they've been good at policy based stuff and they really they know what events are they have network events right things happen all the time. Network management software principles have always been grounded in software so now how do you take that to bridging against hat's why I see a convergence. >> Amanda: We should have a conference around that. >> It's called DevNet Create. Okay so final question for you as you guys have done this how's your team doing with the talks was one going on behind us is a birds of a feather IOT session you've got a hack-a-thon over here. Pretty cool by design that we heard yesterday that it's not 90% Cisco it's 90% community 10% Cisco so this is not a Cisco coming in and saying hey we're in cloud native get used to us we're here you know. >> Absolutely not so it's I'm really proud of how my team came together around that so I have our team of developer evangelists who we connect with the developer community and we really look at our job as this full circle of we get materials out and learning and get people excited about using Cisco APIs and we also bring information back about like here's what customers think about using it, here's what the community's doing all of that. So when we started DevNet Create we set the stake in the ground of we want this to be way more community content than our content we produce ourselves. And so the evangelists did a great job of reaching out into communities, connecting with speakers, finding the content that we wanted to highlight to this audience and bringing it in so that the talks have been fabulous, the workshops have been a huge hit it's like standing room only in there and people getting a seat and not wanting to leave because they want to keep their seat and so they'll stay for four workshops in a row you know it's been amazing. >> I think it's great it's exciting for me to watch 'cause I know the developer goodness is happening. People are donating soft we see Google donating a lot of open source even Amazon on the machine learning you guys have a lot of people that open source but I got to ask you know within Cisco and it's ecosystem of a company we see a lot or Cisco on our Cube events that we go to. We go to 100 events last year we've been to 150 this year. We saw Dehli and Ciro we saw some Cisco folks there. Sapphire there's a deal with Century Link and Honna Cloud, Enterprise Cloud so there's Cisco everywhere. There's relationships that Cisco has, how are you looking at taking DevNet Create or are you going to stay a little bit decoupled, be more startup like and kind of figure that scene out or is that on the radar yet? >> So I think we know with starting DevNet Create for this first year what we really want to do is get foundation out there, stake in the ground, get a community started and get this conversation started. And we're really looking to in the iterative experimental way look at what comes out of this year and where the community really wants to take it. So I think we'll be figuring that out. >> John: So see what grows out of it. It's a thousand flowers kind of thing. >> Yeah and I think that it will be, we will always have the intention of keeping that we want to keep the mix of audience of infrastructure and app and we'll see how that grows so... >> Well Amanda congratulations to you, Rick and Suzie and the teams. I'd like to get some of those experts on the Cube interviews as soon as possible. >> Absolutely! >> And some crowd chats. You guys did an amazing IOT crowd chat. I'll share that out to the hashtag. >> That was really fun. >> Very collaborative you guys are a lot of experts and Cisco's got a lot of experts in hiding behind the curtain there you're bringing them out in public here. >> That's right. >> Congratulations. >> Thank you very much. >> We're here live with special inaugural coverage of DevNet Create, Cisco's new event. Cloud native, open source, all about the community. Like The Cube we care about that and we'll bring you more live coverage after this short break. >> Hi I'm April Mitchell and I'm the Senior director of Strategy and Planning for Cisco.

>> Wait. Okay, We're back. Live here at Stanford University Alumni Center. What a great day. Stanford loved this place. A lot of brilliant minds here. And this is the Stanford Excel Seventeenth annual symposium called Excel Enterprise. That's the hashtag falls on Twitter here with Jeff Kelly. Silicon angles. Exclusive coverage is too cute. Our flagship program about the events extract the signal from the noise. And our next guest is Amanda Richardson, the head of product. That president. Welcome to the Cube. >> Thank you. Awesome. >> So really amazing event. I'LL see a lot of big minds here, and we're also live in San Francisco at the age of us somewhere all the developers air geeking out with Amazon and all the tools you the head of product President, tell us what is President. Tell us what you're doing here. >> So, President, a collaborative presentations will. So we look forward, Teo, helping our users create idea, share ideas and really have a platform for uh, putting. Their message is out there and better sharing with the audience is So we're here because we love excel. I'm here because I'm a GSP alum and any reason to get back to the farm is a good one, and we just think it's a great place to meet people piers and share ideas and hopefully learn from each other's mistakes. >> So what? You're the new business school president? >> So I got you a job before the new business school. It's pretty awesome, but I kind of want to go back. I was joking with my husband this morning. I think it may be time for a phD. >> Yeah, Sanford's Grace, but as the head of product, you can. You still get the geek out? >> Yeah, >> And look at also the market side. You gotta look into engineering also product. So in this whole enterprise two point Oh, thank you just never happened. It's still happening. It's like going and going. But now with cloud with mobile, it's all happening right? So I got that cloud mobile social thing going on. We've been covering. So knowing it's looking angle. What are you seeing now as the market drivers for those two forces cloud and mobile and social is all that coming together? >> Um, it is all coming together, and I think you know, we call it like the consumerism ation of enterprise. Right. So, um people have one phone, one device, one presence. I think five years ago you probably tried to keep your world separated between your enterprise, professional life and your personal life, and now it really all comes together. So you've gotta solve the problems for the enterprise users in the same way you solve problems for consumers, right? What are their big needs? What are their pain points? Where do they find value, focus on those areas and make it easy to use on DH? I think that's what's finally accelerating on bringing really cool, sexy problems to the enterprise users. You just bring a consumer approach. One >> of the biggest barriers that you see in that adopts House of consumer ization of consideration of the enterprise has been talked about for many, many years and finally was seeing a ray of hope. >> Yeah, wave and making the lives the end of the tunnel >> sunrise a face. So it's there, it's there. So one of the key drivers that are helping this go faster now versus years before Oh yes, next two years next year. >> Um so I think I think mobile is actually a great point, so you can't keep pieces like Evernote, Dropbox President out of your users hands. I mean, I remember being in meetings with manager meetings five, seven years ago, talking about how we're gonna ban Facebook, and that just seems quaint now because it's all in your phone and you can't tell people not to bring their phones to work. So I think Mobil's had a huge impact and getting more of these products and tools into the hands of the consumers and out of really this kind of big brother control type situation, Thie Other thing I think that's happening is just worlds are blending together and the availability of of tools on the Internet. It sounds silly to say, but, you know, you can remember five, ten years ago, you couldn't access your perhaps it's near p program. Or perhaps this even productivity tools from home. There was a time when we all had to remote in and yeah, I mean, I'm dating myself and showing why I color my hair. But it really is. You know, the world is changing, and I think, thank goodness for the Internet, thanking us for the Web and thank goodness for >> Mo. It's interesting you mention the dating yourselves first. You look fabulous, you know, you know world. I mean, I'm older, I know how old I am. And I just had the twenty seven year old kid on drop box. So you know, that's young. But, you know, it's a lot of senior folks now. This enterprise market is shifting from consumer. You seeing some of the leaders are those experienced managers because they've lived through the right client server that lived through the that first wave. So is that just because we're more, there's more people that know that market more amusing? You're seeing a lot more cos they're not not the twenty something. It's over thirty five over forty. >> Yeah, eso no comment on age. But Thea, I think what excites me about the space I can just talk about myself is you know, I have a consumer background. So it was super fun to be in consumer five ten years ago when you know Internet was taking off. He finally have a platform on which you have millions of users to test and learn and grow. And now that you can apply that to enterprise, I mean, I think it's new challenges but similar challenges. And I really think one of the more interesting things is that it's actually solving really compelling problems. One of the you know, um, I think there are a lot of opportunities out there around photo sharing and, um, Geo location and, you know, putting together your social graph. But you know, where I find passion and energy is actually providing value and solving problems and really being a key part of someone's someone's life, That's what gets me here. Hope that keeps others here. >> So let's talk about you're solving really interesting problem. What is the mean? What is your wife? What is president about? Why are you doing what you're doing? Is it simply, you know, we've talked. We hear a lot about the concerns around power point and right death by the PowerPoint slide and that kind of thing is that really, uh, the issue you've set out to overcome our tell us a little about what you do and why you do it. >> So, um, we certainly get compared to power point a lot, but where we, uh problem we really like to solve on on a more grand scale is that we believe ideas are best shared and best collaborated about. So if you think of ideas like jeans, they can come together. They can be built on each other. A great example of president uses. There is an organization in Syria rebel organization that used President to really be the platform to explain their ideas and what the issues really were in a quick, meaningful, impactful way. I think having a platform by which you can share ideas and better understand each other can apply Teo making the world a better place but can also apply Teo helping scientists share their information around the globe, building on ideas and I know even within president, we use the tool. Teo better communicate product road maps to engineering so that we can better align. I think it's all about communication. Helping ideas grow faster and helping the world to be a more understanding place. I mean, it's a little peace, love and happiness, but it it is why we get out of bed every morning. We really think because he's a great tool for people to be the platform for them to share their ideas. And >> so I'm actually president User. I've started using recently. Actually, I downloaded. You can see here about the kind of downloaded the desktop version, and I were working on the plane that was coming out here from Boston. But, you know, it's certainly a very interesting platform. It's very different from Power. Point certainly creates much, much more compelling type of way to present information. Uh, what are some of the design principles that's had a product? What are some of the things that you really kind of court your philosophy in terms of design, find it and and implementing our should say, creating the kind of user interface and the way people interact with information? >> Yes. So I'm really proud of President of the co founders have really doubled down, if you will, on our design effort. So we have a full time user research staff. We have a full time data research that we have a full time design staff, all three different roles, all three big teams. I'm really focused on understanding our users. So we saw for key user problems in terms of design principles, specifically that we focus on, we like to, uh, help users understand structure of their ideas. So one of the challenges of President. For those who come from a power point model is everything should be linear. And one of our principles is that not all ideas are linear. There may be areas where we consume into different pieces. So helping to communicate that that is particularly important for us and how to provide simple structure. Um, I think the other ideas, uh, helping to make it beautiful. We believe that words are better. What are? Excuse me? Pictures are better. Way to communicate in words. Um, you know, death by bullet point >> thing is a common affliction, >> eh? So how can you, uh, say something with a picture that would have taken a hundred words? And that's what we try to do. >> So you know what? Your problem is? Both kind of software service, but also down with stop version. Right? Mentioned. But you know what? The software service Mom, you're able, I assume, to collect data on the way people are using your product, right. How does kind of that type of information do you incorporate that into the design process and making changes to the product come to talk about how you used data analysis really >> product. Yeah. So, you know, I believe the role of product managers to understand the user intimately have a point of view on a strategy, but then early validate through data. So not to Pripyat. We do have data about your desktop PC, which is what >> I covered. Big data for what? You have no problem with that. >> So we focus a lot on one or user stew. Do what makes them successful way try toe. Have measurable outcomes for all of our initiatives, whether its user behavior or defining what a good presidents are really helping users to solve their problems. We use data tio, on the small level, optimized and on a big level really define an objective and a goal. So how can we really push things through the funnel to get to the user to their success point, which we measure is giving a presentation. >> So both find ten of tactical issues, but also a kind of inform your larger >> are big company KP eyes. They're all based on data. >> Okay, thanks for coming on The tears. We gotta break that. Their next guest coming in lining up all of the crowd's breaking up the Silicon Angles Exclusive coverage of Stanford Excel seventeen Annual symposium. Hashtag Excel Enterprise Where it sells Doing a lot of great enterprises is Cuba's looking angles. Coverage of Stanford Excel Symposium right back with our next guest after this short break.

(bright upbeat music) >> We're back at the Red Hat Summit at the Seaport in Boston, theCUBE's coverage. This is day two. Dave Vellante and Paul Gillin. Chris Wright is here, the chief technology officer at Red Hat. Chris, welcome back to theCUBE. Good to see you. >> Yeah, likewise. Thanks for having me. >> You're very welcome. So, you were saying today in your keynote. We got a lot of ground to cover here, Chris. You were saying that, you know, software, Andreessen's software is eating the world. Software ate the world, is what you said. And now we have to think about AI. AI is eating the world. What does that mean? What's the implication for customers and developers? >> Well, a lot of implications. I mean, to start with, just acknowledging that software isn't this future dream. It is the reality of how businesses run today. It's an important part of understanding what you need to invest in to make yourself successful, essentially, as a software company, where all companies are building technology to differentiate themselves. Take that, all that discipline, everything we've learned in that context, bring in AI. So, we have a whole new set of skills to learn, tools to create and discipline processes to build around delivering data-driven value into the company, just the way we've built software value into companies. >> I'm going to cut right to the chase because I would say data is eating software. Data and AI, to me, are like, you know, kissing cousins. So here's what I want to ask you as a technologist. So we have the application development stack, if you will. And it's separate from the data and analytics stack. All we talk about is injecting AI into applications, making them data-driven. You just used that term. But they're totally two totally separate stacks, organizationally and technically. Are those worlds coming together? Do they have to come together in order for the AI vision to be real? >> Absolutely, so, totally agree with you on the data piece. It's inextricably linked to AI and analytics and all of the, kind of, machine learning that goes on in creating intelligence for applications. The application connection to a machine learning model is fundamental. So, you got to think about not just the software developer or the data scientist, but also there's a line of business in there that's saying, "Here's the business outcomes I'm looking for." It's that trifecta that has to come together to make advancements and really make change in the business. So, you know, some of the folks we had on stage today were talking about exactly that. Which is, how do you bring together those three different roles? And there's technology that can help bridge gaps. So, we look at what we call intelligent applications. Embed intelligence into the application. That means you surface a machine learning model with APIs to make it accessible into applications, so that developers can query a machine learning model. You need to do that with some discipline and rigor around, you know, what does it mean to develop this thing and life cycle it and integrate it into this bigger picture. >> So the technology is capable of coming together. You know, Amanda Purnell is coming on next. >> Oh, great. >> 'Cause she was talking about, you know, getting, you know, insights in the hands of nurses and they're not coders. >> That's right. >> But they need data. But I feel like it's, well, I feel very strongly that it's an organizational challenge, more so. I think you're confirming. It's not really a technical challenge. I can insert a column into the application development stack and bring TensorFlow in or AI or data, whatever it is. It's not a technical issue. Is that fair? >> Well, there are some technical challenges. So, for example, data scientists. Kind of a scarce kind of skillset within any business. So, how do you scale data scientists into the developer population? Which will be a large population within an organization. So, there's tools that we can use to bring those worlds together. So, you know, it's not just TensorFlow but it's the entire workflow and platform of how you share the data, the data training models and then just deploying models into a runtime production environment. That looks similar to software development processes but it's slightly different. So, that's where a common platform can help bridge the gaps between that developer world and the data science world. >> Where is Red Hat's position in this evolving AI stack? I mean, you're not into developing tool sets like TensorFlow, right? >> Yeah, that's right. If you think about a lot of what we do, it's aggregate content together, bring a distribution of tools, giving flexibility to the user. Whether that's a developer, a system administrator, or a data scientist. So our role here is, one, make sure we work with our hardware partners to create accelerated environments for AI. So, that's sort of an enablement thing. The other is bring together those disparate tools into a workflow and give a platform that enables data scientists to choose which, is it PyTorch, is it TensorFlow? What's the best tool for you? And assemble that tool into your workflow and then proceed training, doing inference, and, you know, tuning and lather, rinse, repeat. >> So, to make your platform then, as receptive as possible, right? You're not trying to pick winners in what languages to work with or what frameworks? >> Yeah, that's right. I mean, picking winners is difficult. The world changes so rapidly. So we make big bets on key areas and certainly TensorFlow would be a great example. A lot of community attraction there. But our goal isn't to say that's the one tool that everybody should use. It's just one of the many tools in your toolbox. >> There are risks of not pursuing this, from an organization's perspective. A customer, they kind of get complacent and, you know, they could get disrupted, but there's also an industry risk. If the industry can't deliver this capability, what are the implications if the industry doesn't step up? I believe the industry will, just 'cause it always does. But what about customer complacency? We certainly saw that a lot with digital transformation and COVID sort of forced us to march to digital. What should we be thinking about of the implications of not leaning in? >> Well, I think that the disruption piece is key because there's always that spectrum of businesses. Some are more leaning in, invested in the future. Some are more laggards and kind of wait and see. Those leaning in tend to be separating themselves, wheat from the chaff. So, that's an important way to look at it. Also, if you think about it, many data science experiments fail within businesses. I think part of that is not having the rigor and discipline around connecting, not just the tools and data scientists together, but also looking at what business outcomes are you trying to drive? If you don't bring those things together then it sort of can be too academic and the business doesn't see the value. And so there's also the question of transparency. How do you understand why is a model predicting you should take a certain action or do a certain thing? As an industry, I think we need to focus on bringing tools together, bringing data together, and building better transparency into how models work. >> There's also a lot of activity around governance right now, AI governance. Particularly removing bias from ML models. Is that something that you are guiding your customers on? Or, how important do you feel this is at this point of AI's development? >> It's really important. I mean, the challenge is finding it and understanding, you know, we bring data that maybe already carrying a bias into a training process and building a model around that. How do you understand what the bias is in that model? There's a lot of open questions there and academic research to try to understand how you can ferret out, you know, essentially biased data and make it less biased or unbiased. Our role is really just bringing the toolset together so that you have the ability to do that as a business. So, we're not necessarily building the next machine learning algorithm or models or ways of building transparency into models, as much as building the platform and bringing the tools together that can give you that for your own organization. >> So, it brings up the question of architectures. I've been sort of a casual or even active observer of data architectures over the last, whatever, 15 years. They've been really centralized. Our data teams are highly specialized. You mentioned data scientists, but there's data engineers and there's data analysts and very hyper specialized roles that don't really scale that well. So there seems to be a move, talk about edge. We're going to talk about edge. The ultimate edge, which is space, very cool. But data is distributed by its very nature. We have this tendency to try to force it into this, you know, monolithic system. And I know that's a pejorative, but for good reason. So I feel like there's this push in organizations to enable scale, to decentralize data architectures. Okay, great. And put data in the hands of those business owners that you talked about earlier. The domain experts that have business context. Two things, two problems that brings up, is you need infrastructure that's self-service, in that instance. And you need, to your point, automated and computational governance. Those are real challenges. What do you see in terms of the trends to decentralize data architectures? Is it even feasible that everybody wants a single version of the truth, centralized data team, right? And they seem to be at odds. >> Yeah, well I think we're coming from a history informed by centralization. That's what we understand. That's what we kind of gravitate towards, but the reality, as you put it, the world's just distributed. So, what we can do is look at federation. So, it's not necessarily centralization but create connections between data sources which requires some policy and governance. Like, who gets access to what? And also think about those domain experts maybe being the primary source of surfacing a model that you don't necessarily have to know how it was trained or what the internals are. You're using it more to query it as a, you know, the domain expert produces this model, you're in a different part of the organization just leveraging some work that somebody else has done. Which is how we build software, reusable components in software. So, you know, I think building that mindset into data and the whole process of creating value from data is going to be a really critical part of how we roll forward. >> So, there are two things in your keynote. One, that I was kind of in awe of. You wanted to be an astronaut when you were a kid. You know, I mean, I watched the moon landing and I was like, "I'm never going up into space." So, I'm in awe of that. >> Oh, I got the space helmet picture and all that. >> That's awesome, really, you know, hat's off to you. The other one really pissed me off, which was that you're a better skier 'cause you got some device in your boot. >> Oh, it's amazing. >> And the reason it angered me is 'cause I feel like it's the mathematicians taking over baseball, you know. Now, you're saying, you're a better skier because of that. But those are two great edge examples and there's a billion of them, right? So, talk about your edge strategy. Kind of, your passion there, how you see that all evolving. >> Well, first of all, we see the edge as a fundamental part of the future of computing. So in that centralization, decentralization pendulum swing, we're definitely on the path towards distributed computing and that is edge and that's because of data. And also because of the compute capabilities that we have in hardware. Hardware gets more capable, lower power, can bring certain types of accelerators into the mix. And you really create this world where what's happening in a virtual context and what's happening in a physical context can come together through this distributed computing system. Our view is, that's hybrid. That's what we've been working on for years. Just the difference was maybe, originally it was focused on data center, cloud, multi-cloud and now we're just extending that view out to the edge and you need the same kind of consistency for development, for operations, in the edge that you do in that hybrid world. So that's really where we're placing our focus and then it gets into all the different use cases. And you know, really, that's the fun part. >> I'd like to shift gears a little bit 'cause another remarkable statistic you cited during your keynote was, it was a Forrester study that said 99% of all applications now have open source in them. What are the implications of that for those who are building applications? In terms of license compliance and more importantly, I think, confidence in the code that they're borrowing from open source projects. >> Well, I think, first and foremost, it says open source has won. We see that that was audited code bases which means there's mission critical code bases. We see that it's pervasive, it's absolutely everywhere. And that means developers are pulling dependencies into their applications based on all of the genius that's happening in open source communities. Which I think we should celebrate. Right after we're finished celebrating we got to look at what are the implications, right? And that shows up as, are there security vulnerabilities that become ubiquitous because we're using similar dependencies? What is your process for vetting code that you bring into your organization and push into production? You know that process for the code you author, what about your dependencies? And I think that's an important part of understanding and certainly there are some license implications. What are you required to do when you use that code? You've been given that code on a license from the open source community, are you compliant with that license? Some of those are reasonably well understood. Some of those are, you know, newer to the enterprise. So I think we have to look at this holistically and really help enterprises build safe application code that goes into production and runs their business. >> We saw Intel up in the keynotes today. We heard from Nvidia, both companies are coming on. We know you've done a lot of work with ARM over the years. I think Graviton was one of the announcements this week. So, love to see that. I want to run something by you as a technologist. The premise is, you know, we used to live in this CPU centric world. We marched to the cadence of Moore's Law and now we're seeing the combinatorial factors of CPU, GPU, NPU, accelerators and other supporting components. With IO and controllers and NICs all adding up. It seems like we're shifting from a processor centric world to a connect centric world on the hardware side. That first of all, do you buy that premise? And does hardware matter anymore with all the cloud? >> Hardware totally matters. I mean the cloud tried to convince us that hardware doesn't matter and it actually failed. And the reason I say that is because if you go to a cloud, you'll find 100s of different instance types that are all reflections of different types of assemblies of hardware. Faster IO, better storage, certain sizes of memory. All of that is a reflection of, applications need certain types of environments for acceleration, for performance, to do their job. Now I do think there's an element of, we're decomposing compute into all of these different sort of accelerators and the only way to bring that back together is connectivity through the network. But there's also SOCs when you get to the edge where you can integrate the entire system onto a pretty small device. I think the important part here is, we're leveraging hardware to do interesting work on behalf of applications that makes hardware exciting. And as an operating system geek, I couldn't be more thrilled, because that's what we do. We enable hardware, we get down into the bits and bytes and poke registers and bring things to life. There's a lot happening in the hardware world and applications can't always follow it directly. They need that level of indirection through a software abstraction and that's really what we're bringing to life here. >> We've seen now hardware specific AI, you know, AI chips and AI SOCs emerge. How do you make decisions about what you're going to support or do you try to support all of them? >> Well, we definitely have a breadth view of support and we're also just driven by customer demand. Where our customers are interested we work closely with our partners. We understand what their roadmaps are. We plan together ahead of time and we know where they're making investments and we work with our customers. What are the best chips that support their business needs and we focus there first but it ends up being a pretty broad list of hardware that we support. >> I could pick your brain for an hour. We didn't even get into super cloud, Chris. But, thanks so much for coming on theCUBE. It's great to have you. >> Absolutely, thanks for having me. >> All right. Thank you for watching. Keep it right there. Paul Gillin, Dave Vellante, theCUBE's live coverage of Red Hat Summit 2022 from Boston. We'll be right back. (mellow music)

>>Well, hi everybody, John Walls here on the cube. And thank you for joining us here for this cube conversation today. And we're talking about data. Of course, it's a blessing and the respect that it's become such a valuable asset. So many companies around the world, it's also a curse, obviously, because it is certainly can be vulnerable. It is under attack and Druva is all about protecting your data and preventing those attacks. And with us to talk about that a little bit more in depth as Jaspreet Singh, who is the founder and CEO at Druva and Steven Manley, who was the company's CTO. Gentlemen, thanks for being with us here on the queue. Good to see you. >>Thank you. Thank you, John. >>So Jaspreet, let me just begin with you. Let's, let's talk about the larger picture of data these days. And, and we read, it seems as though every day about some kind of invasion, you know, where some ransomware attack it's become all too commonplace. So if you wouldn't maybe just set the stage a little bit for the state of ransomware here in 2021. >>That's right. John, I think Lansing has now a new national security threat and at the scene, uh, all around us, this, uh, almost every single day, we hear about businesses getting hit with a, a new ransomware attack, uh, ransomware 1.0 was more a malware situation impacting our data. And as you know, the pandemic transformed the entire data landscape, like the application, the terror, the entire supply chain delivery model as to be more online, more connected, which, you know, for this mortar stores, this whole approach towards a malware coming in, we're also seeing ransomware 2.0, it is all about like insider techs or, or, or in general security misconfiguration, which could lead to data being exfiltrated or traded off in the market. So in general, as data is far more connected, far more expected to be online security techs from either malware or human oriented security issues are becoming more and more dominant threat to, to our, our entire data landscape. Right? >>Yeah. So, so Steven, if you would, I'd like you to just to follow up on this, this, uh, uh, will the landscape to take one of Jaspreet's terms here about what you're seeing in terms of, of kind of these evolving threats now, um, used to be probably, I don't know, five, six years ago, it was a very different, uh, set of problems and challenges and companies maybe weren't as laser focused as they are now. Um, maybe take us through that, that process, what has happened with regard to the client base that you see and you're working with in terms of their recognition and other steps that they need to take going forward as they modernize their operations? >>Yeah. You know, I th I think there's, there's two things we see from, uh, from sort of a technical perspective. The first one is in just pre-call that ransomware 1.0, ransomware 1.0, uh, is mainstream at this point, you know, so, so you, you can go out there and you don't have to be an expert hacker there's ransomware as a service. You know, your average, your average teenager can basically download a ransomware attack kit, uh, you know, get, get a pretty lightweight cloud account and attack school districts, hospitals, municipal organizations, whatever it is, you know, with what we would consider the traditional ransomware and, and that's become ubiquitous. And that's why we see all these reports of, there are multiple ransomware attacks every minute, you know, in the United States and around the world. So, so that's, that's, that's one part which is you're going to get hit. >>Now you'll probably get heading in with the more traditional ransomware, but, you know, like any industry, the ransomware people have evolved. And so it's as just breed said, they are constantly innovating. And so what we're seeing now from, uh, from sort of a marketplace standpoint is, you know, getting smarter about the ransomware attack. So, so laying low, longer, uh, you know, sort of corrupting or attacking data a little bit more slowly. So it's harder to detect specifically attacking backup infrastructure so that you won't be able to recover exfiltrating data. So that, so that now you can have sort of two types of threats, one that your data is encrypted, and the other is if you don't pay us, we're just going to post it on the internet. So, so you've got stage one, which is ubiquitous, and you've got to protect yourself against that because anyone can be attacked at any time. And then you've got stage two where it's getting smarter and that's where organizations then have to step up their game and say, I've got to keep my backup safer. Uh, I've got to be able to detect things a little bit more easily, and I need to start really understanding my data footprint. So I understand what can be exfiltrated and what that's going to mean to me as a business. >>So, Jess, um, to that point, that Steven was just talking about how the organizations need to get smarter in terms of your communications that you're having with the folks in the C-suite, um, is that point, is that you, if they readily identified today, I mean, are, do they get it, um, are the, is the communication going out to their stakeholders, are the business priorities being aligned appropriately? I mean, what, what are organizations and specifically on that executive level, what are they doing right now? Um, in terms of, of preparation in terms of protections that, that, uh, again, are so necessary, I would think. >>Yeah, absolutely. So I think we do see customers truly making strides to solving the problem. There's not a one facet that, you know, one solution fits all problem either, right? So there's, there's, there's, there's a whole productive nature of preventing ransomware detection and response. There's a readiness aspect of it, but what happens when you do get here now that recovery element to it, how do I recover in time in shape from a attack like this, the customers are evolving. They're understanding at the same time, they actually deploying appropriate technologies to, to put all the three aspects of solving the solution. What does Stickney like any of the security challenge? This is, uh, you know, there's not a one application solve all problems. Typically the OLAP and controls built by a multiple group and multiple parties to make sure you're ready to response towards a tech like this. >>And just to jump in, because one of the things I find fascinating as we go through this, the customer conversations I have, I've I've been doing, you know, sort of data protection for a long time. We won't get into that, but, but most of my time I'd spent talking to, you know, VPs of it. Maybe I'd see a CIO. It's fascinating. Now we will have conversations with boards of directors because it becomes such a big issue. And the focus is, is, is so different, right? Because they understand that this isn't just like a usual backup and recovery, or even the traditional disaster recovery that you might do from a natural disaster or some sort of hardware outage. They're seeing that there are so many stages now to an orchestrator recovery. These customers we work with where it's, it's, it's not just about, I need a little bit to technology. They're really looking for how do I operationalize all of this? You know, because once you're up at the board of directors, this is no longer a which product is better than X, Y, or Z. It's a discussion about who can really insulate me from the risk, because these, these can be business sending events. If you're not careful, >>Right? I mean, you're ready. This is a great point. And actually, Steven, I hadn't really thought about these fiduciary responsibilities that boards have. And obviously we think about operations. We think about PNL, right? We think about all, but I hadn't really thought about how also data protection. And I want to talk about data resiliency, how those come into play, as well as those board decisions are made. So let's talk about resiliency. I want you guys to explain this concept to me. Um, so the, you know, what, what's the distinction between protection and resiliency because to me, they're, they're maybe not exactly synonymous, but they're kind of cousins in some respects. So a Jaspreet, if you will talk about resiliency and how you define that. >>Sure. So I just see what I mentioned, right? The prediction was more about how do I actually save guard my data to actually, you know, recover from an incident right there, didn't say residency is all about being ready to respond in time, right? The forward-leaning pusher of making sure, you know, am I ready to not just recover from a very, uh, you know, age, old problem of application failure or, or human errors, but also a cyber attack or a, you know, a true age incident or a cyber recovery or security incident, which I'm prepared to respond in a appropriate SLA across the board. Right. Uh, and resiliency also goes beyond, you know, just the nature of data itself, right? You're, you're talking about applications, environments ecosystem to truly understand that the enterprise operation needs it. Data needs to be holistic. We talked through how do I get my business online, faster. Right. And that's the two nature of differentiation between, uh, protection going towards resiliency. >>And then as obviously driving a lot of your product development. Right. And, and, and I know you've got the data resilience, resiliency, cloud, um, service that you're offering now. So Steven blitz blitz, let's dive into that a little bit. Um, what was the Genesis of that offering and, and what do you see as its primary advantages to your clients? >>Yeah, so, so I think, I think there's, there's really those, those tier two key words there it's resiliency and it's cloud. So just brief, kind of walked about how your resiliency is that step forward. It's that shift left, whatever term you want to use. To me, the best part about the cloud is, and like I said, I've been doing this for a long time and I've yet to meet a customer. Who's come to me and said, I really wish I could spend more money and more time on my data protection infrastructure. I love sticking together, multiple separate products. It's just a great use of my time. Right? Nobody says that what they really say is, could you just solve this problem for me? This is, this is hard capacity planning and patching and upgrades and tying together all the different components from up to seven different vendors. >>This is hard work. And I just need this to work. I need this to work seamlessly. And so we, we, we looked at that cloud part and we said, well, when you think of cloud, you think of something that's flexible. You think of something that's on demand. You think of something that does the job for you. And so, you know, when we talk about this data resiliency cloud, it's about, you know, moving onto your front foot, getting aggressive, being ready for what's coming, but having, you know, frankly, Druva do it for you as opposed to saying here's some technology, good luck. You know, Mr. And Mrs. Customer, you know, we've got this solved for you, it's our job to take care of it. >>And to add to it, you know, this entire resiliency question cannot be solved to a simple, a software is approach is a fundamental belief because the same network, the same principles of operation, the same people involved, you know, what, what those are involved around the primary application that the resiliency aspect has to be air gap appropriately, not just at the data level, but ID and operations limit as well. Right? So a notion of a cloud, almost a social distancing for your data, right? And you're in your ego to the enterprise that, Hey, if anything happens to my primary network application stack data, my second Bree cloud, my redundancy cloud is ready to respond inappropriate, define SNDs to recover my Buddhist business holistically as a combination of integrating with SecOps as a combination of truly integrating disaster recovery elements with cyber recovery elements, truly understanding application recovery from a backup and recovery point of view. So holistically understanding the notion of resiliency and simplifying it to the elements of public cloud. Yes, sir. >>How do you bend that for your clients? Because as you both pointed out, they have different needs, right? And they have, they have different obviously different that they're involved in different sectors of different operations with different priorities and all that. How is the data resiliency cloud, uh, providing them with the kind of flexibility and aid, the kind of adaptability that you need in order to conform it for what you need and not necessarily, you know, what someone else in another sector is, is all about. >>So, so for me, there's a couple of things that, that is great about, about being the data resiliency cloud. One is that we've got well over 3,500 customers, which means that no matter what segment you're looking in, you're not going to be alone, right? If you're, if you're healthcare, if you're finance, if you're a manufacturing, Druva, Druva understands, you know, what you, and many of, of your similar sort of companies look like, which enables us to work in a lot of ways and enables us to understand what trends are happening across your industry, whether it's, you know, ransomware attacks that are coming across, you know, say manufacturing space and how those look or what data growth looks like, or what type of applications are important in those industries. So it's, it's really useful for us to be able to say, we understand these different verticals because we've got such a broad customer base. >>I think the second thing that comes in then is every customer. I meet the number one question they asked me, and Amanda might not be the first one, but it's the one they want to ask. It's always, how am I doing compared to everybody else? And so it's really useful to, to be able to sit down and say, look in your industry. This is what we see as the standards right now. So this is where you fall. You're sort of maybe a stage two, everybody else's at stage three will help you move forward. You, our industry as a whole is actually ahead of many of the other industries, but this is what's coming next for it for others. And so it's really useful for those customers to understand where they sit in respect to, to sort of the broader marketplace. And so that's one of the values I think we bring is that we do have such a broad understanding of our customers because we are a service as opposed to just selling software. >>Yeah. And those customers too, um, as you've talked about, they're looking maybe at their, their, their competitive landscape and trying to decide, okay, are we keeping up with the Joneses, so to speak? Um, but all of you, all of us, we're all trying to, we're trying to keep up with the bad guys. And so in terms of that going forward, what does that challenge for you at Druva in terms of being anticipatory in terms of trying to recognize, uh, their trends and their movements and, and therefore we're thinking so that you can be that, that great, uh, protective mechanism, you can be that prophylactic measure that stands between a company and something bad from happening. >>So I I'll start. And then, uh, it's funny cause, uh, you know, just breed and I had just this morning, we were actually talking about some of the future of ransomware protection and one of the things that we are using a lot in driven, and I get every company says they're doing it is the use of AIML, especially in detecting, uh, sort of unusual trends. Um, but, but you know, but I think we're different than most because the AIML we use is again, across, you know, two and a half billion backups every year, right? Because we, we get, we get visibility across everybody. So it's not just isolated, but we're looking at things like, you know, unusual access patterns in the data and usual access patterns based on administrators, because like Jaspreet said, said at the beginning, one of the things we see the ransomware attackers doing is they're trying to get entire control of your environment because if I control your environment, if I control your phone system, your email, I can get control of your backup application and delete everything. >>So we're even doing things to sort of prevent, oh, you know, we were getting unusual administrative access patterns. Let's stop that. We're getting unusual recovery patterns. Maybe that's somebody trying to steal data out. Let's track that. So our use of AIML is across a much broader data set than anybody else. And it's looking at a lot more than just, you know, sort of data, data pattern changes took to a much broader set of things. And, and basically, again, it's, it's sort of a, a bi-weekly meeting we have where Jaspreet comes in with more ideas that basically for our, for, for our team to start to go, what else can we do? Because the landscape keeps changing. >>And on top of it, I think also if you think about data protection or even data storage was never designed from a security point of view, it was always designed from a point of view of recoverability of data tool. Application issues are basically not corruption, but security or the thinking help us also fundamentally understand how do we think about elements of zero trust all around the platform and how do you make sure to what Steven mentioned, if your IDP gets compromised, if you do have a bad actor, enter a data protection solution, make us, how do you still make sure levels of automatization immutability like multiple levels of control that it plays to make sure no bad actor take construct control and true recoverability resiliency is possible across a variety of scenarios and Trudy customer driven SLA. So both foundationally, uh, we've, we've truly built something which is now, uh, it's very deep in and focused on security. The same time as Steven mentioned to understanding of customer landscape really helps us understand bad actors thought more, better, and more faster than many of our, uh, in the industry competition. >>Well, the need is great. That's for sure. And gentlemen, I want to thank you for the time today to talk about, uh, what Druva is doing and wish you continued success down the road. Thanks to you both. >>Thank >>You. All right. We've been talking about data, keeping it safe, keeping your data safe. That's what Druva is all about. And I'm John Walls and you've been watching the cube.

>>Hello, welcome to the cubes coverage of Boomi's out of this world. I'm John for your host of the cube at two great guests here, Chris port, chief operating officer of Boomi and Mandy deli wall. Who's the chief marketing officer of Boomi, Chris Mandy. Great to see you. Thanks for coming on the cube. Appreciate it. >>Thank you for having us. >>This segment is really about the Boomi, uh, trend and customers, um, and the success you guys had obviously now on a new trajectory go to the next level. And you got a lot of trajectory and success. Chris, as the chief operating officer, we've talked many times about the customer base, uh, and growing poised perfectly for this next wave. Give us the update on the macro trends around your customer base and how Boomi's helping them and how you're, you're getting your growth. >>Absolutely. And John really look forward to seeing you soon later, yo, again, this is a great moment in time. We're now more than 18,000 customers, 800 partners globally. We've actually seen an acceleration of the business through the pandemic. Obviously people are trying to do more with less. So it's just an amazing time to see what our customers are doing. Obviously, an explosion of SAS applications. And when we started thinking about, you know, explosion of endpoints, explosion of data, and now you compound that with a labor sheet, which you know, I know if anyone's looking at movies hiring more than we've ever hired in our life. And obviously we're all seeing this in space. So now basically a high productivity, high time to value tool set like Boomi is an imperative. It's no longer a luxury. And we're seeing that accelerate where our customers you've heard Chris talking about 189,000 unique importance that we now connect to. That's the power of movie. You do that in minutes and that's happening every single day. So again, just extending our footprint, extending our customer, really taking advantage. We're seeing there are real tailwind for the business right now. So really excited. Are you excited to work with, >>You know, Chris, uh, Dave Volante, we're talking about, you know, how do you tell the next big breakout success is rogue usage, shadow it. When you have rogue users, that means there's some innovation happening and you guys have a lot of customers that are hiring because it's all new, it's all new innovation, Mandy. This is kind of like a marketing opportunity. It's like rogue is not a bad word here. There's new functionality. You guys are showing the market that you go with Boomi, you can get more value. And then new things just emerge. New positions, open up value is being created. It's kind of a sign of value. Not, not a negative. It's a positive. >>Yeah, absolutely. We give our customers innovate. They're looking to modernize, transform new business models, right? The world we live in today. And so there's really your choice. We abstract away that complexity. So our platform gives people the ability to go build quickly. And so that's really the thought leadership. >>You know, I love, I love Andy Jassy former CEO of AWS. Now the CEO of Amazon always said, uh, Chris, you know, you know, he's no compression algorithm for experience. And he always talked about Amazon being misunderstood. And then finally people go, oh my God, that's the flow. That's the formula of success. And then they're late to the game. A lot of similarities in the Boomi culture, uh, with his law under undifferentiated, heavy lifting, you guys take away and create net new opportunities. This is an operational opportunity for customers. What's your quick comment on that? >>I love the quote again, 26 billion minutes of working with our customers directly. That's a perfect way to put it. I mean, it's not, it's a mode. There's no substitute for that. Trying to bring that to bear every day. And again would just the imperative of being agile speed, time to value. I mean, Forrester did a study recently, you know, Boomi 65% faster in terms of building integration, manual coding, and more importantly, legacy middleware. And these are now just embarrass. They're not luxuries anymore. So again, you know, when we take the, you know, we bring the bear that 26 billion minutes, everything we do from a successful or which is now double more than double from a footprint, you know, over the last 12 to 18 months. And again, trying to build more and more people into that organization, but cumulating success, successes that part of our DNA. I mean, you know, the thousand plus people across the globe, it's what we think about every single day is how to make customers successful. And again, to your point, there's, there is no substitute for the experience of, >>You know, um, we've been covering Boomi for a long time, Mandy, you know that, and, and we kind of got the picture right away. And you mentioned Chris, some of those KPIs, those are real value points that you look to, but ultimately you guys are, have been successful. And I think one of the tell signs is customer customer value always have great customers. So customer success, this is a pass term SAS term. I I-PASS term is part of the, of the cloud. You have to have customer sets built in from the beginning. You guys always had that as part of your culture, customer success, organizations and operations. What's the update, Chris with customer it's customer success. >>Yeah. Again, I mean, you know, more than doubling the team over the last 18 months in building this even more into the DNA of Boomi overall, we've completely overhauled what we think is a world-class onboarding experience for both our new customers, as well as our existing customers. John, you brought it up, you know, call it road, call it whatever. I mean, we're existing customers every day when you give them the best onboarding experience too, so that they can accelerate their journey, which kind of gets into the Boomi person, our whole community, which when we were together last time, face to face, you wouldn't be seen. We weren't just two years ago, we're now over a hundred thousand members and part of our community growing every single day, incredibly excited about that because that brings the knowledge base to all of their experience. And again, it really brings what customers really want to interact in a digital way and the Boomi versus so, so much significantly the number of knowledge base articles, the number of marketplace type vehicles that our cohorts construct talking to each other about what they're doing is so much more than comms. >>We didn't do this year, but again, you know, the Boomi versus so vibrant now it's kind of a force multiplier for more importantly, how our customers are learning from each other. Yeah. And just to tag onto that, John, over 38% of our customers are publicly. There's a movement here, industry, average of averages are high. So the platform really sells itself and customers nowadays, we're very grateful for that. >>I think you guys are a great example of product market fit and go to market fit. As people look at these metrics, you gotta nail customer success, which from day one, you gotta have the usage metrics. You've gotta have the integration. Now you've got hyper automation. And as you start getting the ecosystem, Mandy, you've got a branding opportunity here. You got, you have, uh, ecosystem, which is another tale sign of success. When you start having that word of mouth. I remember when shadow, it was kind of like poo-pooed, but that was the road behaviors became the cloud. You starting to see you guys see this ecosystem, you've kind of crossed the chasm, create opportunity for your brand. What's your reaction. >>Yeah, absolutely. And we haven't done any brand work yet. Right? That's common. So, you know, we're just getting started. >>Okay. So I have to ask what this viral thing going on. That's going to go, boom, go Boomi it. So a lot of kind of double entendres there, it and boom, you know, everyone knows that icon on their text. Boom. You know, it's good. Things are booming. What's going on? He was the update go, boom. It Boomi is, >>Yeah. So it's go movie. And this was something that our customers brought to us during the pandemic. We didn't have much opportunity. Honestly, we were all sitting behind our computer screens. So we decided that we were going to start to hold wine conversations with customers, just to check in, see how they're doing, see how we can help and get them together to share a story of how they're handling disruptions to the business. So over the course of several months, talking to customers globally, I started to hear people say, well, I told my so-and-so because it'll get done. If you have a problem, doesn't matter what it is. And all of a sudden they crystallized for me like, you know what, this is a movement. And so this wasn't something the marketing team dropped up. This is something we heard from our and have taken it to market. Now our team members talk about it or customers are talking about it. And really, again, it's a Testament to the pervasiveness and capability platform. You start with the connect, but you're able to grow with us as your business changes and opportunities advisement. >>Well, you know, that's a really good indicator of, uh, net, net, net promoter score kind of vibe when people are giving you your marketing slogans, uh, from happy customers. So a really great congratulations to the whole team there. Can you give us some specific examples since you mentioned referenceable customers of customer examples and take me through some of the highlights in your opinion, that kind of show where this is going in terms of customer use case and value. >>Yeah. And I'll start with one that's very near and dear and obviously very relevant, right? There's there's been some press on Moderna here recently. Um, you know, they were in the race to find a cure for COVID-19. They were looking to bring on new employees and they couldn't bring them on onboard these people. So they leveraged the technology to do an integrated, uh, pursuit of driving customers onto their own to their employee platforms. So we ripped, it celebrated their onboarding cut that time in half. So they could actually start working on what matters. So then undifferentiated heavy lifting around the administrative tasks associated with getting my social security number, as well as other aspects that we all have joining a company that's automated, you can get to work faster. So that really helped improve drug development time and make a real difference in terms of getting the vaccine to market. >>So that's a net that's one tangible example, second example, customer of ours, uh, drink customer with net suite. They had to find different routes to market, right? And so they went direct to consumer. So they expanded their business through a global pandemic by leveraging Boomi technology and integrating commerce with their financial systems to be able to get to customers directly and also manage their Omni channel in a, in a new way. So again, innovator die. Right? Great. When you have another customer in India, that's a government, small country, citizens had to go in in-person together for their health ID cards. Well, offices are closed. Nobody's allowed to go be in person anymore. Within one week, they digitally transform. So they can disseminate healthcare cards in a critical time in a global pandemic to their citizens and have them get healthier. So three tangible examples of how we just in the last 18 months have been able to help these customers. >>So Chris, you guys have been operating a great business. Okay. Now you're on your own. You're independent. You got some great financing partners behind you, independent company, great trajectory building on that. A lot of economies of scale, you guys have built into it. Mandy, you've got great customers. Where's the next journey for you guys, take us through the operational growth strategy, uh, for Boomi. >>Well look, I mean, obviously we're on a hiring screen or hiring than we've ever done, and that's pervasive across the entire business, real focus on product engineering, who our go-to market, but we're also, you know, when you heard Chris, we're really redefining I-PASS. I mean, when I think about what I'm most excited about, it's a few things a we're violently aligned from kind of call it the chairman of the board to the newest team member. You know, we know what the opportunity is. We're all aligned, but as importantly, it's what we're doing from a product perspective. You know, when you've heard about intelligent connectivity, you've heard about automating connectivity, what we're doing from a discover perspective, EDA, everything we're doing in the marketplace, really accelerating what the adoption opportunities are for movie across the whole Boomi verse and across all of those new customers that we're acquiring and then ultimately seeing what they do. I mean, again, I, I, I love what Mandy says. I mean, it literally always, I feel so strongly about this within every single company in the world. I mean, it literally should be, no movie is because the opportunities are expansive and endless in terms of what we can do together. And that's what I'm excited about is really kind of unleashing this company on the world, see what we can do next. It was, we really think about this next iteration, >>Mandy, real quick to you, uh, when people say go Boomi it, when your customers say that, what does it mean to them? Why are they saying it? Take us through some of the psychology and some of the implications of, and the meaning of the word go Boomi from a customer perspective. >>Yeah. Great question. I think it's, first of all, it's a Testament of the trust, right? It's just going to work, right? So go get it done. It'll be fast. It'll be easy. It is not complex at all. Drag and drop visual interface. Just go make it happen and go move on to the next data is critical, right? It's the lifeblood of any organization or that backbone of connectivity that gives our customers confidence to go to work. >>Awesome stuff. Chris, final word for you. If you can just share in your opinion and be talking to your customers out there and future customers, what would you say to them as you guys go this next leg of the journey for Boomi? What would you say to them? >>Yeah, I would say come partner with us. Come on, understand what we can do for your business. Come understand what true intelligent, automated connects in Lightspeed in terms of how fast we can do that with you. And let's go explore the art of the possible because to me, that's >>Awesome, Chris. Great to see you, Amanda and great to see you virtually. Can't wait to see you in person and next event, uh, and congratulations on all the success and looking forward to covering the next leg of the journey of Boomi. Thanks for coming on. Okay. This is the cube coverage of Boomi's out of this world event. I'm John furrier hosted the cube. Thanks for watching.

>>Welcome to the Cubes Coverage of Splunk.com 2021. My name is Dave Atlanta and the Cube has been covering.com events since 2012 and I've personally hosted many of them. And since that time we've seen the evolution of Splunk as a company and also the maturation in the way customers analyzed, protect and secure their organizations, data and applications. But the forced march to digital over the past 19 months has brought more rapid changes to sec UP teams than we've ever seen before. The adversary is capable. They're motivated and they're deploying very sophisticated techniques that have pressured security pros like never before. And with me to talk about these challenges and how Splunk is helping customers respond as jane wang is the vice president of security products that Splunk jane. Great to have you on the cube. Thanks for coming on. >>Very nice to meet you. Thank you for having me. >>You're very welcome. So how d how can you think about or how do you think about the fact that the imperative to accelerate digital transformation has impacted security teams? How has it impacted sec ops teams in your view? >>Yeah. Well, just going back to our customers and what I've learned from all the customer conversations I have every every week many of our customers are under a massive digital transformation. They're moving to the cloud and the cloud opens up more attack surface, more attack work surface, there's more threats that come over cloud, new workspaces to attack services, new api is to manage secure and protect and our customers are really struggling to gain the visibility they need to really manage and secure across all that infrastructure. >>Yeah. And we've also seen the whole, obviously the work from home trend, the hybrid work movement, you know, people aren't set up for that. I mean, you remember people were ripping out literally ripping out desktops and bringing them home and you know, the home network had to be upgraded. So lots of changes there. And we've we've talked a lot in the cube jane about the fragmentation of tooling and the lack of qualified talent when we talked to see. So as you ask him, the number one problem, I can't get, I can't hire enough talent in the field of of cybersecurity. So I wonder if you can address how this has made it more difficult for security teams to maintain end to end visibility across their environments. What's the fundamental challenge there? >>Yeah, well you're really you're really nailing this. The fundamental challenges that many security products are not built to integrate seamlessly with one another. When I'm talking to customers, their frontline security operations teams often have 30 different consoles open on their monitor at one time and there really manual disjointed processes, the copying and pasting hash names and iP addresses from one consults the other. It slows them down. It really slows them down in protecting those threats. So because those products aren't assigned to integrate together and all that data from each of those security tools isn't brought into one place. It just exacerbates the challenge for security operations seems makes their job really, really hard to do. Which takes time. It takes time. It makes it harder to detect and respond to threats quickly and today more than ever we need to be able to detect and respond to threats quickly. >>Yeah, I do a weekly program called Breaking Analysis and once a quarter I look at the cyberspace and I use a chart to emphasize this complexity. It's it's a from a company called operative, I don't know if you've ever seen it but it's this eye chart, it's this taxonomy of the security landscape and it's mind blowing how much complexity there is. So how to Splunk help organization organizations address these challenges. >>Yeah, so I think bringing, we have one security operations platform cloud native cloud delivered. There are many parts of being able to streamline workflows for when you're first detect a threat or a potential threat right through to when teams close and immediate that threatened the changes in their environment to ensure they're protected. So the whole thing is helping security teams detects faster, investigate faster and respond faster to threat. There are four parts to that in our security operations, platform Splunk security cloud. The first one is advanced security analytics. So the nature of threats is evolving. They're becoming more sophisticated. We have very smart, well funded Attackers whose day job who spend all their time trying to break into organizations. So you need really advanced security analytics to detect those threats, then we need to automate security operations so that it's not so manual, so you don't have poor folks sitting in front of multiple consoles doing manual tasks to respond to those threats and make sure their organizations are protected. One key thing is that this year Splunk acquired true Star so that we can bring in d do rationalize multiple sources of threat intelligence and apply that threat intelligence both to our analytics and our operations so that you have broader insights from the security community outside Splunk and that intelligence can really help and speed both detection and response. And the last thing that's been true about Splunk since spunk became Splunk many many years ago is that we are committed to partners and we deeply integrate with many other security tools uh in a very seamless way. So whatever investments customers have made within their security operations center, we will integrate and bring together those tools in one workspace. So there's the big advantages I think you get when, when you run your security operations said transplant security cloud, >>that's a nice little description. And having followed Splint for so many years, it's sort of, it tracks the progression of your ascendancy. You know, you started you you we we used to have log analytics that were just impossible. You sort of made that much easier took that to advanced kind of use big data techniques even though Splunk really never used that term. But but you were like the leader and big data um in terms of being able to analyze um uh data to help remediate issues. The automation key is p pieces key the acquisitions. You've made a very interesting um you mentioned around de doop threat intelligence but also you've done some cool stuff in the cloud and we always used to say jane watch for the ecosystem. We early too early, you know, last decade we saw you as a really hot company. We said one of the keys to your growth is going to be the ecosystem. And you've you've clearly made some progress there. I wonder if you could tell us more About the announcements that you're making here at.com. >>Yeah. Well we're going back everything that we do on the security team, every line of code every engineer writes is all around helping detect, investigate and respond faster to really secure organizations. So if I look at those intern I start with faster time to detect what have we done. So bringing in the threat intelligence that I mentioned again, that's really gonna help to take new threats and to take them really, really quickly. You don't have to spend time going and looking manually at external sources of threat intelligence. It will be brought right in to enterprise security at your fingertips. So that that's pretty huge. We're bringing other more advanced content right into our stem enterprise security. So that will help detect threats that our research team sees as emerging again. This is going to just bring bring that intelligence right to customers where they work every day, um faster time to investigate. So this is this is really exciting uh back in november we reduced and we are really something called risk based alerting. That is an amazing new capability that we've iterated on ever since. And we have more iterations that we're announcing um tomorrow actually. And so risk based alerting pulls together what may have been single atomic alerts that can often be overwhelming to a sock brings those together into one overarching alert that helps you see the whole pattern of an attack, the whole series of things that happened over time. That might be an attack on your organization. One customer told us that that reduced the time it took for them to do an investigation from eight hours down to 10 minutes to really helping faster time to investigate. And then the next one is faster time to respond. So we have a new visual playbook editor for our sore security orchestration and response to which is in the cloud but also available on prayer. But that new visual playbook editor really reduces the need for custom code. Makes playbooks more modular, so it can help anyone in the security operations team respond to threats really, really quickly. So faster time to detect, investigate and respond those are, those are really cool for us. And then there's some exciting partnerships that I want to talk about just to really focus on reducing the burden of all those disparate tools on consoles and bringing them down and and integrating them together. So we'll have some announcements. There are new integrations that we're releasing with Mandiant Aziz scalar and detects. I'm personally very excited about a fireside chat that Kevin Mandia, the Ceo and president of Mandiant, we'll be having tomorrow with our Ceo Doug merit. So those are some of the things we're announcing. It's a big year for security. Very excited >>to tell you that's, that's key. I want to just kind of go through and follow up on some of the faster time to detect with the threat intelligence. That's so important because we read about how long it takes sometimes for for organizations to even find out that somebody has infiltrated their environment. This risk based learning, it sounds like and you're so right, it's like paper cuts having a bottoms up analysis. It's almost overwhelming. You don't have a sense as to really where the focus should be. So if you can have more of a top down, hey start here and sort of bucket ties things. It's gonna, it's gonna accelerate and then the faster response time. The thing that strikes me jane with your visual playbook editor is as you well know, the the way in which bad guys get in now they're very stealthy, you almost have to be stealthy in your response. So if you have to write custom code that's going to alert the bad guys that they're they're seeing now seeing code that they've never seen before, they must have detected us and then they escalate, you know, they get you in a harder, tighter headlock. Uh and I love the partnerships, you know, we, we followed the trend toward remote security. Cloud security, where's the scale is a big player, Amanda you mentioned. So that's that's great too. I mean it feels like the puzzle pieces are coming together. It's it's almost like a game of constant, you know, you're never there but you've got to stay vigilant. >>I really think so today. I mean it's been a great 12 months that's blank. We have done so much over the past year leading up to this.com. I'm very excited to talk to folks about it. I think one thing I didn't really mention that I kind of touched on earlier in the talk that we're having was around cloud security monitoring. So holistic cloud security monitoring. We've got some updates there as well with deeper integrations into G C P A W S Azure, one dr SharePoint box net G drive. Like customers are using many, many cloud services today and they don't have a holistic view across all those services I speak to see so every week that tell me they just really need one view. Not to go into each of those cloud service providers or cloud services, one at a time to look at the security posture, they need that all in a central location. So we normalize, we ingest and normalize data from each of those cloud services so you can see threats consistently across each of them. I think that's really, really something different that Splunk is doing um that other security offerings are not doing. >>I think that's a super important point and I do hear that a lot from CsoS where they say look we have so many different environments, so many different tools and they each have their own little framework so we have to go in and and investigate and then come back out and then our teams have to go into a new sort of view and come back out and and they just run out of time and they just don't again, lack of lack of skills to actually do this, can't hire half fast enough, can't train fast enough. So so that higher level view but still the ability to drill down and understand what those root causes. That's it's a it's a it's a top down bottoms up type of approach and and so as opposed to just throwing grains of sand at the second teams and then hoping, you know, they find the pearl, so jane, I'll give you the last word, Maybe some final thoughts. >>No, I just wanted to thank everyone for listening. I want to thank everyone for joining dot com 21. We're very excited to hear from you and speak with you. So thank you very much. >>Excellent. Great having you in the cube, keep it right there, everybody for more coverage of the cube. Splunk dot com 21. We'll be right back, >>Yeah.

>> Narrator: From around the globe its "theCUBE" presenting Adaptive Data Governance, brought to you by Io-Tahoe. >> And we're back with the Data Automation series. In this episode we're going to learn more about what Io-Tahoe is doing in the field of adaptive data governance, how can help achieve business outcomes and mitigate data security risks. I'm Lisa Martin and I'm joined by Ajay Vohora the CEO of Io-Tahoe, and Lester Waters the CTO of Io-Tahoe. Gentlemen it's great to have you on the program. >> Thank you Lisa is good to be back. >> Great to see you Lisa. >> Likewise, very seriously this isn't cautious as we are. Lester were going to start with you, what's going on at Io-Tahoe, what's new? >> Well, I've been with Io-Tahoe for a little over the year, and one thing I've learned is every customer needs are just a bit different. So we've been working on our next major release of the Io-Tahoe product and to really try to address these customer concerns because we want to be flexible enough in order to come in and not just profile the data and not just understand data quality and lineage, but also to address the unique needs of each and every customer that we have. And so that required a platform rewrite of our product so that we could extend the product without building a new version of the product, we wanted to be able to have pluggable modules. We are also focused a lot on performance, that's very important with the bulk of data that we deal with and we're able to pass through that data in a single pass and do the analytics that are needed whether it's a lineage data quality or just identifying the underlying data. And we're incorporating all that we've learned, we're tuning up our machine learning, we're analyzing on more dimensions than we've ever done before, we're able to do data quality without doing an initial reggie expert for example, just out of the box. So I think it's all of these things are coming together to form our next version of our product and We're really excited about. >> Sounds exciting, Ajay from the CEOs level what's going on? >> Wow, I think just building on that, what Lester just mentioned now it's we're growing pretty quickly with our partners, and today here with Oracle we're excited to explain how that's shaping up lots of collaboration already with Oracle, and government in insurance and in banking. And we're excited because we get to have an impact, it's really satisfying to see how we're able to help businesses transform and redefine what's possible with their data. And having Oracle there as a partner to lean in with is definitely helping. >> Excellent, we're going to dig into that a little bit later. Lester let's go back over to you, explain adaptive data governance, help us understand that. >> Really adaptive data governance is about achieving business outcomes through automation. It's really also about establishing a data-driven culture and pushing what's traditionally managed in IT out to the business. And to do that, you've got to enable an environment where people can actually access and look at the information about the data, not necessarily access the underlying data because we've got privacy concern system, but they need to understand what kind of data they have, what shape it's in, what's dependent on it upstream and downstream, and so that they can make their educated decisions on what they need to do to achieve those business outcomes. A lot of frameworks these days are hardwired, so you can set up a set of business rules, and that set of business rules works for a very specific database and a specific schema. But imagine a world where you could just say, you know, (tapping) the start date of a loan must always be before the end date of a loan, and having that generic rule regardless of the underlying database, and applying it even when a new database comes online and having those rules applied, that's what adaptive data governance about. I like to think of it as the intersection of three circles, really it's the technical metadata coming together with policies and rules, and coming together with the business ontologies that are unique to that particular business. And bringing this all together allows you to enable rapid change in your environment, so, it's a mouthful adaptive data governance, but that's what it kind of comes down to. >> So Ajay help me understand this, is this what enterprise companies are doing now or are they not quite there yet? >> Well, you know Lisa I think every organization is going at his pace, but markets are changing economy and the speed at which some of the changes in the economy happening is compelling more businesses to look at being more digital in how they serve their own customers. So what we're saying is a number of trends here from heads of data, chief data officers, CIO stepping back from a one size fits all approach because they've tried that before and it just hasn't worked. They've spent millions of dollars on IT programs trying to drive value from that data, and they've ended up with large teams of manual processing around data to try and hard-wire these policies to fit with the context and each line of business, and that hasn't worked. So, the trends that we're seeing emerge really relate to how do I as a chief data officer, as a CIO, inject more automation and to allow these common tasks. And we've been able to see that impact, I think the news here is if you're trying to create a knowledge graph, a data catalog, or a business glossary, and you're trying to do that manually, well stop, you don't have to do that manual anymore. I think best example I can give is Lester and I we like Chinese food and Japanese food, and if you were sitting there with your chopsticks you wouldn't eat a bowl of rice with the chopsticks one grain at a time, what you'd want to do is to find a more productive way to enjoy that meal before it gets cold. And that's similar to how we're able to help organizations to digest their data is to get through it faster, enjoy the benefits of putting that data to work. >> And if it was me eating that food with you guys I would be not using chopsticks I would be using a fork and probably a spoon. So Lester how then does Io-Tahoe go about doing this and enabling customers to achieve this? >> Let me show you a little story here. So if you take a look at the challenges that most customers have they're very similar, but every customer is on a different data journey, so, but it all starts with what data do I have, what shape is that data in, how is it structured, what's dependent on it upstream and downstream, what insights can I derive from that data, and how can I answer all of those questions automatically? So if you look at the challenges for these data professionals, you know, they're either on a journey to the cloud, maybe they're doing a migration to Oracle, maybe they're doing some data governance changes, and it's about enabling this. So if you look at these challenges, I'm going to take you through a story here, and I want to introduce Amanda. Amanda is not Latin like anyone in any large organizations, she is looking around and she just sees stacks of data, I mean, different databases the one she knows about, the ones she doesn't know about but should know about, various different kinds of databases, and Amanda is this tasking with understanding all of this so that they can embark on her data journey program. So Amanda goes through and she's great, (snaps finger) "I've got some handy tools, I can start looking at these databases and getting an idea of what we've got." But when she digs into the databases she starts to see that not everything is as clear as she might've hoped it would be. Property names or column names have ambiguous names like Attribute one and Attribute two, or maybe Date one and Date two, so Amanda is starting to struggle even though she's got tools to visualize and look at these databases, she's still knows she's got a long road ahead, and with 2000 databases in her large enterprise, yes it's going to be a long journey. But Amanda is smart, so she pulls out her trusty spreadsheet to track all of her findings, and what she doesn't know about she raises a ticket or maybe tries to track down in order to find what that data means, and she's tracking all this information, but clearly this doesn't scale that well for Amanda. So maybe the organization will get 10 Amanda's to sort of divide and conquer that work. But even that doesn't work that well 'cause there's still ambiguities in the data. With Io-Tahoe what we do is we actually profile the underlying data. By looking at the underlying data, we can quickly see that Attribute one looks very much like a US social security number, and Attribute two looks like a ICD 10 medical code. And we do this by using ontologies, and dictionaries, and algorithms to help identify the underlying data and then tag it. Key to doing this automation is really being able to normalize things across different databases so that where there's differences in column names, I know that in fact they contain the same data. And by going through this exercise with Io-Tahoe, not only can we identify the data, but we also can gain insights about the data. So for example, we can see that 97% of that time, that column named Attribute one that's got US social security numbers, has something that looks like a social security number. But 3% of the time it doesn't quite look right, maybe there's a dash missing, maybe there's a digit dropped, or maybe there's even characters embedded in it, that may be indicative of a data quality issues, so we try to find those kinds of things. Going a step further, we also try to identify data quality relationships. So for example we have two columns, one date one date two, through observation we can see the date one 99% of the time is less than date two, 1% of the time it's not, probably indicative of the data quality issue, but going a step further we can also build a business rule that says date one is actually than date two, and so then when it pops up again we can quickly identify and remediate that problem. So these are the kinds of things that we can do with Io-Tahoe. Going even a step further, we can take your favorite data science solution, productionize it, and incorporate it into our next version as what we call a worker process to do your own bespoke analytics. >> Bespoke analytics, excellent, Lester thank you. So Ajay, talk us through some examples of where you're putting this to use, and also what is some of the feedback from some customers. >> Yeah, what I'm thinking how do you bring into life a little bit Lisa lets just talk through a case study. We put something together, I know it's available for download, but in a well-known telecommunications media company, they have a lot of the issues that lasted just spoke about lots of teams of Amanda's, super bright data practitioners, and are maybe looking to get more productivity out of their day, and deliver a good result for their own customers, for cell phone subscribers and broadband users. So, there are so many examples that we can see here is how we went about auto generating a lot of that old understanding of that data within hours. So, Amanda had her data catalog populated automatically, a business glossary built up, and maybe I would start to say, "Okay, where do I want to apply some policies to the data to set in place some controls, whether I want to adapt how different lines of business maybe tasks versus customer operations have different access or permissions to that data." And what we've been able to do that is to build up that picture to see how does data move across the entire organization, across the state, and monitor that over time for improvement. So we've taken it from being like reactive, let's do something to fix something to now more proactive. We can see what's happening with our data, who's using it, who's accessing it, how it's being used, how it's being combined, and from there taking a proactive approach is a real smart use of the tanons in that telco organization and the folks that work there with data. >> Okay Ajay, so digging into that a little bit deeper, and one of the things I was thinking when you were talking through some of those outcomes that you're helping customers achieve is ROI. How do customers measure ROI, What are they seeing with Io-Tahoe solution? >> Yeah, right now the big ticket item is time to value. And I think in data a lot of the upfront investment costs are quite expensive, they happen today with a lot of the larger vendors and technologies. Well, a CIO, an economic buyer really needs to be certain about this, how quickly can I get that ROI? And I think we've got something that we can show just pull up a before and after, and it really comes down to hours, days, and weeks where we've been able to have that impact. And in this playbook that we put together the before and after picture really shows those savings that committed a bit through providing data into some actionable form within hours and days to drive agility. But at the same time being able to enforce the controls to protect the use of that data and who has access to it, so atleast the number one thing I'd have to say is time, and we can see that on the graphic that we've just pulled up here. >> Excellent, so ostensible measurable outcomes that time to value. We talk about achieving adaptive data governance. Lester, you guys talk about automation, you talk about machine learning, how are you seeing those technologies being a facilitator of organizations adopting adaptive data governance? >> Well, as we see the manual date, the days of manual effort are out, so I think this is a multi-step process, but the very first step is understanding what you have in normalizing that across your data estate. So, you couple this with the ontologies that are unique to your business and algorithms, and you basically go across it and you identify and tag that data, that allows for the next steps to happen. So now I can write business rules not in terms of named columns, but I can write them in terms of the tags. Using that automated pattern recognition where we observed the loan starts should be before the loan (indistinct), being able to automate that is a huge time saver, and the fact that we can suggest that as a rule rather than waiting for a person to come along and say, "Oh wow, okay, I need this rule, I need this rule." These are steps that increase, or I should say decrease that time to value that Ajay talked about. And then lastly, a couple of machine learning, because even with great automation and being able to profile all your data and getting a good understanding, that brings you to a certain point, but there's still ambiguity in the data. So for example I might have two columns date one and date two, I may have even observed that date one should be less than date two, but I don't really know what date one and date two are other than a date. So, this is where it comes in and I'm like, "As the user said, can you help me identify what date one and day two are in this table?" It turns out they're a start date and an end date for a loan, that gets remembered, cycled into machine learning step by step to see this pattern of date one date two. Elsewhere I'm going to say, "Is it start date and end date?" Bringing all these things together with all this automation is really what's key to enable this data database, your data governance program. >> Great, thanks Lester. And Ajay I do want to wrap things up with something that you mentioned in the beginning about what you guys are doing with Oracle, take us out by telling us what you're doing there, how are you guys working together? >> Yeah, I think those of us who worked in IT for many years we've learned to trust Oracle's technology that they're shifting now to a hybrid on-prem cloud generation 2 platform which is exciting, and their existing customers and new customers moving to Oracle are on a journey. So Oracle came to us and said, "Now, we can see how quickly you're able to help us change mindsets," and as mindsets are locked in a way of thinking around operating models of IT that are maybe not agile or more siloed, and they're wanting to break free of that and adopt a more agile API driven approach with their data. So, a lot of the work that we're doing with Oracle is around accelerating what customers can do with understanding their data and to build digital apps by identifying the underlying data that has value. And the time we're able to do that in hours, days, and weeks, rather than many months is opening up the eyes to chief data officers, CIO is to say, "Well, maybe we can do this whole digital transformation this year, maybe we can bring that forward and transform who we are as a company." And that's driving innovation which we're excited about, and I know Oracle keen to drive through. >> And helping businesses transform digitally is so incredibly important in this time as we look to things changing in 2021. Ajay and Lester thank you so much for joining me on this segment, explaining adaptive data governance, how organizations can use it, benefit from it, and achieve ROI, thanks so much guys. >> Thanks you. >> Thanks again Lisa. (bright music)