>>Hello everyone and welcome back to Las Vegas. I've got my jazz hands because I am very jazzed to be here at AWS Reinvent Live from the show floor all week. My name is Savannah Peterson, joined with the infamous John Farer. John, how you feeling >>After feeling great? Love? What's going on here? The vibe is a cloud, cloud native. Lot of security conversation, data, stuff we love Cloud Native, >>M I >>A L, I mean big news. Security, security, data lake. I mean, who would've thought Amazon have a security data lake? You know, e k s, I mean >>You might have with that tweet you had out >>Inside outside the containers. Reminds me, it feels like coan here. >>It honestly, and there's a lot of overlap and it's interesting that you mention CubeCon because we talked to the next company when we were in Detroit just a couple weeks ago. Teleport E is the CEO and founder F Welcome to the show. How you doing? >>I'm doing well. Thank you for having me today. >>We feel very lucky to have you. We hosted Drew who works on the product marketing side of Teleport. Yeah, we got to talk caddies and golf last time on the show. We'll talk about some of your hobbies a little bit later, but just in case someone's tuning in, unfamiliar with Teleport, you're all about identity. Give us a little bit of a pitch, >>Little bit of our pitch. Teleport is the first identity native infrastructure access platform. It's used by engineers and it's used by machines. So notice that I used very specific choice of words first identity native, what does it mean? Identity native? It consists of three things and we're writing a book about those, but I'll let you know. Stay >>Tuned on that front. >>Exactly, yes, but I can talk about 'em today. So the first component of identity, native access is moving away from secrets towards true identity. The secrets, I mean things like passwords, private keys, browser cookies, session tokens, API keys, all of these things is secrets and they make you vulnerable. The point is, as you scale, it's absolutely impossible to protect all of the seekers because they keep growing and multiplying. So the probability of you getting hacked over time is high. So you need to get rid of secrets altogether that that's the first thing that we do. We use something called True Identity. It's a combination of your biometrics as well as identity of your machines. That's tpms, HSMs, Ubikes and so on, so forth. >>Go >>Ahead. The second component is Zero Trust. Like Teleport is built to not trust the network. So every resource inside of your data center automatically gets configured as if there is no perimeter it, it's as safe as it was on the public network. So that's the second thing. Don't trust the network. And the third one is that we keep access policy in one place. So Kubernetes clusters, databases on stage, rdp, all of these protocols, the access policy will be in one place. That's identity. Okay, >>So I'm, I'm a hacker. Pretend I'm a hacker. >>Easy. That sounds, >>That sounds really good to me. Yeah, I'm supposed to tell 'em you're hacker. Okay. I can go to one place and hack that. >>I get this question a lot. The thing is, you want centralization when it comes to security, think about your house being your AWS account. Okay? Everything inside your furniture, your valuable, like you'll watch collection, like that's your data, that's your servers, paper clusters, so and so forth. Right Now I have a choice and your house is in a really bad neighborhood. Okay, that's the bad internet. Do you wanna have 20 different doors or do you want to have one? But like amazing one, extremely secure, very modern. So it's very easy for you to actually maintain it and enforce policy. So the answer is, oh, you probably need to have >>One. And so you're designing security identity from a perspective of what's best for the security posture. Exactly. Sounds like, okay, so now that's not against the conventional wisdom of the perimeter's dead, the cloud's everywhere. So in a way kind of brings perimeter concepts into the posture because you know, the old model of the firewall, the moat >>It Yeah. Just doesn't scale. >>It doesn't scale. You guys bring the different solution. How do you fit into the new perimeters dead cloud paradigm? >>So the, the way it works that if you are, if you are using Teleport to access your infrastructure, let's just use for example, like a server access perspective. Like that machine that you're accessing doesn't listen on a network if it runs in Teleport. So instead Teleport creates this trusted outbound tunnels to the proxy. So essentially you are managing devices using out going connection. It's kind of like how your phone runs. Yeah. Like your phone is actually ultimate, it's like a teleport like, like I It's >>Like teleporting into your environment. >>Yeah, well play >>Journal. But >>Think about actually like one example of an amazing company that's true Zero trust that we're all familiar with would be Apple. Because every time you get a new iOS on your phone, the how is it different from Apple running massive software deployment into enormous cloud with billions of servers sprinkle all over the world without perimeter. How is it possible That's exactly the kind of technology that Teleports >>Gives you. I'm glad you clarified. I really wanted to get that out on the table. Cuz Savannah, this is, this is the paradigm shift around what an environment is Exactly. Did the Apple example, so, okay, tell 'em about customer traction. Are people like getting it right away? Are their teams ready? Are they go, oh my god this is >>Great. Pretty much you see we kinda lucky like in a, in a, like in this business and I'm walking around looking at all these successful startups, like every single one of them has a story about launching the right thing at just the right like moment. Like in technology, like the window to launch something is extremely short. Like months. I'm literally talking months. So we built Teleport started to work on it in like 2015. It was internal project, I believe it or not, also a famous example. It's really popular like internal project, put it on GitHub and it sat there relatively unnoticed for a while and then it just like took off around 2000 >>Because people start to feel the pain. They needed it. Exactly, >>Exactly. >>Yeah. The timing. Well and And what a great way to figure out when the timing is right? When you do something like that, put it on GitHub. Yeah. >>People >>Tell you what's up >>Yeah's Like a basketball player who can just like be suspended in the air over the hoop for like half the game and then finally his score and wins >>The game. Or video gamer who's lagged, everyone else is lagging and they got the latency thing. Exactly. Thing air. Okay. Talk about the engineering side. Cause I, I like this at co con, you mentioned it at the opening of this segment that you guys are for engineers, not it >>Business people. That's right. >>Explain that. Interesting. This is super important. Explain why and why that's resonating. >>So there is this ongoing shift on more and more responsibilities going to engineers. Like remember back in the day before we even had clouds, we had people actually racking servers, sticking cables into them, cutting their fingers, like trying to get 'em in. So those were not engineers, they were different teams. Yeah. But then you had system administrators who would maintain these machines for you. Now all of these things are done with code. And when these things are done with code and with APIs, that shifts to engineers. That is what Teleport does with policy. So if you want to have a set of rules that govern who or what and when under what circumstances can access what data like on Kubernetes, on databases, on, on servers wouldn't be nice to use code for it. So then you could use like a version control and you can keep track of changes. That's what teleport enables. Traditionally it preferred more kind of clicky graphical things like clicking buttons. And so it's just a different world, different way of doing it. So essentially if you want security as code, that's what Teleport provides and naturally this language resonates with this persona. >>Love that. Security is coding. It's >>A great term. Yeah. Love it. I wanna, I wanna, >>Okay. We coined it, someone else uses it on the show. >>We borrow it >>To use credit. When did you, when did you coin that? Just now? >>No, >>I think I coined it before >>You wanted it to be a scoop. I love that. >>I wish I had this story when I, I was like a, like a poor little 14 year old kid was dreaming about security code but >>Well Dave Ante will testify that I coined data as code before anyone else but it got 10 years ago. You >>Didn't hear it this morning. Jimmy actually brought it back up. Aws, you're about startups and he's >>Whoever came up with lisp programming language that had this concept that data and code are exact same thing, >>Right? We could debate nerd lexicon all day on the cube. In fact, that could even be a segment first >>Of we do. First of all, the fact that Lisp came up on the cube is actually a milestone because Lisp is a very popular language for object-oriented >>Grandfather of everything. >>Yes, yes, grandfather. Good, good. Good catch there. Yeah, well done. >>All right. I'm gonna bring us back. I wanna ask you a question >>Talking about nerd this LIS is really >>No, I think it's great. You know how nerdy we can get here though. I mean we can just hang out in the weeds the whole time. All right. I wanna ask you a question that I asked Drew when we were in Detroit just because I think for some folks and especially the audience, they may not have as distinctive a definition as y'all do. How do you define identity? >>Oh, that's a great question. So identity as a term was, it was always used for security purposes. But most people probably use identity in the context of single signon sso. Meaning that if your company uses identity for access, which instead of having each application have an account for you, like a data entry with your first name, last name emails and your role. Yeah. You instead have a central database, let's say Okta or something like that. Yep. And then you, you use that to access everything that's kind of identity based access because there is a single source of identity. What we say is that we, that needs to be extended because it it no longer enough because that identity can be stolen. So if someone gets access to your Okta account using your credentials, then they can become you. So in order for identity to be attached to you and become your true identity, you have to rely on physical world objects. That's biometrics your facial fingerprint, like your facial print, your fingerprints as well as biometric of your machine. Like your laptops have PPM modules on it. They're absolutely unique. They cannot be cloned stolen. So that is your identity as well. So if you combine whatever is in Octa with the biker chip in this laptop and with your finger that collectively is your true identity, which cannot be stolen. So it's can't be hacked. >>And someone can take my finger like they did in the movies. >>So they would have to do that. And they would also have to They'd >>Steal your match. Exactly, exactly. Yeah. And they'd have to have your eyes >>And they have to, and you have >>Whatever the figure that far, they meant what >>They want. So that is what Drew identity is from telecom and >>Biometric. I mean it's, we're so there right now it's, it's really not an issue. It's only getting faster and better to >>Market. There is one important thing I said earlier that I want to go back to that I said that teleport is not just for engineers, it's also for machines. Cuz machines they also need the identity. So when we talk about access silos and that there are many different doors into your apartment, there are many different ways to access your data. So on the infrastructure side, machines are doing more and more. So we are offloading more and more tasks to them. That's a really good, what do machines use to access each other? Biome? They use API keys, they use private keys, they use basically passwords. Yeah. Like they're secrets and we already know that that's bad, right? Yeah. So how do you extend biometrics to machines? So this is why AWS offers cloud HSM service. HSM is secure hardware security module. That's a unique private key for the machine that is not accessible by anyone. And Teleport uses that to give identities to machines. Does do >>Customers have to enable that themselves or they have that part of a Amazon, the that >>Special. So it's available on aws. It's available actually in good old, like old bare metal machines that have HSMs on them on the motherboard. And it's optional by the way Teleport can work even if you don't have that capability. But the point is that we tried, you >>Have a biometric equivalent for the machines with >>Take advantage of it. Yeah. It's a hardware thing that you have to have and we all have it. Amazon sells it. AWS sells it to us. Yeah. And Teleport allows you to leverage that to enhance security of the infrastructure. >>So that classic hardware software play on that we're always talking about here on the cube. It's all, it's all important. I think this is really fascinating though. So I had an on the way to the show, I just enrolled in Clear and I had used a different email. I enrolled for the second time and my eyes wouldn't let me have two accounts. And this was the first time I had tried to sort of hack my own digital identity. And the girl, I think she was humoring me that was, was kindly helping me, the clear employee. But I think she could tell I was trying to mess with it and I wanted to see what would happen. I wanted to see if I could have two different accounts linked to my biometric data and I couldn't it, it picked it up right away. >>That's your true >>Identity. Yeah, my true identity. So, and forgive me cuz this is kind of just a personal question. It might be a little bit finger finger to the wind, but how, just how much more secure if you could, if you could give us a, a rating or a percentage or a a number. How much more secure is leveraging biometric data for identity than the secrets we've been using historically? >>Look, I could, I played this game with you and I can answer like infinitely more secure, right? Like but you know how security works that it all depends on implementation. So let's say you, you can deploy teleport, you can put us on your infrastructure, but if you're running, let's say like a compromised old copy of WordPress that has vulnerability, you're gonna get a hack through that angle. But >>Happens happens to my personal website all the time. You just touched Yeah, >>But the fact is that we, I I don't see how your credentials will be stolen in this system simply because your TPM on your laptop and your fingerprint, they cannot be downloaded. They like a lot of people actually ask us a slightly different question. It's almost the opposite of it. Like how can I trust you with my biometrics? When I use my fingerprint? That's my information. I don't want the company I work at to get my fingerprint people. I think it's a legit question to ask. >>Yeah. And it's >>What you, the answer to that question is your fingerprint doesn't really leave your laptop teleport doesn't see your fingerprint. What happens is when your fingerprint gets validated, it's it's your laptop is matching what's on the tpm. Basically Apple does it and then Apple simply tells teleport, yep that's F or whoever. And that's what we are really using. So when you are using this form authentication, you're not sharing your biometric with the company you work at. >>It's a machine to human confirmation first and >>Then it's it. It's basically you and the laptop agreeing that my fingerprint matches your TPM and if your laptop agrees, it's basically hardware does validation. So, and teleport simply gets that signal. >>So Ed, my final question for you is here at the show coupon, great conversations there for your company. What's your conversations here like at reinvent? Are you meeting with Amazon people, customers? What are some of the conversations? Because this is a much broader, I mean it's still technical. Yep. But you know, a lot of business kind of discussions, architectural refactoring of organizations. What are some of the things that you're talking about here with Telepo? What are, >>So I will mention maybe two trends I observed. The first one is not even security related. It's basically how like as a cloud becomes more mature, people now actually at different organizations develop their own internal ways of doing cloud properly. And they're not the same. Because when cloud was earlier, like there were this like best practices that everyone was trying to follow and there was like, there was just a maybe lack of expertise in the world and and now finding that different organizations just do things completely different. Like one, like for example, yeah, like some companies love having handful, ideally just one enormous Kubernetes cluster with a bunch of applications on it. And the other companies, they create Kubernetes clusters for different workloads and it's just like all over the map and both of them are believed that they're doing it properly. >>Great example of bringing in, that's Kubernetes with the complexity. And >>That's kind of one trend I'm noticing. And the second one is security related. Is that everyone is struggling with the access silos is that ideally every organization is dreaming about a day, but they have like one place which is which with great user experience that simply spells out this is what policy is to access this particular data. And it gets a automatically enforced by every single cloud provider, but every single application, but every single protocol, but every single resource. But we don't have that unfortunately Teleport is slowly becoming that, of course. Excuse me for plugging >>TelePro. No, no worries. >>But it is this ongoing theme that everyone is can't wait to have that single source of truth for accessing their data. >>The second person to say single source of truth on this stage in the last 24 >>Hours or nerds will love that. I >>Know I feel well, but it's all, it all comes back to that. I keep using this tab analogy, but we all want everything in one place. We don't wanna, we don't wanna have to be going all over the place and to look for >>Both. Because if it's and everything else places, it means that different teams are responsible for it. Yeah. So it becomes this kind of internal information silo as well. So you not even, >>And the risks and liabilities there, depending on who's overseeing everything. That's awesome. Right? So we have a new challenge on the cube specific to this show thing of this as your 30 minute or 30 minute that would be bold. 32nd sizzle reel, Instagram highlight. What is your hot take? Most important thing, biggest theme of the show this year. >>This year. Okay, so here's my thing. Like I want cloud to become something I want it to be. And every time I come here and I'm like, are we closer? Are we closer? So here's what I want. I want all cloud providers collectively to kind of merge. So then when we use them, it feels like we are programming one giant machine. Kind of like in the matrix, right? The movie. So like I want cloud to feel like a computer, like to have this almost intimate experience you have with your laptop. Like you can like, like do this and the laptop like performs the instructions. So, and it feels to me that we are getting closer. So like walking around here and seeing how everything works now, like on the single signon on from a security perspective, there is so that consolidation is finally happening. So it's >>The software mainframe we used to call it back in 2010. >>Yeah, yeah. Just kind of planetary scale thing. Yes. It's not the Zuckerberg that who's building metaverse, it's people here at reinvent. >>Unlimited resource for developers. Just call in. Yeah, yeah. Give me some resource, spin me up some, some compute. >>I would like alter that slightly. I would just basically go and do this and you shouldn't even worry about how it gets done. Just put instructions into this planetary mainframe and mainframe will go and figure this out. Okay. >>We gotta take blue or blue or red pill. I >>Know. I was just gonna say y'all, we are this, this, this, this segment is lit. >>We got made tricks. We got brilliant. We didn't get super cloud in here but we, we can weave that in. We got >>List. We just said it. So >>We got lisp. Oh great con, great conversation. Cloud native. >>Outstanding conversation. And thank you so much for being here. We love having teleport on the show. Obviously we hope to see you back again soon and and Drew as well. And thank all of you for tuning in this afternoon. Live from Las Vegas, Nevada, where we are hanging out at AWS Reinvent with John Furrier. I'm Savannah Peterson. This is the Cube. We are the source for high tech coverage.

(upbeat music) >> As we said in our analysis of Dell's future, the transformation of Dell into Dell EMC and now Dell Technologies has been one of the most remarkable stories in the history of the technology industry. After years of successfully integrated EMC and becoming VMware's number one distribution channel, the metamorphosis of Dell culminated in the spin out of VMware from Dell and a massive wealth creation milestone pending of course the Broadcom acquisition of VMware. So where's that leave Dell and what does the future look like for this technology powerhouse? Hello, and welcome to theCUBE's exclusive coverage of Dell Technologies Summit 2022. My name is Dave Vellante and I'll be hosting the program. Today, in conjunction with the Dell Tech Summit, we'll hear from four of Dell senior executives. Tom Sweet is the CFO of Dell Technologies. He's going to share his views of the company's position and opportunities and answer the question why is Dell a good long term investment? Then we'll hear from Jeff Boudreau, who's the president of Dell's ISG business unit. He's going to talk about the product angle and specifically how Dell is thinking about solving the multi-cloud challenge. And then Sam Groccot is the senior vice President of marketing. He's going to come in the program and give us the update on Apex, which is Dell's as-a-service offering. And a new edge platform called Project Frontier. By the way, it's also Cybersecurity Awareness Month and we're going to see if Sam has any stories there. And finally, for a company that's nearly 40 years old, Dell has some pretty forward thinking philosophies when it comes to its culture and workforce. And we're going to speak with Jen Saavedra who's Dell's Chief Human Resource officer about hybrid work and how Dell is thinking about the future of work. We're going to geek out all day and talk multi-cloud and Edge and latency, but first, let's talk wallet. Tom Sweet, CFO, and one of Dell's key business architects. Welcome back to "theCUBE." >> Dave, it's good to see you and good to be back with you, so thanks for having me today. >> Yeah, you bet. Tom, it's been a pretty incredible past 18 months. Not only the pandemic and all that craziness, but the VMware spin. You had to give up your gross margin pinky, just kidding, and of course the macro environment. I'm so sick of talking about the macro. But putting that aside for a moment what's really remarkable is that for a company of your size, you've had some success at the top line which I think surprised a lot of people. What are your reflections on the last 18 to 24 months? >> Well Dave, it's been an incredible, not only last 18 months, but the whole transformation journey if you think all the way back maybe to the LBO and forward from there. But stepping into the last 18 months, it's, I think I remember talking with you and saying, "Hey, the scenario planning we did at the beginning of this pandemic journey was 30 different scenarios roughly, and none of which sort of panned out the way it actually did," which was a pretty incredible growth story. As we think about how we helped customers, drive workforce productivity, enable their business model during the all remote work environment that was the pandemic created. And couple that with the rise then and the infrastructure spin as we got towards the tail end of the pandemic coupled with the spin out of VMware, which culminated last November as we completed that, which unlocked a pathway back to investment grade, which then unlocked, quite frankly shareholder value, capital allocation frameworks. It's really been a remarkable 18, 24 months. It's, it's never dull at Dell Technologies. Let me put it that way. >> Well, I was impressed with you Tom before the leverage buyout and then what I've seen you guys navigate through is truly amazing. Well, let's talk about the challenging macro. I mean, I've been through a lot of downturns but I've never seen anything quite like this with Fed tightening, and you're combating inflation, you got this recession looming. There's a bear market. You got, but you got zero unemployment, you're rising wages, strong dollar, and it's very confusing. But IT spending is, it's somewhat softer, but it's still not bad. How are you seeing customers behave? How is Dell responding? >> Yeah look, if you think about the markets we play in Dave, we should start there as a grounding. The total market, the core market that we think about is roughly $750 billion or so, if you think about our core IT services capability. If you couple that with some of the growth initiatives that we're driving and the adjacent markets that that that brings in, you're roughly talking a 1.4 to $1.5 trillion market opportunity total addressable market. And so from that perspective we're extraordinarily bullish on where are we in the journey as we continue to grow and expand. We have, we're number one share in just about every category that we plan, but yet when you look at that, number one share in some of these, our highest share position may be low 30s and maybe in the high end of storage or at the upper end of 30s or 40%. But the opportunity there to continue to expand the core and continue to take share and outperform the market is truly extraordinary. So if you step back and think about that, then you say, okay, what have we seen over the last number of months and quarters? It's been really great performance through the pandemic as you highlighted. We actually had a really strong first half of the year of our fiscal year '23 with revenue up 12% operating income, up 12% for the first half. What we talked about if you might recall in our second quarter earnings was the fact that we were starting to see softness. We had seen it in the consumer PC space, which is not a big area of focus for us in the sense of our total revenue stream. But we started to see commercial PC soften and we were starting to see server demand soften a bit and storage demand was holding quite frankly. And so we gave a framework around guidance for the rest of the year as a result of what we were seeing. The macro environment as you highlighted continues to be challenging. If you look at inflation rates and the efforts by central banks across the globe through interest rate rise to press down and constrain growth and push down inflation, you couple that with supply chain challenges that continue particularly in the ISG space. And then you couple that with the Ukraine war and the energy crisis that that's created. And particularly in Europe, it's a pretty dynamic environment. But I'm confident, I'm confident in the long term. But I do think that there is, there's navigation that we're going to have to do over the coming number of quarters. Who knows quite how long. To make sure the business is properly positioned and we've got a great portfolio and you're going to talk to some of the team later on as you think your way through some of the solution capabilities we're driving, what we're seeing around technology trends. So the opportunity is there. There's some short term navigation that we're going to need to do just to make sure that we address some of the environmental things that we're seeing right now. >> Yeah, and as a global company of course you're converting local currencies back to appreciated dollars. That's another headwind. But as you say, I mean, that's math and you're navigating it. And again, I've seen a lot of downturns, but the best companies not only weather their storm, but they invest in ways they that allow them to come out the other side stronger. So I want to talk about that longer term opportunity the relationship between the core, the the business growth. You mentioned the TAM. I mean, even as a lower margin business, if you can penetrate that big of a TAM, you could still throw off a lot of cash and you've got other levers to turn in potentially acquisitions and software. But so ultimately what gives you confidence in Dell's future? How should we think about Dell's future? >> Yeah look, I think it comes down to we are extraordinarily excited about the opportunity over the long term. Digital transformation continues. I am on numerous customer and CIO conference calls every week. Customers are continuing to invest in digital transformation, in infrastructure, to enable their business model. Yes, maybe it's going to slow or pause, or maybe they're not going to invest quite at the same rate over the next number of quarters but over the long term the needs are there. You look at what we're doing around the growth opportunities that we see, not only in our core space where we continue to invest, but also in the, what we call the strategic adjacencies. Things like 5G and modern telecom infrastructure as our, the telecom providers across the globe open up their what previous been closed ecosystems to open architecture. You think about, what we're doing around the EDGE and the distribution now that we're seeing of compute and storage back to the edge given data, gravity, and latency matters. And so we're pretty bullish on the opportunity in front of us. Yes, we will, and we're continuing to invest. And you hear Jeff Boudreau talk about that I think later on in the program. So I'm excited about the opportunities and you look at our cash flow generation capability, we are in in normal times a cash flow generation machine and we'll continue to do so. We've got a negative CCC in terms of how do we think about efficiency of working capital? And we look at our capital allocation strategy which has now returned somewhere in near 60% of our free cash flow back to shareholders. And so, there's lots to, lots of reasons to think about why this, we are a great sort of, I think value creation opportunity in a over the long term. That the long term trends are with us and I expect them to continue to be so. >> Yeah, and you guys, you do what you say you're going to do. I mean, I said in my other piece that I did recently, I think you guys put $46 billion on the balance sheet in terms of debt. That's down to I think 16 billion in the core which that's quite remarking. That gives you some other opportunities. Give us your closing thoughts. I mean, you kind of just addressed why Dell is a good long term play, but I'll give you an opportunity to bring us home. >> Hey Dave, yeah look, I just think if you look at the grid, the market opportunity, the size and scale of Dell and how we think about the competitive advantages that we have, we can, if you look at say we're a hundred billion dollar revenue company which we were last year as we reported. Roughly 60, 65 billion of that in the client in PC space, roughly 35 to 40 billion in the ISG or infrastructure space. Those markets are going to continue. The opportunity to grow share, grow at a premium to the market, drive cash flow, drive share gain is clearly there. And couple that with what we think the opportunity is in these adjacent markets, whether it's telecom, the EDGE, what we're thinking around data services, data management, we, and you put that together with the long term trends around data creation and digital transformation. We are extraordinarily well positioned. We have the largest direct selling organization in the technology space. We have the largest supply chain. Our services footprint. Well positioned in my mind to take advantage of the opportunities as we move forward. >> Well Tom I really appreciate you taking the time to speak with us. Good to see you again. >> Nice seeing you. Thanks Dave. >> All right, you're watching theCUBE's exclusive behind the scenes coverage of Dell Technology Summit 2022. In a moment, I'll be back with Jeff Boudreau. He's the president of Dell's ISG Infrastructure Solutions Group. He's responsible for all the important enterprise business at Dell, and we're excited to get his thoughts. Keep it right there. (upbeat music)

>>Hello, everyone. Welcome to this cube conversation. I'm here in Palo Alto, California. I'm John furrier, host of the cube, and we have a great guest here. Barack Shuster. Who's in Tel-Aviv senior director of chief architect at bridge crew, a part of Palo Alto networks. He was formerly the co-founder of the company, then sold to Palo Alto networks Brock. Thanks for coming on this cube conversation. >>Thanks John. Great to be here. >>So one of the things I love about open source, and you're seeing a lot more of the trend now that talking about, you know, people doing incubators all over the world, having open source and having a builder, people who are starting companies, it's coming more and more, you you're one of them. And you've been part of this security open source cloud infrastructure infrastructure as code going back a while, and you guys had a lot of success. Now, open source infrastructure as code has moved up to the stack, certainly lot going down at the network layer, but developers just want to build security from day one, right? They don't want to have to get into the, the, the waiting game of slowing down their pipelining of code in the CIC D they want to move faster. And this has been one of the core conversations this year is how to make developers more productive and not just a cliche, but actually more productive and not have to wait to implement cloud native. Right. So you're in the middle of it. And you've got you're in, tell us, tell us what you guys are dealing with that, >>Right? Yeah. So I hear these needles working fast, having a large velocity of releases from many of my friends, the SRAs, the DevOps, and the security practitioners in different companies. And the thing that we asked ourselves three years ago was how can we simplify the process and make the security teams an enabler instead of a gatekeeper that blocks the releases? And the thing that we've done, then we understood that we should do is not only doing runtime scanning of the cloud infrastructure and the cloud native clusters, but also shift left the findings and fixings the remediation of security issues to the level of the code. So we started doing infrastructure is good. We Terraform Kubernetes manifests cloud formation, server less, and the list goes on and we created an open source product around it, named checkup, which has an amazing community of hundreds of contributors. Not all of them are Palo Alto employees. Most of them are community users from various companies. And we tried to and succeeded to the democratic side is the creation of policy as code the ability to inspect your infrastructure as code and tell you, Hey, this is the best practice that you should use consider using it before applying a misconfigured S3 bucket into production, or before applying a misconfigured Kubernetes cluster into your production or dev environment. And the goal, >>The goal, >>The goal is to do that from the ID from the moment that you write code and also to inspect your configuration in CGI and CD and in runtime. And also understand that if there is any drift out there and the ability to fix that in the source code, in the blueprint itself. >>So what I hear you saying is really two problems you're solving. One is the organizational policies around how things were done in a environment before all the old way. You know, the security teams do a review, you send a ticket, things are waiting, stop, wait, hurry up and wait kind of thing. And then there's the technical piece of it, right? Is that there's two pieces to that. >>Yeah, I think that one thing is the change of the methodologies. We understood that we should just work differently than what we used to do. Tickets are slow. They have priorities. You have a bottleneck, which is a small team of security practitioners. And honestly, a lot of the work is repetitive and can be democratized into the engineering teams. They should be able to understand, Hey, I wrote the code piece that provision this instance, I am the most suitable person as a developer to fix that piece of code and reapply it to the runtime environment. >>And then it also sets the table for our automation. It sets the table for policies, things that make things more efficient scaling. Cause you mentioned SRS are a big part of this to dev ops and SRE. Those, those folks are, are trying to move as fast as possible at scale, huge scale challenge. How does that impact the scale piece become into here? >>So both themes Esri's and security teams are about a link to deploying application, but new application releases into the production environment. And the thing that you can do is you can inspect all kinds of best practices, not only security, best practices, but also make sure that you have provision concurrencies on your serverless functions or the amount of auto-scaling groups is what you expect it to be. And you can scan all of those things in the level of your code before applying it to production. >>That's awesome. So good, good benefits scales a security team. It sounds like too as well. You could get that policy out there. So great stuff. I want to really quickly ask you about the event. You're hosting code two cloud summit. What are we going to see there? I'm going to host a panel. Of course, I'm looking forward to that as well. You get a lot of experts coming in there. Why are you having this event and what topics will be covered? >>So we wanted to talk on all of the shifts, left movement and all of the changes that have happened in the cloud security market since inception till today. And we brought in great people and great practitioners from both the dev ops side, the chaos engineering and the security practitioners, and everybody are having their opinion on what's the current status state, how things should be implemented in a mature environment and what the future might hold for the code and cloud security markets. The thing that we're going to focus on is all of the supply chain from securing the CCD itself, making sure your actions are not vulnerable to a shut injection or making sure your version control system are configured correctly with single sign-on MFA and having branch protection rules, but also open source security like SCA software composition analysis infrastructure as code security. Obviously Ron thinks security drifts and Kubernetes security. So we're going to talk on all of those different aspects and how each and every team is mitigating. The different risks that come with. >>You know, one of the things that you bring up when you hear you talking is that's the range of, of infrastructure as code. How has infrastructure as code changed? Cause you're, you know, there's dev ops and SRS now application developers, you still have to have programmable infrastructure. I mean, if infrastructure code is real realize up and down the stack, all aspects need to be programmable, which means you got to have the data, you got to have the ability to automate. How would you summarize kind of the state of infrastructure as code? >>So a few years ago, we started with physical servers where you carried the infrastructure on our back. I, I mounted them on the rack myself a few years ago and connected all of the different cables then came the revolution of BMS. We didn't do that anymore. We had one beefy appliance and we had 60 virtual servers running on one appliance. So we didn't have to carry new servers every time into the data center then came the cloud and made everything API first. And they bill and enabled us to write the best scripts to provision those resources. But it was not enough because he wanted to have a reproducible environment. The is written either in declarative language like Terraform or CloudFormation or imperative like CDK or polluted, but having a consistent way to deploy your application to multiple environments. And the stage after that is having some kind of a service catalog that will allow application developer to get the new releases up and running. >>And the way that it has evolved mass adoption of infrastructure as code is already happening. But that introduces the ability for velocity in deployment, but also new kinds of risks that we haven't thought about before as security practitioners, for example, you should vet all of the open source Terraform modules that you're using because you might have a leakage. Our form has a lot of access to secrets in your environment. And the state really contains sensitive objects like passwords. The other thing that has changed is we today we rely a lot on cloud infrastructure and on the past year we've seen the law for shell attack, for example, and also cloud providers have disclosed that they were vulnerable to log for shell attack. So we understand today that when we talk about cloud security, it's not only about the infrastructure itself, but it's also about is the infrastructure that we're using is using an open source package that is vulnerable. Are we using an open source package that is vulnerable, is our development pipeline is configured and the list goes on. So it's really a new approach of analyzing the entire software bill of material also called Asbell and understanding the different risks there. >>You know, I think this is a really great point and great insight because new opera, new solutions for new problems are new opportunities, right? So open source growth has been phenomenal. And you mentioned some of those Terraform and one of the projects and you started one checkoff, they're all good, but there's some holes in there and it's open source, it's free, everyone's building on it. So, you know, you have, and that's what it's for. And I think now is open source goes to the next level again, another generational inflection point it's it's, there's more contributors there's companies are involved. People are using it more. It becomes a really strong integration opportunity. So, so it's all free and it's how you use it. So this is a new kind of extension of how open source is used. And if you can factor in some of the things like, like threat vectors, you have to know the code. >>So there's no way to know it all. So you guys are scanning it doing things, but it's also huge system. It's not just one piece of code. You talking about cloud is becoming an operating system. It's a distributed computing environment, so whole new area of problem space to solve. So I love that. Love that piece. Where are you guys at on this now? How do you feel in terms of where you are in the progress bar of the solution? Because the supply chain is usually a hardware concept. People can relate to, but when you bring in software, how you source software is like sourcing a chip or, or a piece of hardware, you got to watch where it came from and you gotta track track that. So, or scan it and validate it, right? So these are new, new things. Where are we with? >>So you're, you're you're right. We have a lot of moving parts. And really the supply chain terms of came from the automobile industry. You have a car, you have an engine engine might be created by a different vendor. You have the wheels, they might be created by a different vendor. So when you buy your next Chevy or Ford, you might have a wheels from continental or other than the first. And actually software is very similar. When we build software, we host it on a cloud provider like AWS, GCP, Azure, not on our own infrastructure anymore. And when we're building software, we're using open-source packages that are maintained in the other half of the war. And we don't always know in person, the people who've created that piece. And we do not have a vetting process, even a human vetting process on these, everything that we've created was really made by us or by a trusted source. >>And this is where we come in. We help you empower you, the engineer, we tools to analyze all of the dependency tree of your software, bill of materials. We will scan your infrastructure code, your application packages that you're using from package managers like NPM or PI. And we scan those open source dependencies. We would verify that your CIC is secure. Your version control system is secure. And the thing that we will always focus on is making a fixed accessible to you. So let's say that you're using a misconfigured backup. We have a bot that will fix the code for you. And let's say that you have a, a vulnerable open-source package and it was fixed in a later version. We will bump the version for you to make your code secure. And we will also have the same process on your run time environment. So we will understand that your environment is secure from code to cloud, or if there are any three out there that your engineering team should look at, >>That's a great service. And I think this is cutting edge from a technology perspective. What's what are some of the new cloud native technologies that you see in emerging fast, that's getting traction and ultimately having a product market fit in, in this area because I've seen Cooper. And you mentioned Kubernetes, that's one of the areas that have a lot more work to do or being worked on now that customers are paying attention to. >>Yeah, so definitely Kubernetes is, has started in growth companies and now it's existing every fortune 100 companies. So you can find anything, every large growler scale organization and also serverless functions are, are getting into a higher adoption rate. I think that the thing that we seeing the most massive adoption off is actually infrastructure as code during COVID. A lot of organization went through a digital transformation and in that process, they have started to work remotely and have agreed on migrating to a new infrastructure, not the data center, but the cloud provider. So at other teams that were not experienced with those clouds are now getting familiar with it and getting exposed to new capabilities. And with that also new risks. >>Well, great stuff. Great to chat with you. I want to ask you while you're here, you mentioned depth infrastructure as code for the folks that get it right. There's some significant benefits. We don't get it. Right. We know what that looks like. What are some of the benefits that can you share personally, or for the folks watching out there, if you get it for sure. Cause code, right? What does the future look like? What does success look like? What's that path look like when you get it right versus not doing it or getting it wrong? >>I think that every engineer dream is wanting to be impactful, to work fast and learn new things and not to get a PagerDuty on a Friday night. So if you get infrastructure ride, you have a process where everything is declarative and is peer reviewed both by you and automated frameworks like bridge and checkoff. And also you have the ability to understand that, Hey, once I re I read it once, and from that point forward, it's reproducible and it also have a status. So only changes will be applied and it will enable myself and my team to work faster and collaborate in a better way on the cloud infrastructure. Let's say that you'd done doing infrastructure as code. You have one resource change by one team member and another resource change by another team member. And the different dependencies between those resources are getting fragmented and broken. You cannot change your database without your application being aware of that. You cannot change your load Bonser without the obligation being aware of that. So infrastructure skullduggery enables you to do those changes in a, in a mature fashion that will foes Le less outages. >>Yeah. A lot of people getting PagerDuty's on Friday, Saturday, and Sunday, and on the old way, new way, new, you don't want to break up your Friday night after a nice dinner, either rock, do you know? Well, thanks for coming in all the way from Tel-Aviv really appreciate it. I wish you guys, everything the best over there in Delhi, we will see you at the event that's coming up. We're looking forward to the code to cloud summit and all the great insight you guys will have. Thanks for coming on and sharing the story. Looking forward to talking more with you Brock thanks for all the insight on security infrastructures code and all the cool things you're doing at bridge crew. >>Thank you, John. >>Okay. This is the cube conversation here at Palo Alto, California. I'm John furrier hosted the cube. Thanks for watching.

>>Mhm. Mhm. >>We're here with the Cube covering Calm Vault Connections 21. We're gonna look at the data protection space and how cloud computing has advanced the way we think about backup recovery and protecting our most critical data. Ranga Rajagopalan, who is the vice president of products at Con vault and Stephen Orban, who's the General manager of AWS marketplace and control services gents. Welcome to the cube. Good to see you. >>Thank you. Always A pleasure to see you here >>steve. Thanks for having us. Very >>welcome, Stephen, let's start with you. Look the cloud has become a staple of digital infrastructure. I don't know where we'd be right now without being able to access enterprise services I. T. Services remotely. Um But specifically how our customers looking at backup and recovery in the cloud, is it a kind of a replacement for existing strategies? Is it another layer of protection? How are they thinking about that? >>Yeah. Great question. David again, thank thanks for having me. And I think you know, look if you look back to 15 years ago when the founders of AWS had the hypothesis that many enterprises governments and developers we're gonna want access to on demand pay as you go I. T. Resources in the cloud. Uh None of us would have been able to predict that it would have Matured and um you know become the staple that it has today over the last 15 years. But the reality is that a lot of these enterprise customers, many of whom have been doing their own IT infrastructure for the last 10, 20 or multiple decades do have to kind of figure out how they deal with the change management of moving to the cloud. And while a lot of our customers um will initially come to us because they're looking to save money or costs, almost all of them decided to stay and go big because of the speed at which they are able to innovate on behalf of their customers and when it comes to storage and backup, that just plays right into where they're headed. And there's a variety of different techniques that customers use, whether it be, you know, a lift and shift for a particular set of applications or a data center where they do very much. Look at how can they replace the backup and recovery that they have on premises in the cloud using solutions like, but we're partnering with console to do or completely reimagining their architecture for net new developments that they can really move quickly for their customers. Um and and completely developing something brand new, where it is really a, you know, a brand new replacement and innovation for for for what they've done in the past. >>Great, thank you, Stephen Rachael, I want to ask you about the d were digital. Look, if you're not a digital business today, you're basically out of business. So, my question to you is how have you seen customers change the way they think about data protection during what I call the forced March to digital over the last 18, 19 months or customers, you know, thinking about data protection differently today >>definitely Dave and and thank you for having me and steven. Pleasure to join you on this cube interview first going back to stevens comments can't agree more. Almost every business that we talked with today has a cloud first strategy, a cloud transformation mandate and you know, the reality is back to your digital comment. There are many different paths to the hybrid multi cloud and different customers. You know, there are different parts of the journey. So I still was saying most often customers at least in the data protection perspective start the conversation by thinking here have all these tips. Can I start using cloud as my air gap long term retention target and before they realized they start moving their workloads into the cloud and none of the backup and record yesterday's are going to change. So you need to continue protecting the clothes, which is where the cloud native data protection comes in and then they start innovating around er, can I use cloud as media sites so that you know, I don't need to meet in the other side. So this year is all around us. Cloud transformation is all around us and and the real essence of this partnership between AWS and calm vault is essentially to dr and simplify all the paths to the club regardless of whether you're going to use it as a storage started or you know, your production data center, all your dear disaster recovery site. >>Yeah, it really is about providing that optionality for customers. I talked to a lot of customers and said, hey, our business resilience strategy was really too focused on D. R. I've talked to all the customers at the other end of the spectrum said we don't even have a D. R. Strategy now, we're using the cloud for that. So it's really all over the map and you want that optionality. So steven and then go ahead. >>Please, ransomware plays a big role in many of these considerations that greatly. It's unfortunately not a question of whether you're going to be hit by ransomware, it's almost we can like, what do you do when you're hit by ransomware and the ability to use the clothes scaled immediately, bring up the resources, use the cloud backups has become a very popular choice simply because of the speed with which you can bring the business back to normal our patients. The agility and the power that cloud brings to the table. >>Yeah, ransomware is scary. You don't, you don't even need a high school diploma to be a ransomware ist you can just go on the dark web and by ransomware as a service and do bad things and hopefully you'll end up in jail. Uh Stephen we know about the success of the AWS marketplace, uh you guys are partnering here. I'm interested in how that partnership, you know, kind of where it started and how it's evolving. >>Yeah, happy to highlight on that. So, look when >>we when we started >>Aws or when the founders of aws started aws, as I said 15 years ago we we realized very early on that while we were going to be able to provide a number of tools for customers to have on demand access to compute storage, networking databases that many, particularly enterprise and government government customers still use a wide range of tools and solutions from hundreds, if not in some cases thousands of different partners. I mean I talked to enterprises who literally use thousands of of different vendors to help them deliver their solutions for their customers. So almost 10 years ago, we're almost at our 10 year anniversary for AWS marketplace, we launched the first substantiation of AWS marketplace which allowed builders and customers to find try buy and then deploy third party software solutions running on amazon machine instances also noticed as armies natively right in their AWS and cloud accounts to complement what they were doing in the cloud. And over the last nearly 10 years we've evolved quite a bit to the point where we support software and multiple different packaging types, whether it be amazon machine instances, containers, machine learning models and of course SAS and the rise of software as a service. So customers don't have to manage the software themselves. But we also support data products through the AWS Data exchange and professional services for customers who want to get services to help them integrate the software into their environments. And we now do that across a wide range of procurement options. So what used to be pay as you go amazon machine instances now includes multiple different ways to contract directly, customer can do that directly with the vendor with their channel partner or using kind of our public e commerce capabilities. And we're super excited, um, over the last couple of months we've been partnering with calm vault to get their industry leading backup and recovery solutions listed on AWS marketplace, which is available for our collective customers now. So not only do they have access to convulse awesome solutions to help them protect against ransomware as we talked about and to manage their backup and recovery environments, but they can find and deploy that directly in one click right into their AWS accounts and consolidate their building relationship right on the AWS and voice. And it's been awesome to work with with Rhonda and the product teams and convo to really, um, expose those capabilities where converts using a lot of different AWS services to provide a really great native experience for our collective customers as they migrate to the cloud. >>Yeah, the marketplace has been amazing. We've watched it evolve over the past decade and, and, and it's a, it's a key characteristic of everybody has a cloud today. We're a cloud to butt marketplaces unique uh, in that it's the power of the ecosystem versus the resources of one and Ringo. I wonder from, from your perspective, if you could talk about the partnership with AWS from your view and then specifically you've got some hard news, I wonder if you could talk about that as well. >>Absolute. So the partnership has been extended for more than 12 years. Right. So aws and Commonwealth have been bringing together solutions that help customers solve the data management challenges and everything that we've been doing has been driven by the customer demand that we seek. Right customers are moving their workloads in the cloud. They're finding new ways of deploying their workloads and protecting them. Um, you know, earlier we introduced cloud native integration with the EBS API which has driven almost 70% performance improvements in backup and restores. And when you look at huge customers like coca cola who have standardized on AWS um, combo. That is the scale that they want to operate in. You manage around 1 50,000 snapshots 1200 ec, two instances across six regions. But with just one resource dedicated for the data management strategy. Right? So that's where the real built in integration comes into play and we've been extending it to make use of the cloud efficiencies like our management and auto scale and so on. Another aspect is our commitment to a radically simple customer experience and that's, you know, I'm sure Stephen would agree it's a big month for at AWS as well. That's really together with the customer demand which brought us together to introduce com ball into the AWS marketplace exactly the way Stephen described it. Now the heart announcement is coming back up and recovery is available in native this marketplace. So the exact four steps that Stephen mentioned, find, try buy and deploy everything simplified through the marketplace So that our aws customers can start using far more back of software in less than 20 minutes. A 60 year trial version is included in the product through marketplace and you know, it's a single click buy, we use the cloud formation templates to deploy. So it becomes a super simple approach to protect the AWS workloads and we protect a lot of them. Starting from easy to rds dynamodb document DB um, you know, the containers, the list just keeps going on. So it becomes a very natural extension for our customers to make it super simple to start using convert data protection for the w >>well the con vault stack is very robust. You have extremely mature stack. I want, I'm curious as to how this sort of came about and it had to be customer driven. I'm sure where your customers saying, hey, we're moving to the cloud, we had a lot of workloads in the cloud, we're calm vault customer. That intersection between calm vault and AWS customers. So again, I presume this was customer driven. but maybe you can give us a little insight and add some color to that. >>Everything in this collaboration has been customer driven. We were earlier talking about the multiple paths to chlorine vapor example and still might probably add more color from his own experience at our jones. But I'll bring it to reference Parsons who's a civil engineering leader. They started with the cloud first mandate saying we need to start moving all our backups to the cloud but we have wanted that bad actors might find it easy to go and access the backups edible is um, Conwell came together with the security features and com well brought in its own authorization controls and now we have moved more than 14 petabytes of backup data into the club and it's so robust that not even the backup administrator and go and touch the backups without multiple levels of authorization. Right. So the customer needs, whether it is from a security perspective performance perspective or in this case from a simplicity perspective is really what is driving this. And and the need came exactly like that. There are many customers who have no standardized on it because they want to find everything through the AWS marketplace. They want to use their existing, you know, the AWS contracts and also bring data strategy as part of that so that that's the real um, driver behind this. Um, Stephen and I hope actually announced some of the customers that I actively started using it. You know, many notable customers have been behind this uh, innovation, don't even, I don't know, I wanted to add more to that. >>I would just, I would, I would just add Dave, you know, look if I look back before I joined a W S seven years ago, I was the C I O at dow jones and I was leading a a fairly big cloud migration there over a number of years. And one of the impetus is for us moving to the cloud in the first place was when Hurricane Sandy hit, we had a real disaster recovery scenario in one of our New Jersey data centers um, and we had to act pretty quickly convert was, was part of that solution. And I remember very clearly Even back then, back in 2013, they're being options available to help us accelerate are moved to the cloud and just to reiterate some of the stuff that Rhonda was talking about consoles, done a great job over the last more than a decade, taking features from things like EBS and S three and EC two and some of our networking capabilities and embedding them directly into their services so that customers are able to more quickly move their backup and recovery workloads to the cloud. So each and every one of those features was as a result of, I'm sure combo working backwards from their customer needs just as we do at >>AWS >>and we're super excited to take that to the next level to give customers the option to then also by that right on their AWS invoice on AWS marketplace. >>Yeah, I mean, we're gonna have to leave it there steven, you've mentioned several times the sort of the early days of back then we were talking about gigabytes and terabytes and now we're talking about petabytes and beyond. Guys. Thanks so much. I really appreciate your time and sharing the news with us. >>Dave. Thanks for having us. >>All right. Keep it right there more from combat connections. 21. You're watching the >>cube. Mm hmm.

(Techno music plays in intro) >> We're here with theCUBE covering Commvault Connections 21. And we're going to look at the data protection space and how cloud computing has advanced the way we think about backup, recovery and protecting our most critical data. Ranga Rajagopalan who is the Vice President of products at Commvault, and Stephen Orban who's the General Manager of AWS Marketplace & Control Services. Gents! Welcome to theCUBE. Good to see you. >> Thank you, always a pleasure to see you Dave. >> Dave, thanks for having us. Great to be here. >> You're very welcome. Stephen, let's start with you. Look, the cloud has become a staple of digital infrastructure. I don't know where we'd be right now without being able to access enterprise services, IT services remotely, Um, but specifically, how are customers looking at backup and recovery in the cloud? Is it a kind of a replacement for existing strategies? Is it another layer of protection? How are they thinking about that? >> Yeah. Great question, Dave. And again, thanks. Thanks for having me. And I think, you know, look. If you look back to 15 years ago, when the founders of AWS had the hypothesis that many enterprises, governments, and developers were going to want access to on demand, pay as you go, IT resources in the cloud. None of us would have been able to predict that it would have matured and, um, you know become the staple that it has today over the last 15 years. But the reality is that a lot of these are enterprise customers. Many of whom have been doing their own IT infrastructure for the last 10, 20 or or multiple decades do have to kind of figure out how they deal with it. The change management of moving to the cloud, and while a lot of our customers will initially come to us because they're looking to save money or costs. Almost all of them decide to stay and go big because of the speed at which they're able to innovate on behalf of their customers. And when it comes to storage and backup, that just plays right into where they're headed and there's a variety of different techniques that customers use. Whether it be, you know, a lift and shift for a particular set of applications. Or a data center or where it, where they do very much look at how can they replace the backup and recovery that they have on premises in the cloud using solutions like what we're partnering with Commvault to do. Or completely re-imagining their architecture for net new developments that they can really move quickly for, for their customers and, and completely developing something brand new, where it is really a, um, you know a brand new replacement and innovation for, for, for what they've done in the past. >> Great. Thank you, Stephen. Ranga, I want to ask you about the D word, digital. Look, if you're not a digital business today, you're basically out of business. So my question to you Ranga is, is how have you seen customers change the way they think about data protection during what I call the forced March to digital over the last 18, 19 months? Are customers thinking about data protection differently today? >> Definitely Dave, and and thank you for having me and Stephen pleasure to join you on this CUBE interview. First, going back to Stephen's comments, can't agree more. Almost every business that we talk with today has a cloud first strategy, a cloud transmission mandate. And, you know, the reality is back to your digital comment. There are many different paths to the hybrid micro cloud. And different customers. You know, there are different parts of the journey. So as Stephen was saying, most often customers, at least from a data protection perspective. Start the conversation their thinking, hey, I have all these tapes, can I start using cloud as my air gap, long-term retention target. And before they realize they start moving their workloads into the cloud, and none of the backup and recovery facilities are going to change. So you need to continue protecting the cloud, which is where the cloud meta data protection comes in. And then they start innovating around DR Can I use cloud as my DR sites so that, you know, I don't need to meet in another site. So this is all around us, cloud transmissions, all around us. And, and the real essence of this partnership between AWS and Commvault is essentially to drive, and simplify all the paths to the cloud Regardless of whether you're going to use it as a storage target or, you know, your production data center or your DR. Disaster Recovery site. >> Yeah. So really, it's about providing that optionality for customers. I talked to a lot of customers and said, hey, our business resilience strategy was really too focused on DR. I've talked to all the customers at the other end of the spectrum said, we didn't even have a DR strategy. Now we're using the cloud for that. So it's a, it's really all over the map and you want that optionality. So Stephen, >> (Ranga cuts in) >> Go ahead, please. >> And sorry. Ransomware plays a big role in many of these considerations as well, right? Like, it's unfortunately not a question of whether you're going to be hit by ransomware. It's almost become like, what do you do when you're hit by ransomware? And the ability to use the cloud scale to immediately bring up the resources. Use the cloud backers has become a very popular choice simply because of the speed with which you can bring the business back to normal operations. The agility and the power that cloud brings to the table. >> Yeah. Ransomware is scary. You don't, you don't even need a high school degree diploma to be a ransomware-ist. You could just go on the dark web and buy ransomware as a service and do bad things. And hopefully you'll end up in jail. Stephen, we know about the success of the AWS Marketplace. You guys are partnering here. I'm interested in how that partnership, you know, kind of where it started and how it's evolving. >> Yeah. And happy to highlight on that. So look, when we, when we started AWS or when the founders of AWS started AWS, as I said, 15 years ago. We realized very early on that while we were going to be able to provide a number of tools for customers to have on demand access to compute storage, networking databases, that many particularly, enterprise and government government customers still use a wide range of tools and solutions from hundreds, if not in some cases, thousands of different partners. I mean, I talked to enterprises who who literally used thousands of of different vendors to help them deliver those solutions for their customers. So almost 10 years ago, we're almost at our 10 year anniversary for AWS Marketplace. We launched the first instantiation of AWS Marketplace, which allowed builders and customers to find, try, buy, and then deploy third-party software solutions running on Amazon Machine Instances, also known as AMI's. Natively, right in their AWS and cloud accounts to compliment what they were doing in the cloud. And over the last, nearly 10 years, we've evolved quite a bit. To the point where we support software in multiple different packaging types. Whether it be Amazon Machine Instances, containers, machine learning models, and of course, SAS and the rise of software as a service, so customers don't have to manage the software themselves. But we also support a data products through the AWS data exchange and professional services for customers who want to get services to help them integrate the software into their environments. And we now do that across a wide range of procurement options. So what used to be pay as you go Amazon Machine Instances now includes multiple different ways to contract directly. The customer can do that directly with the vendor, with their channel partner or using kind of our, our public e-commerce capabilities. And we're super excited, um, over the last couple of months, we've been partnering with Commvault to get their industry leading backup and recovery solutions listed on AWS Marketplace. Which is available for our collective customers now. So not only do they have access to Commvault's awesome solutions to help them protect against ransomware, as we talked about and, and to manage their backup and recovery environments. But they can find and deploy that directly in one click right into their AWS accounts and consolidate their, their billing relationship right on the AWS invoice. And it's been awesome to work with with Ranga and the, and the product teams at Commvault to really expose those capabilities where Commvault's using a lot of different AWS services to, to provide a really great native experience for our collective customers as they migrate to the cloud. >> Yeah. The Marketplace has been amazing. We've watched it evolve over the past decade and it's just, it's a key characteristic of cloud. Everybody has a cloud today, right? Ah, we're a cloud too, but Marketplace is unique in, in, in that it's the power of the ecosystem versus the resources of one. And Ranga, I wonder if from your perspective, if you could talk about the partnership with AWS from your view, and and specifically you've got some hard news. Would, if you could, talk about that as well. >> Absolutely. So the partnership has been extending for more than 12 years, right? So AWS and Commvault have been bringing together solutions that help customers solve the data management challenges and everything that we've been doing has been driven by the customer demand that we see, right. Customers are moving their workloads to the cloud. They are finding new ways of deploying the workloads and protecting them. You know, earlier we introduced cloud native integration with the EBS AVI's which has driven almost 70% performance improvements in backup and restore. When you look at huge customers like Coca-Cola, who have standardized on AWS and Commvault, that is the scale that they want to operate on. They manage around one through 3,000 snapshots, 1200 easy, two instances across six regions, but with just one resource dedicated for the data management strategy, right? So that's where the real built-in integration comes into play. And we've been extending it to make use of the cloud efficiencies like power management and auto-scale, and so on. Another aspect is our commitment to a radically simple customer experience. And that's, you know, I'm sure Stephen would agree. It's a big mantra at AWS as well. That's really, together, the customer demand that's brought us together to introduce combo into the AWS Marketplace, exactly the way Stephen described it. Now the hot announcement is calmer, backup and recovery is available in AWS Marketplace. So the exact four steps that Stephen mentioned: find, try, buy, and deploy everything simplified to the Marketplace so that our AWS customers can start using our more backup software in less than 20 minutes. A 60 day trial version is included in the product through Marketplace. And, you know, it's a single click buy. We use the cloud formation templates to deploy. So it becomes a super simple approach to protect the AWS workloads. And we protect a lot of them starting from EC2, RDS DynamoDB, DocumentDB, you know, the, the containers, the list just keeps going on. So it becomes a very natural extension for our customers to make it super simple, to start using Commvault data protection for the AWS workloads. >> Well, the Commvault stack is very robust. You have an extremely mature stack. I want to, I'm curious as to how this sort of came about? I mean, it had to be customer driven, I'm sure. When your customers say, hey, we're moving to the cloud, we had a lot of workloads in the cloud. We're a Commvault customer, that intersection between Commvault and AWS customer. So, so again, I presume this was customer driven, but maybe you can give us a little insight and add some color to that, Ranga. >> Every everything, you know, in this collaboration has been customer driven. We were earlier talking about the multiple paths to cloud and a very good example, and Stephen might probably add more color from his own experience at Dow Jones, but I I'll, I'll bring it to reference Parsons. Who's, you know, civil engineering leader. They started with the cloud first mandate saying, we need to start moving all our backups to the cloud, but we averted that bad actors might find it easy to go and access the backups. AWS and Commvault came together with AWS security features and Commvault brought in its own authorization controls. And now we are moved more than 14 petabytes of backup data into the cloud, and it's sort of as that, not even the backup administrators can go and patch the backups without multiple levels of authorization, right? So the customer needs, whether it is from a security perspective, performance perspective, or in this case from a simplicity perspective is really what is driving us and, and the need came exactly like that. There are many customers who have now standardized on AWS, they want to find everything related to this Marketplace. They want to use their existing, you know, the AWS contracts and also bring data strategy as part of that. So that, that's the real driver behind this. Stephen and I were hoping that we could actually announce some of the customers that have actively started using it. You know, many notable customers have been behind this innovation. And Stephen I don't know if you wanted to add more to that. >> I would just, I would just add Dave, you know, like if I look back before I joined AWS seven years ago, I was the CIO at Dow Jones. And I was leading a, a fairly big cloud migration there over a number of years. And one of the impetuses for us moving to the cloud in the first place was when Hurricane Sandy hit, we had a real disaster recovery scenario in one of our New Jersey data centers. And we had to act pretty quickly. Commvault was, was part of that solution. And I remember very clearly, even back then, back in 2013, there being options available to help us accelerate our move to the cloud. And, and just to reiterate some of the stuff that Ranga was talking about, you know, Commvault's done a great job over the last, more than a decade. Taking features from things like EBS, and S3, and TC2 and some of our networking capabilities and embedding them directly into their services so that customers are able to, you know, more quickly move their backup and recovery workloads to the cloud. So each and every one of those features was, is a result of, I'm sure, Commvault working backwards from their customer needs just as we do at AWS. And we're super excited to take that to the next level, to give customers the option to then also buy that right on their AWS invoice on AWS Marketplace. >> Yeah. I mean, we're going to have to leave it there. Stephen you've mentioned this several times, there's sort of the early days of AWS. We went back then we were talking about gigabytes and terabytes, and now we're talking about petabytes and beyond. Guys thanks so much. We really appreciate your time and sharing the news with us. >> Dave, thanks for having us. >> All right, keep it right there more from Commvault Connections 21, you're watching theCUBE.

>>Welcome to the AWS Startup. Showcase new breakthroughs in devops, did analytics and cloud management tools. I'm lisa martin, I've got Jordan share here with the next vice president of corporate marketing Ops ramp, Jordan welcome to the program >>lisa It's great to be here. Great to talk about some of the stuff. Thanks for having me. >>Yeah let's break this down. Tell me, first of all about Ops ramp, how is it facilitating the transformation of I. T. Ops helping companies as your website says control the chaos. >>Sure. So option is an availability platform for the modern enterprise. We consolidate digital I. T. Operations management into one place. So availability as you can imagine um is a consistent challenge for I. T. Operations teams in large enterprises maintaining service assurance, making sure that services are up available, performing uh Ops tramp is the platform that powers all of that and we bring a lot of different features and functions to bear in driving availability. I think about ai ops I think about hybrid infrastructure monitoring, multi cloud monitoring, that's all part of the options offering. Modern enterprise. >>Talk to me about back in 2014 what the founders saw of Ops ramps, what were some of the gaps in the market that they saw that this needs to be addressed and no one's >>doing? It's a great question. So abstract was originally founded as part of an MSP offering. So we were a platform serving managed service providers who wanted to consolidate the infrastructure of their clients onto one multi tenant platform. What they noticed was that these enterprise customers of the MSP s whom we served. Really appreciated that promise of being able to consolidate infrastructure, being able to visualize different alerts, different critical incidents that might arise all on one platform. And so that's when we decided to raise around and take it directly to the enterprise so they could have the same kind of visibility and control that MSP s were delivering back to them, >>Visibility and control is essential, especially if your objective is to help control the chaos. Talk to me about some of the trends that you've seen, especially in the last 18 months, as we've been in such a dynamic market, we've seen the rapid acceleration of digital business transformation. What are some of those key trends especially with respect to a I ops that you think are really poignant. >>Yeah. You know, we like to think over here that the pandemic didn't really change a whole lot, accelerated a whole lot. And so we started to see at least within the past 12 to 18 months this acceleration of moving to the cloud, you know, Gardner forecasted that I thi enterprises, large enterprises are going to be spending upwards of 300 billion um in the move to the public cloud. So that has really facilitated some of the decisions that we have made and the promises that we offer to our customers, number one, Number two, with the move to remote work and the adoption of a lot of different digital tools and uh the creation and implementation of a lot of different digital customer services. Um It has forced these enterprises whom we serve to really rethink how they provide flexibility and control to their larger enterprise. I. T. Teams that might be distributed might be working remote might be in different locations. How can they consolidate infrastructure as it gets more and more complex. So that's where ops tramp has really created the most value. So we think about two things. Number one I want to consolidate my multi cloud environments so services via AWS for example or other cloud providers. How do I bring that within? How do I bring that control within my enterprise within the context of maybe additional private cloud offerings or public cloud infrastructure. Number one. Number two how do I get control over the constant flood of alerts but I'm getting from these different digital services and tools all in one place. Um you know so we are responding to that need by for example uh implementing a really rich robust ai ops functionality within the train platform to both be able to consolidate those alerts that are coming through and really escalate the critical ones um for to allow I. T. Operations seems to be a little bit more proactive and understand how incidents are happening and giving them the ability to remediate those incidents become before they become business critical and can really shut down the internet. >>Speaking of the enterprise. I'm curious if your customer conversations have changed in level in the last 18 months as everything has become chaotic for quite a while. We're still in we've been in a hybrid cloud world for a while. We are in a hybrid workforce situation. Have you noticed an escalation up the stack in terms of the c suite of going we need to make sure that we're leveraging cloud properly financially responsibly and ensuring that we have this ability and all the services that we're delivering. >>You mean are they sweating more And are they coming to us when they're sweating more? Yeah. Yeah for sure. The short answer is yes. So let me give you a great example. Um One of our recent customers they manufacture chips microchips and what they've noticed is that number one demand has grown um due to the increase in digital transformation. Um Number two supply chains have become more constricted for them specifically so they're asking themselves. All right how can we equip our I. T. Operations teams to maintain the availability of different logistics services within our organization So that they can both maintain service availability of these different logistic logistic services um and be able to stay on deadline as much as they possibly can um during a supply chain crisis that we're facing right now. And number two how can we as we move to the cloud and we see a distribution of our workforce still be able to maintain I. T. Operation services regardless. Um That is a need in particular in particular the supply chain um constraint issue. Uh That is a need that has arisen only in the last 18 months and it is a perfect use case for ops ramp or a platform that allows you to consolidate I. T. Operations to one place and give flexibility control across a distributed environment with a number of different new digital services that have been implemented. To solve some of these challenges. >>Talk to me about Ai ops as a facilitator of that availability visibility in this hybrid world that is still somewhat chaotic. >>Yeah great question. So originally it was al gore algorithmic operations is coined by Gardner today it's artificial intelligence in its operations. So the notion there is simple right there's a lot of data coming in on throughout the I. T. Operations organization. How can we look for patterns within that data to help us understand and act more proactively. Um From an operational perspective well there are a lot of promises uh that go along with A. I. Ops that it's going to completely transform these I. T. Organizations that it's going to reduce headcount. Um We don't necessarily find that to be true. What we do find true though is that the original promise behind a IOP still exists right we need to look for patterns in the data and we need to be able to drive insights from those patterns so that is what the Ai ops feature functionality within abstract really does. It looks for patterns within alerts and helps you understand what these patterns ultimately mean. Let me give you a great example so we have different algorithms within the train platform for co occurring events or for downstream events that help us indicate, okay if a number of these events are happening across one geography or one um business service for example we can actually look for those co occurring patterns and we can see that there may be one resource or set of resources that is actually causing a bunch of these incidents for a bunch of these alerts upstream of all the actual alerts themselves. So instead of the ICTy Operations organization having to go in and remediate a bunch of different distributed alerts, they can actually look at that upstream alert and say okay that's the one that really matters, that's where I need to pay most of my attention to. Um and that's where I'm going to deploy a team or open up a ticket or escalate to I. T. S. M. Or a variety of different things because I know that these co occurring alerts are creating a pattern that's driving some insight. Um so that's just part of the overall Ops tramp Ai Ops um promise or uh you know there's there's tons more that goes along with the biopsy but we really want to take some of the load and reduce some of the alerts that these icy operations teams are having to deal with on a daily basis. >>So let's talk about how you do that from a practical perspective, is looking at some of the notes that your team provided and according to I. D. C. This was a report from asia pacific excluding Japan that 75% of global two K enterprises are going to adopt a I Ai Ops by 2023 but a lot of Ai ops projects have been built on and haven't been successful. How does abstract help change flip the script on that? >>So it really comes down to the quality of the data right? If you have a bolt on tool, you have to optimize that tool for the different data lakes or data warehouses or sources of data that exists within your operational organization. I think about multi cloud apps across the multiplied environment. So I have to optimize the data that is coming in from each of those different cloud providers onto a bolt on tool to make sure that the data that's being fed to the tool is accurate and it is a true reflection of what's going on in the operational organization. That's number one. If you look at ops tramp and the differentiation there. Um op tramp is a big data platform at its core. So you bring ops tramp in, you optimize it for your overall infrastructure mix and then the data that gets fed into the ai ops feature functionality is the same across the board. There is no further optimization. So what that means is that the insights that are being driven by the outside perhaps platform are more sophisticated, they're more nuanced, there are more accurate representation and they're probably driving ultimately better insights than sticking a tool on top of five different existing data warehouses or data lakes. >>So if you've got a customer and I'm sure that you do enterprises, as we said, going to be adopting this substantially by 2023 which is just around the corner, how do you help them sort through the infrastructure and the ecosystem that they have so that they're not bolting things on but rather they can actually really build this very intuitively to deliver that availability and the visibility that they need fast. >>Yeah, so a couple of different comments on that ways that we try to help. Number one, I think it's critical for us to understand the challenges of the modern I. T. Infrastructure environment, across different verticals, different industries. So when we walk into any of our clients, we already have a good mix of their challenges. Is it Iot? Are they dealing with a bunch of different devices at the edge, are they, you know, a telecom with uh critical incidents is incidents in the network that they need to remediate. Um Number two, we try to smooth the glide path into understanding the obscene ramp platform and promise early. So what does that mean? It means we offer a free trial of the platform itself at tried out abstract dot com, you can set up up to 1000 resources for free with an unlimited number of users for 14 days and kick the tires particularly in multi cloud monitoring and see what sorts of insights you can determine um, just within those two weeks and in fact we're, we put our cards on the table and we say you can probably see your first insights into your infrastructure within 20 minutes of setting up the abstract free trial um, and if you don't want to bring your resources, your own resources to it will even provide a collection of resources preloaded onto the platform so you can try it out yourself without having to get, you know, a bunch of approvals to load infrastructure in there. So two pieces, number one, it's this proof of concept proof of value where we try to understand the clients pain and number two, if you want to kick the tires on it yourself, we can offer that with this free trial offering. >>So what I'm hearing and that is fast time to value which in these days is absolutely essential. How does that differentiate ops ramp as a technology company and >>from your customer's perspective? Yeah, so I appreciate that. And the meantime to incite is one of the critical aspects of our product roadmap, we really want to drive down that time to value coefficient because it's what these operations teams need as complexity grows really if you take a step back right, everything is getting more complex. So it's not only the pandemic and the rise of multi cloud but it's more digital customer experience is to compete. It's the availability, it's the need of a modern enterprise to be agile. All of those things translate basically into speed and flexibility and agility. So if there's one guiding light of ops tram it's really to equip the operations team with the tools that they need to move flexibly with the business. There is a department in any modern enterprise today if they need access to the public cloud and they have a credit card they're getting on AWS right now and they are spinning up a host of services. We want to be the platform that still gives the central IT operations team some aspect of control over that with the ability with without taking away the ability of that you know siloed operations team somewhere in some geo geographic region. We want to empower them to be able to spend up that AWS service but at the same time we want to just know that exists and be able to control it. >>How can A I A facilitator of better alignment between I. T. Tops and the business as you just gave a great example of the business getting the credit card spending up services that they need for their line of business or their function and then from a cultural perspective I'm just curious how can A. I. R. S. B. A facilitator of those two groups working better together in a constantly complex environment. >>That's a great question. So imagine if I. T. Operations did more than just keep the lights on. Imagine if you knew that your I. T. Operations team could be more proactive and more productive about alerts incidents and insights from infrastructure monitoring. What that means is that you are free to create any kind of digital customer experience that you would want to drive value back to your end user. It means that no longer do you think about it? Operations is this big hodgepodge of technology that you have to spend you know hundreds of millions of dollars a year in network operations teams and centers and technologies just to keep control of right by consolidating everything down to one place one sas based platform like this it frees up the business to be able to innovate. Um You know take advantage of new technologies that come around and really to work flexibly with the needs of the business as it grows. That's the promise of a tramp. We're here to replace you know these old appliances or different management packs of tools that exists that you consistently have to add an optimized and tune to feel to to empower the operations team to act like that. Um The truth is that is that everything is SAT space now, everything is status based and when you get to the core of infrastructure, it needs to be managed to be a SAs and thats ops ramp in a nutshell, >>I like that nutshell, that's excellent. I want to know a little bit about your go to market with a W. S. Talk to me a little bit about the partnership there and where can what's your go to market like? Essentially, >>yeah, so were included in the AWS marketplace, we have an integration with a W. S um as the de facto biggest cloud provider in the world. We have to play nice with them. Um and obviously the insights that we drive on the option platform have to be insights that you need from your AWS experience. You know, it has to be similar to cloudwatch or in a lot of, in a lot of cases um it has to be as rich as the cloudwatch experience in order for you to want to use op tramp within the context of the different other multi cloud providers, so that's how abstract works. Um you know, we understand that there's a lot of AWS certified professionals who work with who work at Ops tramp, who understand what AWS is doing and who consistently introduce new features that play well with the service is the service library that AWS currently offers today. >>Got it as we look ahead to 2022 hopefully a better year than 2020 and 2021. What are some of the things that you're excited about? What are some of the things on the ops ramp road map that you can share with us? >>Yeah, so you know, the other, the other big aspect of uh the new landscape of IT operations is observe ability. We're really excited about observe ability, we think that it is the new landscape of monitoring um you know, the idea of being able to find unknown unknowns that exists within your operational stack is important to us to be able to consolidate that with the power of ai ops so that you now have machine learning on top of your ability to find unknown unknown issues. That's that's going to be super exciting for us. I know the product team is taking a hard look at how to drive hybrid, observe ability within the abstract platform. So how do we give a better operational perspective to on prem public cloud and private cloud infrastructure moving forward and how do we ingest alerts before they're even alerts? I mean that's observe ability in a nutshell, if I'm getting in and I'm checking the option platform every day, then that's a workflow that we can remove by creating a better observe ability posture within the train platform. So now the platform is going to run unsupervised right in the background um and ai apps is going to be able to take action on predictive incidents before they ever occur, that's what we're looking at in the future. You know, everything is getting more complex. We've heard this story a million times before, we want to be the platform that can handle that complexity on a massive scale, >>finding the unknown, unknowns, converting them into knowns I imagine is going to be more and more critical across every industry. Last question for you, given the culture and the dynamics of the market that we're in, are there any industries and all of trump's is seeing is really key targets for this type of technology. >>The nice thing about ops tramp is we are we are really vertical neutral, right? Any industry that has complexity and that's every industry can really take advantage of a platform like this. We have seen recent success particularly in finance manufacturing, health care because they deal with new emerging types of complexity that they are not necessarily cared for. So I think about some of our clients, some of our friends in the finance industry, you know, um as transactions accelerate as new customer experiences arise uh these are things that their operations teams need to be equipped for and that's where up tramp really drives value. What's more is that these uh these industries are also somewhat legacy, so they have a foot in the old way of doing things, they have a foot in the data center, you know, there are many financial institutions that have large data center footprint for security considerations. And so if they are living in the data center and they want to make the move to cloud, then they need something like cops ramp to be able to keep a foot in both sides of the equation, >>right, Keep that availability and that visibility. Jordan, thank you for joining me today and talking to us about ops around the capabilities that Ai ops can deliver to enterprises in any industry. The facilitation of of the I. T. Folks in the business folks and what you guys are doing with AWS, we appreciate your time. >>Absolutely lisa, thank you very much. Thanks for the great questions. If you ever need a job in corporate marketing, you seem like you're a natural fit. I'll >>call you awesome. >>Thank you >>for Jordan share. I'm lisa martin, You're watching the AWS startup showcase.

>> Welcome to the AWS Startup Showcase: New Breakthroughs in DevOps, Data Analytics, and Cloud Management Tools. I'm Lisa Martin. I'm pleased to welcome JT Giri, the CEO and founder of nOps, to the program. JT, welcome. It's great to have you. >> Thank you, Lisa. Glad to be here. >> Talk to me about nOps. This was founded in 2017, you're the founder. What do you guys do? >> Yeah. So just a little bit background on myself. You know, I've been migrating companies to AWS ever since EC2 was in beta. And you know, in the beginning I had to convince people like, "Hey, you should move to cloud." And the question people used to ask me, like, "Is cloud secure?" I'm glad no one is asking that question anymore. So, as I was building and migrating customers to the cloud, one of the things I realized very early on, is just cloud, there are so many resources, so many teams provisioning resources, then how do you align with your business goals? So we created nOps so that, for a mission, how do you are you build a platform where you make sure every single change and every single resource in the cloud is aligned with the business needs, right? Like we really helped people to make the right trade-offs. >> So you mentioned you've been doing this since EC2 was in beta, and we just celebrated, with AWS, EC2's 15th birthday. So you've been doing this awhile. You don't look old enough, but you've been doing this for awhile. So one of the things that I read on the website, I always love to understand messaging, that nOps says about itself, "The first cloud ops platform "designed to sync revenue growth across your teams." Talk to me about how you do that. >> Yeah. So one of the problems we see in the market right now, there are a lot of tools, there are a lot of dashboards that shows like, "Hey, you have this many issues, "here's the opportunity to fix issues. "And here are the security issues." We're more focused on how do we take those issues from a backlog and fixing those issues. Right? So our focus is more on operationalizing, so your teams could actually own that, prioritize, and actually remediate those issues. So that's where we focus our energy. >> Got it. Let's talk about cloud ops now, and how it varies or differs from traditional cloud management. >> Yeah, I think, like I mentioned, cloud management seems to be more like visibility. And everyone knows that there are challenges in their cloud environment. But when you focus more on the operation side, what we really try to do, from an issue, how do you actually fix that issue? How do you prioritize? How do you make the right trade-offs. Right? Trade offs is important because we make a lot of decisions in the cloud when you're building your infrastructure. Sometime you might have to prioritize for costs, sometime you might have to prioritize based on the SLA. You might have to add more resources to hit your SLAs. So we really help you to prioritize. And we build sort of accountability. You know, you can create roles. Most of the time, what we noticed, I truly believe that if it's everyone's responsibility, it's no one's responsibility. You know? So what we do is we help, within the tool, to establish clear roles and responsibilities. And we show audit log of people reviewing and fixing security issues. And we show audit log of people fixing and reviewing cost issues. That's one way we're trying to bring accountability. >> I like what you said, if everyone's responsible, then really no one is. And that seems to be a persistent problem that we see in businesses across industries, is just still that challenge with aligning IT and business. And especially with the dynamics of the market, JT, that we've seen in the last 18 months, things are moving so quickly. Talk to me about how you guys have been helping companies, especially in the last 18 months, with such change to get that alignment. So that that visibility and those clear roles are established and functional. >> Yeah. You know, what we really do is obviously listen to the customers. Right? And one of the challenges we hear over and over is like, you know, I know I have issues in the cloud environment that I really need help prioritizing. And they're really looking for a framework where they can come in and say, "Okay these are the people who are responsible for security. "These are the people who are responsible for the cost." So as part of onboarding with nOps, that's one of the things you do, you define your workloads. By the way, we automatically create your workload across all your accounts. And then we allow you to move resources around if you like. But then one of the first thing we do is assign roles and responsibilities for each one of these workloads. Oh, it's been incredible to see, when you have that kind of accountability, people actually do make sure that the resources are aligned with the business needs. >> So are you seeing, I mean, that's kind of a cultural shift. That changed management is a challenging process. How are you seeing that evolve in organizations who've been used to doing things maybe in a little bit of a blinders on kind of mode? >> Yeah. Well, changed management is an area where we spent a lot of time, because in cloud, changed management is almost like a fire hose. Right? There's so many changes and you could have 20 people or 20 different teams making changes. I think what people really want is sort of root cause analysis. Like, "Hey, this is what changed here. "Here's why it changed. "And here's how actions we could take, or you could take." So this is where we focus on this, where nOps focuses on. We really help people to show the root cause analysis, these three, four things, these three, four changes are related to this cost increase or these security issues. And we show like a clear path on taking action on those issues. >> That's critical. The ability to show the paths, to take the action to remediate or make any changes, course corrections. As we've learned in the last 18 months, real time is no longer for so many industries, a nice-to-have. The ability to be able to pivot on the fly is a survival and thriving mechanism. So that is really key. I do want to talk about the relationship with nOps and AWS. Here we are at the AWS startup showcase. Give me a little overview on the partnership. >> It's been an incredible. Like I said, I have a long history of working with AWS, and I started a consulting company, a very, very successful one. And so I have years of working with AWS partner teams. I think it's incredible. We were the first company in this, maybe not first, maybe very early. We were part of this Well-Architected framework. And when I came out of that training, the Well-Architected training, I was so excited. I was like, "Wow, this is amazing." You know? Because, to me, whenever you're building infrastructure, you really are making trade-offs. You know, sometime you optimize for cost, sometime you optimize for reliability. So it has been incredible to work with the Well-Architected team. Or Amazon also has this, another program, called FTR: Foundational Technical Review. We've been working closely with that team. So yeah, it's been amazing to collaborate with AWS. >> It sounds pretty synergistic. Have you had a chance influence infrastructure, and some of the technical direction? >> Oh, absolutely. Yeah. We work very closely. One of the cool thing about AWS is that they do take customers' feedback very, very seriously. And, Lisa, also other way around. Right? If AWS is going to build something, having that insight into the roadmap is very beneficial. Because if they're doing it, there's no point of us trying to reinvent the wheel. So that kind of synergy is very helpful. >> That's excellent. Let's talk about customers, now. I always loved talking about customer use cases and outcomes. You guys have a great story with Uber. Walk us through what the challenges were, how nOps came in, what you deployed, and how the business is being impacted positively. >> Yeah, I think Uber and all the enterprises, they sort of have the same challenge, right? There are many teams provisioning infrastructure. How do you make sure all those resources are aligned with your business needs? And in addition to that, not only you have different teams provisioning resources, there are different workloads. And these workloads have different requirements. Right? Some are production workloads, some are just maybe task workloads. So one of the things Uber did, they really embraced sort of nOps' way of managing infrastructure, building accountability, sharing these dashboards with all the different teams. And it was incredible, because within first 30 days they were able to save up to 15%. This was in their autonomous vehicle unit. And they spent a lot of money. And having to see that kind of cost saving, it was just amazing. And we see this over and over. And so like when customers are using platform, it's just incredible how much cost savings are there. >> So Uber, you said, in their autonomous vehicle department saved 15% in just the first 30 days alone. And you said that's a common positive business outcome that you're seeing from customers across industries, is that immediate cost savings. Tell me a little bit more about that as a differentiator of nOps' business. >> Yeah. Because as I mentioned earlier, one of the things we do, we bring accountability. Right? Most of the time when people, before nOps, maybe there are resources that are not accounted for. There is not clear owners, there's no budgets, there's no chargebacks. So I do think that's a huge differentiator of nOps, because, as part of onboarding, as you establish these roles and these responsibilities, you find so much unaccounted resources. And sometimes you don't even need those resources, and you shut them down. And those are the easiest next steps. Right? Like, you don't need to architect, you just shut it down. Like no one needs these resources. So that, I do believe, that's our strength. And we were able to demonstrate this over and over, this, on average, 15-30% cost saving in the first month or so. >> That's excellent. That's a lot of what customers, especially these days, are looking for, is cost optimization across the organization. What are some of the things that you've seen, that nOps has experienced in the last 18 months, with so much acceleration? Anything that surprised you, any industries that you see as really leading edge here, or prime candidates for your technology? >> Yeah. A couple of things. We see a lot of partners, a lot of other consulting company, leveraging nOps as a part of their offering. That's been amazing, we have a lot of partners who really leverage nOps as a go to market and ongoing management of their customers. And I do see that shift from the customer side as well. I think the complexity of cloud continues to kind of increase, like you just mentioned, it sounds like from last 18 months, it accelerated even more. How do you stay up to date, you know? And how do you always make sure that you're following best practices? So companies bring in partners to help them implement solutions. And then these partners are leveraging tools like nOps. And we've seen a lot of momentum around that. >> Tell me a little bit about how partners are leveraging nOps. What are some of the synergistic benefits on both sides? >> Yeah, so normally partners leverage nOps, you know, they will use it for Well-Architected assessments. And, you know, I've personally done a lot of these Well-Architected assessments. And, you know, early on, I kind of learned that, assessments are only good if you're able to move forward with fixing issues in the customer's environment. So what we really do, we really help customers, or sorry, we really help partners to actually do these Well-Architected assessments automatically. We auto discover issues, and then we help them to create proposals so they can present it to the customers like, "Hey, here are the five things we can help you with, "and here's how much it will cost." And, you know, we really streamline that whole process. And it's amazing that some partners used to take like days to do these assessments. Now they can do it an hour. And we also increase the close rate on SoW's because they are a lot more clear. You know, like here are the issues and here's how we can help you to fix those issues. >> You got some great business metrics there, in terms of speed and reduction in cost, reduction in speed. But it sounds like what you're doing is helping those partners build a business case for their customers far more efficiently and more clearly than they've ever been able to do before. >> Absolutely. Yeah, yeah. And... >> Go ahead. >> Yeah, so absolutely. Before nOps, everyone is using spreadsheets most of the time. Right? It's spreadsheets to collect information, and emails back and forth. And after the partner's start using nOps, they use nOps to facilitate these assessments. And once they have these customers as ongoing customers, they use nOps for checks and balances to make sure they're constantly aligned. Right? And we have a lot of success of having real revenue impact on partners' business, by leveraging nOps. >> Excellent. That's true value and true trust there. Last question. Where can you point folks, a CTA or URL that you want people to go to to learn more about nOps? >> Yeah. Basically just go to nops.io and just put on signup. Yeah. I love doing this stuff. I love talking to the customers. Feel free to reach out to me, as well: jt@nops. I would love to have a conversation. But yeah, just nops.io is the best place to get started. >> Awesome, nops.io. And I can hear enthusiasm for this, and your genuineness comes through the zoom screen here, JT. I totally thought that the whole time. Thank you for talking to me about nOps, how you guys are helping organizations really embrace cloud ops and evolve from traditional cloud management tools. We appreciate your time. >> Thanks, Lisa. >> For JT Giri, I'm Lisa Martin. You're watching the AWS Startup Showcase.

>>mhm >>Hello and welcome to this cube conversation here in Palo alto California, I'm john for a year host of the cube, we're here with a great guest Jt gear, Ceo and founder and ops Hot Startup. Jt Welcome to the cube conversation. >>Hey, that sound, thanks for having me. It sounds like we know each other, we used to run into each other at meat out. So yeah, >>it's fun to talk to you because I know you're, you know, scratching the devops it from the beginning before devops was devops before infrastructure of code was infrastructure as code. All that's played out. So it's really a great ride. I know you had a good time doing it a lot of action though. If you look at devops it's kind of like this new, I won't say devops two point because it kind of cliche but you're starting to see the mature ization of companies besides the early adopters and the people who are hardcore adopting and they realize this is amazing and then they? Re platform in the cloud and they go great, let's do more and next thing, you know, they have an operations issue and they got a really kind of stabilize and then also not break anything. So this is kind of the wheelhouse of what you guys are doing in ops reminds me of no ops, no operations, you know, we don't want to have a lot of extra stuff. This is a big thing. Take a but take them in to explain the company, you're what you guys stand for and what you're all about. >>Yeah, so you know, our main focus is more on the operation side, so, you know the reason why you move to cloud or the reason why you have devops practices, you want to go fast. Um but you know when you're building cloud infrastructure, you have to make trade offs right? You have to maybe some environment, maybe you have to optimize for S L A. And maybe another workload, you have to optimize for um you know, maybe costs, right? So what we're on a mission to do is to make sure that companies are able to make the right trade offs, right? We help companies to make sure all their workload, every single resource in the cloud is aligned with the business needs, you know, so we do a lot of cool things by like, you know, bringing accountability mapping and we're close to different genes. But yeah, the end goal is, can we make sure that every single resource on data Bs is aligned with the business needs >>and they're also adding stuff. Every reinvent zillion more services get announced. So a lot, a lot of stuff going on, I gotta ask you while I got you here, what is the definition of cloud apps these days, from your standpoint and why is it important? A lot of folks are looking at this and they want to have stable operations. They love the cloud really can't deny the cloud value at all. But cloud ops has become a big topic. What is cloud apps and why is it important. >>Right? I mean, first of all, Like you just mentioned, right? Like Amazon keeps on launching more services. It's over 200. So the environment is very complex, Right? And then mm complexity within the services is uh pretty uh you really need to be the main expert for example, know everything about do So, you know, our question to us is, let's say if you find a critical issue, uh let's say you want to uh you know, enable multi AZ on your RDS for example. Uh and it's critical because you know, you're running a uh high availability workloads on AWS. How do you follow up on that right to us. Operation is how do you build a cloud backlog? How do you prioritize, how do you come together as a team to actually remediate those issues? No one is tackling that job, everyone's surfaces like, hey, here's 1000 things that are wrong with your environment. No one is focused on like how do you go from these issues to prioritization to backlog to actually coming together as a team. You know, I've been fixing some of those issues. That's that's what operation means is >>I know it's totally hard because sometimes I don't even know what's going on. I gotta ask you why, why is it harder now? Why are people, I mean I get the impression that people like looking the other way? I hope it goes the problem kind of goes away. What are the challenges? What's the big blocker from getting at the root cause or trying to solve these problems? What's the big thing that's holding people back? >>Yeah, I mean, when I first got into, you know, I t you know, I was working in data center and every time we needed a server, you know, we have to ask for approvals, right? And you finally got a server, but nowadays anyone could provision resources. And normally you have different people within the team's provisioning resources and you can have hundreds of different teams who are provisioning resources. So the complexity uh and the speed that we are, you know, provisioning resources across multiple people, it just continues to go higher and higher. So that's why uh you know, on the surface it might look that hey, this, you know, maybe the biggest instance uh is, you know, aligned with the business needs, you know, looking at the changes, it's hard to know, are those aligned with the business? They're not? So that's that's that's where the complexity and player. >>So the question I get a lot from people we talk about devops and cloud, cloud apps or cloud management or whatever kind of buzz words out there, it kind of comes down to cloud apps and cloud management seems to be the category, people focus on. How is cloud ops different then? Say the traditional cloud management and what impact does it have for customers and why should they care and what do they need an option. >>Right. So one of the things we do uh and and we do think that cloud operation is sort of an evolution from cloud management. We make sure that Every single resource 1st, first of all blondes and workload. So and you know, workload could be a group of microservices uh and then uh you know every single workload has owners like define owners who are responsible for making sure they managed budget that they're responsible for security that normally doesn't exist. Right? Cloud is this black box, you know where multiple people are provisioning resources, you know, everyone tries to sort of build sort of a structure to kind of see like what are these resources for? What are these resources for as part of onboarding to end up? So what we do, we actually, you know, analyze all your metadata. We create like 56 workloads and then we say here is a bucket where there's there, this is totally unassigned, right? And then we actually walked them through assigning different roles and also we walk them through to kinda looking under this unallocated resources and assign resources for those as well. So once you're done, every single resource has clear definition, right? Is this a compliant? Uh you know hip hop workload, what are the run books, what is this for? John I don't know if he heard that before. Sometimes there are workloads running and how people don't know, I don't even know who is the owner, right? So after you're done with an office and after you're managing and uh, you know, uh, managing your workload on and off, you have full visibility and clear understanding of what are the. It's funny, it's >>funny you mentioned the workloads being kind of either not knowing the owners, but also we see people um, with the workloads sometimes it's like throwing a switch and leaving the hose on the water on. And next thing you know, they get the bill. They're like, oh my God, what happened? Why did I leave? What, what is this? So there's a lot of things that you could miss. This brings up the point you just said and what you said earlier aligning resources across the cloud uh and and having accountability. And then you, you mentioned at the top of this interview that aligning with the business needs. I find that fastest. I would like to take him in to explain because it sounds really hard. I get how you can align the resources and do some things, identify what's going on, accountability kind of map that that's, that's good tech. How does that, how do you get that to the alignment on the business side. >>Yeah. I mean we start by, first of all, like I said, you know, we use machine learning to play these workloads? And then we asked basic questions about the workload. You know, what is this workload for? Uh Do you need to meet with any kind of compliance is for this workload? Uh What is your S. O. A. For this workload? You know, depending on that. We we make recommendations. Uh So we kind of ask those questions and we also walk them through where they create roles. Like we asked who was responsible for creating budgets or managing security for this workload and guess what also the you know the bucket where resources are allocated for. We ask for you know, owners for that as well like in this bucket who's the owner for who's going to monitor the budget and things like that. So you know we asked, you know, we start by just asking the question, having teams complete that sort of information and also you know, why do you a little bit more information on how this aligns with the business needs? You know, >>talk about the complexity side of it. I love that conversation around the number of services. You said 200 services depending how you count what you call services in the thousands of so many different things uh knobs to turn on amazon uh web services. So why are people um focused on the complexity and the partnering side? Because you know, it's the clouds at E. P. I. Based system. So you're dealing with a lot of different diverse resources. So you have complexity and diversity. Can you talk me through how that works? Because that's that seems to be a tough beast to tame the difference between the complexity of services and also working with other people. >>Yeah for sure like this this normal to have um you know maybe thousands of lambda functions in their application. We're working with a customer where within last month there were nine million containers that launched and got terminated right there, pretty much leveraging, auto scaling and things like that. So these environments are like very complex. You know, there's a lot of moving pieces even, you know, depending on the type of services they're using. So again what we do, you know we when we look at tags and we look at other variables like environments and we look at who's provisioning resources, those resources and we try to group them together and that way there's accountability uh you know if the cost goes up for one workload were able to show that team like your cost is going up uh And also we can show uh unallocated bucket that hey within last week Your cost is you know, $4,000 higher in the unallocated bucket. Where would you like to move this these resources to just like an ongoing game. You >>know, you know jt I was talking with my friend jerry Chen is that Greylock partners is a V. C. Has been on the cube many times a couple of years ago. We're talking about how you can build a business within the cloud, in the shadows of the clouds, what he called it, but I called it more the enabling side and and that's happened now, you're seeing the massive growth. I'm also talking to some C X O C IOS or CSOs and they're like trying to figure out which companies that are evolving and growing to be to buy from, get to get the technology. Uh and they always say to me john I'm looking for game changing kind of impact. I'm looking for the efficiency and you know, enablement, the classic kind of criteria. So how would you guys position yourself to those buyers out there that might want to look at you guys as a solution and ups what game changing aspect of what you do is out there, how would you talk to that that C I O or C. So or buyer um out in the end the enterprise and the thieves ran his piece. What would you say to them? >>Yeah, I think the biggest uh advantage and I think right now it's a necessity, you hear these stories where, you know, people provision resources, they don't even know which project is it for. It's just very hard to govern the cloud environment, but I believe we're the only tool. Mhm where you want to compromise on the speed, right? The whole reason um cloud but they want to innovate faster. No one wants to follow that. Right? But I think what's important. We need to make sure everything is aligned with the business value. Uh, we allow people to do that. You know, we, we, we can both fast at the same time. You can have some sort of guard rails. So there are proper ownership. There's accountability. People are collaborating and people are also rightsizing terminating resources, they're not using. It's like, you know, I think if companies are looking for a tool that's gonna drive better accountability on how people build and collaborate on cloud, I think reply the best solution. >>So people are evolving with the cloud and you mentioned terminating services. That's a huge deal in cloud. Native things are being spun up and turned off all the time. So you need to have good law, You have a good visibility, observe ability is one of the hottest buzzwords out there. We see a zillion companies saying, hey, we're observe ability, which is to me is just monitoring stuff. They can sure you're tracking everything. So when you have all this and you start to operationalize this next gen, next level cloud scale, cost optimization and visibility is huge. Um, what is the, what is the secret sauce uh, for that you guys offer? Because the change management is a big 12 teams are changing too cost team accountability. All this is kind of, it's not just speeds and feeds, there's, it's kind of intersection of both. What's your take on that reaction to that? >>Yeah, I think it's the Delta. Right? So change management, What you're really looking for is not a, like a fire hose, you're looking for. What changed what the root cause who did it, what happened? Right. Because it's totally normal for someone to provision maybe thousands or even millions containers. But how many of those got shut down? What is the delta and uh, you know, if there is a, there is an anomaly, what is the root cause? Right? Uh, how we fix it. So you know the way we've changed managers, change management is a lot different. We really get to the root cause analysis and we really help companies to make, really show what changed and how they can take action to a media. But if there were issues, >>I want to put a little plug in for you guys. I noticed you guys have a really strong net promoter score. You have happy customers also get partners. A lot of enablement there. You kind of got a lot of things going on. Um, explain what you guys are all about. How did you get here? What's the day in the life of a customer that you're serving? Why then why are the scores so high? Um, take us through a use case of someone getting that value. >>Yeah. So I, I come from like a consulting background, john so you know, I was migrating companies to read the Bs when the institute was in beta and then I, you know, founded a consulting company over 100 employees. Really successful interview. S premier partner called in clouds. And so Enos was born there because because you know it was, it was born out a consulting company, there are a lot of other partners who are leveraging the tools to help their customers and it goes back to our point earlier, john like amazon has to wonder services, right? We are noticing customers are open to work with partners and uh you know with different partners that really helped them to make sure they're making the right decisions when they are building on cloud. So a lot of the partners, a lot of the consulting companies are leveraging uh and hopes to deliver value to their customers as far as uh you know how we actually operate. You know, we pay attention to uh you know what, what customers are looking for, what, where are the next sort of challenges uh you know, customers are facing in a cloud environment world like super obsessed, you know, like we're trying to figure out how do we make sure every single resource is aligned with the business value without slowing companies down so that really drives us, we're constantly welcome customers to stay true to the admission >>and that's the ethos of devops moving fast. The old quote Mark Zuckerberg used to have move fast, break stuff and then he revised it to move move fast and make it stable, which is essentially operational thing. Right, so you're starting to see that maturity, I noticed that you guys also have a really cool pricing model, very easy to get in and you have a high end too. So talk us through about how to engage with you guys, how do people get involved? Just click and just jump in there, buying software buying services, take a minute to explain how people can, can work with you. >>Yeah, it's just, it's just signing up on our site, you know, our pricing is tier model, uh you know, once you sign up, if you do need help with, you know, remediating high risk issues we can bring in partners, we have a strong partner ecosystem. Uh we could definitely help you do interviews to the right partners but it's as simple as just signing up and just taking me out. First thing I guess. >>Jt great chatting with you have been there from early days of devops, born in the field, getting, getting close to the customers and you mentioned ec two and beta, they just celebrate their 15th birthday and I remember one of my starts that didn't actually get off the off the blocks, they didn't even have custom domains at that time was still the long remember the long you are else >>everything was ephemeral like when you restart server, everything will go away a cool >>time. And I just remember saying to myself man, every entrepreneur is going to use this service who would ever go out and buy and host the server. So you were there from the beginning and it's been great to see the success. Thanks for coming on the cube >>all That's >>okay. Jt thanks so much as a cube conversation here in Palo alto. I'm john for your host. Thanks for watching. Mhm.

>>from >>Around the globe, it's the cube with digital coverage of IBM think 2021 brought to you by IBM. >>Welcome back to IBM Think 2021 we're gonna dig into the intersection of finance and business strategy. My name is Dave Volonte and you're watching the cubes continuous coverage of IBM thinking with me is brian Hoffman is the chief operating officer of IBM Global financing, brian, thanks for coming on the cube today. >>Good morning, Great to be here. >>Hey, good morning. So I think we've heard a lot about the impact of hybrid cloud ai digital transformation and I wonder as a finance person in a former CFO, what do you see? And how do you think about some of the key considerations and financials and strategies that are supporting these major projects? Right? We got to come to the CFO and say, hey, we want to spend some money and here's the benefit, here is the cost. How can see IOS and their teams work with CFOs to try to really accelerate that digital transformation. >>Great question. And actually that question, I think I might have answered it a little bit differently, like two years ago, a year ago before the pandemic, I think it's actually changed a little bit with pandemic in my experience is the CFO people would come into me for projects and there's three ways you can justify it, but you can justify short term immediate, quick payback kind of hitters, you can justify it with, you know, improving our efficiency or effectiveness, um you know, reducing costs in the long run, making the client experience better or more from a strategic point of view, um you know, growing revenue getting to new clients, improving margins right? And so the the hybrid cloud transformation journey really still addresses those three things and when we come in, a lot of people focus like I said, on that third strategic point, but but all three of those come into play, and what's really interesting now is is as I'm dealing with it, I'm talking to other Cfos. The pandemic is really, if you will throw in a wrinkle in here, right? So the clients that I'm talking to, the IBM clients, they have to operate their business very differently and and their business models, some of them are changing clearly. Their clients, their business models are changing their operating differently as well. Um So, so our clients have to react to that and Hybrid Cloud and that that that type of of a structure really can support that. So there's really an emphasis here now to act with much more speed on this journey to get moving on it to get there because you have to make these changes and doing those two things in concert really has a ton of business value. >>Yeah I mean the cfos that I've talked to in the C. I. O. S. It's really kind of industry dependent, right? If you're in airlines or hospitality was like uh we got to cut costs. A lot of organizations said okay we're gonna support remote workers put in V. D. I. Or deal with endpoint security or whatever it was. But we're actually gonna double down on our digital transformation. This is we're gonna lean into an opportunity for us to come out stronger. How did you guys approach it in terms of your own internal digital >>transformation? Yeah. We we we were working on our digital transformation uh a little bit before the pandemic and it kind of followed those those three uh those three items when they when they first started implementing it, they came in and said hey if we can if we can move to a cloud platform, our infrastructure savings will be pretty significant. You know the I. T. Infrastructure savings will be 30 to 40%. So you know, quick payback CFO types love that. So you know, we went forward with that. Um but then quickly we saw the real benefits of moving to a hybrid cloud strategy. So just as an example as we were making some of these changes, we found a workflow tool in one of our markets in europe, that was a great tool and uh if we wanted to implement that across the business um in the old days, You know, we're in 40 countries, we've got 2500 employees, three lines of business. It would have been very complex because our operating structure is is very robust, very complex. Um Probably have taken a year, two years to do that. But since we are now on a cloud platform we got that rolled out that workflow tool rolled out across our business in months, Saving 20-30 of of workload. Being much more um efficiently getting to our clients and reacting quickly to them. And in fact that tool got adopted across IBM because that cloud platform enabled that to happen. And then the great thing which I didn't even realize at the time but now thinking more strategically um are my I. T. Resource earlier was running at about 50 50 50 people working on maintenance. The kind of things with 50 on development as we've now transition to this cloud. My I. T. Resources now 70 plus percent dedicated to new development. So now we can go attack new things that really provide customer value in the pandemic. You know the first thing to look at is can we get into more um you know electronic contracts, E signatures, things that would provide value to customers anyway. But in the pandemic is like really a significant, you know differentiator for us. So all those things were enabled by that journey that we've been taking, >>interesting. I mean most of the CF I uh in fact every CFO I know of a public company took advantage of cheap debt and improving their balance sheets. And liquidity is not the problem today, especially in the tech industry at the same time. You know I'm interested in how companies are using financing. They don't want to necessarily build out data centers but they do want to fund their digital transformation. So what are you seeing in terms of how your customers are using financing? You know, what's the conversation like? What advice are you giving? >>Yeah. So um you know, it depends a little bit on the type of customer, like you said, you know, we we deal with a lot of the biggest, strongest customers in the world. And, and as we deal with them, financing really helps the return on their investment, right, aligning the payments of those cash flows for when they're getting the benefits. Uh And and we see a real good value in improving the return on those investments in helping, you know, if it's something that's going to go to the board that really makes a difference to them. Uh So, you know, that that's always been a value proposition. It continues to be. Um The other thing that's helping now, like you said, is even in this environment, people want to accelerate this transition. Um but it's a, it's a, it's a big time of uncertainty. So, you know, some of the smaller clients, some of the more uh you know, the industries that are a little more cash constrained airlines, et cetera, you know, they're looking for the the immediate cash flow benefits. Um But many of the cfos are saying, hey, listen, you know, I can I want to go as fast as I can help me put together a structure that lets me, you know, get this in place as quick as possible, but not below my budget is not make me take too much risk in this time of uncertainty, but keeps me moving and I think that's where financing really comes in as well. Um And we're kind of talking much more about that value proposition than just if you will be improved ri proposition that we've had all along. >>I want to talk a little bit more about IBM global financing. I mean, people, a lot of times people misunderstand it. You know when you look at I. B. M. S. Debt, you gotta you gotta take out the piece that IBM global financing because that's a significant portion and that's sort of self self fulfilling. But what do people need to know about IBM global financing, >>We actually run three different businesses and we've been transforming our strategy over time. So you know right now with with IBM being all in on hybrid, we are very focused on helping IBM and IBM clients on this digital journey on IBM growing their revenue. Um you know, we we in the past have been more of if you're really full service. It finance are doing a lot more than just IBM but we are really focused now on on helping IBM. So I think the best thing for for IBM clients to know is as you're talking to IBM about the total solution, the total value profit IBM brings that financing, that cash flow solution should be embedded in what they're looking at and can provide a lot of value. Um You know, the second thing I think most people know is we provide financing for IBM s channel, so you know, distributors, resellers etcetera, if you're an IBM distributor or reseller, you know about us, because just about 100% of IBM partners use us to provide that working capital financing, uh you know, we have a state of the art platforms were just so integrated with them. Again, I don't have to I don't have to do a sales pitch on that because they don't know us. Um and the third one just because people might not realize this is, we do haven't we call it an asset recovery business, um it's a pretty small business, you know, it's bringing back equipment that comes off lease, so that uh is used by IBM internally. Um and while, you know, it's not, it's not as well known, I'm pretty proud of it because it really does help with the focus that the world that IBM has on sustainability and reuse and um and making sure that, you know, we're treating the planet fairly here, so that that's a small but powerful piece of our business well, >>You're quite broader than leasing mainframes in the 80s, >>that's for sure. >>Talking more about give, you can double click on that sort of hybrid cloud and obviously machine intelligence is a big piece of those digital transformation. So, so how specifically are you, are you helping clients really take advantage of things like hybrid cloud? >>So yeah, so um what we have typically had been doing and I can give you a couple different examples if you will, you know, for larger clients. What we tend to be doing is helping them like I said, accelerate their business. So um, you know, they're looking to modernize their applications but they still have a big infrastructure in place and so they'll run into uh you know, budget constraints and and you know, cash is still be careful to managed. So for them we are much more typically focused on, you know, if you will project based financing that allows those cash flows to line up with the savings. Again, those are tend to be bigger projects that often go to boards that return benefit is very important. Ah a little bit different value proposition for more mid market customers. So, you know, as I was kind of just looking recently, we have a couple of different customers like form engineering um or or Novi still there to smaller uh compared to some of the other customers we use uh they are again much more focused on how do I, how do I conserve and best use my cash immediately? But they want to get this, they want to get this transformation going. So you know we provide flexible payment plans to them so they can go at the rate and pace that they need to, they can align up those cash deals with their budgets for their business cycles etcetera. So again, where smaller customers where timing of the cash flow in their business cycle is very important. We provide that benefit as well. >>You know, I wonder if I could ask you. So you remember of course the early days of public cloud, one of the first tail winds for public cloud was the pen was not the pandemic, the for the financial crisis of 2007. And a lot of CFO said, Okay let's shift to uh to an apex model. And now you can always provide financial solutions to customers. But it seems like today when I talk to clients, it's it's much more integrated, it's not just the public cloud, you can do that for on premises and again you always could do that. But it seems like there's much more simpatico uh in the way in which you provide that that that solution is that >>fair? Absolutely. And this might be a little to finance geeky, I don't know. But if you go back, well if you go back to the financial crisis and all that and at that time um a lot of people were looking to financing for you call that ah please. But you know if if I was talking about off balance sheet transactions right? Um and and you know between regulation etcetera etcetera, that that off balance sheet thing. First of all, people are seeing through it that much more clearly. But second, you know the the uh financial disclosure say you kind of have to show that stuff so that that if you will, window dressing benefit has gone away. So now which is great for me, we really get to talk about what's the real benefit, what is the, you know, what is the real benefit of? You know, you want to make sure that you have known timed expenditures. You know that if your business grows that your your expenses can grow evenly with those with that business growth, you don't have to take big chunky things and so you know uh financing under the covers of an integrated solution and IBM has a lot of those integrated solutions allows businesses to have that, you know, known timing known quantities. Most of the benefits that people were looking for from that affects cloud model. Um without, you know, some of the problems that you have, when you try to have to go straight to a public cloud for very, you know, big sensitive businesses, confidential confidential data etcetera. >>Thanks for that. So, okay, we're basically out of time. But I wonder if you could give us the bumper sticker and key takeaways, maybe you could summarize for our audience. >>Yeah. For those that noah global financing or dealing with IBM, my view would be in the past we might have been a little more, you know, out there with our own with our own banner etcetera. In the future. I think that you should expect to see us very well integrated into anything you're doing. I think our value proper is clear and compelling and and and will be included uh in these hybrid con transformations to the benefit of our clients. So that's that's our objective and we're well on our way there. >>Great. Anywhere, anywhere I'm gonna go for more, more familiar, obviously IBM dot com. You got some resources there. But there is >>there any Absolutely dot com? There's there's a thank you. Just probably a slash financing. But yeah, there's >>were >>loaded with information of people. >>Excellent brian thanks so much for coming to the cube. Really great to have you today. >>I appreciate the time. >>My pleasure. Thank you for watching everybody's day. Volonte for the Cuban. Our coverage of IBM think 2021, the virtual edition right back.

>>From the cubes studios in Palo Alto, in Boston, connecting with thought leaders all around the world. This is a cute conversation. >>The external storage array business, as we know it has changed forever. You know, you can see that in the survey data that we do and the financial information from the largest public storage companies. And it's not just because of COVID, although that's clearly a factor which has accelerated the shifts that we see in the market, specifically, those CIO is, are rationalizing their infrastructure portfolios by consolidating workloads to simplify, reduce costs and minimize vendor sprawl. So they can shift resources toward digital initiatives that include cloud containers, machine intelligence, and automation all while reducing their risks. Hello everyone. This is Dave Vellante and welcome to this cube conversation where we're going to discuss strategies related to workload consolidation at petabyte scale. And with me is Dr. Rico. He's the vice president office of the CTO at INFINIDAT welcome back to the cube doc, always a pleasure to see you >>And great to be here. Always a pleasure to work with you, Dave. >>So doc, I just published a piece over the weekend and I pointed out that of the largest storage companies, only one showed revenue growth last quarter, and that was on a significantly reduced compare with last year. So my first question to you is, is INFINIDAT growing its business. >>Oh, absolutely. It's been a very interesting year all across as you can quite imagine. Um, but you know, our footprint is such that with our elastic pricing models and the, and the fact that we've got excess capacity, uh, in almost every single system that's out there, we were really given our customers a, an opportunity to take advantage of that, to increase their capacity levels while maintaining the same levels of performance and availability, but not have to have anybody on premises during this crazy, you know, COVID struck era. >>Yeah. So you're bringing that cloud model to the, to the data center, which has obviously been a challenge. I mean, you mentioned the subscription sort of like pricing, we're going to get into the cloud more, but I wonder if we could step back a little bit and look at some of the macro trends that you're seeing in the market and specifically as it relates to on-prem storage strategies that CEO's are taking. >>Yeah. You know, it's been interesting, we've seen over the course of the past five years or so, certainly a big uptick in people looking at next generation or what they believe in perceived to be next generation storage platforms, which are really just evolutions of media. They're not really taking advantage of any new innovations in storage and, you know, not withstanding our own products, which are all software driven. We've talked about that before, but what what's really happened in this past year, as you, as you said, CEOs and CTOs, they're always looking for that, that next point of leverage advantage. And they're looking for more agility in application deployment, they're looking in a way to rapidly respond to business requirements. So they're looking very much at those cloud-like requirements. They're looking at those capabilities to containerize applications. They're looking at how they can, um, you know, shift out virtual machines if they're not in a directly in a container, uh, and how the storage by the way, can, can have the same advantage and in order to do so, they really need to look at storage consolidation. You know, I think Dave, to, to sum it up from the storage perspective, you know, I love Ken Steinhardt was recently on a video and, you know, he was, he was challenged that, you know, people aren't looking at spinning rust, riff, you know, a derogatory wave of referring a disc and, and Ken, so rightly and accurately responded. Yeah. But people weren't really looking for QLC either. You know, what they're looking for is performance, scale availability and certainly cost effectiveness and price. >>Yeah. It was like, I set up front dock. I mean, if you're a C level executive today, you don't want to worry about your storage infrastructure. You've got bigger problems to worry about. You just want it to work. And so when you talk about consolidating workloads, people often talk about the so-called blast radiation. In other words, people who run data centers, they understand that things fail. And sometimes something as simple, it might be a power supply can have a catastrophic downstream effect on application availability. So my question is, how do you think about architecting systems? So as to minimize the effects of component failures on the business? >>Yeah. You know, it's a very interesting term, Dave blast radius, right? We've, we've heard this referred to storage over the last several decades. In fact, when it really should refer to the data center and the application infrastructure. Uh, but you know, if we're talking about just the storage footprint itself, one of the things that we really need to look, look at is the resilience and the reliability of the architecture. And when you look at something that is maybe dual controller single or double power supply, there are issues and concerns that take in, in, into, into play. And what we've done is we've designed something that's really triple redundant, which is typically only been applied to the very high end of the market before. And we do it in a very active, active, active manner. And naturally we have suggestions for best practices for deployment within a data center as well, you know, multiple sources of power coming into the array and things of that nature. But everything needs to be this active, active, active type of architecture in order to bring those reliability levels up to the point where as long as it's a component failure within the array, it's not going to cause an outage or data on availability event. >>Yeah. So imagine a heat map when people talk about the blast radius. So imagine the heat map is green. There's a big, you know, there's a yellow area and there's a, there's a red area. And what you're saying is, as far as the array goes, you're essentially eliminating the red area. Now, if you take it to the broader installation, you know, that red area, you have to deal with it in different ways, remote replication, then you can at the sink and in a sink. Uh, but, but essentially what I'm hearing you say, doc, is, is you're squeezing that red area out. So, so your customers could sleep at night. >>That absolutely sleep at night is so appropriate. And in fact, we've got a large portion of our customer base is, or they're running mission critical businesses. You know, we have some of the most mission critical companies in our, in our logo portfolio, in the world. We also have, by the way, some very significant service provider businesses who were we're providing, you know, mission critical capabilities to their customers in turn, and they need to sleep at night. And it it's, you know, availability is only one factor. Certainly manageability is another cause you know, not meeting a service level is just like data unavailability in some respects. So making manageability is automatic as it can be making sure that the, that the system is not only self-healing, but can re respond to variations in workload appropriately is very, very critically important as well. >>Yeah. So that, that you mentioned mission critical workloads, and those are the, those are the workloads that let's face it. They're not moving into the cloud, certainly not in any, any big way, you know, why would they generally are CIO CTO is they're putting a brick wall around that saying, Hey, it works. We don't want to migrate that piece, but I want to talk more about how your customers are thinking about workload consolidation and rationalizing their storage portfolios. What are those conversations like? Where do they start and what are some of the outcomes that you're seeing with your customers? >>Yeah, I think the funny thing about that point Dave, is that customers are really starting to think about a cloud in an entirely different way. You know, at one point cloud meant public cloud and men, this entity, uh, outside the walls of the data center and people were starting to use services without realizing that that was another type of cloud. And then they were starting to build their own versions of cloud. You know, we were referring to them as private clouds, but they were, you know, really spread beyond the walls of a single data center. So now it's a very hybrid world and there's lots of different ways to look at it, hybrid cloud multi-cloud, whatever moniker you want to put on it. It really comes down to a consistency in how you manage that infrastructure, how you interface with that infrastructure and then understanding what the practicality is of putting workloads in different places. >>And practicality means not only the, you know, the latency of access of the data, but the costs associated with it. And of course the other aspects that we talked about, like what the, the availability metrics, and as you increase the availability and performance metrics, those costs go up. And that's one of the reasons why some of these larger mission critical data centers are really, you know, repatriating their, their mission, critical workloads, at least the highest, highest levels of them and others are looking at other models, for example, AWS outposts, um, which, you know, talked about quite a bit recently in AWS reinvent. >>Yeah. I just wrote, again, this weekend that you guys were one of the, uh, partners that was qualified now, uh, to run on AWS outpost, it's interesting as Amazon moves, it's, you know, it's, it's it's model to the edge, which includes the data center to them. They need partners that can, that really understand how to operate in an on-premise world, how to service those customers. And so that's great to see you guys as part of that. >>Yeah. Thank you. And, you know, it was actually a very seamless integration because of the power and capability of all of the different interface models that we have is they all are fully and tightly integrated and work seamlessly. So if you want to use a, you know, a CSI type model, uh, you know, do you interface with your storage again, uh, with, with INFINIDAT and, you know, we work with all of the different flavors so that the qualification process, the certification process and the documentation process was actually quite easy. And now we're able to provide, you know, people who have particularly larger workloads that capability in the AWS on premises type environment. >>Yeah. Now I implied upfront that that cloud computing was the main factor, if not the primary factor, really driving some of the changes that we're seeing in the marketplace. Now, of course, it's all, not all pink roses with the cloud. We've seen numerous public cloud outages this year, certainly from Microsoft. We saw the AWS Kinesis outage in November. Google just had a major outage this month. Gmail was down G suite was down for an extended period of time. And that disrupted businesses, we rely on that schools, for example. So it's always caveat emptor as we know, but, but talk to INFINIDAT cloud strategy, you mentioned hybrid, uh, particularly interested in, in how you're dealing with things like orchestration and containers and Kubernetes. >>Yeah, well, of course we have a very feature rich set of interfaces for containers, Kubernetes interfaces, you know, downloadable through native, uh, native. So they're, they're very easy to integrate with, you know, but our cloud strategy is that, you know, we are a software centric model and we, you know, all of the, all of the value and feature function that we provide is through the software. The hardware of infiniboxes really a reference architecture that we, uh, we deliver to make it easier for customers to enjoy say 100% availability model. But if, if you want to run something in a traditional on premises data center, you know, straighten InfiniBox is fine, but we also give you the flexibility of cloud-like consumption through our pricing models, our, our elastic pricing models. So you don't need to consume an entire InfiniBox day one. You can grow and shrink that environment with, uh, with an OPEX model, or you can, um, buy it as you consume it in a, in a cap ex model. >>And you can switch, uh, from OPEX over to CapEx if it becomes more cost effective for you in time, which I think is, is what a lot of people are looking for. If you're looking for that public cloud, we, you know, we have our new tricks cloud offering, which is now being delivered more through partners, but you know, some businesses and especially the, the mid tier, um, you know, the SMB all the way through the mid enterprise are also now looking to cloud service providers, many of which use InfiniBox as, as their backend. And now with AWS outposts, of course, you know, we can give you that on premises, uh, uh, experience of the public cloud, >>You guys were early on. And obviously in that, that subscription-based model, and now everyone's doing it. I noticed in the latest Gartner magic quadrant on, on storage arrays, which you guys were named a leader, uh, they, I think they had a stat in there and said, I, I forget what the exact timeframe was that 50% of customers would be using that type of model. And again, I guarantee you by whatever time frame, that was a hundred percent of the vendor community is going to be delivering that type of model. So, so congratulations on being named a leader, I will say this there's there's there's consolidation happening in the market. So this, to me, this bodes well, to the extent that you can guarantee high availability and consistent performance, uh, at, at scale, that bodes well for, for you guys in a consolidating market. And I know IDC just released a paper, it was called, uh, I got, uh, I got a copy here. >>It's called a checklist for, uh, storage, workload consolidation at petabyte scale. It was written by Eric Bergner, who I've known for a number of years. He's the VP of infrastructure. Uh, he knows his stuff and the paper is very detailed. So I'm not going to go through the checklist items, but I, but I think if you don't mind, doc, I think it's worth reading an excerpt from this. If I can, as part of his conclusions, when workload consolidation, it organizations should carefully consider their performance availability, functionality, and affordability requirements. Of course, few storage systems in the market will be able to cost effectively consolidate different types of workloads with different IO profiles onto a single system. But that is in INFINIDAT forte. They're very good at it. So that's a, that's quite a testimonial, you know, why is that your thoughts on what Eric wrote? >>Well, you know, first of all, thank you for the kudos on the Gartner MQ, you know, being a leader on the second year in a row for primary storage, only because that documents only existed for two years, but, uh, you know, we were also a leader in hybrid storage arrays before that. And, you know, we, we love Gardner. We think they're, they're, you know, um, uh, real critical, you know, reliable source for, for a lot of large companies and, and IDC, you know, Eric of course is, uh, he's a name in the industry. So we, you know, we very much appreciate when he writes something, you know, that positive about us. But to answer your question, Dave, you know, there's, there's a lot that goes on inside InfiniBox and is the neural cash capabilities, the deep learning engine that is able to understand the different types of workloads, how they operate, uh, how to provide, you know, predictable performance. >>And that I think is ultimately key to an application. It's not just high performance. It's, it's predictable performance is making sure the application knows what to expect. And of course it has to be performant. It can't just be slow, but predictable. It has to be fast and predictable providing a multi-tenant infrastructure that is, that is native to the architecture, uh, so that these workloads can coexist whether they're truly just workloads from multiple applications or workloads from different business units, or potentially, as we mentioned with cloud service providers, workloads from different customers, you know, they, they need to be segmented in such a way so that they can be managed, operating and provide that performance and availability, you know, at scale because that's where data centers go. That's where data centers are. >>Great. Well, so we'll bring that graphic back up just to show you, obviously, this is available on your website. Uh, you can go download this paper from Erik, uh, from IDC, www infinidat.com/ian/resource. I would definitely recommend you check it out. Uh, as I say, Ericsson, you know, I've been in the business a long, long time, so, so that's great, doc, we'll give you the last word. Anything we didn't cover any big takeaways you want to, you want to share with the audience? >>Yeah. You know, I think I'll go back to that point. You know, consolidation is absolutely key for, uh, not just simplicity of management, but capability for you respond quickly to changing business requirements and or new business requirements, and also do it in a way that is cost-effective, you know, just buying the new shiny object is it's expensive and it's very limited in, in shelf life. You're just going to be looking for the next one the next year. You want to provide something that is going to provide you that predictable capability over time, because frankly, I have never met a C X O of anything that wasn't trying to increase their profit. >>You know, that's a great point. And I just, I would add, I mean, the shiny new object thing. Look, if you're in an experimental mode and playing around with, you know, artificial intelligence or automation thinking, you know, areas that you really don't know a lot about, you know, what, check out the shiny new objects, but I would argue you're on-prem storage. You don't want to be messing around with that. That's, it's not a shiny new objects business. It's really about, you know, making sure that that base is stable. And as you say, predictable and reliable. So doc Terico thanks so much for coming back into cube. Great to see you. >>Great to see you, David, and look forward to next time. >>And thank you for watching everybody. This is Dave Volante and we'll see you next time on the queue.

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel, AWS and our community partners. >>Hello and welcome to the Cube virtual here with coverage of aws reinvent 2020. I'm your host, Justin Warren. And today I'm joined by J. Snyder, who is the chief chief customer officer at New Relic J. Welcome to the Cube. >>It is fantastic. Me back with the Cube. One of my favorite things to do has been for years. So I appreciate you having me. >>Yes, a bit of a cube veteran. Been on many times. So it's great to have you with us here again. Eso you've got some news about new relic and and Amazon away W s strategic collaboration agreement. I believe so. Maybe tell us a bit more about what that actually is and what it means. >>Yes. So we've been partners with AWS for years, but most recently in the last two weeks, we've just announced a five year strategic partnership that really expands on the relationship that we already had. We had a number of integrations and competencies already in place, but this is a big deal to us. and and we believe a big deal. Teoh A W s Aziz Well, so really takes all the work we've done to what I'll call the next level. It's joint technology development where were initially gonna be embedding new relic one right into the AWS management console for ease of use and really agility for anyone who's developing and implementing Ah cloud strategy, uh, big news as well from an adoption relative to purchase power so you can purchase straight through the AWS marketplace and leverage your existing AWS spend. And then we're gonna really be able to tap into the AWS premier partner ecosystem. So we get more skills, more scale as we look to drive consulting and skills development in any implementation for faster value realization and overall success in the cloud. So that's the high level. Happy to get into a more detailed level if you're interested around what I think it means to companies but just setting the stage, we're really excited about it as a company. In fact, I just left a call with a W S to join this call as we start to build out the execution plan for the next five years look like >>fantastic. So for those who might be new to new relic and aren't particularly across the sort of field of observe ability, could you just give us a quick overview of what new relic does? And and then maybe talk about what the strategic partnership means for for the nature of new relics business? >>Yes, so when I think about observe ability and what it means to us as opposed to the market at large, I would say our vision around observe ability is around one word, and that word is simplification. So, you know, I talked to a lot of customers. That's what I do all the time. And every time I do, I would say that there's three themes that come up over and over. It's the need to deliver a customer experience with improved up time and ever improving importance. It's the need to move more quickly to public cloud to embrace the scale and efficiency public cloud services have to offer. And then it's the need to improve the efficiency and speed of their own engineering teams so they can deliver innovation through software more quickly. And if you think about all those challenges And what observe ability is it's the one common thread that cuts across all those right. It's taking all of the operational data that your system admits it helps you measure improve the customer, experience your ability to move to public cloud and compare that experience before you start to after you get there. The effectiveness of your team before you deploy toe after you get there. And it's all the processes around that right, it helps you be almost able to be there before your there there. I mean, if that makes sense right, you'll be able to troubleshoot before the event actually happens or occurs. So our vision for this is like I talked about earlier is all about simply simplification. And we've broken this down into literally three piece parts, right? Three products. That's all we are. The first is about having a much data as you possibly can. I talked about admitting that transactional telemetry data, so we've created a telemetry data platform which rides on the world's most powerful database, and we believe that if we can take all of that data, all that infrastructure and application data and bring it into that database, including open source data and allow you to query it, analyze it and take action against it. Um, that's incredibly powerful, but that's only part one. Further, we have a really strong point of view that anybody who has the ability to break production should have the ability to fix production. And for us, that's giving them full stack observe ability. So it's the ability to action against all of that data that sits in the data platform. And then finally, we believe that you need to have applied intelligence because there's so many things that are happening in these complex environments. You wanna be able to cut through the noise and reduce it to find those insights and take action in a way that leverages machine learning. And that, for us, is a i ops. So really for us. Observe ability. When I talked about simplification, we've simplified what is a pretty large market with a whole bunch of products, just down to three simple things. A data platform, the ability to operationalize in action against that data and then layer on top in the third layer, that cake machine learning so it could be smarter than you can be so it sees problems before they occur. And that And that's what that's what I would say observe, ability is to us, and it's the ability to do that horizontally and vertically across your entire infrastructure in your entire stack. I hope that makes sense. >>Yeah, there's a lot of dig into there, So let's let's start with some of that operational side of things because I've long been a big believer in the idea of cloud is being a state of mind rather than a particular location on. A lot of people have been embracing Cloud Way Know that for we're about 10 or so years. And the and the size of reinvent is proven out how popular cloud could be. Eso some of those operational aspects that you were talking about there about the ability to react are particularly like that. You you were saying that anyone who could break production should be able to fix production. That's a very different way of working than what many organizations would be used to. So how is new relic helping customers to understand what they need to change about how they operate their business as they adopt some of these methods. >>Well, it's a great question. There's a couple of things we do. So we have an observe ability, maturity framework by which we employ deploy and that, and I don't want to bore the audience here. But needless to say, it's been built over the last year, year and a half by using hundreds of customers as a test case to determine effectively that there is a process that most companies go through to get to benefits realization. And we break those benefit categories into two different areas, one around operational efficiency and agility. The other is around innovation and digital experience. So you were talking about operational efficiency, and in there we have effectively three or four different ways and what I call boxes on how we would double, click and triple click into a set of actions that would lead you to an operational outcome. So we have learned over time and apply to methodology and approach to measure that. So depending on what you're trying to do, whether it's meantime to recover or meantime, to detect, or if you've got hundreds of developers and you're finding that they're ineffective or inefficient and you want to figure out how to deploy those resource is to different parts of the environment so you can get them to better use their time. It all depends on what your business outcome and business objective is. We have a way to measure that current state your effectiveness ply rigor to it and the design a process by using new relic one to fill in those gaps. And it can take on the burden of a lot of those people. E hate to say it because I'm not looking to replace any individual. It's really about freeing up their time to allow them to go do something in a more effective and more effective, efficient manner. So I don't know if that's answering the question perfectly, but >>e don't think there is a perfect answer to its. Every customer is a bit different. >>S So this is exactly why we developed the methodology because every customer is a little different. The rationale, though, is yeah, So the rationale there's a lot of common I was gonna say there's a lot of common themes, So what we've been able to develop over time with this framework is that we've built a catalog of use cases and experiences that we can apply against you. So depending on what your business objectives are and what you're trying to achieve, were able to determine and really auger in there and assess you. What is your maturity level of being able to deliver against these? Are you even using the platform to the level of maturity that would allow you to gain this benefit realization? And that's where we're adding a massive amount of value. And we see that every single day with our customers who are actually quite surprised by the power of the platform. I mean, if you think traditionally back not too far, two or even three years. People thought of new relic as an a P M. Company. And I think with the launch this summer, this past July with new relic one, we've really pivoted to a platform company. So while a lot of companies love new relic for a PM, they're now starting to see the power of the platform and what we can do for them by operationally operationalize ing. Those use cases around agility and effectiveness to drive cost and make people b'more useful and purposeful with their time so they can create better software. >>Yeah, I think that's something that people are realizing a lot more lately than they were previously. I think that there was a lot of TC analysis that was done on a replacement of FTE basis, but I think many organizations have realized that well, actually, that doesn't mean that those people go away. They get re tasked to do new things. So any of these efficiency, you start with efficiency. And it turns out actually being about business agility about doing new things with the same sort with the same people that you have who now don't have to do some of these more manual and fairly boring tasks. >>Yeah, just e Justin. If this if this cube interview thing doesn't work out for you were hiring some value engineers Right now it sounds like you've got the talk track down perfectly, because that's exactly what we're seeing in the market place. So I agree. >>So give us some examples, if you can, of maybe one or two off things that you've seen that customers have have used new relic where they've stripped out some of that make work or the things that they don't really need to be doing. And then they're turning that into new agility and have created something new, something more individual. Have you got an example you could share with us? >>You know, it's it's funny way were just I just finished doing our global customer advisory boards, which is, you know, rough and tough about 100 customers around the world. So we break it into the three theaters, and we just we were just talking with a particular customer. I don't want to give their name, but the session was called way broke the sessions into two different buckets, and I think every customer buys products like New Relic for two reasons. One is to either help them save money or to help them make money. So we actually split the sessions into those two areas and e think you're talking about how do we help them? How do we help them save money? And this particular company that was in the media industry talked at great length about the fact that they are a massive news conglomerate. They have a whole bunch of individual business units. They were decentralized and non standardized as it related to understanding how their software was getting created, how they were defining and, um, determining meantime to recover performance metrics. All these things were happening around them in a highly complex environment, just like we see with a lot of our customers, right? The complexity of the environments today are really driving the need for observe ability. So one of the things we did with them is we came in and we apply the same type of approach that we just discussed. We did a maturity assessment for them, and we find a found a variety of areas where they were very immature and using capabilities that existed within the platform. So we're able to light up a variety of things around. Insights were able to take more data in from a logging perspective. And again, I'm probably getting a little bit into the weeds for this particular session. But needless to say, way looked at the full gamut of metrics, events, logs and traces which was wasn't really being done in observe, ability, strategy, manner, and deploy that across the entire enterprise so created a standard platform for all the data in this particular environment. Across 5th, 14 different business units and as a byproduct, they were able to do a variety of things. One, the up time for a lot of their customer facing media applications improved greatly. We actually started to pivot from actually driving cost to showing how they could quote unquote make money, because the digital experience they were creating for a lot of their customers reduced the time to glass, if you will, for clicking the button and how quickly they could see the next page, the next page or whatever online app they were looking to get dramatically. So as a byproduct of this, they were about the repurpose to the point you made Justin. Dozens of resource is off of what was traditionally maintenance mode and fighting fires in a reactive capability towards building new code and driving new innovation in the marketplace. And they gave a couple of examples of new applications that they were able to bring to market without actually having to hire any net New resource is so again, I don't want to give away the name, the company, it maybe it was a little too high level, but it actually plays perfectly into exactly what what you're describing, Um, >>that is a good example of one of those that one of the it's always nice to have a specific concrete customer doing one of these kinds of things that you you describe in generic terms. Okay. No, this is this is being applied very specifically to one customer. So we're seeing those sorts of things more and more. >>Yeah, and I was gonna give you, you know, I thought about in advance of this session. You know, what is a really good example of what's happening in the world around us today? And I thought of particular company that we just recently worked with, which is check. I don't know if you're familiar with keg, if you've heard of them. But their education technology company based in California and they do digital and physical textbook rentals. They do online tutoring an online customer services. So, Justin, if you're like me or the rest of the world and you have kids who are learning at home right now, think about the amount of pressure and strain that's now being put on this poor company Check to keep their platform operational 24 77 days a week. So that students can learn at pace and keep up right. And it's an unbelievable success story for us and one that I love, because it touches me personally because I have three kids all doing online, learning in a variety of different manners right now. And, you know, we talked about it earlier. The complexity of some of the environments today, this is a company that you would never gas, but they run 500 micro services and highly complex, uh, technical architectural right. So we had to come in and help these folks, and we're able to produce their meantime to recover because they were having a lot of issues with their ability to provide a seamless performance experience. Because you could imagine the volume of folks hitting them these days on. Reduce that meantime to recover by five X. So it's just another example we're able to say, you know, it's a real world example. Were you able to actually reduce the time to recover, to provide a better experience and whether or not you want to say that saving money or making money? What I know for sure is is giving an incredible experience so that folks in the next generation of great minds aren't focused on learning instead of waiting to learn right, So very cool. >>That is very cool. And yes, and I have gone through the whole teaching kids >>about on >>which is, uh, which it was. It was disruptive, not necessarily in a good way, but we all we adapted and learned how to do it in a new way, which is, uh, it was a lot easier towards the end than it was at the beginning. >>I'd say we're still getting there at the Snyder household. Justin, we're still getting >>was practice makes perfect eso for organizations like check that who might be looking at JAG and thinking that that sounds like a bit of a success story. I want to learn more about how new relic might be able to help me. How should they start? >>Well, there's a lot of ways they can start. I mean, one of the most exciting things about our launch in July was that we have a new free tier. So for anybody who's interested in understanding the power of observe ability, you could go right to our website and you can sign up for free and you can start to play with new relic one. I think once you start playing for, we're gonna find the same thing that happens to most of the folks to do that. They're gonna play more and more and more, and they're gonna start Thio really embrace the power. And there's an incredible new relic university that has fantastic training online. So as you start to dabble in that free tier, start to see with the power and the potential is you'll probably sign up for some classes. Next thing you know, you're often running, so that is one of the easiest ways to get exposed to it. So certainly check us out at our website and you can find out all about that free tier. And what observe ability could potentially mean to you or your business. >>And as part of the AWS reinvent experience, are they able to engage with you in some way? >>It could definitely come by our booth, check us out, virtually see what we have to say. We'd love to talk to them, and we'd be happy to talk to you about all the powerful things we're doing with A. W. S. in the marketplace to help meet you wherever you are in your cloud journey, whether it's pre migration during migration, post migration or even optimization. We've got some incredible statistics on how we can help you maximize and leverage your investment in AWS. And we're really excited to be a strategic partner with them. And, you know, it's funny. It's, uh, for me to see how observe ability this platform can really touch every single facet of that cloud migration journey. And, you know, I was thinking originally, as I got exposed to this, it would be really useful for identity Met entity relationship management at the pre migration phase and then possibly at the post migration flays is you try to baseline and measure results. But what I've come to learn through our own process, of moving our own business to the AWS cloud, that there's tremendous value everywhere along that journey. That's incredibly exciting. So not only are we a great partner, but I'm excited that we will be what I call first and best customer of AWS ourselves new relic as we make our own journey to the cloud >>or fantastic and I'm I encourage any customers who might be interested in new relic Thio definitely gone and check you out as part of the show. Thank you. J. J. Snyder from New Relic. You've been watching the Cube virtual and our coverage of AWS reinvent 2020. Make sure that you check out all the rest of the cube coverage of AWS reinvent on your desktop laptop your phone wherever you are. I've been your host, Justin Warren, and I look forward to seeing you again soon.

>>Thank you. Thank you so much for having me. I'm thrilled to be in conversation with you today. And I thought I would just kick things off with some opening reflections on this really important session theme, and then we can jump into discussion. So I'd like us to, as a starting point, um, wrestle with these buzz words, empowerment and inclusion so that we can, um, have them be more than kind of big platitudes and really have them reflected in our workplace cultures and the things that we design and the technologies that we put out into the world. And so to do that, I think we have to move beyond techno determinism and I'll explain what that means in just a minute. And techno determinism comes in two forms. The first on your left is the idea that technology automate. Um, all of these emerging trends are going to harm us are going to necessarily, um, harm humanity. >>They're going to take all the jobs they're going to remove human agency. This is what we might call the techno dystopian version of the story. And this is what Hollywood loves to sell us in the form of movies like the matrix or Terminator. The other version on your right is the techno utopian story that technologies automation, the robots, as a shorthand are going to save humanity. They're going to make everything more efficient, more equitable. And in this case, on the surface, they seem like opposing narratives, right? They're telling us different stories. At least they have different endpoints, but when you pull back the screen and look a little bit more closely, you see that they share an underlying logic, that technology is in the driver's seat and that human beings, that social society can just respond to what's happening. But we don't, I really have a say in what technologies are designed. >>And so to move beyond techno determinism, the notion that technology is in the driver's seat, we have to put the human agents and agencies back into the story protagonists and think carefully about what the human desires, worldviews values assumptions are that animate the production of technology. We have to put the humans behind the screen back into view. And so that's a very first step in when we do that. We see as was already mentioned that it's a very homogenous group right now in terms of who gets the power and the resources to produce the digital and physical infrastructure that everyone else has to live with. And so, as a first step, we need to think about how to, to create more participation of those who are working behind the scenes to design technology. Now, to dig a little more deeper into this, I want to offer a kind of low tech example before we get to the more high tech ones. >>So what you see in front of you here is a simple park bench public it's located in Berkeley, California, which is where I went to graduate school. And on this one particular visit, I was living in Boston. And so I was back in California, it was February, it was freezing where I was coming from. And so I wanted to take a few minutes in between meetings to just lay out in the sun and soak in some vitamin D. And I quickly realized actually I couldn't lay down on the bench because of the way it had been designed with these arm rests at intermittent intervals. And so here I thought, okay, th th the armrests have a functional reason why they're there. I mean, you could literally rest your elbows there, or, um, you know, it can create a little bit of privacy of someone sitting there that you don't know. >>Um, when I was nine months pregnant, it could help me get up and down or for the elderly the same thing. So it has a lot of functional reasons, but I also thought about the fact that it prevents people who are, are homeless from sleeping on the bench. And this is the Bay area that we're talking about, where in fact, the tech boom has gone hand in hand with a housing crisis. Those things have grown in tandem. So innovation has grown with inequity because we have, I haven't thought carefully about how to address the social context in which technology grows and blossoms. And so I thought, okay, this crisis is growing in this area. And so perhaps this is a deliberate attempt to make sure that people don't sleep on the benches by the way that they're designed and where the, where they're implemented. And so this is what we might call structural inequity, by the way something is designed. >>It has certain yeah. Affects that exclude or harm different people. And so it may not necessarily be the intent, but that's the effect. And I did a little digging and I found, in fact, it's a global phenomenon, this thing that architect next call, hostile architecture around single occupancy, benches and Helsinki. So only one booty at a time, no Nolan down there. I've found caged benches in France. Yeah. And in this particular town, what's interesting here is that the mayor put these benches out in this little shopping Plaza and within 24 hours, the people in the town rally together and have them removed. So we see here that just because we, we have a discriminatory design in our public space, doesn't mean we have to live with it. We can actually work together to ensure that our public space reflects our better values. But I think my favorite example of all is the metered bench. >>And then this case, this bench is designed with spikes in them and to get the spikes to retreat into the bench, you have to feed the meter. You have to put some coins in, and I think it buys you about 15, 20 minutes, then the spikes come back up. And so you will be happy to know that in this case, uh, this was designed by a German artist to get people to think critically about issues of design, not the design of physical space, but the design of all kinds of things, public policies. And so we can think about how our public life in general is metered, that it serves those that can pay the price and others are excluded or harmed. Whether we're talking about education or healthcare. And the meter bench also presents something interesting for those of us who care about technology, it creates a technical fix for a social problem. >>In fact, it started out as art, but some municipalities in different parts of the world have actually adopted this in their public spaces, in their parks in order to deter so-called loiters from using that space. And so by a technical fix, we mean something that creates a short-term effect, right? It gets people who may want to sleep on it out of sight. They're unable to use it, but it doesn't address the underlying problems that create that need to sleep outside of the first place. And so, in addition to techno determinism, we have to think critically about technical fixes, that don't address the underlying issues that the tech tech technology is meant to solve. And so this is part of a broader issue of discriminatory design, and we can apply the bench metaphor to all kinds of things that we work with, or that we create. >>And the question we really have to continuously ask ourselves is what values are we building in to the physical and digital infrastructures around us? What are the spikes that we may unwittingly put into place? Or perhaps we didn't create the spikes. Perhaps we started a new job or a new position, and someone hands us something, this is the way things have always been done. So we inherit the spiked bench. What is our responsibility? When we notice that it's creating these kinds of harms or exclusions or technical fixes that are bypassing the underlying problem, what is our responsibility? All of this came to a head in the context of financial technologies. I don't know how many of you remember these high profile cases of tech insiders and CEOs who applied for apples, >>The Apple card. And in one case, a husband and wife applied, and the husband, the husband received a much higher limit, almost 20 times the limit as his, >>His wife, even though they shared bank accounts, they lived in common law state. Yeah. >>And so the question there was not only the fact that >>The husband was receiving a much better rate and a high and a better >>The interest rate and the limit, but also that there was no mechanism for the individuals involved to dispute what was happening. They didn't even know how, what the factors were that they were being judged that was creating this form of discrimination. So >>In terms of financial technologies, it's not simply the outcome, that's the issue, or that can be discriminatory, >>But the process that black box is all of the decision-making that makes it so that consumers and the general public have no way to question it, no way to understand how they're being judged adversely. And so it's the process, not only the product that we have to care a lot about. And so the case of the Apple card is part of a much broader phenomenon >>Of, um, races >>And sexist robots. This is how the headlines framed it a few years ago. And I was so interested in this framing because there was a first wave of stories that seemed to be shocked at the prospect, that technology is not neutral. Then there was a second wave of stories that seemed less surprised. Well, of course, technology inherits its creators biases. And now I think we've entered a phase of attempts to override and address the default settings of so-called racist and sexist robots for better or worse than here. Robots is just a kind of shorthand that the way that people are talking about automation and emerging technologies more broadly. And so, as I was encountering these headlines, I was thinking about how these are not problems simply brought on by machine learning or AI. They're not all brand new. And so I wanted to contribute to the conversation, a kind of larger context and a longer history for us to think carefully about the social dimensions of technology. And so I developed a concept called the new Jim code, >>Which plays on the phrase, >>Jim Crow, which is the way that the regime of white supremacy and inequality in this country was defined in a previous era. And I wanted us to think about how that legacy continues to haunt the present, how we might be coding bias into emerging technologies and the danger being that we imagine those technologies to be objective. And so this gives us a language to be able to name this phenomenon so that we can address it and change it under this larger umbrella of the new Jim code are four distinct ways that this phenomenon takes shape from the more obvious engineered inequity. Those are the kinds of inequalities tech mediated in the qualities that we can generally see coming. They're kind of obvious, but then we go down the line and we see it becomes harder to detect it's happening in our own backyards, it's happening around us. And we don't really have a view into the black box. And so it becomes more insidious. And so in the remaining couple of minutes, I'm just, just going to give you a taste of the last three of these, and then a move towards conclusion. Then we can start chatting. So when it comes to default discrimination, this is the way that social inequalities >>Become embedded in emerging technologies because designers of these technologies, aren't thinking carefully about history and sociology. A great example of this, uh, came to, um, uh, the headlines last fall when it was found that widely used healthcare algorithm, effecting millions of patients, um, was discriminating against black patients. And so what's especially important to note here is that this algorithm, healthcare algorithm does not explicitly take note of race. That is to say it is race neutral by using cost to predict healthcare needs this digital triaging system unwittingly reproduces health disparities, because on average, black people have incurred fewer costs for a variety of reasons, including structural inequality. So in my review of this study, by Obermeyer and colleagues, I want to draw attention to how indifference to social reality can be even more harmful than malicious intent. It doesn't have to be the intent of the designers to create this effect. >>And so we have to look carefully at how indifference is operating and how race neutrality can be a deadly force. When we move on to the next iteration of the new Jim code, coded exposure, there's a tension because on the one hand, you see this image where the darker skin individual is not being detected by the facial recognition system, right on the camera, on the computer. And so coded exposure names, this tension between wanting to be seen and included and recognized whether it's in facial recognition or in recommendation systems or in tailored advertising. But the opposite of that, the tension is with when you're over, it >>Included when you're surveilled, when you're >>Too centered. And so we should note that it's not simply in being left out, that's the problem, but it's in being included in harmful ways. And so I want us to think carefully about the rhetoric of inclusion and understand that inclusion is not simply an end point, it's a process, and it is possible to include people in harmful processes. And so we want to ensure that the process is not harmful for it to really be effective. The last iteration of the new Jim code. That means the, the most insidious let's say is technologies that are touted as helping us address bias. So they're not simply including people, but they're actively working to address bias. And so in this case, there are a lot of different companies that are using AI to hire, uh, create hiring, um, software and hiring algorithms, including this one higher view. >>And the idea is that there there's a lot that, um, AI can keep track of that human beings might miss. And so, so the software can make data-driven talent decisions after all the problem of employment discrimination is widespread and well-documented, so the logic goes, wouldn't this be even more reason to outsource decisions to AI? Well, let's think about this carefully. And this is the idea of techno benevolence, trying to do good without fully reckoning with what, how technology can reproduce inequalities. So some colleagues of mine at Princeton, um, tested a natural learning processing algorithm and was looking to see whether it exhibited the same, um, tendencies that psychologists have documented among humans. And what they found was that in fact, the algorithm associated black names with negative words and white names with pleasant sounding words. And so this particular audit builds on a classic study done around 2003 before all of the emerging technologies were on the scene where two university of Chicago economists sent out thousands of resumes to employers in Boston and Chicago. >>And all they did was change the names on those resumes. All of the other work history education were the same. And then they waited to see who would get called back and the applicants, the fictional applicants with white sounding names received 50% more callbacks than the, the black applicants. So if you're presented with that study, you might be tempted to say, well, let's let technology handle it since humans are so biased. But my colleagues here in computer science found that this natural language processing algorithm actually reproduced those same associations with black and white names. So two with gender coded words and names as Amazon learned a couple years ago, when its own hiring algorithm was found discriminating against women, nevertheless, it should be clear by now why technical fixes that claim to bypass human biases are so desirable. If only there was a way to slay centuries of racist and sexist demons with a social justice bot beyond desirable, more like magical, magical for employers, perhaps looking to streamline the grueling work of recruitment, but a curse from any job seekers as this headline puts it. >>Your next interview could be with a racist bot, bringing us back to that problem space. We started with just a few minutes ago. So it's worth noting that job seekers are already developing ways to subvert the system by trading answers to employers tests and creating fake applications as informal audits of their own. In terms of a more collective response. There's a Federation of European trade unions call you and I global that's developed a charter of digital rights for workers that touches on automated and AI based decisions to be included in bargaining agreements. And so this is one of many efforts to change the ecosystem, to change the context in which technology is being deployed to ensure more protections and more rights for everyday people in the U S there's the algorithmic accountability bill that's been presented. And it's one effort to create some more protections around this ubiquity of automated decisions. >>And I think we should all be calling for more public accountability when it comes to the widespread use of automated decisions. Another development that keeps me somewhat hopeful is that tech workers themselves are increasingly speaking out against the most egregious forms of corporate collusion with state sanctioned racism. And to get a taste of that, I encourage you to check out the hashtag tech, won't build it among other statements that they've made and walking out and petitioning their companies. One group said as the, at Google at Microsoft wrote as the people who build the technologies that Microsoft profits from, we refuse to be complicit in terms of education, which is my own ground zero. Um, it's a place where we can, we can grow a more historically and socially literate approach to tech design. And this is just one resource that you all can download, um, by developed by some wonderful colleagues at the data and society research Institute in New York. >>And the, the goal of this intervention is threefold to develop an intellectual understanding of how structural racism operates and algorithms, social media platforms and technologies not yet developed and emotional intelligence concerning how to resolve racially stressful situations within organizations and a commitment to take action, to reduce harms to communities of color. And so as a final way to think about why these things are so important, I want to offer, uh, a couple last provocations. The first is pressed to think a new about what actually is deep learning when it comes to computation. I want to suggest that computational depth when it comes to AI systems without historical or social depth is actually superficial learning. And so we need to have a much more interdisciplinary, integrated approach to knowledge production and to observing and understanding patterns that don't simply rely on one discipline in order to map reality. >>The last provocation is this. If as I suggested at the start in the inequity is woven into the very fabric of our society. It's built into the design of our, our policies, our physical infrastructures, and now even our digital infrastructures. That means that each twist coil and code is a chance for us to weave new patterns, practices, and politics. The vastness of the problems that we're up against will be their undoing. Once we, that we are pattern makers. So what does that look like? It looks like refusing colorblindness as an anecdote to tech media discrimination, rather than refusing to see difference. Let's take stock of how the training data and the models that we're creating. Have these built in decisions from the past that have often been discriminatory. It means actually thinking about the underside of inclusion, which can be targeting and how do we create a more participatory rather than predatory form of inclusion. And ultimately it also means owning our own power in these systems so that we can change the patterns of the past. If we're, if we inherit a spiked bench, that doesn't mean that we need to continue using it. We can work together to design more, just an equitable technologies. So with that, I look forward to our conversation.

>>from the Cube Studios in Palo Alto and Boston connecting with thought leaders all around the world. >>This is a cube conversation. I'm stew Minuteman, and this is the Cube's virtual coverage of AWS Summit online. Happy to welcome back to the program to help give us some insight into what's happening. Aws last week. And today, that is Cory Quinn is the cloud economist at the Duck Bill Group. Cory, I know it's >>thank you. Always a >>pleasure to see you >>now it is always a pleasure to see me. Thank you for once again exhibiting remarkably poor judgment and inviting me back onto your program. >>Yeah, you know, Korea, you've been on the program a few times now, including in some of the AWS goes Ah, 18 San Francisco AWS, New York City. You know, reinvent we see you. But this is the first time we've had you on online. So give us a little bit about you know what? That impact of the global pandemic has been meaning to you and more importantly, what you've been seeing from our dear friends at AWS. >>Sure, the fact that not traveling anymore and spending almost all of my time at home means that I'm a lot closer to the edge when it comes to the content I put out because I no longer have to worry about someone punching me in the face. But other than that, from a business perspective, things tend to be continuing on much as they have before with four different customer concerns. The more interesting question from my side has been what is the effect this is having on people Because we're working from home remotely? It's not really a fair test of how well you can do remote. I've been doing it like this for years, and there's a There's a sense of existential dread that's hanging over people's at more so than usual, more so than right before the AWS re invent. You know, when you're wondering if you're about to have your entire business put out of business by an AWS. Now, it's just that sort of dread that never goes away because they won't deliver the keynote If you'll pardon me if using a metal >>Yeah, it's been really interesting to watch, you know, for you, of course. I mean, Amazon is, you know, a big player in the industry before this Amazon one that gets talked about a lot in the news. You know Amazon overall, You know, when this first pitch they announced they were hiring 1000 then they went through that faster than anyone could believe. You know, you think about having to hire a driver remotely. You know, my joke was you know, Alexa the screen. Everybody and I are everyone. But then they hired another 75,000. And it's not just the warehouse and the whole food people, because I've seen a number of people that I know getting hired by AWS do. So you know, you talk. It's all about the people that you know, the number one in the endemic people. How's Amazon doing? What feedback are you getting for? How they're doing? >>Well, I don't have too many internal sources that confirm or deny things of strategic import because it turns out that I'm generally not for those things. Who knew something I'm picking up on across the industry has been that if you're building a hyper scale cloud provider, you're not looking to next border. The investments you make today are going to be realized 3 to 5 years No one is currently predicting a dramatic economic impact community felt for a decade, based on the current question. So, yeah, AWS is still investing in people, which is always going to be the limiting constraint there still launching regions we have to launch within a month, and we're still seeing a definite acceleration of anything of the pace of innovation as a W was like. Now my perspective, that's both reassuring that some things never change. And, of course, the usual level of depression where oh, good, there's still more services to learn what they do. Learn how the names work, find ways to poke holes in their various presentational aspects. And, of course, try and keep the content relatively fresh. There's only so many times you could make the same joke for people. >>Yeah, absolutely. And of course, you bring up a really good point. You know, Amazon that they have a long strategic plan there. If they're building new data centers, they're building the power in perfect for these things. It's not something that they're going to change on a dime. They plan these things out far in advance, and AWS does, of course, have a global scope. Um, you know, I really, you know, wonder. You know, from an operational standpoint, are there any pressures on them? You wrote an article you know, relatively recently talking about one of the other public cloud providers that is by our customers. And we even have performance issues. AWS seems to be running through this dealing with acid. You know, I've had phone systems that have problems. You know, everybody as when they're working from home engine internally. Even if you've got a gig bandwidth When the fire neighborhood has Children on, you know, the classrooms online for video. There's pressures there. So you know where your teams from what I've seen, you know, AWS operationally is running well and, you know, keeping things all up and running Is am I missing anything? >>No. I mean the database is fond of saying there's no compression algorithm for experience, as I'm fond of saying, that's why they charge per gigabyte. But what that means is that they've gone through a lot of these growing pains and largest instructional stories in 2010 to 2012 EBS outages, causing a cascading failures as everyone saturates links as they roll from region to region or availability zone availability zone. They understand what those workloads look like and what those years are, and they've put in credible amount of engineering into solving these problems. I think that anyone who looks at this and doesn't see this happening is unfortunate place because we don't have to its approach utility level of reliability. You don't wonder every time you turn the faucet on whether water is going to, and we're now at a point of seeing that with AWS Resource. Now they're still going to be recurring issues. And there have been basically since this thing watched a particular instance. Size and family in a particular availability zone of a particular region may be constrained for a period of weeks, and that is something that we've seen across the board. But that has less to do with the fact that they didn't see this stuff coming in that appropriately and more to do with the fact that there's a lot of different options and customer demand is never going to be an exact thing we are seeing some customers dramatically turn off city and others sporadically scrapping capacity up. It comes down to what is the nature of this endemic on >>there. Yeah, well, this absolutely does. But you know, some of those promises of the cloud test I should be able to spin things down some things I should be able to turn off. And if I have to know shut down by business, I should be able to do that. Um, I'm curious what you've heard on changing demand out there. Worry. Um, you know, on the one hand, you know customers there re buying, they're getting reserved. They're making for that. They can, you know, optimize every dollar. But when something like this comes up and they need a major change, you know, are they stuck with a lot of capacity that they didn't necessarily want? >>Sometimes it comes down to a lot of interesting variables For me, the more interesting expression of this is when companies see demand falling off a cliff. As users, we're no longer using what their what they built out. But their infrastructure spend doesn't change. That tells me that it's not a particularly elastic infrastructure. And in fact, when people are building the elasticity into their applications, they always interpret that is scaling up rather than scaling down because the failure mode of not scaling up fast enough is you're dropping customer requests on the floor. The failure mode of not scaling down fast enough just means you're spending money. So when you see user demand for environment cut by 80% but the infrastructure cost remains constant or the infrastructure usage defending. That's a more interesting problem. And you're not gonna have a lot of success asking any cloud provider for adjustment when? Well, okay, you're suddenly not seeing the demand, but you're still remains the same. What is this based upon? You need to actually demonstrate a shortfall. First of wow, you know, we normally spend a $1,000,000 a month. Well, now we're spending 200 grand a month. Yeah, about that. And once you could do that, there are paths forward. I have not yet heard stories about, frankly, any of the big Three cloud providers, absolutely hanging customers out to dry in the cloud I have heard whispers about, for example, with G suite, where they're not willing to. And this this feels like a very dark way to go. But I'm going for it. Where will we just laid off 1/3 of our staff and we get a break on the annual licensing for those seats on G suite. And the answer is no. That feels like it stings and is more than a little capricious. >>Yeah, No, absolutely. You know, one of the things that the underbelly of fast is, you know? Oh, it should be elastic like cloud. But often times you're locked one or your contract, and if all of a sudden you find yourself with that meeting half the demand and you call them up, you know, Are they going to give you that break? So you know, Price and Corey, you know better >>than most. So all right, let me spoil it for you. Every provider is going to give you a break on this because this is a temporary aberration. As far as the way the world works, we're not going to start seeing Global 10 X every year, I hope. And when this crisis passes, people are going to remember how their vendors treated. And if it's well, we held your feet to the fire and made you live up to that contract that sticks with me, and it doesn't take too many stories like that, or people pulling lawsuits out of Acer to demonstrate that a company beat the crap out of them to say, Huh? Maybe that's not where I want to thank my sizeable cloud. Invest. >>Yeah. So, Corey, how about you know, there are there certain areas where I heard, you know, certain that maybe were slow rolling cloud and all of a sudden realize that when they're working from home, they plug and adjust their servers that are saying, Oh, jeez, maybe I need to hop on this. Then there's other services. You think VPN usage must be through the roof workspaces. So when first announced, you know, many years ago was a bit of a slow roll had been a growth ah, area for Amazon for the last couple of years. Are you hearing anything specific to new services or increase growth in certain services like I'm in? >>There are two patterns we're seeing. Of all. One is the traditional company you just described, where they build out a VPN that assumes some people will occasionally be working from home at a 5% rate versus the entire workforce 40 hours a week that that model that model is training every. Whereas if you go back the last 10 years or so and look at a bunch of small businesses that have started up or startups that have launched where everything they're using is a SAS service or a cloud service, then there is no VPN. I don't have a VPN. For example, the fact that I have a wireless network here in my house and I'm at dislocation. There's this I p address isn't white listed anywhere. The only benefit that this network has over others is that there's a printer plugged in here, and that's it. The identity model of Ioffe indicate to these services by the credentials of a user name and password by enchanting something, and they send an email that I click the link that that winds up handling the Asian night and there is no bottleneck in the same direction. I feel like this is going to be the death now for a lot of VM centric for tonight. >>Alright, Corey, want one of the other things about aws is they don't stop. And what I mean is, you know, you talked about them always being online. But you know every week there's a new announcement. It keeps feeding your newsletter, feeding your feet. You know everything going on there. How is number one? You know the announcement? Brains from AWS going and anything specific. You know, John Furrier was, you know, interest in, you know, Amazon Apolo, something that was released relatively recently. >>The problem with a lot of these new services that get released relatively recently is that it requires time to vet out how it works, how it doesn't work, how it should have wound up being implemented to solve your particular use case or, in my case, how they could have named it better. But you're not able to come up with those things off the top of your head the first time you see it because it's irresponsible at scale to deploy anything in production. You don't understand. It's failure cases right now, with everyone scrambling, most companies are not making significant investments in new capabilities. They are desperately trying to get their workforces online and stay afloat and adjust very rapidly changing. And oh, they built a new data store or something of that. Nature is not going to be this sort of thing that gets people super excited in most shops, that time will change. But I do feel a bit of it right now for a lot of these product teams who've been working away on these things for months or years. And now suddenly they're releasing something into a time when people don't I care about it enough to invest the effort that, yeah, you bring up a really good >>point. Corey, you know, there's certain things. If I was working on a project that was going to help me be more agile and be more flexible, I needed that yesterday. But I still need that today. Um, some other projects, you know, might take years to roll out a eyes. Technology that has been growing bring over the last couple of years were I O T solutions are a little bit more nascent. So is what you're thinking. It's a little bit more Stick to your knitting and the solutions and the products that you're leveraging today. And some of the, you know, more visionary and futuristic ones might be a little bit of a pause button for the next couple months. >>Exactly if you're looking at exploring something that isn't going to pay dividends for 18 months. Right now, the biggest question everyone has is what is the long term repercussion of this going to be? What is the year? What we're gonna look like in three years? Because that's where a lot of these planning horizons are stretching to. And the answer is, Look, when I wind up doing a pre recorded video or podcast where I talk about this stuff and it's not going to release for four days, I'm worried about saying something that was going to be eclipsed by the new site. I worry on my podcast reporting, for example, that I'm going to wind up saying something about that dynamic, and by the time it airs in two months, it's Oh, look at this guy. He's talking about the pandemic. He doesn't even mention the meteor, and that's the place right now where people are operating from, it becomes much more challenging to be able to adequately and intelligently address the long term. When you don't know what it's going to look like, >>Yeah, absolutely. For our viewers, when you hear my segment on Cory's ask and you wonder why we could talk about that it's because we missed that one week window that we're in right now When we're talking about murder Hornet, Not when we recorded it. Not when we released the really good point court. You know, Corey, you know, data is one of the most important things. You've done a lot about data portability, you know, all the costs involved. Cloud Amazon's trying to help people, you know, with, you know, bringing data together. You know, I said in one of the interviews with Andy Jassy a couple years ago, while customers were really the flywheel for AWS for a number of years, I think it is data that is that next flywheel. So I'm curious your thoughts as our, you know, enterprises think about their data, and AWS is role >>there incorrectly. If you want me to be blunt, there's an awful lot of movement, especially as we look at AI and machine learning to gather all of the data. I've been on cost optimization projects where Wow, that's an awful lot of data sitting there. And that s three bucket. Do you need it all? And I'm assured that yes, all of the sales transaction logs from 2012 are absolutely going to be a treasure trove of data just as soon as they figure out what to do with it, and they're spending our piles of money on >>it. But >>it's worse than that because it's not just that you have this data that's costing you money. That's almost a by product. There's risk to an awful lot of forms of data with regulation that continues to expand. Data can become a toxic asset in many respects. But there's this belief of never throw anything away that's not really ideal. Part of the value of a same data management strategy is making sure that you can remove all of the stuff that you don't absolutely need right now, with AI and ML being where they are, there's this movement or keep everything because we don't know what that's going to be useful for. Down the road, it's a double edged sword, and enterprises are at this point not looking at this through a lens of this thing could hurt me so much as they are. This thing could possibly benefit that the business in the future. >>Alright, so Cory, I I've really noticed over the last few months you've spent a bit more. I'm talking publicly about some of the other clouds that aren't AWS, though. You know what we are covering? AWS Summit online. Give us what you're hearing from Microsoft, Google and others. You know any strategies that Aaron you any you know, customer movement? That is worth >>sure. I think that we're seeing customers move in the way that they've always been moving. People made a bit of a kerfuffle about a block post I put out with the extremely Clickbait idle of Zoom chose Oracle Cloud over AWS. Maybe you should, too, and there were a few. There are few conclusions people drew understandably from that particular headline, which was, for example, the idea that AWS have lost a workload that was being moved from AWS to Oracle. Not true. It was net new. They do already has existing relationships with both Azure and AWS by their own admission. But the argument what what I took that particular change to be in my case was an illustration of something that's been bugging me for a while. If you look at AWS data transfer pricing publicly posted stop, which again, no one of this scale is going to pay. It is over 10 times more expensive than Oracle. Wow. And what that tells me is that I'm now sitting here in a position where I can make you made a good faith recommendation to choose Oracle's for cost reasons, which sounds nuts. But that's the world in which we live. It's a storytelling problem, far more than it is a technical shortcoming. But that was interpreted to mean that Oracle's on the rise. AWS is in decline. Zoom is a very strong AWS customer and has made public commitments. They will remain so right now. This is what we're seeing across the board. You see Zoom doing super well. They're not building out a whole lot of net new, either. What they're doing is building is just it's desperately trying to stay up under brushing unprecedented demand. That's where the value is coming from right now, clouds elasticity and they're not doing. You know, we're going to go ahead and figure out if we can build a new continuous deploy process or something that it makes on call a little bit less brutal. That's not what anyone's focusing on it here. Wow, this boat is sinking. If we don't stay up, grab a bucket, start bailing. And that is what they're doing. The fact that they're working with every cloud provider, it shouldn't come as a surprise. >>Yeah, well, it's interesting. I'm thinking about Zoom, and one of the things that I've been watching them for the last couple of everybody has is, you know, the daily updates that are happening Related security. Um, you know, I think back, you know, 67 years ago, Amazon had This is our security model. We're not changing it for anyone now. You know Amazon as a much more flexible and nuanced. So there are >>still in violent principles that Amazon will not and cannot shift. So, to be clear, they have different ways of interfacing with security in different ways of handling data classification. But there are rules that you knew are not changing. It's not well surprised. Now, suddenly, every Amazonian who works there can look through your private data that none of that is >>happening. I >>just want to very clear on >>that. Yeah, No, you're absolutely right. It's more security, you know, getting more engine even than ever. And it was already coming into 2020 before everything changed. What was one of the hot topic? Great. You know, I'm curious. You know, we're looking at a virtual event for AWS. Have you been to some of these? You know, you're getting burnt out from all of the online content. I'm sure everybody's getting tired of you. So are you getting tired of everyone else? >>I don't accept that anyone ever get tired of me. I'm a treasure and of the light. But as far as online events go, I think that people are getting an awful lot profoundly wrong about that. For example, I think that people focus on, well, I need to get the best video and the best microphone, and that's the thing that people are going to focus on, rather than maybe I should come up with something that someone wants to listen. People are also assuming that the same type of delivery and content works super well in a stage for 45 minutes is not going to work when people can tab over to something else and stop paying attention. You've got to be more dynamic. You've got to be able to grab people's, and I think that people are missing the forest for the trees. Here, you're just trying to convert existing format into something that will work online in the immediate short term. Everyone is super sympathetic. It's not going to last. People are going to get very tired of the same tired formatting ropes, and there's only so much content people are going to consume. You've got to stand out and you've got to make it compelling and interesting. I've been spending a lot of time trying to find ways to make that >>work. Yeah, I had a great conversation with John Troyer, he said. You know, we can learn something about what? Some of the late those Ah, you know, I think there's a new opportunity for you to say There's a house band, you know. You have a small child at home, divert Amerine there's your house band. You know you can have a lot of fun with >>Oh, absolutely, especially during a tantrum that's going to go super. Well, I'm just gonna watch one of her meltdowns about some various innocuous topic, and then I'm going to wind up having toddler meltdown the Amazon s three remix, and I'm sure we could wind up tying it back to something that is hilarious in the world of cloud. But I'm trying to pull off a little bit longer before I start actively exploiting her for Internet points. I mean, I'm going to absolutely do it. I just wanted to get a little color. >>All right. Well, Corey, want to give you the final word on AWS? The online events happening, you know, give our audience that what they should be looking at when it comes to their AWS estate, >>cool as usual attention to what's coming out. It's always been to have a low level awareness of what's coming out on stage. I don't feel you need to jump in and adopt any of it immediately. Focus on the things that matter to your business. Just because something new and shiny has announced on stage does not need a fit for you doesn't mean it's not, but remain critical. I tend not to be one of the early adopters in production, things that have a potential to wind up housing challenges, and I'm not saying, Oh, stay on the exact old stuff from 2010 and nothing newer, but there is a bit of a happy medium. Don't think that just because they released something that a you need to try it or B, it's even for, you know, AWS service is for everyone but every AWS services for someone. >>Alright, Well, Cory Quinn, always a pleasure to catch up with you. Thanks so much for joining with you joining us. >>Thank you. It was over the suffering. The slings and arrows Appreciate >>it. All right. Thank you for watching everyone. Lots of coverage of the cube at the AWS Summit online. Check out the cube dot net for all the offering. And thank you for what? >>Yeah, yeah, yeah.

>> Jeff: Hello, everybody, and thank you for joining us today for the virtual Vertica BDC 2020. Today's breakout session is entitled "A Deep Dive "into the Vertica Mangement Console Enhancements and Roadmap." I'm Jeff Healey of Vertica Marketing. I'll be your host for this breakout session. Joining me are Bhavik Gandhi and Natalia Stavisky from Vertica engineering. But before we begin, I encourage you to submit questions or comments during the virtual session. You don't have to wait, just type your question or comment in the question box below the slides and click submit. There will be a Q and A session at the end of the presentation. We'll answer as many questions as we're able to during that time. Any questions we don't address, we'll do our best to answer them offline. Alternatively visit Vertica Forums at forum.vertica.com. Post your question there after the session. Our engineering team is planning to join the forums to keep the conversation going well after the event. Also, a reminder that you can maximize the screen by clicking the double arrow button in the lower right corner of the slides. And yes, this virtual session is being recorded and will be available to you on demand this week. We'll send you a notification as soon as it's ready. Now let's get started. Over to you, Bhavik. >> Bhavik: All right. So hello, and welcome, everybody doing this presentation of "Deep Dive into the Vertica Management Console Enhancements and Roadmap." Myself, Bhavik, and my team member, Natalia Stavisky, will go over a few useful announcements on Vertica Management Console, discussing a few real scenarios. All right. So today we will go forward with the brief introduction about the Management Console, then we will discuss the benefits of using Management Console by going over a couple of user scenarios for the query taking too long to run and receiving email alerts from Management Console. Then we will go over a few MC features for what we call Eon Mode databases, like provisioning and reviving the Eon Mode databases from MC, managing the subcluster and understanding the Depot. Then we will go over some of the future announcements on MC that we are planning. All right, so let's get started. All right. So, do you want to know about how to provision a new Vertica cluster from MC? How to analyze and understand a database workload by monitoring the queries on the database? How do you balance the resource pools and use alerts and thresholds on MC? So, the Management Console is basically our answer and we'll talk about its capabilities and new announcements in this presentation. So just to give a brief overview of the Management Console, who uses Management Console, it's generally used by IT administrators and DB admins. Management Console can be used to monitor both Eon Mode and Enterprise Mode databases. Why to use Management Console? You can use Management Console for provisioning Vertica databases and cluster. You can manage the already existing Vertica databases and cluster you have, and you can use various tools on Management Console like query execution, Database Designer, Workload Analyzer, and set up alerts and thresholds to get notified by some of your activities on the MC. So let's go over a few benefits of using Management Console. Okay. So using Management Console, you can view and optimize resource pool usage. Management Console helps you to identify some critical conditions on your Vertica cluster. Additionally, you can set up various thresholds thresholds in MC and get other data if those thresholds are triggered on the database. So now let's dig into the couple of scenarios. So for the first scenario, we will discuss about queries taking too long and using workload analyzer to possibly help to solve the problem. In the second scenario, we will go over alert email that you received from your Management Console and analyzing the problem and taking required actions to solve the problem. So let's go over the scenario where queries are taking too long to run. So in this example, we have this one query that we are running using the query execution on MC. And for some reason we notice that it's taking about 14.8 seconds seconds to execute this query, which is higher than the expected run time of the query. The query that we are running happens to be the query used by MC during the extended monitoring. Notice that the table name and the schema name which is ds_requests_issued, and, is the schema used for extended monitoring. Now in 10.0 MC we have redesigned the Workload Analyzer and Recommendations feature to show the recommendations and allow you to execute those recommendations. In our example, we have taken the table name and figured the tuning descriptions to see if there are any tuning recommendations related to this table. As we see over here, there are three tuning recommendations available for that table. So now in 10.0 MC, you can select those recommendations and then run them. So let's run the recommendations. All right. So once recommendations are run successfully, you can go and see all the processed recommendations that you have run previously. Over here we see that there are three recommendations that we had selected earlier have successfully processed. Now we take the same query and run it on the query execution on MC and hey, it's running really faster and we see that it takes only 0.3 seconds to run the query and, which is about like 98% decrease in original runtime of the query. So in this example we saw that using a Workload Analyzer tool on MC you can possibly triage and solve issue for your queries which are taking to long to execute. All right. So now let's go over another user scenario where DB admin's received some alert email messages from MC and would like to understand and analyze the problem. So to know more about what's going on on the database and proactively react to the problems, DB admins using the Management Console can create set of thresholds and get alerted about the conditions on the database if the threshold values is reached and then respond to the problem thereafter. Now as a DB admin, I see some email message notifications from MC and upon checking the emails, I see that there are a couple of email alerts received from MC on my email. So one of the messages that I received was for Query Resource Rejections greater than 5, pool, midpool7. And then around the same time, I received another email from the MC for the Failed Queries greater than 5, and in this case I see there are 80 failed queries. So now let's go on the MC and investigate the problem. So before going into the deep investigation about failures, let's review the threshold settings on MC. So as we see, we have set up the thresholds under the database settings page for failed queries in the last 10 minutes greater than 5 and MC should send an email to the individual if the threshold is triggered. And also we have a threshold set up for queries and resource rejections in the last five minutes for midpool7 set to greater than 5. There are various other thresholds on this page that you can set if you desire to. Now let's go and triage those email alerts about the failed queries and resource rejections that we had received. To analyze the failed queries, let's take a look at the query statistics page on the database Overview page on MC. Let's take a look at the Resource Pools graph and especially for the failed queries for each resource pools. And over to the right under the failed query section, I see about like, in the last 24 hours, there are about 6,000 failed queries for midpool7. And now I switch to view to see the statistics for each user and on this page I see for User MaryLee on the right hand side there are a high number of failed queries in last 24 hours. And to know more about the failed queries for this user, I can click on the graph for this user and get the reasons behind it. So let's click on the graph and see what's going on. And so clicking on this graph, it takes me to the failed queries view on the Query Monitoring page for database, on Database activities tab. And over here, I see there are a high number of failed queries for this user, MaryLee, with the reasons stated as, exceeding high limit. To drill down more and to know more reasons behind it, I can click on the plus icon on the left hand side for each failed queries to get the failure reason for each node on the database. So let's do that. And clicking the plus icon, I see for the two nodes that are listed, over here it says there are insufficient resources like memory and file handles for midpool7. Now let's go and analyze the midpool7 configurations and activities on it. So to do so, I will go over to the Resource Pool Monitoring view and select midpool7. I see the resource allocations for this resource pool is very low. For example, the max memory is just 1MB and the max concurrency is set to 0. Hmm, that's very odd configuration for this resource pool. Also in the bottom right graph for the resource rejections for midpool7, the graph shows very high values for resource rejection. All right. So since we saw some odd configurations and odd resource allocations for midpool7, I would like to see when this resource, when the settings were changed on the resource pools. So to do this, I can preview the audit logs on, are available on the Management Console. So I can go onto the Vertica Audit Logs and see the logs for the resource pool. So I just (mumbles) for the logs and figuring the logs for midpool7. I see on February 17th, the memory and other attributes for midpool7 were modified. So now let's analyze the resource activity for midpool7 around the time when the configurations were changed. So in our case we are using extended monitoring on MC for this database, so we can go back in time and see the statistics over the larger time range for midpool7. So viewing the activities for midpool7 around February 17th, around the time when these configurations were changed, we see a decrease in resource pool usage. Also, on the bottom right, we see the resource rejections for this midpool7 have an increase, linear increase, after the configurations were changed. I can select a point on the graph to get the more details about the resource rejections. Now to analyze the effects of the modifications on midpool7. Let's go over to the Query Monitoring page. All right, I will adjust the time range around the time when the configurations were changed for midpool7 and completed activities queries for user MaryLee. And I see there are no completed queries for this user. Now I'm taking a look at the Failed Queries tab and adjusting the time range around the time when the configurations were changed. I can do so because we are using extended monitoring. So again, adjusting the time, I can see there are high number of failed queries for this user. There about about like 10,000 failed queries for this user after the configurations were changed on this resource pool. So now let's go and modify the settings since we know after the configurations were changed, this user was not able to run the queries. So you can change the resource pool settings of using Management Console's database settings page and under the Resource Pools tab. So selecting the midpool7, I see the same odd configurations for this resource pool that we saw earlier. So now let's go and modify it, the settings. So I will increase the max memory and modify the settings for midpool7 so that it has adequate resources to run the queries for the user. Hit apply on the right hand top to see the settings. Now let's do the validation after we change the resource pool attributes. So let's go over to the same query monitoring page and see if MaryLee user is able to run the queries for midpool7. We see that now, after the configuration, after the change, after we changed the configuration for midpool7, the user can run the queries successfully and the count for Completed Queries has increased after we modified the settings for this midpool7 resource pool. And also viewing the resource pool monitoring page, we can validate that after the new configurations for midpool7 has been applied and also the resource pool usage after the configuration change has increased. And also on the bottom right graph, we can see that the resource rejections for midpool7 has decreased over the time after we modified the settings. And since we are using extended monitoring for this database, I can see that the trend in data for these resource pools, the before and after effects of modifying the settings. So initially when the settings were changed, there were high resource rejections and after we again modified the settings, the resource rejections went down. Right. So now let's go work with the provisioning and reviving the Eon Mode Vertica database cluster using the Management Console on different platform. So Management Console supports provisioning and reviving of Eon Mode databases on various cloud environments like AWS, the Google Cloud Platform, and Pure Storage. So for Google, for provisioning the Vertica Management Console on Google Cloud Platform you can use launch a template. Or on AWS environment you can use the cloud formation templates available for different OS's. Once you have provisioned Vertica Management Console, you can provision the Vertica cluster and databases from MC itself. So you can provision a Vertica cluster, you can select the Create new database button available on the homepage. This will open up the wizard to create a new database and cluster. In this example, we are using we are using the Google Cloud Platform. So the wizard will ask me for varius authentication parameters for the Google Cloud Platform. And if you're on AWS, it'll ask you for the authentication parameters for the AWS environment. And going forward on the Wizard, it'll ask me to select the instance Type. I will select for the new Vertica cluster. And also provide the communal location url for my Eon Mode database and all the other preferences related to the new cluster. Once I have selected all the preferences for my new cluster I can preview the settings and I can hit, if I am, I can hit Create if all looks okay. So if I hit Create, this will create a new, MC will create a new GCP instances because we are on the GCP environment in this example. It will create a cluster on this instance, it'll create a Vertica Eon Mode Database on this cluster. And it will, additionally, you can load the test data on it if you like to. Now let's go over and revive the existing Eon Mode database from the communal location. So you can do it the same using the Management Console by selecting the Revive Eon Mode database button on the homepage. This will again open up the wizard for reviving the Eon Mode database. Again, in this example, since we are using GCP Platform, it will ask me for the Google Cloud storage authentication attributes. And for reviving, it will ask me for the communal location so I can enter the Google Storage bucket and my folder and it will discover all the Eon Mode databases located under this folder. And I can select one of the databases that I would like to revive. And it will ask me for other Vertica preferences and for this video, for this database reviving. And once I enter all the preferences and review all the preferences I can hit Revive the database button on the Wizard. So after I hit Revive database it will create the GCP instances. The number of GCP instances that I created would be seen as the number of hosts on the original Vertica cluster. It will install the Vertica cluster on this data, on this instances and it will revive the database and it will start the database. And after starting the database, it will be imported on the MC so you can start monitoring on it. So in this example, we saw you can provision and revive the Vertica database on the GCP Platform. Additionally, you can use AWS environment to provision and revive. So now since we have the Eon Mode database on MC, Natalia will go over some Eon Mode features on MC like managing subcluster and Depot activity monitoring. Over to you, Natalia. >> Natalia: Okay, thank you. Hello, my name is Natalia Stavisky. I am also a member of Vertica Management Console Team. And I will talk today about the work I did to allow users to manage subclusters using the Management Console, and also the work I did to help users understand what's going on in their Depot in the Vertica Eon Mode database. So let's look at the picture of the subclusters. On the Manage page of Vertica Management Console, you can see here is a page that has blue tabs, and the tab that's active is Subclusters. You can see that there are two subclusters are available in this database. And for each of the subclusters, you can see subcluster properties, whether this is the primary subcluster or secondary. In this case, primary is the default subcluster. It's indicated by a star. You can see what nodes belong to each subcluster. You can see the node state and node statistics. You can also easily add a new subcluster. And we're quickly going to do this. So once you click on the button, you'll launch the wizard that'll take you through the steps. You'll enter the name of the subcluster, indicate whether this is secondary or primary subcluster. I should mention that Vertica recommends having only one primary subcluster. But we have both options here available. You will enter the number of nodes for your subcluster. And once the subcluster has been created, you can manage the subcluster. What other options for managing subcluster we have here? You can scale up an existing subcluster and that's a similar approach, you launch the wizard and (mumbles) nodes. You want to add to your existing subcluster. You can scale down a subcluster. And MC validates requirements for maintaining minimal number of nodes to prevent database shutdown. So if you can not remove any nodes from a subcluster, this option will not be available. You can stop a subcluster. And depending on whether this is a primary subcluster or secondary subcluster, this option may be available or not available. Like in this picture, we can see that for the default subcluster this option is not available. And this is because shutting down the default subcluster will cause the database to shut down as well. You can terminate a subcluster. And again, the MC warns you not to terminate the primary subcluster and validates requirements for maintaining minimal number of nodes to prevent database shutdown. So now we are going to talk a little more about how the MC helps you to understand what's going on in your Depot. So Depot is one of the core of Eon Mode database. And what are the frequently asked questions about the Depot? Is the Depot size sufficient? Are a subset of users putting a high load on the database? What tables are fetched and evicted repeatedly, we call it "re-fetched," in Depot? So here in the Depot Activity Monitoring page, we now have four tabs that allow you to answer those questions. And we'll go a little more in detail through each of them, but I'll just mention what they are for now. At a Glance shows you basic Depot configuration and also shows you query executing. Depot Efficiency, we'll talk more about that and other tabs. Depot Content, that shows you what tables are currently in your Depot. And Depot Pinning allows you to see what pinning policies have been created and to create new pinning policies. Now let's go through a scenario. Monitoring performance of workloads on one subcluster. As you know, Eon Mode database allows you to have multiple subclusters and we'll explore how this feature is useful and how we can use the Management Console to make decisions regarding whether you would like to have multiple subclusters. So here we have, in my setup, a single subcluster called default_subcluster. It has two users that are running queries that are accessing tables, mostly in schema public. So the query started executing and we can see that after fetching tables from Communal, which is the red line, the rest of the time the queries are executing in Depot. The green line is indicating queries running in Depot. The all nodes Depot is about 88% full, a steady flow, and the depot size seems to be sufficient for query executions from Depot only. That's the good case scenario. Now at around 17 :15, user Sherry got an urgent request to generate a report. And at, she started running her queries. We can see that picture is quite different now. The tables Sherry is querying are in a different schema and are much larger. Now we can see multiple lines in different colors. We can see a bunch of fetches and evictions which are indicated by blue and purple bars, and a lot of queries are now spilling into Communal. This is the red and orange lines. Orange line is an indicator of a query running partially in Depot and partially getting fetched from Communal. And the red line is data fetched from Communal storage. Let's click on the, one of the lines. Each data point, each point on the line, it'll take you to the Query Details page where you can see more about what's going on. So this is the page that shows us what queries have been run in this particular time interval which is on top of this page in orange color. So that's about one minute time interval and now we can see user Sherry among the users that are running queries. Sherry's queries involve large tables and are running against a different schema. We can see the clickstream schema in the name of the, in part of the query request. So what is happening, there is not enough Depot space for both the schema that's already in use and the one Sherry needs. As a result, evictions and fetches have started occurring. What other questions we can ask ourself to help us understand what's going on? So how about, what tables are most frequently re-fetched? So for that, we will go to the Depot Efficiency page and look at the middle, the middle chart here. We can see the larger version of this chart if we expand it. So now we have 10 tables listed that are most frequently being re-fetched. We can see that there is a clickstream schema and there are other schemas so all of those tables are being used in the queries, fetched, and then there is not enough space in the Depot, they getting evicted and they get re-fetched again. So what can be done to enable all queries to run in Depot? Option one can be increase the Depot size. So we can do this by running the following queries, which (mumbles) which nodes and storage location and the new Depot size. And I should mention that we can run this query from the Management Console from the query execution page. So this would have helped us to increase the Depot size. What other options do we have, for example, when increasing Depot size is not an option? We can also provision a second subcluster to isolate workloads like Sherry's. So we are going to do this now and we will provision a second subcluster using the Manage page. Here we're creating subcluster for Sherry or for workloads like hers. And we're going to create a (mumbles). So Sherry's subcluster has been created. We can see it here, added to the list of the subclusters. It's a secondary subcluster. Sherry has been instructed to use the new SherrySubcluster for her work. Now let's see what happened. We'll go again at Depot Activity page and we'll look at the At a Glance tab. We can see that around >> 18: 07, Sherry switched to running her queries on SherrySubcluster. On top of this page, you can see subcluster selected. So we currently have two subclusters and I'm looking, what happened to SherrySubcluster once it has been provisioned? So Sherry started using it and the lines after initial fetching from Depot, which was from Communal, which was the red line, after that, all Sherry's queries fit in Depot, which is indicated by green line. Also the Depot is pretty full on those nodes, about 90% full. But the queries are processed efficiently, there is no spilling into Communal. So that's a good case scenario. Let's now go back and take a look at the original subcluster, default subcluster. So on the left portion of the chart we can see multiple lines, that was activity before Sherry switched to her own designated subcluster. At around 18:07, after Sherry switched from the subcluster to using her designated subcluster, there is no, she is no longer using the subcluster, she is not putting a load in it. So the lines after that are turning a green color, which means the queries that are still running in default subcluster are all running in Depot. We can also see that Depot fetches and evictions bars, those purple and blue bars, are no longer showing significant numbers. Also we can check the second chart that shows Communal Storage Access. And we can see that the bars have also dropped, so there is no significant access for Communal Storage. So this problem has been solved. Each of the subclusters are serving queries from Depot and that's our most efficient scenario. Let's also look at the other tabs that we have for Depot monitoring. Let's look at Depot Efficiency tab. It has six charts and I'll go through each one of them quickly. Files Reads by Location gives an indicator of where the majority of query execution took place in Depot or in Communal. Top 10 Re-Fetches into Depot, and imagine the charts earlier in our user case, it shows tables that are most frequently fetched and evicted and then fetched again. These are good candidates to get pinned if increasing Depot size is not an option. Note that both of these charts have an option to select time interval using calendar widget. So you can get the information about the activity that happened during that time interval. Depot Pinning shows what portion of your Depot is pinned, both by byte count and by table count. And the three tables at the bottom show Depot structure. How long tables stay in Depot, we would like tables to be fetched in Depot and stay there for a long time, how often they are accessed, again, the tables in Depot, we would like to see them accessed frequently, and what the size range of tables in Depot. Depot Content. This tab allows us to search for tables that are currently in Depot and also to see stats like table size in Depot. How often tables are accessed and when were they last accessed. And the same information that's available for tables in Depot is also available on projections and partition levels for those tables. Depot Pinning. This tab allows users to see what policies are currently existing and so you can do this by clicking on the first little button and click search. This'll show you all existing policies that are already created. The second option allows you to search for a table and create a policy. You can also use the action column to modify existing policies or delete them. And the third option provides details about most frequently re-fetched tables, including fetch count, total access count, and number of re-fetched bytes. So all this information can help to make decisions regarding pinning specific tables. So that's about it about the Depot. And I should mention that the server team also has a very good presentation on the, webinar, on the Eon Mode database Depot management and subcluster management. that strongly recommend it to attend or download the slide presentation. Let's talk quickly about the Management Console Roadmap, what we are planning to do in the future. So we are going to continue focusing on subcluster management, there is still a lot of things we can do here. Promoting/demoting subclusters. Load balancing across subclusters, scheduling subcluster actions, support for large cluster mode. We'll continue working on Workload Analyzer enhancement recommendation, on backup and restore from the MC. Building custom thresholds, and Eon on HDFS support. Okay, so we are ready now to take any questions you may have now. Thank you.

>> Jeff: Hello, everybody and thank you for Joining us today for the virtual "Vertica VBC" 2020. Today's breakout session has been titled "Optimizing Query Performance and Resource Pool Tuning" I'm Jeff Ealing, I lead Vertica marketing. I'll be your host for this breakout session. Joining me today are Rakesh Banula, and Abhi Thakur, Vertica product technology engineers and key members of the Vertica customer success team. But before we begin, I encourage you to submit questions or comments during the virtual session. You don't have to wait. Just type your question or comment in the question box below the slides and click Submit. There will be a Q&A session at the end of the presentation. We'll answer as many questions we're able to during that time. Any questions we don't address, we'll do our best to answer them offline. Alternatively, visit Vertica forums at forum.vertica.com to post your questions there after the session. Our engineering team is planning to Join the forums to keep the conversation going. Also a reminder that you can maximize your screen by clicking the double arrow button in the lower right corner of your slides. And yes, this virtual session is being recorded, will be available to view on demand this week. We'll send you a notification as soon as it's ready. Now let's get started. Over to you Rakesh. >> Rakesh: Thank you, Jeff. Hello, everyone. My name is Rakesh Bankula. Along with me, we have Bir Abhimanu Thakur. We both are going to cover the present session on "Optimizing Query Performance and Resource Pool Tuning" In this session, we are going to discuss query optimization, how to review the query plans and how to get the best query plans with proper production design. Then discuss on resource allocations and how to find resource contention. And we will continue the discussion on important use cases. In general, to successfully complete any activity or any project, the main things it requires are the plan. Plan for that activity on what to do first, what to do next, what are things you can do in parallel? The next thing you need, the best people to work on that project as per the plan. So, first thing is a plan and next is the people or resources. If you overload the same set of people, our resources by involving them in multiple projects or activities or if any person or resource is sick in a given project is going to impact on the overall completion of that project. The same analogy we can apply through query performance too. For a query to perform well, it needs two main things. One is the best query plan and other is the best resources to execute the plan. Of course, in some cases, resource contention, whether it can be from system side or within the database may slow down the query even when we have best query plan and best resource allocations. We are going to discuss each of these three items a little more in depth. Let us start with query plan. User submits the query to database and Vertica Optimizer generates the query plan. In generating query plans, optimizer uses the statistics information available on the tables. So, statistics plays a very important role in generating good query plans. As a best practice, always maintain up-to-date statistics. If you want to see how query plan looks like, add explain keyword in front of your query and run that query. It displays the query plan on the screen. Other option is BC explained plans. It saves all the explained plans of the queries run on the database. So, once you have a query plan, once you're checking it to make sure plan is good. The first thing I would look for, no statistics are predicted out of range. If you see any of these, means table involved in the query, have no up to date statistics. It is now the time to update the statistics. Next thing to explain plans are broadcast, three segments around the Join operator, global re segments around a group by operators. These indicate during the runtime of the query, data flow between the nodes over the network and will slow down the query execution. As far as possible, prevent such operations. How to prevent this, we will discuss in the projection design topic. Regarding the Join order, check on inner side and outer side, which tables are used, how many rows each side processing. In (mumbles) picking a table, having smaller number of rows is good in case of as shown as, as Join built in memory, smaller the number of rows, faster it is to build the hash table and also helps in consuming less memory. Then check if the plan is picking query specific projection or default projections. If optimizer ignoring any query specific projection, but picking the default super projection will show you how to use query specific hints to follow the plant to pick query specific projections which helps in improving the performance. Okay, here is one example query plan of a query trying to find number of products sold from a store in a given state. This query is having Joins between store table, product table and group by operation to find the count. So, first look for no statistics particularly around storage access path. This plan is not reporting any no statistics. This means statistics are up to date and plan is good so far. Then check what projections are used. This is also around the storage access part. For Join orders check, we have Hash Join in path ID 4 having it In Path ID 6 processing 60,000 rows and outer is in Path ID 7 processing 20 million rows. Inner side processing last record is good. This helps in building hash table quicker by using less memory. Check if any broadcast re segments, Joins in Path ID 4 and also Path ID 3. Both are having inner broadcast, Inners are having 60,000 records are broadcasted to all nodes in the cluster. This could impact the query performance negatively. These are some of the main things which we normally check in the explained plans. Still now, We have seen that how to get good query plans. To get good query plans, we need to maintain up to date statistics and also discussed how to review query plans. Projection design is the next important thing in getting good query plans, particularly in preventing broadcasts re segments. Broadcast re segments happens during Join operation, random existing segmentation class of the projections involved in the Join not matching with the Join columns in the query. These operations causes data flow over the network and negatively impacts the query performance particularly when it transfers millions or billions of rows. These operations also causes query acquire more memory particularly in network send and receive operations. One can avoid these broadcast re segments with proper projection segmentation, say, Join involved between two fact tables, T1, T2 on column I then segment the projections on these T1, T2 tables on column I. This is also called identically segmenting projections. In other cases, Join involved between a fact table and a dimension table then replicate or create an unsegmented projection on dimension table will help avoiding broadcast re segments during Join operation. During group by operation, global re segment groups causes data flow over the network. This can also slow down the query performance. To avoid these global re segment groups, create segmentation class of the projection to match with the group by columns in the query. In previous slides, we have seen the importance of projection segmentation plus in preventing the broadcast re segments during the Join operation. The order by class of production design plays important role in picking the Join method. We have two important Join methods, Merge Join and Hash Join. Merge Join is faster and consumes less memory than hash Join. Query plan uses Merge Join when both projections involved in the Join operation are segmented and ordered on the Join keys. In all other cases, Hash Join method will be used. In case of group by operation too, we have two methods. Group by pipeline and group by Hash. Group by pipeline is faster and consumes less memory compared to group by Hash. The requirements for group by pipeline is, projection must be segmented and ordered by on grouping columns. In all other cases, group by hash method will be used. After all, we have seen importance of stats and projection design in getting good query plans. As statistics are based on estimates over sample of data, it is possible in a very rare cases, default query plan may not be as good as you expected, even after maintaining up-to-date stats and good projection design. To work around this, Vertica providing you some query hints to force optimizer to generate even better query plans. Here are some example Join hints which helps in picking Join method and how to distribute the data, that is broadcast or re segment on inner or outer side and also which group by method to pick. The table level hints helps to force pick query specific projection or skipping any particular projection in a given query. These all hints are available in Vertica documentation. Here are a few general hints useful in controlling how to load data with the class materialization et cetera. We are going to discuss some examples on how to use these query hints. Here is an example on how to force query plan to pick Hash Join. The hint used here is JTYPE, which takes arguments, H for HashJoin, M for MergeJoin. How to place this hint, just after the Join keyword in the query as shown in the example here. Another important Join in this, JFMT, Join For My Type hint. This hint is useful in case when Join columns are lost workers. By default Vertica allocates memory based on column data type definition, not by looking at the actual data length in those columns. Say for example, Join column defined as (mumbles) 1000, 5000 or more, but actual length of the data in this column is, say, less than 50 characters. Vertica going to use more memory to process such columns in Join and also slow down the Join processing. JSMP hint is useful in this particular case. JSMP parameter uses the actual length of the Join column. As shown in the example, using JFMP of V hint helps in reducing the memory requirement for this query and executes faster too. Distrib hint helps in how to force inner or outer side of the Join operator to be distributed using broadcast or re segment. Distrib takes two parameters. First is the outer site and second is the inner site. As shown in the example, DISTRIB(A,R) after Join keyword in the query helps to force re segment the inner side of the Join, outer side, leaving it to optimizer to choose that distribution method. GroupBy Hint helps in forcing query plan to pick Group by Hash or Group by Pipeline. As shown in the example, GB type or hash, used just after group by class in the query helps to force this query to pick Group by Hashtag. See now, we discussed the first part of query performance, which is query plans. Now, we are moving on to discuss next part of query performance, which is resource allocation. Resource Manager allocates resources to queries based on the settings on resource pools. The main resources which resource pools controls are memory, CPU, query concurrency. The important resource pool parameters, which we have to tune according to the workload are memory size, plan concurrency, mass concurrency and execution parallelism. Query budget plays an important role in query performance. Based on the query budget, query planner allocate worker threads to process the query request. If budget is very low, query gets less number of threads, and if that query requires to process huge data, then query takes longer time to execute because of less threads or less parallelism. In other case, if the budget is very high and query executed on the pool is a simple one which results in a waste of resources, that is, query which acquires the resources holds it till it complete the execution, and that resource is not available to other queries. Every resource pool has its own query budget. This query budget is calculated based on the memory size and client and currency settings on that pool. Resource pool status table has a column called Query Budget KB, which shows the budget value of a given resource pool. The general recommendation for query budget is to be in the range of one GB to 10 GB. We can do a few checks to validate if the existing resource pool settings are good or not. First thing we can check to see if query is getting resource allocations quickly, or waiting in the resource queues longer. You can check this in resource queues table on a live system multiple times, particularly during your peak workload hours. If large number of queries are waiting in resource queues, indicates the existing resource pool settings not matching with your workload requirements. Might be, memory allocated is not enough, or max concurrency settings are not proper. If query's not spending much time in resource queues indicates resources are allocated to meet your peak workload, but not sure if you have over or under allocated the resources. For this, check the budget in resource pool status table to find any pool having way larger than eight GB or much smaller than one GB. Both over allocation and under allocation of budget is not good for query performance. Also check in DC resource acquisitions table to find any transaction acquire additional memory during the query execution. This indicates the original given budget is not sufficient for the transaction. Having too many resource pools is also not good. How to create resource pools or even existing resource pools. Resource pool settings should match to the present workload. You can categorize the workload into well known workload and ad-hoc workload. In case of well-known workload, where you will be running same queries regularly like daily reports having same set of queries processing similar size of data or daily ETL jobs et cetera. In this case, queries are fixed. Depending on the complexity of the queries, you can further divide it into low, medium, high resource required pools. Then try setting the budget to 1 GB, 4 GB, 8 GB on these pools by allocating the memory and setting the plan concurrency as per your requirement. Then run the query and measure the execution time. Try couple UP iterations by increasing and then decreasing the budget to find the best settings for your resource pools. For category of ad-hoc workload where there is no control over the number of users going to run the queries concurrently, or complexity of queries user going to submit. For this category, we cannot estimate, in advance, the optimum query budget. So for this category of workload, we have to use cascading resource pool settings where query starts on the pool based on the runtime they have set, then query resources moves to a secondary pool. This helps in preventing smaller queries waiting for resources, longer time when a big query consuming all resources and rendering for a longer time. Some important resource pool monitoring tables, analyze system, you can query resource cues table to find any transaction waiting for resources. You will also find on which resource pool transaction is waiting, how long it is waiting, how many queries are waiting on the pool. Resource pool status gives info on how many queries are in execution on each resource pool, how much memory in use and additional info. For resource consumption of a transaction which was already completed, you can play DC resource acquisitions to find how much memory a given transaction used per node. DC resource pool move table shows info on what our transactions moved from primary to secondary pool in case of cascading resource pools. DC resource rejections gives info on which node, which resource a given transaction failed or rejected. Query consumptions table gives info on how much CPU disk network resources a given transaction utilized. Till now, we discussed query plans and how to allocate resources for better query performance. It is possible for queries to perform slower when there is any resource contention. This contention can be within database or from system side. Here are some important system tables and queries which helps in finding resource contention. Table DC query execution gives the information on transaction level, how much time it took for each execution step. Like how much time it took for planning, resource allocation, actual execution etc. If the time taken is more in planning, which is mostly due to catalog contentions, you can play DC lock releases table as shown here to see how long transactions are waiting to acquire global catalog lock, how long transaction holding GCL x. Normally, GCL x acquire and release should be done within a couple of milliseconds. If the transactions are waiting for a few seconds to acquire GCL x or holding GCL x longer indicates some catalog contention, which may be due to too many concurrent queries or due to long running queries, or system services holding catalog mutexes and causing other transactions to queue up. A query is given here, particularly the system tables will help you further narrow down the contention. You can vary sessions table to find any long-running user queries. You can query system services table to find any service like analyze row counts, move out, merge operation and running for a long time. DC all evens table gives info on what are slower events happening. You can also query system resource usage table to find any particular system resource like CPU memory, disk IO or network throughput, saturating on any node. It is possible once slow node in the cluster could impact overall performance of queries negatively. To identify any slow node in the cluster, we use queries. Select one, and (mumbles) Clearly key one query just executes on initiative node. On a good node, kV one query returns within 50 milliseconds. As shown here, you can use a script to run this, select kV one query on all nodes in the cluster. You can repeat this test multiple times, say five to 10 times then reveal the time taken by this query on all nodes in all tech (mumbles) . If there is any one node taking more than a few seconds compared to other notes taking just milliseconds, then something is wrong with that node. To find what is going on with the node, which took more time for kV one query, run perf top. Perf top gives info on stopped only lister functions in which system spending most of the time. These functions can be counter functions or Vertica functions, as shown here. Based on their systemic spending most of the time we'll get some clue on what is going on with that code. Abhi will continue with the remaining part of the session. Over to you Abhi. >> Bir: Hey, thanks, Rakesh. My name is Abhimanu Thakur and today I will cover some performance cases which we had addressed recently in our customer clusters which we will be applying the best practices just showed by Rakesh. Now, to find where the performance problem is, it is always easy if we know where the problem is. And to understand that, like Rakesh just explained, the life of a query has different phases. The phases are pre execution, which is the planning, execution and post execution which is releasing all the required resources. This is something very similar to a plane taking a flight path where it prepares itself, gets onto the runway, takes off and lands back onto the runway. So, let's prepare our flight to take off. So, this is a use case which is from a dashboard application where the dashboard fails to refresh once in a while, and there is a batch of queries which are sent by the dashboard to the Vertica database. And let's see how we can be able to see where the failure is or where the slowness is. To reveal the dashboard application, these are very shortly queries, we need to see what were the historical executions and from the historical executions, we basically try to find where is the exact amount of time spent, whether it is in the planning phase, execution phase or in the post execution and if they are pretty consistent all the time, which means the plan has not changed in the execution which will also help us determine what is the memory used and if the memory budget is ideal. As just showed by Rakesh, the budget plays a very important role. So DC query executions, one-stop place to go and find your timings, whether it is a timing extra or is it execute plan or is it an abandoned plan. So, looking at the queries which we received and the times from the scrutinize, we find most of the time average execution, the execution is pretty consistent and there is some time, extra time spent in the planning phase which users of (mumbles) resource contention. This is a very simple matrix which you can follow to find if you have issues. So the system resource convention catalog contention and resource contention, all of these contribute mostly because of the concurrency. And let's see if we can drill down further to find the issue in these dashboard application queries. So, to get the concurrency, we pull out the number of queries issued, what is the max concurrency achieved, what are the number of threads, what is the overall percentage of query duration and all this data is available in the V advisor report. So, as soon as you provide scrutinize, we generate the V advisor report which helps us get complete insight of this data. So, based on this we definitely see there is very high concurrency and most of the queries finish in less than a second which is good. There are queries which go beyond 10 seconds and over a minute, but so definitely, the cluster had concurrency. What is more interesting is to find from this graph is... I'm sorry if this is not very readable, but the topmost line what you see is the Select and the bottom two or three lines are the create, drop and alters. So definitely this cluster is having a lot of DDL and DMLs being issued and what do they contribute is if there is a large DDL and DMLs, they cause catalog contention. So, we need to make sure that the batch, what we're sending is not causing too many catalog contention into the cluster which delays the complete plan face as the system resources are busy. And the same time, what we also analyze is the analyze tactics running every hour which is very aggressive, I would say. It should be scheduled to be need only so if a table has not changed drastically that's not scheduled analyzed tactics for the table. A couple more settings has shared by Rakesh is, it definitely plays a important role in the modeled and mode operations. So now, let's look at the budget of the query. The budget of the resource pool is currently at about two GB and it is the 75 percentile memory. Queries are definitely executing at that same budget, which is good and bad because these are dashboard queries, they don't need such a large amount of memory. The max memory as shown here from the capture data is about 20 GB which is pretty high. So what we did is, we found that there are some queries run by different user who are running in the same dashboard pool which should not be happening as dashboard pool is something like a premium pool or kind of a private run way to run your own private jet. And why I made that statement is as you see, resource pools are lik runways. You have different resource pools, different runways to cater different types of plane, different types of flights which... So, as you can manage your resource pools differently, your flights can take off and land easily. So, from this we did remind that the budget is something which could be well done. Now let's look... As we saw in the previous numbers that there were some resource weights and like I said, because resource pools are like your runways. So if you have everything ready, your plane is waiting just to get onto the runway to take off, you would definitely not want to be in that situation. So in this case, what we found is the coolest... There're quite a bit number of queries which have been waited in the pool and they waited almost a second and which can be avoided by modifying the the amount of resources allocated to the resource pool. So in this case, we increase the resource pool to provide more memory which is 80 GB and reduce the budget from two GB to one GB. Also making sure that the plan concurrency is increased to match the memory budget and also we moved the user who was running into the dashboard query pool. So, this is something which we have gone, which we found also in the resource pool is the execution parallelism and how this affects and what what number changes. So, execution parallelism is something which allocates the plan, allocates the number of threads, network buffers and all the data around it before even the query executes. And in this case, this pool had auto, which defaults to the core count. And so, dashboard queries not being too high on resources, they need to just get what they want. So we reduced the execution parallelism to eight and this drastically brought down the amount of threads which were needed without changing the time of execution. So, this is all what we saw how we could tune before the query takes off. Now, let's see what path we followed. This is the exact path what we followed. Hope of this diagram helps and these are the things which we took care of. So, tune your resource pool, adjust your execution parallelism based on the type of the queries the resource pool is catering to and match your memory sizes and don't be too aggressive on your resource budget. And see if you could replace your staging tables with temporary tables as they help a lot in reducing the DDLs and DMLs, reducing the catalog contention and the places where you cannot replace them with the truncate tables, reduce your analyzed statics duration and if possible, follow the best practices for a couple more operations. So moving on, let's let our query take a flight and see what best practices can be applied here. So this is another, I would say, very classic example of query where the query has been running and suddenly stops to fail. And if there is... I think most of the other seniors in a Join did not fit in memory. What does this mean? It basically means the inner table is trying to build a large Hash table, and it needs a lot of memory to fit. There are only two reasons why it could fail. One, your statics are outdated and your resource pool is not letting you grab all the memory needed. So in this particular case, the resource pool is not allowing all the memory it needs. As you see, the query acquire 180 GB of memory, and it failed. When looking at the... In most cases, you should be able to figure out the issue looking at the explained plan of the query as shared by Rakesh earlier. But in this case if you see, the explained plan looks awesome. There's no other operator like in a broadcast or outer V segment or something like that, it's just Join hash. So looking further we find into the projection. So inner is on segmented projection, the outer is segmented. Excellent. This is what is needed. So in this case, what we would recommend is go find further what is the cost. The cost to scan this row seems to be pretty high. There's the table DC query execution in their profiles in Vertica, which helps you drill down to every smallest amount of time, memory and what were the number of rows used by individual operators per pack. So, while looking into the execution engine profile details for this query, we found the amount of time spent is on the Join operator and it's the Join inner Hash table build time, which has taking huge amount of time. It's just waiting basically for the lower operators can and storage union to pass the data. So, how can we avoid this? Clearly, we can avoid it by creating a segmented projection instead of unsegmented projection on such a large table with one billion rows. Following the practice to create the projection... So this is a projection which was created and it was segmented on the column which is part of the select clause over here. Now, that plan looks nice and clean still, and the execution of this query now executes in 22 minutes 15 seconds and the most important you see is the memory. It executes in just 15 GB of memory. So, basically to what was done is the unsegmented projection which acquires a lot of memory per node is now not taking that much of memory and executing faster as it has been divided by the number of nodes per node to execute only a small share of data. But, the customer was still not happy as 22 minutes is still high. And let's see if we can tune it further to make the cost go down and execution time go down. So, looking at the explained plan again, like I said, most of the time, you could see the plan and say, "What's going on?" In this case, there is an inner re segment. So, how could we avoid the inner re segments? We can avoid the inner re segment... Most of the times, all the re segments just by creating the projection which are identically segmented which means your inner and outer both have the same amount, same segmentation clause. The same was done over here, as you see, there's now segment on sales ID and also ordered by sales ID which helps us execute the query drop from 22 minutes to eight minutes, and now the memory acquired is just equals to the pool budget which is 8 GB. And if you see, the most What is needed is the hash Join is converted into a merge Join being the ordered by the segmented clause and also the Join clause. So, what this gives us is, it has the new global data distribution and by changing the production design, we have improved the query performance. But there are times when you could not have changed the production design and there's nothing much which can be done. In all those cases, as even in the first case of Vertica after fail of the inner Join, the second Vertica replan (mumbles) spill to this operator. You could let the system degrade by acquiring 180 GB for whatever duration of minutes the query had. You could simply use this hand to replace and run the query in the very first go. Let the system have all the resources it needs. So, use hints wherever possible and filter disk is definitely your option where there're no other options for you to change your projection design. Now, there are times when you find that you have gone through your query plan, you have gone through every other thing and there's not much you see anywhere, but you definitely look at the query and you feel that, "Now, I think I can rewrite this query." And how what makes you decide that is you look at the query and you see that the same table has been accessed several times in my query plan, how can I rewrite this query to access my table just once? And in this particular use case, a very simple use case where a table is scanned three times for several different filters and then a union in Vertica union is kind of costly operator I would say, because union does not know what's the amount of data which should be coming from the underlying query. So we allocate a lot of resources to keep the union running. Now, we could simply replace all these unions by simple "Or" clause. So, simple "Or" clause changes the complete plan of the query and the cost drops down drastically. And now the optimizer almost know the exact amount of rows it has to process. So change, look at your query plans and see if you could make the execution in the profile or the optimizer do better job just by doing some small rewrites. Like if there are some tables frequently accessed you could even use a "With" clause which will do an early materialization and make use the better performance or for the union which I just shared and replace your left Joins with right Joins, use your (mumbles) like shade earlier for you changing your hash table types. This is the exact part what we have followed in this presentation. Hope this presentation was helpful in addressing, at least finding some performance issues in your queries or in your class test. So, thank you for listening to our presentation. Now we are ready for Q&A.