>>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.

>> Narrator: From theCube studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is theCube conversation. >> Hi everybody. Welcome to theCUBE, this is Dave Vellante, and we're here to talk about a very important topic around de-risking infrastructure with business continuity. This is critical, especially in the era of COVID. And with me, to really explore this issue is Dr. Rico, who's the vice president office of the CTO at INFINIDAT Doc. Good to see you. >> Good to see you again, Dave. >> And Ken Steinhardt, is also here as a field CTO at INFINIDAT and I got to tell the audience, Doc, you're also the chairman of the Mass Motorcycles Association. You're a very cool guy. You're a pilot, you're a firearms instructor, all about safety, and Ken and Doc you're both musicians, right? Doc, I think he played the drums, and Ken, I know when we first met, you're a music guy, so wow. Surrounded by talent so, thank you so much for coming on. >> Glad to be here. Great to see you. >> For the other thing too is that you guys are long time storage industry experts. I've known you both for many, many years. INFINIDAT deep engineering expertise of course, everybody knows about Moshay, he created the most successful product in the history of the storage industry. And we're going to talk about the importance of data, especially in this era of COVID, and how mission criticality has really become more and more important. So, I want to start Doc with you and this notion of business continuity. How are you thinking about, and INFINIDAT thinking about business continuity in this isolation era? >> Well, that's a really great question Dave, because it has changed quite a bit. And as you said, we've known each other a long time, all the way back to when I still had hair, that was how long ago it was. But, business continuity is something that every business constantly looks at throughout their evolution. And it's one of these things where certain applications are typically more mission critical than others. And lately, what we've seen is this genre of a lights out data center that has become absolutely critical operating a business today. People can't just be on site anymore. People need to be working remotely, and that includes data center personnel and in many respects. So, this whole concept of business continuity now encompasses not only the operation equipment that's on premises, or sometimes even off premises, but it also encompasses applications that people need access to that they may not have thought of mission critical before, because working from home was a convenience or working remotely was a convenience, not a requirement for that business. >> You, Ken, I know you talked to a lot of CIOs. I was sitting at a CIO round table with my friends down at ETR recently, and one of the CIO said, when COVID hit, we realized that our business quote unquote business continuity plans were just way too narrowly focused on DR. What do you see from the IT community? >> It's funny because I literally was on a CIO round table with the West Coast this morning. And there were a couple of interesting comments that really stuck out to me from some of the people there. One was commenting of just reaffirming, what Doc said, how much people are working from home now. They said, traditionally they'd had traditional offices and they've just recently hired in this company about 250 people. He said, all of them are going to be remote workers and their normal from here on out, for the next 150 they're looking to hire is just that business as usual will be remote work. And one of the other CIOs chimed in with a quote that really stuck out to me. He said, "Remote work requires always on infrastructure in this day and age." And it's just a whole new way of having to make sure that businesses are operational and their workers can do what they're supposed to do. >> Well, so let's stay on that. I mean, ransomware's on everybody's mind. I mean, all you have to do is look at the stock market, you see, what's happened with Zoom, it's exploded. All the end point securities, identity access management security companies are going crazy, because (chuckles) people are now so vulnerable. So, they're more exposed to ransomware, Ken, what do we really need to know about ransomware? First, the smart company, smart organization is the one that is prepared and assumes the worst. Which means don't think it can't happen to you, especially when you look at a couple of the more public examples in the last couple of years in particular. So, it means you must take steps to protect yourself, particularly for the sake of your company, your business, your employees, your shareholders, your customers, everyone else. And that means deploying technology that assumes that if the worst case scenario could happen to you, how do you make sure that you have taken the steps that you can avoid the worst possible scenarios that could happen? >> Well, you know, Doc, lot of times when you have this discussion on ransomware, people say, well, should I pay the ransom? And sometimes people say, well, yeah, maybe it should go. You hope you never get there, right? (chuckles) >> Right, you absolutely hope you never get there. There is such horrible examples of paying ransom that just don't work. Just look at the Somalia pirates as an example, right? It doesn't stop them at all, but, take a look at what the potential impact is, not the potential impact to your business and your employees, but the potential impact to society. A couple of years ago with Sony, was very notorious case. More recently, a couple of months ago, Garmin. As you mentioned, I'm a pilot, but I was very worried as what reservoir, a lot of people in the aircraft and in aviation industry. What's going to happen not only with our private information, the account information, but what's going to happen with avionics updates? If Garmin didn't have a fallback plan, a way to recover, then what was going to happen? And I'm sure they were going through the process and the thoughts of, should we pay this year? How else do we get out of this? But, fortunately they had a very good plan in place and it only took them a couple of days to restore back to normal operations. Arguably as far as avionics goes, they were lucky in the sense that this happened to them right in the middle of an update cycle, which is 28 day cycle. But the fact that it only took them a couple of days, congratulations to them. I'm sure that with even better plans and a little bit of extra effort, it could have been a matter of hours instead of days. >> Well, let's come back to business continuity. Ken, do you feel as though businesses are not prepared based on the conversation we were having earlier? >> Some are, some aren't. It will be getting into that, I think in a little bit more detail as well, but historically, organizations I think have focused far too much just on traditional disaster recovery, usually with things like some of the technologies that have been around a long while like backup, and onto often having focused towards the technologies that really do keep the business running without human intervention if something were to ever go wrong. >> So, Doc, anything you'd add to that? I mean, what's the state of business continuity from your perspective? Are people having to really starting to accelerate a journey because of this COVID? >> I absolutely think they're accelerating a journey. They're also looking now at, this concept of multiple active sites. The concept of active sites is not something new, it's something that dates back a couple of decades and a lot of the financial industry. When they were struck, they were looking at some very significant changes in their operational paradigm because they realized that the system is going down and is only a small percentage of the problem that people impact is far worse. The operational procedures, the human intervention. So, what they would do is typically build out multiple sites and rotate the applications between them. What they really haven't done yet, at least not on a broad scale and certainly not in the U.S and some cases in Europe, they started this journey, having applications running simultaneously in multiple sites accessing the same data sets. It's not a brand new concept, but it's something that has improved significantly. The technologies have improved significantly over the course of the past decade. And with the introduction of our active backend solution, a couple of years ago, even brought it to an entirely new level. >> The people aspect that Doc mentioned is so critical. And that's certainly been one of the key lessons learned when real disasters have occurred is that the systems have to be, if you really want to keep your business operating making an assumption that people are going to have depending upon the nature of the disaster. Very different priorities and one of them is not, Gee, do I keep these ITs systems running or not? They're going to be worried about their co-workers, their families, other things, et cetera. So, the ultimate has to be systems that are capable of continuing the operation of the business in the face of a site failure, a metropolitan area failure or whatever it takes without the requirement necessarily for human intervention. >> So, I want to get into active-active. But before we do, I wonder if we could do a little sort of data protection one on one, a back up, a replication, you got snapshots, Doc, what do we need to know about each in the context of this discussion? >> I think the important thing to look at when you think about the different types of technologies and say you apply the solutions is that some of them apply to specific equipment failures, and some of them apply to data failure. And I separate equipment from data in the sense that data can be corrupted in some shape or form. It can be through malicious attack, like ransomware as an example, only one example, other types of malware can play a factor as well, or it can be incidental. Somebody pressing the wrong button, it can be an operational procedure, perhaps another system failure that causes a change in the data or corruption in the data that makes it essentially unusable. So, whenever we're looking at this, we have to start with what is the recovery point objective. The RPO that's where most people start with. And in the RPO, in essence, if you think of time zero, right now, it's where the failure occurs. Walk backwards. How far back can I go and still sustain my business? Now, there may be other procedural things you can do to catch up as close to that RPO and zero as you can, but each of these technologies that we're talking about give you a different RPOs, like rewinding a tape back to a point in time. So, that's the first place to start. >> Okay. So, let's bring up that slide actually. I actually liked this as the fireball slide I call it, but this is how people measure sort of the business impact, if you will, RPO and RTO. And what I like about this is in this digital world, it's kind of a cliche, but everything's getting more intense. People want, they don't want to lose data when you ask a customer, how much data are you willing to lose? They say none. >> None. >> And you say, well, how much are you willing to pay? So, Ken, I wonder if you could sort of describe that tension and that dynamic that's really underscored in this slide. >> Yeah. Oh, yeah, you hit it on the head David. It's the traditional trade off between RPO, RTO and cost. As Doc described with RPO, the objective would be to get as close to zero data loss as you could possibly get, with RTO which measures the time associated with how long will it take you to get back to your acceptable level of RPO. That is a time factor where for every minute or second, that goes by that you're not in business, that's the extension of the RTO. And historically, the closer you get as you approach zero RPO and zero RTO, usually the greater the cost goes up. And it's always been the eternal trade off, is a great analogy. It's sort of like if you want to buy a car. RPO equates for the quality of the solution, RTO is time or speed and cost is cost. If you buy a car, if it's good and it's fast, it won't be cheap. If it's good, and it's cheap, it won't be fast. And if it's fast, and it's cheap, it won't be good. So, usually that's the kind of tradeoff we will have to deal with there. And, the factors that will impact that, as Doc alluded to can be many. There's many aspects that you have to consider in terms of what is the service level that the business requires, and do we have solutions in place that can actually give us what is the real service level of the business requires if something were to go bad. >> Because, customers have gone through, unnatural acts, and Doc before you were kind of describing what some people would refer to as, as a three site, data centers and all kinds of things that people will do, but that brings us to active-active, Doc, what is active-active? >> Yeah, let me interject a point there, and then I'll get to your question about active-active. First is the question I can raise about service level, that's absolutely critical. And business may have different service levels for different applications. >> Dave: Right. >> And you never really know what that is. For example, I was working with a university a few years back, you normally think, well, universities is where they worried about, they're worried about their grading systems. Everybody's always worried about their financial systems. This particular university was worried about their golf course reservations system. (laughs) And their number one mission critical application, and I'm sure there was a little chunk tongue and cheek there as well, was the golf course reservation system because that directly impacted, there were alumni and had a direct correlation to the incoming donations for the following year. So, you never know what's going to be mission critical. Closer to home working very recently, there's a great case study from Aultman Hospital on a website. One of the things that they did, which I thought was absolutely astounding, was they took advantage of our offer to loan them free storage for a while, leveraging some of the COD that they're passing on demand that they weren't using. One of the reasons that they wanted this extra capacity was so that they can make telepresence available to their patients to visit with their families. At a time when families can't go into the hospital visit, when people are ill, what a great comfort to their family. So, this is a great way to look at it. When you think about these different service levels now, and you think about the different types of replication technologies that are available. Look at the multisite, what is multisite really doing for you? Multisite is giving you some level of synchronous replication so that you have an RPO of zero recovery point objective. It still may not be an RTO or zero, but it will be darn close to it. But more importantly, it's giving you an additional site to really maintain that RPO of zero in case the disaster radius, the blast area, the impact zone is even further away. Now, this isn't going to prevent any type of malicious intent, it's not going to prevent the ransomware case, and things like that, but it'll certainly prevent the catastrophic failure of the data center. What does active-active do? Well, active-active now, gives you the read write capability. And now our multisite implementation by the way, leverages our active-active. So, gives you the ability now to have the simultaneously running instance of an application in multiple data centers, reading and writing from the same dataset. And what that gives you, is not only an RPO of zero, but an RTO of zero, because now you can have an application in another data center stand in and take over for it. Naturally, the application needs to be able to do that. There are a lot of applications that are capable of it. The Oracle parallel server or rack technology, gives you that capability. There are other types of clustering technologies that will fail almost instantaneously, that will give you that capability. So, that's where really active-active comes into play. >> Yeah, makes sense for me. When I started the industry, the VAX clusters were sort of the now thing, right? >> Yup. >> (indistinct) (Dave chuckles) >> All right. So, what are you seeing in the marketplace? Are you seeing... What's the adoption look like? Are there any differences that you see by region? What can you tell us there? >> Yeah, it's interesting. Some of the first organizations that obviously jumped on to active-active type solutions, were those where there were in particularly, in things like financial services, some compliance requirements or financial incentives or motivation to make sure that the business was always operational. And it's interesting because there was a study that was done all the way back in 2003, by Roper, that asked business executives and IT executives the same questions relative to their perceptions of their companies or organizations ability to meet RPO or RTO service level agreements. >> Right. And we have some data on this that I want to bring up. So, this is the RPO data but please carry on. >> Ken: Exactly, and so they asked questions that really were about RPO or RTO. Hey, if a disaster hit, would you lose data and how much? And what the data showed was that the business executives and IT executives in Europe, were actually pretty much on the same page. They both said, yeah, we probably would lose some data or a reasonable amounts associated with it. But what was a little frightening, was there appeared to be a chasm of disconnect between the business executives, from the IT executives in the U.S. And what it showed was that the IT executives were on the same page as the European IT executives and the business executives from Europe, saying that, yeah, we'd probably lose some data. But it showed that very few of the business executives thought that they would. And then similarly, when they were asked the question about RTO, how long would it take? In terms of days, hours, et cetera, for your full operation to be back in operational and granted they were talking in 2003 terms back then, which was a little longer than where the technology can now address it now. There was, again, this consistency between the IT executives in both continents and countries, as well as the European business executives, but again, a disconnect where the business executives in the U.S thought, oh, no, we'll be fine. We'll have everything back in a couple of days or less than, it won't be an issue. In my opinion, in looking at that data, when it first came out, my impression was, well, now I understand why a lot of business continuity projects don't get approved because the IT people know that they need it, but the business executives have, if I could be so bold, an unrealistically optimistic view of their ability to achieve RPO and RTO, I'll give you a great example. There was a major high tech company around that timeframe that actually had a major outage in their email system. And email was not perceived to be at the time, ultra mission critical application for them. I know it seems strange in this day and age, but back then it was considered sort of an afterthought and they had a four hour SLA in case something went down where, hey, if we're down for four hours, we get it back and four hours, we're fine. And so, IT thought, they were doing a great job, 'cause they got it back in less than four. It was about three point something. And it turned out that the real impact of the business was so overwhelming, they had to completely overhaul the IT infrastructure that they've put in place to deliver that. So, it's an interesting issue, and it's the kind of thing where, as a result, I believe that as we sit here today in 2020, the disconnect in the U.S still exists. If you look across Europe, you tend to find a lot of deployments of active-active. The first country that probably did a ton of it was Germany, and then, lot of the other European countries did as well. For a multitude of reasons, you tend to see a lot of active-active deployments in Europe, but you don't see anywhere near as many as if I could be so bold, we probably should be seeing in the U.S, and I believe a major contributing factor to that is that there is still this disconnect, between business executives having a false sense of security that is unfounded by the infrastructures that they have in place. And if they were to ask their IT people, and maybe that's a good idea for them to talk more, they'd probably find that they're more exposed than they ever realized. >> Right. And of course in Europe, you've got, much tighter proximity, and you're up against borders of a 200 mile or a 200 kilometer roll, governments have tried to impose here, really can't be imposed in a lot of cases. Okay. Let's get into what you guys are doing here in the space. So, Doc, how do you approach ensuring access to mission critical data? What's INFINIDAT's angle? >> Yeah, I think it's several different layers that need to be applied here. The first INFINIDAT angle starts with the fact that our storage is a hundred percent data availability guarantee. It's simple enough. It's triple redundant architecture, seven nines reliability design, which equates to 3.16 seconds per year of downtime, which is less than a scuzzy time (laughs) I bet you know. Let's start with just, right, forget the nonsense, the system's are a hundred percent available guaranteed. We put some teeth behind that, and that's a great way to start. It's not necessarily going to fundamentally protect your data from site outages and network outages and server outages and things like that, so, let's be fed up and can go to in active-active infrastructure. And now you can take the system and put it either elsewhere behind a firewall on the same data center floor, or in a metropolitan area. Wherever you need it to be, separate power zones, separate networks zones, make it even more available. And then if you really want to go that next level of protection because you're worried about regional outages and things of that nature, multisite replication. But now it's up the ante even further. Let's look at the malicious intent, let's look at the data corruption. Let's look at all of the other possibilities of things that can happen to your data. So, implement snapshotting technology, in this snapshot technology, and InfiniBox is essentially free. There's no cost for the software, there is no performance impact because it's part of metadata updates that are happening all the time anyway. So, there's zero additional overhead of that. There's no additional, there's no copying of data going on with a snapshot, so there's no additional cost penalty associated with it. And you can snapshot this frequently for a Snapshot any of your data frequently to protect against data corruption. And if you're worried about some sort of malicious aspect, that's going to engage and perhaps gain access to the snapshots, we have immutable technology, and that is also free. It's there, it doesn't cost you anything other than the time it takes for the administrator to determine what the policy is. And now that can not be modified. It can't be deleted, it can't be modified, it can't be updated, can't be written to your inside whatever the polyp the defined policy is. So, now you're protected, you're a hundred percent availability, increase data hundred percent availability with active-active, and then increase your RPO capability with dissonance and protect yourself against data corruption with immutable snapshots. Or some combination of standard snapshots and immutable snapshots. >> Yeah, so, I was going to ask Ken, if this is a cost effective approach, but, I mean, it's free, it comes in the stack. >> That is the key word, and you both just said it. Standard and included functionality all based on that great snapshot technology, which was the foundation for it that Doc described. Active-active, standard and included, the ability to go to a third site for disaster recovery at the industry's lowest asynchronous RPO with a remote site. Standard and included, immutable snaps, standard and included. So, compared to traditional views of what most people had back to our illustrious triangle earlier of RPO versus RTO versus cost, you're still going to have the additional cost of media and remote site for protecting your data, obviously, but in terms of software license costs, we're making it simpler, we're making it easier, we're making it standard and included, and we're just making it so much more readily available for organizations to be able to achieve superior RTO and RPO at a cost point that maybe certainly is a little bit higher than just having that single system that Doc alluded to, it's still a hundred percent available, but it's way below what the expectations of this industry have been over the last 20 years. >> Yeah, which is double, triple, I mean easily. Well, can I understand you for a second. You've worked for a lot of different storage companies, Doc you as well, but how different is this? How unique is this? >> There are surprisingly few vendors that can offer true zero RPO at two zero RTO. There's really only a handful. We're one of them. And by handful, I mean about three in the industry, including ourselves, and where I think we differentiate is fundamentally to a lot of those points we just mentioned. The software standard and included so we're not going to charge you extra for it. It's going to be relatively simple to deploy and integrate a stock alluded to earlier with server cluster software and the key components that people would use there in terms of databases and in terms of operating systems. And it's fundamentally going to be able to offer not just that zero RPO, zero RTO active-active environment, but if you do, and when you do need to go to a third site at distance for the true disaster recovery, if you ever lost a metropolitan area, we're going to be able to do it at an RPO that is lower than anything else on the market. >> Doc, are there complexities associated with doing this at petabyte scale? I mean, you guys make a big deal out of that, and you're clearly excited about it, but, is it extra hard to do at that kind of volume at scale? >> I'm going to give you two answers, and say, yes, it's incredibly difficult to do, but then I'm going to say it's incredibly easy for the customer to do because we've made it easy. There a lot of ramifications to doing things at petabyte scale. There's the size of the caching cables that you don't have to worry about. There's the numbers of things that need to be checked, and counter checked and constantly crosscheck for validity. There's also the scale of things that happen like silent data corruption that need to be factored in. All of those things are being done by InfiniBox, on a constant basis with no impact to the customer, no impact to the administrator, no impact to the running application. And I think that's a frankly, another differentiator as well. Ken and I have some common history as well. (chuckles) Used to constantly talk about internally, what happens as things get larger, systems slow down. That simply doesn't happen with InfiniBox. And that's why service providers use us as well. Cloud service providers managed service providers are some of our biggest customers. Because they know they can have these large scale systems running with all these different workloads, all these different functions, be they snapshots, clones, whatever they are, with no impact and very easy and rapid to deploy. >> Yeah, I set up top, you got to be storage hardos to make this stuff work. (laughs) It's very complicated and we've seen it for years and years. Last question. Again, huge changes in the last 150 days where people are just really tuned in to things like digital transformation, I talked about security, business resiliency, business continuity. Where... I'll start with you Ken, how should users be thinking about this? What steps should they be taking like now? >> What a great question. And back to sort of where we started, because of the nature of how things have changed, more applications are mission critical than they've ever been before. And providing, and always on infrastructure to make sure that you can give your users and your customers and your business, the opportunity to stay alive in the face of just about anything that could happen has never been more important in the history of this industry. >> Doc, I'll give you the final word, you can pile on that. >> I think Ken summed it up really well, but I'm going to take a different twist on it. It's all about de-risking, and a lot of the CIOs and CTOs of companies that I've been talking to over the course of the past couple of months, have basically said, hey, my digital transformation initiatives are on hold right now because I've got to keep the lights on, I've got to keep my business running. In some cases, maybe I've had to sadly pare down my staff, but I've got, remote workers have got to worry about. So, find a partner that's going to de-risk your infrastructure for you. Take a look at some of the things that we've announced in the past few months as well. We'll take a lot of that risk way, not only from the availability perspective, but we're going to take the risk away from a cost perspective. If you want to talk about INFINIDAT, don't worry about things like, how am I going to migrate over to it? We're going to do that for you. We're going to work with you, we're going to come up with a plan, we're going to make as much of it non-disruptive as we can, and we're going to assume the cost of doing it. We're going to take away all the risk of availability. We just talked about all of that. We're going to give you guarantees, that are a hundred percent availability. We'll help you architect the right solution for you and we'll protect you moving forward. You might need some flex area of capacity as you work through some of these new applications and new initiatives, so, you've got to be willing to take the risk away with our elastic pricing models. Use the storage when you need it, return it when you don't, and you don't have to pay for it anymore. We'll make it that simple for you. We'll give you that cloud operating paradigm on premises, and by the way, no egress costs. (Dave laughs) >> Well, this is a hard problem for people because they've had to do the work from home pivot, IT people, specifically, I mean, they've had to spend to shore up that infrastructure and of course, organizations just saying, well, we're going to pull from other places, but, look, if you're not digital today, you're not being able to transact business. And so, you can't relax your business continuity plans, in fact, you have to evolve them. Guys, thanks very much for sharing your perspectives and insights on this whole notion of de-risking infrastructure with business continuity. Thanks for coming on. >> Thank you, Dave. >> Dave, is always a pleasure. Thank you. >> Cheers, and thank you everybody for watching, this is Dave Vallante for theCube, and we'll see you next time. (upbeat music)

>> Narrator: From theCube studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is theCube conversation. >> Hi everybody. Welcome to theCUBE, this is Dave Vellante, and we're here to talk about a very important topic around de-risking infrastructure with business continuity. This is critical, especially in the era of COVID. And with me, to really explore this issue is Dr. Rico, who's the vice president office of the CTO at INFINIDAT Doc. Good to see you. >> Good to see you again, Dave. >> And Ken Steinhardt, is also here as a field CTO at INFINIDAT and I got to tell the audience, Doc, you're also the chairman of the Mass Motorcycles Association. You're a very cool guy. You're a pilot, you're a firearms instructor, all about safety, and Ken and Doc you're both musicians, right? Doc, I think he played the drums, and Ken, I know when we first met, you're a music guy, so wow. Surrounded by talent so, thank you so much for coming on. >> Glad to be here. Great to see you. >> For the other thing too is that you guys are long time storage industry experts. I've known you both for many, many years. INFINIDAT deep engineering expertise of course, everybody knows about Moshay, he created the most successful product in the history of the storage industry. And we're going to talk about the importance of data, especially in this era of COVID, and how mission criticality has really become more and more important. So, I want to start Doc with you and this notion of business continuity. How are you thinking about, and INFINIDAT thinking about business continuity in this isolation era? >> Well, that's a really great question Dave, because it has changed quite a bit. And as you said, we've known each other a long time, all the way back to when I still had hair, that was (indistinct). But, business continuity is something that every business constantly looks at throughout their evolution. And it's one of these things where certain applications are typically more mission critical than others. And lately, what we've seen is this genre of a lights out data center that has become absolutely critical operating a business today. People can't just be on site anymore. People need to be working remotely, and that includes data center personnel and in many respects. So, this whole concept of business continuity now encompasses not only the operation equipment that's on premises, or sometimes even off premises, but it also encompasses applications that people need access to that they may not have thought of mission critical before, because working from home was a convenience or working remotely was a convenience, not a requirement for that business. >> You, Ken, I know you talked to a lot of CIOs. I was sitting at a CIO round table with my friends down at ETR recently, and one of the CIO said, when COVID hit, we realized that our business quote unquote business continuity plans were just way too narrowly focused on DR. What do you see from the IT community? >> It's funny because I literally was on a CIO round table with the West Coast this morning. And there were a couple of interesting comments that really stuck out to me from some of the people there. One was commenting of just reaffirming, what Doc said, how much people are working from home now. They said, traditionally they'd had traditional offices and they've just recently hired in this company about 250 people. He said, all of them are going to be remote workers and their normal from here on out, for the next 150 they're looking to hire is just that business as usual will be remote work. And one of the other CIOs chimed in with a quote that really stuck out to me. He said, "Remote work requires always on infrastructure in this day and age." And it's just a whole new way of having to make sure that businesses are operational and their workers can do what they're supposed to do. >> Well, so let's stay on that. I mean, ransomware's on everybody's mind. I mean, all you have to do is look at the stock market, you see, what's happened with Zoom, it's exploded. All the end point securities, identity access management security companies are going crazy, because (chuckles) people are now so vulnerable. So, they're more exposed to ransomware, Ken, what do we really need to know about ransomware? First, the smart company, smart organization is the one that is prepared and assumes the worst. Which means don't think it can't happen to you, especially when you look at a couple of the more public examples in the last couple of years in particular. So, it means you must take steps to protect yourself, particularly for the sake of your company, your business, your employees, your shareholders, your customers, everyone else. And that means deploying technology that assumes that if the worst case scenario could happen to you, how do you make sure that you have taken the steps that you can avoid the worst possible scenarios that could happen? >> Well, you know, Doc, lot of times when you have this discussion on ransomware, people say, well, should I pay the ransom? And sometimes people say, well, yeah, maybe it should go. You hope you never get there, right? (chuckles) >> Right, you absolutely hope you never get there. There is such horrible examples of paying ransom that just don't work. Just look at the Somalia pirates as an example, right? It doesn't stop them at all, but, take a look at what the potential impact is, not the potential impact to your business and your employees, but the potential impact to society. A couple of years ago with Sony, was very notorious case. More recently, a couple of months ago, Garmin. As you mentioned, I'm a pilot, but I was very worried as what reservoir, a lot of people in the aircraft and in aviation industry. What's going to happen not only with our private information, the account information, but what's going to happen with avionics updates? If Garmin didn't have a fallback plan, a way to recover, then what was going to happen? And I'm sure they were going through the process and the thoughts of, should we pay this year? How else do we get out of this? But, fortunately they had a very good plan in place and it only took them a couple of days to restore back to normal operations. Arguably as far as avionics goes, they were lucky in the sense that this happened to them right in the middle of an update cycle, which is 28 day cycle. But the fact that it only took them a couple of days, congratulations to them. I'm sure that with even better plans and a little bit of extra effort, it could have been a matter of hours instead of days. >> Well, let's come back to business continuity. Ken, do you feel as though businesses are not prepared based on the conversation we were having earlier? >> Some are, some aren't. It will be getting into that, I think in a little bit more detail as well, but historically, organizations I think have focused far too much just on traditional disaster recovery, usually with things like some of the technologies that have been around a long while like backup, and onto often having focused towards the technologies that really do keep the business running without human intervention if something were to ever go wrong. >> So, Doc, anything you'd add to that? I mean, what's the state of business continuity from your perspective? Are people having to really starting to accelerate a journey because of this COVID? >> I absolutely think they're accelerating a journey. They're also looking now at, this concept of multiple active sites. The concept of active sites is not something new, it's something that dates back a couple of decades and a lot of the financial industry. When they were struck, they were looking at some very significant changes in their operational paradigm because they realized that the system is going down and is only a small percentage of the problem that people impact is far worse. The operational procedures, the human intervention. So, what they would do is typically build out multiple sites and rotate the applications between them. What they really haven't done yet, at least not on a broad scale and certainly not in the U.S and some cases in Europe, they started this journey, having applications running simultaneously in multiple sites accessing the same data sets. It's not a brand new concept, but it's something that has improved significantly. The technologies have improved significantly over the course of the past decade. And with the introduction of our active backend solution, a couple of years ago, even brought it to an entirely new level. >> The people aspect that Doc mentioned is so critical. And that's certainly been one of the key lessons learned when real disasters have occurred is that the systems have to be, if you really want to keep your business operating making an assumption that people are going to have depending upon the nature of the disaster. Very different priorities and one of them is not, Gee, do I keep these ITs systems running or not? They're going to be worried about their co-workers, their families, other things, et cetera. So, the ultimate has to be systems that are capable of continuing the operation of the business in the face of a site failure, a metropolitan area failure or whatever it takes without the requirement necessarily for human intervention. >> So, I want to get into active-active. But before we do, I wonder if we could do a little sort of data protection one on one, a back up, a replication, you got snapshots, Doc, what do we need to know about each in the context of this discussion? >> I think the important thing to look at when you think about the different types of technologies and say you apply the solutions is that some of them apply to specific equipment failures, and some of them apply to data failure. And I separate equipment from data in the sense that data can be corrupted in some shape or form. It can be through malicious attack, like ransomware as an example, only one example, other types of malware can play a factor as well, or it can be incidental. Somebody pressing the wrong button, it can be an operational procedure, perhaps another system failure that causes a change in the data or corruption in the data that makes it essentially unusable. So, whenever we're looking at this, we have to start with what is the recovery point objective. The RPO that's where most people start with. And in the RPO, in essence, if you think of time zero, right now, it's where the failure occurs. Walk backwards. How far back can I go and still sustain my business? Now, there may be other procedural things you can do to catch up as close to that RPO and zero as you can, but each of these technologies that we're talking about give you a different RPOs, like rewinding a tape back to a point in time. So, that's the first place to start. >> Okay. So, let's bring up that slide actually. I actually liked this as the fireball slide I call it, but this is how people measure sort of the business impact, if you will, RPO and RTO. And what I like about this is in this digital world, it's kind of a cliche, but everything's getting more intense. People want, they don't want to lose data when you ask a customer, how much data are you willing to lose? They say none. >> None. >> And you say, well, how much are you willing to pay? So, Ken, I wonder if you could sort of describe that tension and that dynamic that's really underscored in this slide. >> Yeah. Oh, yeah, you hit it on the head David. It's the traditional trade off between RPO, RTO and cost. As Doc described with RPO, the objective would be to get as close to zero data loss as you could possibly get, with RTO which measures the time associated with how long will it take you to get back to your acceptable level of RPO. That is a time factor where for every minute or second, that goes by that you're not in business, that's the extension of the RTO. And historically, the closer you get as you approach zero RPO and zero RTO, usually the greater the cost goes up. And it's always been the eternal trade off, is a great analogy. It's sort of like if you want to buy a car. RPO equates for the quality of the solution, RTO is time or speed and cost is cost. If you buy a car, if it's good and it's fast, it won't be cheap. If it's good, and it's cheap, it won't be fast. And if it's fast, and it's cheap, it won't be good. So, usually that's the kind of tradeoff we will have to deal with there. And, the factors that will impact that, as Doc alluded to can be many. There's many aspects that you have to consider in terms of what is the service level that the business requires, and do we have solutions in place that can actually give us what is the real service level of the business requires if something were to go back? >> Because, customers have gone through, unnatural acts, and Doc before you were kind of describing what some people would refer to as, as a three site, data centers and all kinds of things that people will do, but that brings us to active-active, Doc, what is active-active? >> Yeah, let me interject a point there, and then I'll get to your question about active-active. First is the question I can raise about service level, that's absolutely critical. And business may have different service levels for different applications. >> Dave: Right. >> And you never really know what that is. For example, I was working with a university a few years back, you normally think, well, universities is where they worried about, they're worried about their grading systems. Everybody's always worried about their financial systems. This particular university was worried about their golf course reservations system. (laughs) And their number one mission critical application, and I'm sure there was a little chunk tongue and cheek there as well, was the golf course reservation system because that directly impacted, there were alumni and had a direct correlation to the incoming donations for the following year. So, you never know what's going to be mission critical. Closer to home working very recently, there's a great case study from Aultman Hospital on a website. One of the things that they did, which I thought was absolutely astounding, was they took advantage of our offer to loan them free storage for a while, leveraging some of the COD that they're passing on demand that they weren't using. One of the reasons that they wanted this extra capacity was so that they can make telepresence available to their patients to visit with their families. At a time when families can't go into the hospital visit, when people are ill, what a great comfort to their family. So, this is a great way to look at it. When you think about these different service levels now, and you think about the different types of replication technologies that are available. Look at the multisite, what is multisite really doing for you? Multisite is giving you some level of synchronous replication so that you have an RPO of zero recovery point objective. It still may not be an RTO or zero, but it will be darn close to it. But more importantly, it's giving you an additional site to really maintain that RPO of zero in case the disaster radius, the blast area, the impact zone is even further away. Now, this isn't going to prevent any type of malicious intent, it's not going to prevent the ransomware case, and things like that, but it'll certainly prevent the catastrophic failure of the data center. What does active-active do? Well, active-active now, gives you the read write capability. And now our multisite implementation by the way, leverages our active-active. So, gives you the ability now to have the simultaneously running instance of an application in multiple data centers, reading and writing from the same dataset. And what that gives you, is not only an RPO of zero, but an RTO of zero, because now you can have an application in another data center stand in and take over for it. Naturally, the application needs to be able to do that. There are a lot of applications that are capable of it. The Oracle parallel server or rack technology, gives you that capability. There are other types of clustering technologies that will fail almost instantaneously, that will give you that capability. So, that's where really active-active comes into play. >> Yeah, makes sense for me. When I started the industry, the VAX clusters were sort of the now thing, right? >> Yup. >> (indistinct) (Dave chuckles) >> All right. So, what are you seeing in the marketplace? Are you seeing... What's the adoption look like? Are there any differences that you see by region? What can you tell us there? >> Yeah, it's interesting. Some of the first organizations that obviously jumped on to active-active type solutions, were those where there were in particularly, in things like financial services, some compliance requirements or financial incentives or motivation to make sure that the business was always operational. And it's interesting because there was a study that was done all the way back in 2003, by Roper, that asked business executives and IT executives the same questions relative to their perceptions of their companies or organizations ability to meet RPO or RTO service level agreements. >> Right. And we have some data on this that I want to bring up. So, this is the RPO data but please carry on. >> Ken: Exactly, and so they asked questions that really were about RPO or RTO. Hey, if a disaster hit, would you lose data and how much? And what the data showed was that the business executives and IT executives in Europe, were actually pretty much on the same page. They both said, yeah, we probably would lose some data or a reasonable amounts associated with it. But what was a little frightening, was there appeared to be a chasm of disconnect between the business executives, from the IT executives in the U.S. And what it showed was that the IT executives were on the same page as the European IT executives and the business executives from Europe, saying that, yeah, we'd probably lose some data. But it showed that very few of the business executives thought that they would. And then similarly, when they were asked the question about RTO, how long would it take? In terms of days, hours, et cetera, for your full operation to be back in operational and granted they were talking in 2003 terms back then, which was a little longer than where the technology can now address it now. There was, again, this consistency between the IT executives in both continents and countries, as well as the European business executives, but again, a disconnect where the business executives in the U.S thought, oh, no, we'll be fine. We'll have everything back in a couple of days or less than, it won't be an issue. In my opinion, in looking at that data, when it first came out, my impression was, well, now I understand why a lot of business continuity projects don't get approved because the IT people know that they need it, but the business executives have, if I could be so bold and unrealistically optimistic view of their ability to achieve RPO and RTO, I'll give you a great example. There was a major high tech company around that timeframe that actually had a major outage in their email system. And email was not perceived to be at the time, ultra mission critical application for them. I know it seems strange in this day and age, but back then it was considered sort of an afterthought and they had a four hour SLA in case something went down where, hey, if we're down for four hours, we get it back and four hours, we're fine. And so, IT thought, they were doing a great job, 'cause they got it back in less than four. It was about three point something. And it turned out that the real impact of the business was so overwhelming, they had to completely overhaul the IT infrastructure that they've put in place to deliver that. So, it's an interesting issue, and it's the kind of thing where, as a result, I believe that as we sit here today in 2020, the disconnect in the U.S still exists. If you look across Europe, you tend to find a lot of deployments of active-active. The first country that probably did a ton of it was Germany, and then, lot of the other European countries did as well. For a multitude of reasons, you tend to see a lot of active-active deployments in Europe, but you don't see anywhere near as many as if I could be so bold, we probably should be seeing in the U.S, and I believe a major contributing factor to that is that there is still this disconnect, between business executives having a false sense of security that is unfounded by the infrastructures that they have in place. And if they were to ask their IT people, and maybe that's a good idea for them to talk more, they'd probably find that they're more exposed than they ever realized. >> Right. And of course in Europe, you've got, much tighter proximity, and you're up against borders of a 200 mile or a 200 kilometer roll, governments have tried to impose here, really can't be imposed in a lot of cases. Okay. Let's get into what you guys are doing here in the space. So, Doc, how do you approach ensuring access to mission critical data? What's INFINIDAT's angle? >> Yeah, I think it's several different layers that need to be applied here. The first INFINIDAT angle starts with the fact that our storage is a hundred percent data availability guarantee. It's simple enough. It's triple redundant architecture, seven nines reliability design, which equates to 3.16 seconds per year of downtime, which is less than a scuzzy time (laughs) I bet you know. Let's start with just, right, forget the nonsense, the system's are a hundred percent available guaranteed. We put some teeth behind that, and that's a great way to start. It's not necessarily going to fundamentally protect your data from site outages and network outages and server outages and things like that, so, let's be fed up and can go to in active-active infrastructure. And now you can take the system and put it either elsewhere behind a firewall on the same data center floor, or in a metropolitan area. Wherever you need it to be, separate power zones, separate networks zones, make it even more available. And then if you really want to go that next level of protection because you're worried about regional outages and things of that nature, multisite replication. But now it's up the ante even further. Let's look at the malicious intent, let's look at the data corruption. Let's look at all of the other possibilities of things that can happen to your data. So, implement snapshotting technology, in this snapshot technology, and InfiniBox is essentially free. There's no cost for the software, there is no performance impact because it's part of metadata updates that are happening all the time anyway. So, there's zero additional overhead of that. There's no additional, there's no copying of data going on with a snapshot, so there's no additional cost penalty associated with it. And you can snapshot this frequently for a Snapshot any of your data frequently to protect against data corruption. And if you're worried about some sort of malicious aspect, that's going to engage and perhaps gain access to the snapshots, we have immutable technology, and that is also free. It's there, it doesn't cost you anything other than the time it takes for the administrator to determine what the policy is. And now that can not be modified. It can't be deleted, it can't be modified, it can't be updated, can't be written to your inside whatever the polyp the defined policy is. So, now you're protected, you're a hundred percent availability, increase data hundred percent availability with active-active, and then increase your RPO capability with dissonance and protect yourself against data corruption with immutable snapshots. Or some combination of standard snapshots and immutable snapshots. >> Yeah, so, I was going to ask Ken, if this is a cost effective approach, but, I mean, it's free, it comes in the stuff. >> That is the key word, and you both just said it. Standard and included functionality all based on that great snapshot technology, which was the foundation for it that Doc described. Active-active, standard and included, the ability to go to a third site for disaster recovery at the industry's lowest asynchronous RPO with a remote site. Standard and included, immutable snaps, standard and included. So, compared to traditional views of what most people had back to our illustrious triangle earlier of RPO versus RTO versus cost, you're still going to have the additional cost of media and remote site for protecting your data, obviously, but in terms of software license costs, we're making it simpler, we're making it easier, we're making it standard and included, and we're just making it so much more readily available for organizations to be able to achieve superior RTO and RPO at a cost point that maybe certainly is a little bit higher than just having that single system that Doc alluded to, it's still a hundred percent available, but it's way below what the expectations of this industry have been over the last 20 years. >> Yeah, which is double, triple, I mean easily. Well, can I understand you for a second. You've worked for a lot of different storage companies, Doc you as well, but how different is this? How unique is this? >> There are surprisingly few vendors that can offer true zero RPO at two zero RTO. There's really only a handful. We're one of them. And by handful, I mean about three in the industry, including ourselves, and where I think we differentiate is fundamentally to a lot of those points we just mentioned. The software standard and included so we're not going to charge you extra for it. It's going to be relatively simple to deploy and integrate a stock alluded to earlier with server cluster software and the key components that people would use there in terms of databases and in terms of operating systems. And it's fundamentally going to be able to offer not just that zero RPO, zero RTO active-active environment, but if you do, and when you do need to go to a third site at distance for the true disaster recovery, if you ever lost a metropolitan area, we're going to be able to do it at an RPO that is lower than anything else on the market. >> Doc, are there complexities associated with doing this at petabyte scale? I mean, you guys make a big deal out of that, and you're clearly excited about it, but, is it extra hard to do at that kind of volume at scale? >> I'm going to give you two answers, and say, yes, it's incredibly difficult to do, but then I'm going to say it's incredibly easy for the customer to do because we've made it easy. There a lot of ramifications to doing things at petabyte scale. There's the size of the caching cables that you don't have to worry about. There's the numbers of things that need to be checked, and counter checked and constantly crosscheck for validity. There's also the scale of things that happen like silent data corruption that need to be factored in. All of those things are being done by InfiniBox, on a constant basis with no impact to the customer, no impact to the administrator, no impact to the running application. And I think that's a frankly, another differentiator as well. Ken and I have some common history as well. (chuckles) Used to constantly talk about internally, what happens as things get larger, systems slow down. That simply doesn't happen with InfiniBox. And that's why service providers use us as well. Cloud service providers managed service providers are some of our biggest customers. Because they know they can have these large scale systems running with all these different workloads, all these different functions, be they snapshots, clones, whatever they are, with no impact and very easy and rapid to deploy. >> Yeah, I set up top, you got to be storage hardos to make this stuff work. (laughs) It's very complicated and we've seen it for years and years. Last question. Again, huge changes in the last 150 days where people are just really tuned in to things like digital transformation, I talked about security, business resiliency, business continuity. Where... I'll start with you Ken, how should users be thinking about this? What steps should they be taking like now? >> What a great question. And back to sort of where we started, because of the nature of how things have changed, more applications are mission critical than they've ever been before. And providing, and always on infrastructure to make sure that you can give your users and your customers and your business, the opportunity to stay alive in the face of just about anything that could happen has never been more important in the history of this industry. >> Doc, I'll give you the final word, you can pile on that. >> I think Ken summed it up really well, but I'm going to take a different twist on it. It's all about de-risking, and a lot of the CIOs and CTOs of companies that I've been talking to over the course of the past couple of months, have basically said, hey, my digital transformation initiatives are on hold right now because I've got to keep the lights on, I've got to keep my business running. In some cases, maybe I've had to sadly pare down my staff, but I've got, remote workers have got to worry about. So, find a partner that's going to de-risk your infrastructure for you. Take a look at some of the things that we've announced in the past few months as well. We'll take a lot of that risk way, not only from the availability perspective, but we're going to take the risk away from a cost perspective. If you want to talk about INFINIDAT, don't worry about things like, how am I going to migrate over to it? We're going to do that for you. We're going to work with you, we're going to come up with a plan, we're going to make as much of it non-disruptive as we can, and we're going to assume the cost of doing it. We're going to take away all the risk of availability. We just talked about all of that. We're going to give you guarantees, that are a hundred percent availability. We'll help you architect the right solution for you and we'll protect you moving forward. You might need some flex area of capacity as you work through some of these new applications and new initiatives, so, you've got to be willing to take the risk away with our elastic pricing models. Use the storage when you need it, return it when you don't, and you don't have to pay for it anymore. We'll make it that simple for you. We'll give you that cloud operating paradigm on premises, and by the way, no egress costs. (Dave laughs) >> Well, this is a hard problem for people because they've had to do the work from home pivot, IT people, specifically, I mean, they've had to spend to shore up that infrastructure and of course, organizations just saying, well, we're going to pull from other places, but, look, if you're not digital today, you're not being able to transact business. And so, you can't relax your business continuity plans, in fact, you have to evolve them. Guys, thanks very much for sharing your perspectives and insights on this whole notion of de-risking infrastructure with business continuity. Thanks for coming on. >> Thank you, Dave. >> Dave, is always a pleasure. Thank you. >> Cheers, and thank you everybody for watching, this is Dave Vallante for theCube, and we'll see you next time. (upbeat music)

>> from the Silicon Angle Media Office in Boston, Massachusetts. It's the cue Now, here's your host. Day Volonte. >> Hi, buddy. This is David Lantz. Welcome to this cube. Conversation with Dr Rico is the CMO of infinite out. It's still I still have a hard time saying that doctor or an engineer and I love having you on because we could talk storage. We could go deep and we could talk trends and marketing trends, too. But so welcome. Thanks for coming on my sled. So tell me what's new since the scale to win launch that you guys had. Tell me what you know. Is everything shipping Now What's the uptake been like with customers? And the reaction? Yeah, >> they're the reaction has been phenomenal. This, as you may recall, you were there. It was biggest launch in our history, which was fantastic. And the reaction has just been overwhelmingly positive, with customers with partners with analysts. Human scum cases with competitors is an interesting you know, we had a lot of things that were already shipping. They were an early customer release. There were a few things that we had started shipping in December on the things that we said we'd be coming in three Q. We G eight on time. So there, there now all generally available except the stuff that we talked about that would be available in 2020 which right now looks like it's on track. It's doing very, very well. >> So VM wear VM world eyes coming up later on this month, things are obviously changing. There was announcement recently that that VM wears gonna choir pivotal. So a little bit of financial engineering going on stock stock rose 77% on the day when the Dow dropped 800. So okay, the funny money. But things are changing in the V m where ecosystem you certainly saw we we This is our 10th year the M world. We go back and you hear Tod Nielsen back in the day, talk about for every dollar spent on a V M where lice and 15 was spent a Negro system, you know, we're kinda del izing vm wear now, which is sort of interesting, but I'm curious as to what you're seeing what that all means to you. I mean, still half a million 600,000 customers, you've got to be there you guys have great success at that show. So your thoughts what's going on? But VM world this year? Yeah, I >> kind of kind of loaded their first of all congratulations on the milestone. That's great. 10 years is super. Remember, probably seeing you with the 1st 1 there. Of course we knew each other longer. Uh, you know, and sure I get the incestuous, you know, money changing of hand there, I think I think it's it's good in one respect. You certainly CBM where, you know, making big inroads with VM wear on AWS. And this isn't now with Pivotal will be a good launching platform for Della's well, a svm where to be a little bit more in control of their own destiny. And it's certainly the way a lot of people are going. We're doing a lot of that ourselves. Not so much, in a sense. We don't have a cloud platform that we sell is a total encompassing platform. But of course, with new tricks cloud on big players and then certainly a large portion of our our customer base, our cloud service providers, they love our stuff. It helps them compete. It actually gives them in some respects, a competitive advantage, but VM world itself. Lots going on there. We have amplified our presence once again because VM where does represent a large portion of our customer base? So we're we're very proud of that. We're very proud to be a technology alliance partner of the M wears Andi. We're expecting to see a really good show in a really good cloud. A cloud crowd has they return back to their home base in San Francisco for us this year, it's It's gonna be a different experience. Were tellingme or of the software story, more of the portfolio story more about how you scare scale the win. We have a virtual presence this year, which is going to be very helpful in telling that story. Customers can come in and they can see more than just a ah box that in our world is really not important because it's for us. It's all about the software and stuff we do. We even in Booth Theater, we have some private meeting spaces well, to take people into a bigger, deeper drill down. But the virtual experience will allow them to touch and feel stuff that maybe they didn't get to do before, and that's gonna be kind of exciting as well. >> So you mentioned C S P s. We had Michael Gray thrive on a while back, and you know, he was saying that Look, he likes your product because it allows him to do other things. And don't worry about, you know, the old sort of tuning and managing and ableto re shift labor. I felt like that was an interesting discussion, primarily because you've got all these cloud service providers that everybody thought aws was just gonna kill. And if anything, it's elevated them. What are you seeing in the CSP space? Yeah, you know, >> Michael had a lot of interesting things to say that definitely love the fact that we enable multiple workloads without them having to do lots of cautious planning and re planning and shifting and shuffling. And we are seeing C S P is becoming more value. Add to a lot of businesses, especially the mid market and the smaller enterprise where people may want more than just infrastructure. You know, they don't they need that application level support and companies like thrive in some of our other really good customer, US signal and you know they're all capable of Flex Central's. Another one they're all capable of providing service is beyond the hardware they're capable of providing that application support the guidance and, in the case of Thrive, the cybersecurity guidance especial Really, which is really, really critical. So they're growing, and they're also, by the way, working with eight of us and Google and Azure to provide that capabilities well, when necessary. >> Well, that leads me to the sort of multi cloud discussion in our industry. We tend to have this alphabet soup of acronyms like another reason I like talking to you because we can kind of cut through that. And, you know, I love the marketing. I think marketing helps people understand what's going on differentiate. It gives you an indication of where the industry is going, and multi cloud is one of those things that I mean. I've kind of said it's a symptom of multi vendor and more so than a strategy. But increasingly it seems like it's becoming a strategy with customers, and you just gave an example of thrive working with multiple cloud vendors. Clearly, VM where wants to be in that business. What your thoughts on multi cloud and and hybrid. What does it mean for for infinite at What's your strategy there? You know, it's it's interesting because I >> just read an article the other day about you know, the definition of multi cloud on whether it's being abused and, you know, I I look at it as someone just trying to tell their story and give it. Give it some favor. I think at the end of the day, uh, every business is going to be talking to multiple platforms whether they want to or not. You know, there are many customers and companies out there, businesses who are in our customers who have gone the way of the cloud and repatriated. Certain things is they've they found that it it may work. It may not work, and there are many cloud providers who were trying to do things to accelerate migration of applications because they see that certain applications don't work. You know, we got one of the cloud providers buying Ah, now as provider, another one buying very recently, you know, an envy me based flash company to try to pick up those loose workloads where they might struggle today. But the end of the day everybody's going to be multiple. And whether it's because they're using cloud service is from from a software perspective or whether they just need to basically broker and maintain sort of that that independence so that they can maintain some cost control, availability, control, security, control and in some cases it will remain on premises. And some of things will be off just so they could get the applications closer to their end users. So you know what is multi Cloud? Multi Cloud really is just one of those terms that literally means what it says. It's your business running in multiple places. It doesn't have to necessarily be simultaneously by the same application. >> A big part of your value proposition is the simplicity. We've heard that from your customers, and you guys obviously push that out there. I want to ask you because you mentioned repatriation and you know, Cloud keeps growing like crazy. Sure, and the on prem not so much. You guys are smaller company. You're growing your stealing share, So yep. So maybe is that simplicity thing. Here's my question. So it's around automation. The cloud providers, generally an Amazon specifically have have driven automation. They've attacked the IittIe labor problem and they're able to charge for that on Dhe. So my question is, are you seeing that you're able to attack that labor problem in a similar sense and bring forth the value proposition to customers is Look, we can create a cloud like experience on Prem if you want MacLeod. Great. But if you want to stay on Prem, you're gonna get the benefit of being able to shift. Resource is two more strategic things and not have to worry about all this heavy, heavy lifting. You You seeing tangible evidence of that? >> We're seeing significant tangible evidence of that on and, you know, a couple of things. You know, you talk about growth, right? And I think when we did the launch, you know, only a few months ago we were at about 4.6 exabytes of capacity shipped. We just passed 5.1. That's some significant growth in in just a few months. It's like a 33% growth just from the same time last year, which is which is fairly significant. And of course, if you're familiar with the way we talk, you know you have an engineer is the head of marketing. We like to tell the truth. You know, we don't like to mask, do many things and confuse people. We don't like talking about effective storage because effective capacity doesn't really mean much to some people. So that's, you know, this is what we This is what we shipped and it's growing rapidly. And a lot of that is growing, in part because of the significance of the message and in part because of this need to control costs, contain costs and really operate in a more modern way. So get back to your comments about cloud and cloud operation. That's really what people want. People like the consumption model of cloud. They don't always like the cost on hidden costs. So simplifying that, but giving them the flexibility Thio have either an op X or cap ex that allows him to grow and shrink as they move workloads around. Because everybody grows even on Prem is growing. It's just, you know, it's the law of numbers, right? Cloud is growing, absolutely. But on Prem really is growing. And then the other thing I want is they want the operational flexibility. And that's what we talked about in our elastic data fabric. They don't like constantly having to re jigger and re balance workloads. Infinite box by itself. The platform of infinite Box takes away a lot of that mystery and magic, because it it kind of hides all of the complexity of that workload. And it, you know, we take the randomness out of the I o. I think maybe Craig Hibbert mentioned in his video is he was describing in detail how that happens. Remember Michael Gray talking about that as well, you know, So those those things come out in a single infinite box. But even if you said well, I still want to move my workload from, uh, you know this data center to an adjacent data center or perhaps a data center in another facility. Um, excuse me, Another city. So that's closer to the end user. Making that transparent to the applications is critically important. >> Yes, he talked about growth in about 1/2 a PETA bite. Sorry, half an exabyte in just a few months. A couple months? Really Right. That's that's growth. But I want to ask you about petabytes. Petabytes scales. Kind of key of companies that don't do that in a year day, eh? Exactly. So that's a petabytes scale. Is big party of marketing two questions? Why is that relevant? Or is that relevant to VM? Where customers? Why so and then, does it scare some people owe you? Asked a great question. >> It absolutely scared some people. And I know that there are some pundits out their industry pundits who who basically don't agree with our messaging. But this is this is the business problem that we we targeted the solve rate. Um, there are a lot of people out there who don't think they're petabytes scale yet because maybe they're individual applications aren't petabytes scale. But when you add it up, they get there and a lot of our customers are existing. Customers didn't start with infinite at at petabytes scale. They started a couple 100 terabytes, perhaps, but they're petabytes skill now. In fact, over 80% of the customers and systems that we have out there today or above the petty bite. We have customers that are in the tens of petabytes. We have customers that are in the hundreds of petabytes. They grow, they grow rapidly on. Why is that? Well, to two factors. Really. Number one, if you go back to. Probably when I first met you back when I had your hair, at least in quantity, way had way. Were kind of crusting that terabyte mark. Right? Right. And what was the problem? The problem was nobody could figure out how to deal with the performance. Nobody wanted to put that much risk on a single platform, so they couldn't deal with the availability. And they really didn't know how to deal with even the serviceability of that scale. So terabyte was a problem solved No, 25 years ago, and then things were rapidly from there. Now we're at the same juncture, just three orders of magnitude later. Right? >> Well, that's interesting, because, you know, you're right. People didn't want to put all all that capacity under an actuator that cost performance problems. They were concerned about, you know, just availability. And then two things happen so simultaneously, flash comes along. And, you know, you would say was put sort of a Band aid to some of the performance problems. Sure. And you guys came up with, like, this magic sauce to actually use spinning disc and get the same performance or better performance you would argue with flash. And so as a result, you were now able to do a lot Maur with the data, the concerns about that much date under the actuator somewhat attenuated because, I mean, you've got now so much data, you've got to do something that's almost that's flywheel effective. You've got tons of data machine intelligence and a I. Now, coming into the picture, you've got Cloud, which has been this huge tail when for the industry and for data creation in general. And so I see. You know, you see, like the I. D. C numbers and for forecasting growth of data and storage could be low. I mean, the curve could be bending, you know, kind of more than exponentially your thoughts on that. >> Yeah, it's an interesting, interesting observation. I think what it really comes down to is our storyline is math is greater than media, all right? And when you when you look at the flash being, you know, the panacea to performance it was just a step in the evolution, right? You go back and and say, spinning disc was the same solution to the performance problem 20 years ago. 25 years ago, even it was 5400 rpm discs and then very rapidly. Servers got faster. The interconnects got a little bit faster. They were still mostly differential. Scuzzy. There was 7200 rpm discs. And I promise you, by the way, that if you're running 5400 rpm desk, you install 7200 rpm. All yours performance problems will go away until the day you install it. And then it was 10,000 rpm discs and I was 15,000 rpm disc, and it still wasn't getting fast enough because, you know, you went to Fibre Channel One Gig Fibre channel and then to Geek Fibre, Channel four, Gig fibre, Channel eight, gig fibre channel. The unified connects got faster. The servers got faster. That was more cash on the servers. Then this thing came along, cuts called solid state disc. Right. And then it was it was SLC single layer cell technology. But don't worry about it's very expensive. Not a problem. You only need 4% of your application, right? Jerry? No, no, I'm sorry. percent. No, I'm sorry. 30%. What the heck? You know, M l c is now a little bit more reliable, so let's just make make it all slash. Right? So that was the end of the story, right? No. Servers continue to get faster. Uh, the media continue to get faster and denser, right? So now the interconnect isn't fast enough, So envy me. Is that the answer to life? The universe and everything? Well, wait. I got a better answer for your test. CIA storage class memory in parallel with that. By the way, there are some vendors out there who said that's still not fast enough. We want to put more d ram and the servers and do things in memory. We went in memory databases. I guarantee whatever you do from a media perspective on my personal guarantee to you, it's obsolete by the time you're up and running. By the time you get your applications migrated, configured and running with business value, it's already obsolete. Some vendors got something better coming out. The right answers. This stuff you talked about, the right answer is everything that you're doing for your business. APs. It's a it's a Mel. It's solving the problems in software and, you know, you said we use disc and make it fast. It's not despite itself, of course, right? It's D Bram. It's a lot of the Ram, which, by the way, is orders of magnitude faster than flash the NAND flash. And even if its ECM and still orders of magnitude faster than that, what we use the disk for today in the architecture is the cost factor. We take the random ization out in the flash and we take the >> end and in the in the diagram >> and we used the SAS in the back end to manage costs. But we use it in a way that it performs well, which is highly sequential, massively parallel. And we take full advantage of that Beck and Ben with to do that with that massive dear am front end. Our cash ratios are unparalleled in the industry and and we use it even more effectively that way. But if architecture already evolves, so if if SCM becomes more stable and becomes more cost effective, we can replace that that S S D layer with the cm. And if you know, if the economics of Q L C or something beyond that. Come down will replace the back end with that, do you? Do >> you ever look at what you're doing today as sort of a modern day symmetric. So I mean, a lot of things you just said. I mean, you've got a lot of memory. You've got a massive back end. You know, those were two of the characteristics of symmetric snow. Of course. Fast forward. Whatever. 30 years, right. But a lot of it was sort of intelligence and understanding. Sure. So how data works, is it Is it a fair sort of, or is it radically different? Well, in terms of mindset, I mean, I know the implementation is >> right, right? >> Yeah. I mean, it's not an unfair comparison. I mean, tiered storage was around before some metrics. Right? So it's certainly existed existed then, too. It was just at the time. It was a significant innovation course to layer at the time, right? A big cash front, ending some slower media and then taking advantage of the media on the back end. The big difference today is that if you look at what some metrics became through its Evolution's DMX and V Max and now Power Max. It's still tiered storage, you know, you still have some cash. That's that's for unending some faster media with power. Max, you're you're dealing now with us with an SS a back end. But what happened with those types of architectures is the tearing became more automated. But you're still moving information around. You're still moving Information from one said it This to another set of this leader in the cycle. You're still trying to promote things you know, to to the cash up front. We're doing it in real time. We're >> doing it by analyzing >> the data on the way it comes in. We're reassembling it again, taking the random ization out we're reassembling it and storing it across multiple disks in a way that it it increases our probability of pulling that information associated information back when we need it later. So there's there's no movement. Once its place, we don't have to replace it. You know it's already associated with other data that makes sense, and that gives us a lot of value. >> And secret sauce is the outcome of the secret sauce is you're able to very efficiently. Well, historically, you haven't been able to do a lot of garbage collection, a lot of data movement, and that just kills performance. There's >> really no garbage collection necessary in our in our world way. Also use very modern data structures or patents. Ah, lot of them on our neural cash Deal with the fact that we use a try data structure. So we're not using old fashioned hash tables and you know, l are you algorithms, You know it Sze very, very rapid traverse a ll of these trees >> and you're taking advantage of machine intelligence inside the software architecture. That really is some of the new innovation that really wasn't around to be able to take advantage of that 20 years ago. Maybe it was it was just not cost effective. Do the math was there, put it that the math of the mouth was there and >> there there There's been lots of evolutions of that over the years, a swell, but we continue to evolve and innovate. And, you know, one of the one of the cool things I think about working infinite at is is the multiple multiple generations of engineer where you've got people who understand that math they understand the real nuances of what it means to operate in a world of storage, which is quite a bit different than operating, saying networks or proceed be used because data integrity is paramount. There's lots of lots of things that go on there as well. But we also have younger generations, generations who like new challenges and like to re invent things so they find newer and greater ways to do things. >> This is exciting. So systems, thinkers and I mean server thinkers. I mean, people who understand, you know, systems designed it all the way through and and, you know, newbies who are super smart like you say, wanna learn and solve problems? Go back to the petabytes scale discussion, >> solve problems at petabytes scale, right? Even if the customer doesn't need that necessarily to solve that problem is critically important because even if you look at Les, just take, you know NFS, for example, most NFS systems deal with thousands of objects. Hundreds to thousands of objects are an F s. Implementation deals with billions, right? Do you need billions? How many applications you know that have billions of objects, But being able to do that in a way where performance doesn't degrade over time and also do it in a way where we say our nlm implementation isn't impacted by any any type of service events, we can take a note out, and it doesn't impact in ln There's no no degradation and performance. There's no impact or outage in service. All that's important. Even when you're dealing with smaller application sizes because they add up, they really do add up. He also brought up the point about, you know, density and actually intensity. Great. You know, back 25 years ago, when we were dealing with, you know, the first terabyte storage system, you know, how much how much stories did you have on your laptop? How much you have today, right? You know, you're probably more than a terabyte. They were laughing about putting things terabyte on the floor. And now you get more than a terabyte on your laptop. Things changing? >> Yeah. Um, I wanna ask you where you see the competition. We talked about all flash. We've had a long conversation, long, many conversations in the past about this, But you really, you know, the all flashy kind of described it as a Band Aid, essentially my words, but it was sort of a step function. Okay, great. Um, you have one company, really us who achieve escape velocity in that business in terms of pure But is that where you see in competition and you're seeing it from, you know, the hyper scale er's where you Yeah, you know, >> it's interesting. You know, you look at companies like, you know, we admire what they dio, especially with regard to marketing. They do a really good job of that. They also, um I have some really interesting ideas innovating the media, which is which is great. It helps us in the long run as well. Um, we just look at it as a component of our system, not these system, which makes it different. We don't really see the A f a. You know, the small scale a FAA is are the majority of our competition. We do run into them, but typically it the lower end of the opportunity. Even within the bigger companies that have competitors to those products, we run into them and smaller opportunities, not bigger opportunities where we run into them where there's a significant performance advantage as long as you don't mind the scale out approach to solving the problem. Unfortunately, when you're using a phase two skill out, you know you're putting all of the intelligence requirements on some poor storage administrator or system administrator to figure out what those where right, we take all of that away. So once it starts to scale, that's where we come in a plan. We don't see tons of competition there. Certainly, we're seeing competition from the clouds. And the competition from the clouds is more born of customer mandates and company mandates. Sometimes they I'm not quite sure that everybody knows why there who think to the cloud and we're problem they're trying to solve. But once they start to see a story that says, Hey, if the reasons are and you do understand those reasons, if the reasons are agility and financial flexibility and operational agility not as well as his acquisition agility, you know, we have answers to that and it starts to become a little bit more interesting and compelling. >> All right. One of the highlights of the M world each year is your dinner. Your customer I crashed in a couple of years ago when there were no other analysts there. And then last year again, it was in Vegas. Shows a nice steak house. This year we're in San Francisco, but But I had some great conversations with customers. I remember speaking to one customer about juxtaposing the sand thio to infinite debts platform. And you know the difference. The Sands taken off doing really well, but But he helped me understand the thinking from their standpoint of how they're applying it to solve problems and why v san wasn't a good fit. Your system was, um that was just one of many conversations last year had again other great conversations with customers. What do you do in this year? You have a customer dinner. We are? Yeah. We love to have you in and gave the invitation there. Yeah, the invitation. Is that definitely there? You know, a couple of >> years ago we didn't invite analysts, and you know what it was? It was a mistake. We and we learned that lesson into a large part. We credit you for for showing us how wrong we are. Our customers are very loyal. They're some of the most loyal in the industry. Don't take my word for it going. The gardener Pierre Insights and and look at our numbers compared to everybody else's any pick. Pick a vendor. We're at the top of the list with regard to not only the ratings but, more importantly, the customers willingness to recommend in every category, too. By the way, it's It's not just product quality and performance, and it's it's service support. It's easy doing business. It's an entirely different experience. So we love having the customers there, and the customers love having you there, too. They love having you and your appears in the industry there because they love learning from you and they love answering the questions and getting new insights. And we'd love to have you there. We're gonna be in the Mint this year. San Francisco meant not the not the current one that that's pretty coins, but the original historical site on duh. You know we have. We have invitations out thio to about 130 people because there's only so much room we have it at the event, but we're looking forward to a great time and a great meal and good conversation. >> That's great. Well, VM World is obviously one of the marquee events in our industry. It's the It's the fat middle of where the IittIe pro goes on dhe We're excited. Used to be Labor Day started the fall season. Now it's VM world. Well, Doc will see you out there. Thanks very much for your good to see you. All right. Excellent. All right. Thank you for watching everybody. This is day Volonte in the Cube will see you next time we'll see you at the M World 2019.

>>Hey guys and girls, welcome back to Motor City, Lisa Martin here with John Furrier on the Cube's third day of coverage of Coon Cloud Native Con North America. John, we've had some great conversations over the last two and a half days. We've been talking about identity and security management as a critical need for enterprises within the cloud native space. We're gonna have another quick conversation >>On that. Yeah, we got a great segment coming up from someone who's been in the industry, a long time expert, running a great company. Now it's gonna be one of those pieces that fits into what we call super cloud. Others are calling cloud operating system. Some are calling just Cloud 2.0, 3.0. But there's definitely a major trend happening around how cloud is going Next generation. We've been covering it. So this segment should be >>Great. Let's unpack those trends. One of our alumni is back with us, O Rika Zi, co-founder and CEO of Aerio. Omri. Great to have you back on the >>Cube. Thank you. Great to be here. >>So identity move to the cloud, Access authorization did not talk to us about why you found it assertive, what you guys are doing and how you're flipping that script. >>Yeah, so back 15 years ago, I helped start Azure at Microsoft. You know, one of the first few folks that you know, really focused on enterprise services within the Azure family. And at the time I was working for the guy who ran all of Windows server and you know, active directory. He called it the linchpin workload for the Windows Server franchise, like big words. But what he meant was we had 95% market share and all of these new SAS applications like ServiceNow and you know, Workday and salesforce.com, they had to invent login and they had to invent access control. And so we were like, well, we're gonna lose it unless we figure out how to replace active directory. And that's how Azure Active Directory was born. And the first thing that we had to do as an industry was fix identity, right? Yeah. So, you know, we worked on things like oof Two and Open, Id Connect and SAML and Jot as an industry and now 15 years later, no one has to go build login if you don't want to, right? You have companies like Odd Zero and Okta and one login Ping ID that solve that problem solve single sign-on, on the web. But access Control hasn't really moved forward at all in the last 15 years. And so my co-founder and I who were both involved in the early beginnings of Azure Active directory, wanted to go back to that problem. And that problem is even bigger than identity and it's far from >>Solved. Yeah, this is huge. I think, you know, self-service has been a developer thing that's, everyone knows developer productivity, we've all experienced click sign in with your LinkedIn or Twitter or Google or Apple handle. So that's single sign on check. Now the security conversation kicks in. If you look at with this no perimeter and cloud, now you've got multi-cloud or super cloud on the horizon. You've got all kinds of opportunities to innovate on the security paradigm. I think this is kind of where I'm hearing the most conversation around access control as well as operationally eliminating a lot of potential problems. So there's one clean up the siloed or fragmented access and two streamlined for security. What's your reaction to that? Do you agree? And if not, where, where am I missing that? >>Yeah, absolutely. If you look at the life of an IT pro, you know, back in the two thousands they had, you know, l d or active directory, they add in one place to configure groups and they'd map users to groups. And groups typically corresponded to roles and business applications. And it was clunky, but life was pretty simple. And now they live in dozens or hundreds of different admin consoles. So misconfigurations are rampant and over provisioning is a real problem. If you look at zero trust and the principle of lease privilege, you know, all these applications have these course grained permissions. And so when you have a breach, and it's not a matter of if, it's a matter of when you wanna limit the blast radius of you know what happened, and you can't do that unless you have fine grained access control. So all those, you know, all those reasons together are forcing us as an industry to come to terms with the fact that we really need to revisit access control and bring it to the age of cloud. >>You guys recently, just this week I saw the blog on Topaz. Congratulations. Thank you. Talk to us about what that is and some of the gaps that's gonna help sarto to fill for what's out there in the marketplace. >>Yeah, so right now there really isn't a way to go build fine grains policy based real time access control based on open source, right? We have the open policy agent, which is a great decision engine, but really optimized for infrastructure scenarios like Kubernetes admission control. And then on the other hand, you have this new, you know, generation of access control ideas. This model called relationship based access control that was popularized by Google Zanzibar system. So Zanzibar is how they do access control for Google Docs and Google Drive. If you've ever kind of looked at a Google Doc and you know you're a viewer or an owner or a commenter, Zanzibar is the system behind it. And so what we've done is we've married these two things together. We have a policy based system, OPPA based system, and at the same time we've brought together a directory, an embedded directory in Topaz that allows you to answer questions like, does this user have this permission on this object? And bringing it all together, making it open sources a real game changer from our perspective, real >>Game changer. That's good to hear. What are some of the key use cases that it's gonna help your customers address? >>So a lot of our customers really like the idea of policy based access management, but they don't know how to bring data to that decision engine. And so we basically have a, you know, a, a very opinionated way of how to model that data. So you import data out of your identity providers. So you connect us to Okta or oze or Azure, Azure Active directory. And so now you have the user data, you can define groups and then you can define, you know, your object hierarchy, your domain model. So let's say you have an applicant tracking system, you have nouns like job, you know, know job descriptions or candidates. And so you wanna model these things and you want to be able to say who has access to, you know, the candidates for this job, for example. Those are the kinds of rules that people can express really easily in Topaz and in assertive. >>What are some of the challenges that are happening right now that dissolve? What, what are you looking at to solve? Is it complexity, sprawl, logic problems? What's the main problem set you guys >>See? Yeah, so as organizations grow and they have more and more microservices, each one of these microservices does authorization differently. And so it's impossible to reason about the full surface area of, you know, permissions in your application. And more and more of these organizations are saying, You know what, we need a standard layer for this. So it's not just Google with Zanzibar, it's Intuit with Oddy, it's Carta with their own oddy system, it's Netflix, you know, it's Airbnb with heed. All of them are now talking about how they solve access control extracted into its own service to basically manage complexity and regain agility. The other thing is all about, you know, time to market and, and tco. >>So, so how do you work with those services? Do you replace them, you unify them? What is the approach that you're taking? >>So basically these organizations are saying, you know what? We want one access control service. We want all of our microservices to call that thing instead of having to roll out our own. And so we, you know, give you the guts for that service, right? Topaz is basically the way that you're gonna go implement an access control service without having to go build it the same way that you know, large companies like Airbnb or Google or, or a car to >>Have. What's the competition look like for you guys? I'm not really seeing a lot of competition out there. Are there competitors? Are there different approaches? What makes you different? >>Yeah, so I would say that, you know, the biggest competitor is roll your own. So a lot of these companies that find us, they say, We're sick and tired of investing 2, 3, 4 engineers, five engineers on this thing. You know, it's the gift that keeps on giving. We have to maintain this thing and so we can, we can use your solution at a fraction of the cost a, a fifth, a 10th of what it would cost us to maintain it locally. There are others like Sty for example, you know, they are in the space, but more in on the infrastructure side. So they solve the problem of Kubernetes submission control or things like that. So >>Rolling your own, there's a couple problems there. One is do they get all the corner cases who built a they still, it's a company. Exactly. It's heavy lifting, it's undifferentiated, you just gotta check the box. So probably will be not optimized. >>That's right. As Bezo says, only focus on the things that make your beer taste better. And access control is one of those things. It's part of your security, you know, posture, it's a critical thing to get right, but you know, I wanna work on access control, said no developer ever, right? So it's kind of like this boring, you know, like back office thing that you need to do. And so we give you the mechanisms to be able to build it securely and robustly. >>Do you have a, a customer story example that is one of your go-tos that really highlights how you're improving developer productivity? >>Yeah, so we have a couple of them actually. So there's the largest third party B2B marketplace in the us. Free retail. Instead of building their own, they actually brought in aer. And what they wanted to do with AER was be the authorization layer for both their externally facing applications as well as their internal apps. So basically every one of their applications now hooks up to AER to do authorization. They define users and groups and roles and permissions in one place and then every application can actually plug into that instead of having to roll out their own. >>I'd like to switch gears if you don't mind. I get first of all, great update on the company and progress. I'd like to get your thoughts on the cloud computing market. Obviously you were your legendary position, Azure, I mean look at the, look at the progress over the past few years. Just been spectacular from Microsoft and you set the table there. Amazon web service is still, you know, thundering away even though earnings came out, the market's kind of soft still. You know, you see the cloud hyperscalers just continuing to differentiate from software to chips. Yep. Across the board. So the hyperscalers kicking ass taking names, doing great Microsoft right up there. What's the future? Cuz you now have the conversation where, okay, we're calling it super cloud, somebody calling multi-cloud, somebody calling it distributed computing, whatever you wanna call it. The old is now new again, it just looks different as cloud becomes now the next computer industry, >>You got an operating system, you got applications, you got hardware, I mean it's all kind of playing out just on a massive global scale, but you got regions, you got all kinds of connected systems edge. What's your vision on how this plays out? Because things are starting to fall into place. Web assembly to me just points to, you know, app servers are coming back, middleware, Kubernetes containers, VMs are gonna still be there. So you got the progression. What's your, what's your take on this? How would you share, share your thoughts to a friend or the industry, the audience? So what's going on? What's, what's happening right now? What's, what's going on? >>Yeah, it's funny because you know, I remember doing this quite a few years ago with you probably in, you know, 2015 and we were talking about, back then we called it hybrid cloud, right? And it was a vision, but it is actually what's going on. It just took longer for it to get here, right? So back then, you know, the big debate was public cloud or private cloud and you know, back when we were, you know, talking about these ideas, you know, we said, well you know, some applications will always stay on-prem and some applications will move to the cloud. I was just talking to a big bank and they basically said, look, our stated objective now is to move everything we can to the public cloud and we still have a large private cloud investment that will never go away. And so now we have essentially this big operating system that can, you know, abstract all of this stuff. So we have developer platforms that can, you know, sit on top of all these different pieces of infrastructure and you know, kind of based on policy decide where these applications are gonna be scheduled. So, you know, the >>Operating schedule shows like an operating system function. >>Exactly. I mean like we now, we used to have schedulers for one CPU or you know, one box, then we had schedulers for, you know, kind of like a whole cluster and now we have schedulers across the world. >>Yeah. My final question before we kind of get run outta time is what's your thoughts on web assembly? Cuz that's getting a lot of hype here again to kind of look at this next evolution again that's lighter weight kind of feels like an app server kind of direction. What's your, what's your, it's hyped up now, what's your take on that? >>Yeah, it's interesting. I mean back, you know, what's, what's old is new again, right? So, you know, I remember back in the late nineties we got really excited about, you know, JVMs and you know, this notion of right once run anywhere and yeah, you know, I would say that web assembly provides a pretty exciting, you know, window into that where you can take the, you know, sandboxing technology from the JavaScript world, from the browser essentially. And you can, you know, compile an application down to web assembly and have it real, really truly portable. So, you know, we see for example, policies in our world, you know, with opa, one of the hottest things is to take these policies and can compile them to web assemblies so you can actually execute them at the edge, you know, wherever it is that you have a web assembly runtime. >>And so, you know, I was just talking to Scott over at Docker and you know, they're excited about kind of bringing Docker packaging, OCI packaging to web assemblies. So we're gonna see a convergence of all these technologies right now. They're kind of each, each of our, each of them are in a silo, but you know, like we'll see a lot of the patterns, like for example, OCI is gonna become the packaging format for web assemblies as it is becoming the packaging format for policies. So we did the same thing. We basically said, you know what, we want these policies to be packaged as OCI assembly so that you can sign them with cosign and bring the entire ecosystem of tools to bear on OCI packages. So convergence is I think what >>We're, and love, I love your attitude too because it's the open source community and the developers who are actually voting on the quote defacto standard. Yes. You know, if it doesn't work, right, know people know about it. Exactly. It's actually a great new production system. >>So great momentum going on to the press released earlier this week, clearly filling the gaps there that, that you and your, your co-founder saw a long time ago. What's next for the assertive business? Are you hiring? What's going on there? >>Yeah, we are really excited about launching commercially at the end of this year. So one of the things that we were, we wanted to do that we had a promise around and we delivered on our promise was open sourcing our edge authorizer. That was a huge thing for us. And we've now completed, you know, pretty much all the big pieces for AER and now it's time to commercially launch launch. We already have customers in production, you know, design partners, and you know, next year is gonna be the year to really drive commercialization. >>All right. We will be watching this space ery. Thank you so much for joining John and me on the keep. Great to have you back on the program. >>Thank you so much. It was a pleasure. >>Our pleasure as well For our guest and John Furrier, I'm Lisa Martin, you're watching The Cube Live. Michelle floor of Con Cloud Native Con 22. This is day three of our coverage. We will be back with more coverage after a short break. See that.

>>Hey, everyone, welcome back to the cubes on the ground. Coverage of Pedro Duty Summit 22. I'm your host, Lisa Martin. I'm very excited to be joined by Manjula Toleration, the S VP and chief customer officer at page duty. Welcome to the programme. >>Thank you, Lisa. It's great to have chatted with you this morning as well, >>isn't it? I have had the great fortune of watching her fireside chat. That Mandela did, um, with is the logic monitor that was >>she of logic. >>And I thought, She's got great energy. We're gonna have a great conversation. So let's talk about the customer experience these days. One of the things I think that's been very, very short supply in the pandemic is patience. I know it's been in short supply with me and, of course, in our consumer lives in our business lives. The customer experience, though, has been something that every company needs to really pin their businesses on. Because if it's not a good customer experience, that customer goes right to social media. They churn. They leave, but they take others down with them. Talk to me about how the customer experience fits into this year's summit. Especially for this, we have to be ready for everything in a digital world environment. >>I love this question, and I reason I love this question is I even look at my own behaviour. But before we get into that, let's talk about data. I'm just reading an article. Mackenzie did a survey. Did you know that from pre covid to today customer interactions that have moved to digital are from 41% to 65%? That's exponential. That's huge. And guess what? We've all got impatient. You become like our kids, and I think about myself as an individual. If I need tied right now to do my laundry, I need it right now. So if I go to Costco website to order it so that it can get delivered in the next hour, and even if there's a second glitch on it, I'll swap over to Amazon and I'll swap over to target. That's what's happening in real world, whether it be to see or it's b to B, and why is it important to the points we are making in terms of ready for anything in the world of digital everything. It's important because customers are impatient. It's a digital world. I don't walk into the store to do any interactions anymore. And the reality of all of this is it's grounded on trust. Customers have to trust you and the window of choice not only in the B two b, but a lot in the enterprise and the B to B world. It's about trust, right? And what does pager duty do? Pager duty is at the heart of this pager. Duty is at the heart of making every second matter, and every second is equal to money. Absolutely. And it's about customer experience. And it isn't about just the experience where of an employee who may not sleep at night because they got a disruption due to an incident which is also super important during the mass resignation. But it is also about the CEO agenda and the boardroom, because how our CEO s driving customer trust in order to keep customers and drive this new era of digital everything as digital transformation is occurring. Well, >>I know patriarchy was doing that. I had the chance to watch um, CEO Jennifer to, uh, fireside chat, her keynote, and then her fireside chat with the CEO of Doc, You Sign And you. The Storey was very bidirectional, very symbiotic in terms of the trust that he has in Houston and Austin has and Pedro duty. But talk to me as the chief customer officer. What is it that's unique about how patriarchy works with its customers? 21,000 plus now to build and maintain that trust, especially in such volatile times? >>You know what is really cool? I joined page duty a little less than two years ago. In the next few days, it'll be two years now. What do I find exciting as a chief customer officer and the go to market teams differentiation versus other customers? We had a born SAS company and what do we have access to form our customers? We have access to their operations data and that combination of our core values that is championing the customer and the data science that we have about how customers are using our data is a differentiation. That's the magic. So if you think about why pager duty is bringing this level of trust to the customers, it's because we know how many and let's take an example. Employee retention, mass resignation. We know which employee was called. How many times at night during an outage. Can we give that guidance to managers and leaders in order to drive that trust? Absolutely. And on the other hand, we are driving amazing return on investment at the executive levels for the customer experience that they are driving. So Peter Duty is becoming the trusted advisor all the way from practitioners, where we are improving their work life balance to the executive levels, >>improving work. Life balance is so critical. There was a stat that Sean Scott shared this morning that that was looking at the amount of work volume from 2020 compared to 2021 42% of people said, I am working more hours. I don't think I've ever heard anyone say, Can I work more? Please? No. That work life balance is critical, but also the ability to deliver that seamless digital customer experience that we all expect, Um, and and to get it right the first time is critical. But using that customer data as you're saying, empowering the organisations, not just the customer support folks or the SRS or the develops folks but all the way up to the C suite to ensure that their brand reputation is valuable, it's maintained, and that trust is really bidirectional. That's the secret sauce. >>You're absolutely right. You know, there's a different dimension to this as well. We think about how we're using customer data in order to achieve the results. We want three vectors here. Number one is we'll use customer data to really understand what is best in class on up time. What is the best in class to reduce noise during alert, what is best in best in class for customer service operations? And because we have customer data, we can benchmark we can benchmark. What industry? What's happening in the financial services industry? What's happening in the technology industry? What's happening in the retail industry. Our customers love that, so we will share with them. The customer success organisation, especially the customer success managers, will go in and meet with the customers and say This is where you stand in reference to your peers and customers love here about that. This is the differentiated value proposition, right? The second thing that our customer success managers do is share with the customers This is where you are in reference to your peers in your vertical other vertical. But let me tell you how you can improve your deployment, the performance of our technology and you're all operating model. As a result of the data we've got, >>there's the proactive nous. That's another differentiator of of what I was hearing today from pager duty. That you're enabling those CSM is to be proactive when so often many are reactive, and it's the customer that's found the problem first. >>Yes, I'll even talk more about the reactive to proactive. We build a methodology, and I'm sure Shaun Scott covered it as well, which is a maturity curve moving from reactive to proactive because so many of our customers are saying we are reacting when we have a disruption on our digital platform, but 30% of the times we are hearing from customers before we are hearing from ourselves. So how do we become proactive? And how does that data signs actually start showing the signs when a potential disruption could occur? And that is about moving reactive to overall proactive. I'd also like to add one more dimension to this, you know, when customers are doing really well. They're optimised on our platform. They don't want to hear from our post sales organisation all the time. They want a human touch when they need it. They want a digital touch when they need it. By using our data and our data science, we are becoming one of the best world class customer success organisations in the world and you ask why? The reason is because we are using data science in order to build and we have built the early warning system. The early warning system tells us how every single of our customers is doing in terms of both their growth as well as the risk that they may leave us. So if a customer is very healthy on a scale of 1 200 if we have a healthy customer, we will engage with them potentially just digitally and engage with them with our services are customer success team and our entire post sales organisation, when there is an optimisation and when they really need us. So data scientists being used not only in terms of giving customer the right information to grow them, but how we interact with them as well, >>that's brilliant. And there's so many organisations that I talked to across industries that cannot get that right. >>And >>so customers are being contacted too frequently. They may have said. I opted out, I don't want and then suddenly that that the first responders, the incident responders, is marketing. But that happens so frequently, you think. But there's an opportunity there. It's not rocket science, but it's about leveraging that data in an optimal, smart way. But you guys are light years ahead of a lot of other companies that haven't figured that >>out. No, we are leading edge and we are leading edge because we had a born SAS company and we've got effective operations data of the customer, and we have some of the best data scientists and the analysts within my organisation. Looking at this, engaging with the customer and only optimising the magic is data science and humans coming together to engage with customers and drive customer success for the customer and ultimately building their customer experience for their customers. >>Let's talk about some of the numbers Mandela, because they are really impressive. I was looking at some stats. You're paid your duties renewal rates are over 95%. Your growth is incredible, just coming off the biggest quarter ever, but also the gross annual benefit from customers. Talk to me about that alone. That can be up to $10 million. These read these tangible business outcomes that pager duty is delivering to customers are significant, >>and again, it's based on data science. This is not making you know what traditional companies do. Traditional companies will go to the customer and say, Tell me your business imperatives. Tell me your what are the business problems you're solving are because we have the data science. We have our oi arranging from 309 100% very impressive within a couple of months. We think about it if we are able to drive incidents that are very, very significant. And I know you've got the numbers in terms of growing our reducing the workload on very expensive engineering. Uh, individuals within the organisation from, I believe, 3200 and 25,000, and I know you have those numbers think about If 30% of your organisation focuses just on innovation and product development, worse is on an incident, and they work, life balance, the quality of life increases, the retention of the employees, and yet the company's only driving their growth. That is why our customers love us. That is why our renewal rates are greater than 95%. That's why a net retention scores are greater than 100 and 2020% over five quarters. And that is why we have more than 30% growth year over year, quarter over quarter. >>When I saw that stat Manville about you know, the number of incidents reduced, >>that >>translates to employee productivity and and looking at it in terms of FTE. From a quantity perspective, that's the first time I've seen a company and I interview a lot of companies actually put it in that perspective, and I thought, That is huge. That's how organisations should be talking about that rather than reducing feeds are going. We are victims of the great resignation is look at the impact that can be made here by using data science by using the right mix of human and automation together. It's that's the first time. So congratulations to you and Pedro duty for the first time I've seen that and I think everybody needs to be working to be able to explain it that way, especially the fact that we're still in a volatile environment. >>Absolutely. It's about customer experience, but it is just as much employee experience. There is so much that the industry is talking about. That's top of mind for board levels. That's top of mind from CEO S. How do I retain my employees and drive greater operational efficiency? And now, with the macro economic challenges that are occurring in terms of inflation and in and the cost to serve and increasing the profits are customers are making. Operational efficiency is becoming even more important so that the employees are focusing more on innovation rather than downtime or disruptions. And it's actually about growing the business rather than just running the business. And if we can optimise running the business growth is what our customers are looking >>for, right? I always think, and we're almost out of time here. But I always think the employee experience and the customer experience are like this, and they should be. But it's critical to optimise both. How do you when you talk to some of those big and our price customers. We have Doc Watson on the main stage this morning, but I was looking at the website and three that jumped out to me that I use peloton, salesforce and slack. How do you advise them? You have this wealthiest gold of information on customers. This is how you need to leverage it in the right way to grow your business. What are some of the top three things you recommend those customers do, for example, >>that so let me talk about a couple of customers as an example. There are some customers of ours in the retail business, or it is a telecommunication company that is trying to increase their, um, up time from 98.7% to 3 nines as an example, or a tech company that doesn't even know that they were down for six hours in one small part of their business. And we're trying to figure out how do we solve for that as customers are overall complaining. So for us as a organisation, the magic is again bringing data together employee engagement, and what we do is we use the data to engage with their customers to ultimately understand what is their business value proposition. If you don't do it in isolation, you do it in. What is the customer trying to achieve? Are they trying to achieve the best in class website? Are they trying to achieve increased operational efficiency? What are their metrics? What are their numbers? And we take our data, our people, to marry all of that together. And that's the magic. >>I love it. I wish we had more time. Angela. We are out of time but talking about the value of the customer experience, the impact that is possible to be made leveraging technologies like pager duty. It's It's revolutionising operations. It's revolutionising customers 21,000 plus one million plus users at a time. It's awesome. You have to come back so we can talk more because I can. No, we're just scratching the surface here. >>Yes, we are. This is a very, very exciting area right now, and it is a great opportunities for chief customer officers on really rallying the whole company on championing the customers because whether it's a product, our capabilities, it's really a major transformation happening in the in the industry, and we need to stay very close to it? >>Absolutely. Thank you so much for joining me today. It's been such a pleasure talking to you. I look forward to seeing you again. >>Real pleasure, Lisa, To get to know you. And the gun was she was awesome. >>Good. Thank you for Manjula. Televisa. I'm Lisa Martin. You're watching the cubes on the ground. Coverage of pager duty. Summit 22 from San Francisco. Thanks for watching. And bye for now. Mm mm. Mm mm.

>>Hi everybody. This is Dave Volante. Welcome to this cube conversation where we're going to go back in time a little bit and explore the early days of Kubernetes. Talk about how it formed the improbable events, perhaps that led to it. And maybe how customers are taking advantage of containers and container orchestration today, and maybe where the industry is going. Matt Provo is here. He's the founder and CEO of storm forge and Chandler Huntington hoes. Hoisington is the general manager of EKS edge and hybrid AWS guys. Thanks for coming on. Good to see you. Thanks for having me. Thanks. So, Jenny, you were the vice president of engineering at miso sphere. Is that, is that correct? >>Well, uh, vice-president engineering basis, fear and then I ran product and engineering for DTQ masons. >>Yeah. Okay. Okay. So you were there in the early days of, of container orchestration and Matt, you, you were working at a S a S a Docker swarm shop, right? Yep. Okay. So I mean, a lot of people were, you know, using your platform was pretty novel at the time. Uh, it was, it was more sophisticated than what was happening with, with Kubernetes. Take us back. What was it like then? Did you guys, I mean, everybody was coming out. I remember there was, I think there was one Docker con and everybody was coming, the Kubernetes was announced, and then you guys were there, doc Docker swarm was, was announced and there were probably three or four other startups doing kind of container orchestration. And what, what were those days like? Yeah. >>Yeah. I wasn't actually atmosphere for those days, but I know them well, I know the story as well. Um, uh, I came right as we started to pivot towards Kubernetes there, but, um, it's a really interesting story. I mean, obviously they did a documentary on it and, uh, you know, people can watch that. It's pretty good. But, um, I think that, from my perspective, it was, it was really interesting how this happened. You had basically, uh, con you had this advent of containers coming out, right? So, so there's new novel technology and Solomon, and these folks started saying, Hey, you know, wait a second, wait if I put a UX around these couple of Linux features that got launched a couple of years ago, what does that look like? Oh, this is pretty cool. Um, so you have containers starting to crop up. And at the same time you had folks like ThoughtWorks and other kind of thought leaders in the space, uh, starting to talk about microservices and saying, Hey, monoliths are bad and you should break up these monoliths into smaller pieces. >>And any Greenfield application should be broken up into individuals, scalable units that a team can can own by themselves, and they can scale independent of each other. And you can write tests against them independently of other components. And you should break up these big, big mandalas. And now we are kind of going back to model this, but that's for another day. Um, so, so you had microservices coming out and then you also had containers coming out, same time. So there was like, oh, we need to put these microservices in something perfect. We'll put them in containers. And so at that point, you don't really, before that moment, you didn't really need container orchestration. You could just run a workload in a container and be done with it, right? You didn't need, you don't need Kubernetes to run Docker. Um, but all of a sudden you had tons and tons of containers and you had to manage these in some way. >>And so that's where container orchestration came, came from. And, and Ben Heineman, the founder of Mesa was actually helping schedule spark at the time at Berkeley. Um, and that was one of the first workloads with spark for Macy's. And then his friends at Twitter said, Hey, come over, can you help us do this with containers at Twitter? He said, okay. So when it helped them do it with containers at Twitter, and that's kinda how that branch of the container wars was started. And, um, you know, it was really, really great technology and it actually is still in production in a lot of shops today. Um, uh, more and more people are moving towards Kubernetes and Mesa sphere saw that trend. And at the end of the day, Mesa sphere was less concerned about, even though they named the company Mesa sphere, they were less concerned about helping customers with Mesa specifically. They really want to help customers with these distributed problems. And so it didn't make sense to, to just do Mesa. So they would took on Kubernetes as well. And I hope >>I don't do that. I remember, uh, my, my co-founder John furrier introduced me to Jerry Chen way back when Jerry is his first, uh, uh, VC investment with Greylock was Docker. And we were talking in these very, obviously very excited about it. And, and his Chandler was just saying, it said Solomon and the team simplified, you know, containers, you know, simple and brilliant. All right. So you guys saw the opportunity where you were Docker swarm shop. Why? Because you needed, you know, more sophisticated capabilities. Yeah. But then you, you switched why the switch, what was happening? What was the mindset back then? We ran >>And into some scale challenges in kind of operationalize or, or productizing our kind of our core machine learning. And, you know, we, we, we saw kind of the, the challenges, luckily a bit ahead of our time. And, um, we happen to have someone on the team that was also kind of moonlighting, uh, as one of the, the original core contributors to Kubernetes. And so as this sort of shift was taking place, um, we, we S we saw the flexibility, uh, of what was becoming Kubernetes. Um, and, uh, I'll never forget. I left on a Friday and came back on a Monday and we had lifted and shifted, uh, to Kubernetes. Uh, the challenge was, um, you know, you, at that time, you, you didn't have what you have today through EKS. And, uh, those kinds of services were, um, just getting that first cluster up and running was, was super, super difficult, even in a small environment. >>And so I remember we, you know, we, we finally got it up and running and it was like, nobody touch it, don't do anything. Uh, but obviously that doesn't, that doesn't scale either. And so that's really, you know, being kind of a data science focused shop at storm forge from the very beginning. And that's where our core IP is. Uh, our, our team looked at that problem. And then we looked at, okay, there are a bunch of parameters and ways that I can tune this application. And, uh, why are the configurations set the way that they are? And, you know, uh, is there room to explore? And that's really where, unfortunately, >>Because Mesa said much greater enterprise capabilities as the Docker swarm, at least they were heading in that direction, but you still saw that Kubernetes was, was attractive because even though it didn't have all the security features and enterprise features, because it was just so simple. I remember Jen Goldberg who was at Google at the time saying, no, we were focused on keeping it simple and we're going from mass adoption, but does that kind of what you said? >>Yeah. And we made a bet, honestly. Uh, we saw that the, uh, you know, the growing community was really starting to, you know, we had a little bit of an inside view because we had, we had someone that was very much in the, in the original part, but you also saw the, the tool chain itself start to, uh, start to come into place right. A little bit. And it's still hardening now, but, um, yeah, we, as any, uh, as any startup does, we, we made a pivot and we made a bet and, uh, this, this one paid off >>Well, it's interesting because, you know, we said at the time, I mean, you had, obviously Amazon invented the modern cloud. You know, Microsoft has the advantage of has got this huge software stays, Hey, just now run it into the cloud. Okay, great. So they had their entry point. Google didn't have an entry point. This is kind of a hail Mary against Amazon. And, and I, I wrote a piece, you know, the improbable, Verizon, who Kubernetes to become the O S you know, the cloud, but, but I asked, did it make sense for Google to do that? And it never made any money off of it, but I would argue they, they were kind of, they'd be irrelevant if they didn't have, they hadn't done that yet, but it didn't really hurt. It certainly didn't hurt Amazon EKS. And you do containers and your customers you've embraced it. Right. I mean, I, I don't know what it was like early days. I remember I've have talked to Amazon people about this. It's like, okay, we saw it and then talk to customers, what are they doing? Right. That's kind of what the mindset is, right? Yeah. >>That's, I, I, you know, I've, I've been at Amazon a couple of years now, and you hear the stories of all we're customer obsessed. We listened to our customers like, okay, okay. We have our company values, too. You get told them. And when you're, uh, when you get first hired in the first day, and you never really think about them again, but Amazon, that really is preached every day. It really is. Um, uh, and that we really do listen to our customers. So when customers start asking for communities, we said, okay, when we built it for them. So, I mean, it's, it's really that simple. Um, and, and we also, it's not as simple as just building them a Kubernetes service. Amazon has a big commitment now to start, you know, getting involved more in the community and working with folks like storm forage and, and really listening to customers and what they want. And they want us working with folks like storm florigen and that, and that's why we're doing things like this. So, well, >>It's interesting, because of course, everybody looks at the ecosystem, says, oh, Amazon's going to kill the ecosystem. And then we saw an article the other day in, um, I think it was CRN, did an article, great job by Amazon PR, but talk about snowflake and Amazon's relationship. And I've said many times snowflake probably drives more than any other ISV out there. And so, yeah, maybe the Redshift guys might not love snowflake, but Amazon in general, you know, they're doing great three things. And I remember Andy Jassy said to me, one time, look, we love the ecosystem. We need the ecosystem. They have to innovate too. If they don't, you know, keep pace, you know, they're going to be in trouble. So that's actually a healthy kind of a dynamic, I mean, as an ecosystem partner, how do you, >>Well, I'll go back to one thing without the work that Google did to open source Kubernetes, a storm forge wouldn't exist, but without the effort that AWS and, and EKS in particular, um, provides and opens up for, for developers to, to innovate and to continue, continue kind of operationalizing the shift to Kubernetes, um, you know, we wouldn't have nearly the opportunity that we do to actually listen to them as well, listen to the users and be able to say, w w w what do you want, right. Our entire reason for existence comes from asking users, like, how painful is this process? Uh, like how much confidence do you have in the, you know, out of the box, defaults that ship with your, you know, with your database or whatever it is. And, uh, and, and how much do you love, uh, manually tuning your application? >>And, and, uh, obviously nobody's said, I love that. And so I think as that ecosystem comes together and continues expanding, um, it's just, it opens up a huge opportunity, uh, not only for existing, you know, EKS and, uh, AWS users to continue innovating, but for companies like storm forge, to be able to provide that opportunity for them as well. And, and that's pretty powerful. So I think without a lot of the moves they've made, um, you know, th the door wouldn't be nearly as open for companies like, who are, you know, growing quickly, but are smaller to be able to, you know, to exist. >>Well, and I was saying earlier that, that you've, you're in, I wrote about this, you're going to get better capabilities. You're clearly seeing that cluster management we've talked about better, better automation, security, the whole shift left movement. Um, so obviously there's a lot of momentum right now for Kubernetes. When you think about bare metal servers and storage, and then you had VM virtualization, VMware really, and then containers, and then Kubernetes as another abstraction, I would expect we're not at the end of the road here. Uh, what's next? Is there another abstraction layer that you would think is coming? Yeah, >>I mean, w for awhile, it looked like, and I remember even with our like board members and some of our investors said, well, you know, well, what about serverless? And, you know, what's the next Kubernetes and nothing, we, as much as I love Kubernetes, um, which I do, and we do, um, nothing about what we particularly do. We are purpose built for Kubernetes, but from a core kind of machine learning and problem solving standpoint, um, we could apply this elsewhere, uh, if we went that direction and so time will tell what will be next, then there will be something, uh, you know, that will end up, you know, expanding beyond Kubernetes at some point. Um, but, you know, I think, um, without knowing what that is, you know, our job is to, to, to serve our, you know, to serve our customers and serve our users in the way that they are asking for that. >>Well, serverless obviously is exploding when you look again, and we tucked the ETR survey data, when you look at, at the services within Amazon and other cloud providers, you know, the functions off, off the charts. Uh, so that's kind of an interesting and notable now, of course, you've got Chandler, you've got edge in your title. You've got hybrid in, in your title. So, you know, this notion of the cloud expanding, it's not just a set of remote services, just only in the public cloud. Now it's, it's coming to on premises. You actually got Andy, Jesse, my head space. He said, one time we just look at it. The data centers is another edge location. Right. Okay. That's a way to look at it and then you've got edge. Um, so that cloud is expanding, isn't it? The definition of cloud is, is, is evolving. >>Yeah, that's right. I mean, customers one-on-one run workloads in lots of places. Um, and that's why we have things like, you know, local zones and wavelengths and outposts and EKS anywhere, um, EKS, distro, and obviously probably lots more things to come. And there's, I always think of like, Amazon's Kubernetes strategy on a manageability scale. We're on one far end of the spectrum, you have EKS distro, which is just a collection of the core Kubernetes packages. And you could, you could take those and stand them up yourself in a broom closet, in a, in a retail shop. And then on the other far in the spectrum, you have EKS far gate where you can just give us your container and we'll handle everything for you. Um, and then we kind of tried to solve everything in between for your data center and for the cloud. And so you can, you can really ask Amazon, I want you to manage my control plane. I want you to manage this much of my worker nodes, et cetera. And oh, I actually want help on prem. And so we're just trying to listen to customers and solve their problems where they're asking us to solve them. Cut, >>Go ahead. No, I would just add that in a more vertically focused, uh, kind of orientation for us. Like we, we believe that op you know, optimization capabilities should transcend the location itself. And, and, and so whether that's part public part, private cloud, you know, that's what I love part of what I love about EKS anywhere. Uh, it, you know, you shouldn't, you should still be able to achieve optimal results that connect to your business objectives, uh, wherever those workloads, uh, are, are living >>Well, don't wince. So John and I coined this term called Supercloud and people laugh about it, but it's different. It's, it's, you know, people talk about multi-cloud, but that was just really kind of vendor diversity. Right? I got to running here, I'm running their money anywhere. Uh, but, but individually, and so Supercloud is this concept of this abstraction layer that floats wherever you are, whether it's on prem, across clouds, and you're taking advantage of those native primitives, um, and then hiding that underlying complexity. And that's what, w re-invent the ecosystem was so excited and they didn't call it super cloud. We, we, we called it that, but they're clearly thinking differently about the value that they can add on top of Goldman Sachs. Right. That to me is an example of a Supercloud they're taking their on-prem data and their, their, their software tooling connecting it to AWS. They're running it on AWS, but they're, they're abstracting that complexity. And I think you're going to see a lot, a lot more of that. >>Yeah. So Kubernetes itself, in many cases is being abstracted away. Yeah. There's a disability of a disappearing act for Kubernetes. And I don't mean that in a, you know, in an, a, from an adoption standpoint, but, uh, you know, Kubernetes itself is increasingly being abstracted away, which I think is, is actually super interesting. Yeah. >>Um, communities doesn't really do anything for a company. Like we run Kubernetes, like, how does that help your bottom line? That at the end of the day, like companies don't care that they're running Kubernetes, they're trying to solve a problem, which is the, I need to be able to deploy my applications. I need to be able to scale them easily. I need to be able to update them easily. And those are the things they're trying to solve. So if you can give them some other way to do that, I'm sure you know, that that's what they want. It's not like, uh, you know, uh, a big bank is making more money because they're running Kubernetes. That's not, that's not the current, >>It gets subsumed. It's just become invisible. Right. Exactly. You guys back to the office yet. What's, uh, what's the situation, >>You know, I, I work for my house and I, you know, we go into the office a couple of times a week, so it's, it's, uh, yeah, it's, it's, it's a crazy time. It's a crazy time to be managing and hiring. And, um, you know, it's, it's, it's, it's definitely a challenge, but there's a lot of benefits of working home. I got two young kids, so I get to see them, uh, grow up a little bit more working, working out of my house. So it's >>Nice also. >>So we're in, even as a smaller startup, we're in 26, 27 states, uh, Canada, Germany, we've got a little bit of presence in Japan, so we're very much distributed. Um, we, uh, have not gone back and I'm not sure we will >>Permanently remote potentially. >>Yeah. I mean, w we made a, uh, pretty like for us, the timing of our series B funding, which was where we started hiring a lot, uh, was just before COVID started really picking up. So we, you know, thankfully made a, a pretty good strategic decision to say, we're going to go where the talent is. And yeah, it was harder to find for sure, especially in w we're competing, it's incredibly competitive. Uh, but yeah, we've, it was a good decision for us. Um, we are very about, you know, getting the teams together in person, you know, as often as possible and in the safest way possible, obviously. Um, but you know, it's been a, it's been a pretty interesting, uh, journey for us and something that I'm, I'm not sure I would, I would change to be honest with you. Yeah. >>Well, Frank Slootman, snowflakes HQ to Montana, and then can folks like Michael Dell saying, Hey, same thing as you, wherever they want to work, bring yourself and wherever you are as cool. And do you think that the hybrid mode for your team is kind of the, the, the operating mode for the, for the foreseeable future is a couple of, >>No, I think, I think there's a lot of benefits in both working from the office. I don't think you can deny like the face-to-face interactions. It feels good just doing this interview face to face. Right. And I can see your mouth move. So it's like, there's a lot of benefits to that, um, over a chime call or a zoom call or whatever, you know, that, that also has advantages, right. I mean, you can be more focused at home. And I think some version of hybrid is probably in the industry's future. I don't know what Amazon's exact plans are. That's above my pay grade, but, um, I know that like in general, the industry is definitely moving to some kind of hybrid model. And like Matt said, getting people I'm a big fan at Mesa sphere, we ran a very diverse, like remote workforce. We had a big office in Germany, but we'd get everybody together a couple of times a year for engineering week or, or something like this. And you'd get a hundred people, you know, just dedicated to spending time together at a hotel and, you know, Vegas or Hamburg or wherever. And it's a really good time. And I think that's a good model. >>Yeah. And I think just more ETR data, the current thinking now is that, uh, the hybrid is the number one sort of model, uh, 36% that the CIO is believe 36% of the workforce are going to be hybrid permanently is kind of their, their call a couple of days in a couple of days out. Um, and the, the percentage that is remote is significantly higher. It probably, you know, high twenties, whereas historically it's probably 15%. Yeah. So permanent changes. And that, that changes the infrastructure. You need to support it, the security models and everything, you know, how you communicate. So >>When COVID, you know, really started hitting and in 2020, um, the big banks for example, had to, I mean, you would want to talk about innovation and ability to, to shift quickly. Two of the bigger banks that have in, uh, in fact, adopted Kubernetes, uh, were able to shift pretty quickly, you know, systems and things that were, you know, historically, you know, it was in the office all the time. And some of that's obviously shifted back to a certain degree, but that ability, it was pretty remarkable actually to see that, uh, take place for some of the larger banks and others that are operating in super regulated environments. I mean, we saw that in government agencies and stuff as well. >>Well, without the cloud, no, this never would've happened. Yeah. >>And I think it's funny. I remember some of the more old school manager thing people are, aren't gonna work less when they're working from home, they're gonna be distracted. I think you're seeing the opposite where people are too much, they get burned out because you're just running your computer all day. And so I think that we're learning, I think everyone, the whole industry is learning. Like, what does it mean to work from home really? And, uh, it's, it's a fascinating thing is as a case study, we're all a part of right now. >>I was talking to my wife last night about this, and she's very thoughtful. And she w when she was in the workforce, she was at a PR firm and a guy came in a guest speaker and it might even be in the CEO of the company asking, you know, what, on average, what time who stays at the office until, you know, who leaves by five o'clock, you know, a few hands up, or who stays until like eight o'clock, you know, and enhancement. And then, so he, and he asked those people, like, why, why can't you get your work done in a, in an eight hour Workday? I go home. Why don't you go in? And I sit there. Well, that's interesting, you know, cause he's always looking at me like, why can't you do, you know, get it done? And I'm saying the world has changed. Yeah. It really has where people are just on all the time. I'm not sure it's sustainable, quite frankly. I mean, I think that we have to, you know, as organizations think about, and I see companies doing it, you guys probably do as well, you know, take a four day, you know, a week weekend, um, just for your head. Um, but it's, there's no playbook. >>Yeah. Like I said, we're a part of a case study. It's also hard because people are distributed now. So you have your meetings on the east coast, you can wake up at seven four, and then you have meetings on the west coast. You stay until seven o'clock therefore, so your day just stretches out. So you've got to manage this. And I think we're, I think we'll figure it out. I mean, we're good at figuring this stuff. >>There's a rise in asynchronous communication. So with things like slack and other tools, as, as helpful as they are in many cases, it's a, it, isn't always on mentality. And like, people look for that little green dot and you know, if you're on the you're online. So my kids, uh, you know, we have a term now for me, cause my office at home is upstairs and I'll come down. And if it's, if it's during the day, they'll say, oh dad, you're going for a walk and talk, you know, which is like, it was my way of getting away from the desk, getting away from zoom. And like, you know, even in Boston, uh, you know, getting outside, trying to at least, you know, get a little exercise or walk and get, you know, get my head away from the computer screen. Um, but even then it's often like, oh, I'll get a slack notification on my phone or someone will call me even if it's not a scheduled walk and talk. Um, uh, and so it is an interesting, >>A lot of ways to get in touch or productivity is presumably going to go through the roof. But now, all right, guys, I'll let you go. Thanks so much for coming to the cube. Really appreciate it. And thank you for watching this cube conversation. This is Dave Alante and we'll see you next time.

(upbeat music) >> Hello, and welcome to this startup showcase. It's great to be here and talk about some of the innovations we are doing at AWS, how we work with our partner community, especially our open source partners. My name is Deepak Singh. I run our compute services organization, which is a very vague way of saying that I run a number of things that are connected together through compute. Very specifically, I run a container services organization. So for those of you who are into containers, ECS, EKS, fargate, ECR, App Runner Those are all teams that are within my org. I also run the Amazon Linux and BottleRocketing. So anything AWS does with Linux, both externally and internally, as well as our high-performance computing team. And perhaps very relevant to this discussion, I run the Amazon open source program office. Serving at AWS for over 13 years, almost 14, involved with compute in various ways, including EC2. What that has done has given me a vantage point of seeing how our customers use the services that we build for them, how they leverage various partner solutions, and along the way, how AWS itself has gotten involved with opensource. And I'll try and talk to you about some of those factors and how they impact, how you consume our services. So why don't we get started? So for many of you, you know, one of the things, there's two ways to look at AWS and open-source and Amazon in general. One is the number of contributors you may have. And the number of repositories that contribute to. Those are just a couple of measures. There are people that I work with on a regular basis, who will remind you that, those are not perfect measures. Sometimes you could just contribute to one thing and have outsized impact because of the nature of that thing. But it address being what it is, increasingly we'll look at different ways in which we can help contribute and enhance open source 'cause we consume a lot of it as well. I'll talk about it very specifically from the space that I work in the container space in particular, where we've worked a lot with people in the Kubernetes community. We've worked a lot with people in the broader CNCF community, as well as, you know, small projects that our customers might have got started off with. For example, I want to like talking about is Argo CD from Intuit. We were very actively involved with helping them figure out what to do with it. And it was great to see how into it. And we worked, etc, came together to think about get-ups at the Kubernetes level. And while those are their projects, we've always been involved with them. So we try and figure out what's important to our customers, how we can help and then take because of that. Well, let's talk about a little bit more, here's some examples of the kinds of open source projects that Amazon and AWS contribute to. They arranged from the open JDK. I think we even now have our own implementation of Java, the Corretto open source project. We contribute to projects like rust, where we are very active in the rest foundation from a leadership role as well, the robot operating system, just to pick some, we collaborate with Facebook and actively involved with the pirates project. And there's many others. You can see all the logos in here where we participate either because they're important to us as AWS in the services that we run or they're important to our customers and the services that they consume or the open source projects they care about and how we get to those. How we get and make those decisions is often depends on the importance of that particular project. At that point in time, how much impact they're having to AWS customers, or sometimes very feel that us contributing to that project is super critical because it helps us build more robust services. I'll talk about it in a completely, you know, somewhat different basis. You may have heard of us talk about our new next generation of Amazon Linux 2022, which is based on fedora as its sub stream. One of the reasons we made this decision was it allows us to go and participate in the preneurial project and make sure that the upstream project is robust, stays robust. And that, that what that ends up being is that Amazon Linux 2022 will be a robust operating system with the kinds of capabilities that our customers are asking for. That's just one example of how we think about it. So for example, you know, the Python software foundation is something that we work with very closely because so many of our customers use Python. So we help run something like PyPy which is many, you know, if you're a Python developer, I happened to be a Ruby one, but lots of our customers use Python and helping the Python project be robust by making sure PyPy is available to everybody is something that we help provide credits for help support in other ways. So it's not just code. It can mean many different ways of contributing as well, but in the end code and operations is where we hang our happens. Good examples of this is projects that we will create an open source because it makes sense to make sure that we open source some of the core primitives or foundations that are part of our own services. A great example of that, whether this be things that we open source or things that we contribute to. And I'll talk about both and I'll talk about things near and dear to my heart. There's many examples I've picked the two that I like talking about. The first of these is firecracker. Many of you have heard about it, a firecracker for those of you who don't know is a very lightweight virtual machine manager, which allows you to run these micro VMs. And why was this important many years ago when we started Lambda and quite honestly, Fugate and foggy, it still runs quite a bit in that mode, we used to have to run on VMs like everything else and finding the right VM for the size of tasks that somebody asks for the size of function that somebody asks for is requires us to provision capacity ahead of time. And it also wastes a lot of capacity because Lambda function is small. You won't even if you find the smallest VM possible, those can be a little that can be challenging. And you know, there's a lot of resources that are being wasted. VM start at a particular speed because they have to do a whole bunch of things before the operating system spins up and the virtual machine spins up and we asked ourselves, can we do better? come up with something that allows us to create right size, very lightweight, very fast booting. What's your machines, micro virtual machine that we ended up calling them. That's what led to firecracker. And we open source the project. And today firecrackers use, not just by AWS Lambda or foggy, but by a number of other folks, there's companies like fly IO that are using it. We know people using firecracker to run Kubernetes on prem on bare metal as an example. So we've seen a lot of other folks embrace it and use it as the foundation for building their own serverless services, their own container services. And we think there's a lot of value and learnings that we can bring to the table because we get the experience of operating at scale, but other people can bring to the table cause they may have specific requirements that we may not find it as important from an AWS perspective. So that's firecracker an example of a project where we contribute because we feel it's fundamentally important to us as continually. We were found, you know, we've been involved with continuity from the beginning. Today, we are a whole team that does nothing else, but contribute to container D because container D underlies foggy. It underlies our Kubernetes offerings. And it's increasingly being used by customers directly by their placement. You know, where they're running container D instead of running a full on Docker or similar container engine, what it has allowed us to do is focus on what's important so that we can operate continuously at scale, keep it robust and secure, add capabilities to it that AWS customers need manifested often through foggy Kubernetes, but in the end, it's a win-win for everybody. It makes continuously better. If you want to use containers for yourself on AWS, that's a great way to you. You know, you still, you still benefit from all the work that we're doing. The decision we took was since it's so important to us and our customers, we wanted a team that lived in breathed container D and made sure a super robust and there's many, many examples like that. No, that we ended up participating in, either by taking a project that exists or open sourcing our own. Here's an example of some of the open source projects that we have done from an AWS on Amazon perspective. And there's quite a few when I was looking at this list, I was quite surprised, not quite surprised I've seen the reports before, but every time I do, I have to recount and say, that's a lot more than one would have thought, even though I'd been looking at it for such a long time, examples of this in my world alone are things like, you know, what work had to do with Amazon Linux BottleRocket, which is a container host operating system. That's been open-sourced from day one. Firecracker is something we talked about. We have a project called AWS peril cluster, which allows you to spin up high performance computing clusters on AWS using the kind of schedulers you may use to use like slum. And that's an open source project. We have plenty of source projects in the web development space, in the security space. And more recently things like the open 3d engine, which is something that we are very excited about and that'd be open sourced a few months ago. And so there's a number of these projects that cover everything from tooling to developer, application frameworks, all the way to database and analytics and machine learning. And you'll notice that in a few areas, containers, as an example, machine learning as an example, our default is to go with open source option is where we can open source. And it makes sense for us to do so where we feel the product community might benefit from it. That's our default stance. The CNCF, the cloud native computing foundation is something that we've been involved with quite a bit. You know, we contribute to Kubernetes, be contribute to Envoy. I talked about continuity a bit. We've also contributed projects like CDK 8, which marries the AWS cloud development kit with Kubernetes. It's now a sandbox project in Kubernetes, and those are some of the areas. CNCF is such a wide surface area. We don't contribute to everything, but we definitely participate actively in CNCF with projects like HCB that are critical to eat for us. We are very, very active in just how the project evolves, but also try and see which of the projects that are important to our customers who are running Kubernetes maybe by themselves or some other project on AWS. Envoy is a good example. Kubernetes itself is a good example because in the end, we want to make sure that people running Kubernetes on AWS, even if they are not using our services are successful and we can help them, or we can work on the projects that are important to them. That's kind of how we think about the world. And it's worked pretty well for us. We've done a bunch of work on the Kubernetes side to make sure that we can integrate and solve a customer problem. We've, you know, from everything from models to work that we have done with gravity on our arm processor to a virtual GPU plugin that allows you to share and media GPU resources to the elastic fabric adapter, which are the network device for high performance computing that it can use at Kubernetes on AWS, along with things that directly impact Kubernetes customers like the CDKs project. I talked about work that we do with the container networking interface to the Amazon control of a Kubernetes, which is an open source project that allows you to use other AWS services directly from Kubernetes clusters. Again, you notice success, Kubernetes, not EKS, which is a managed Kubernetes service, because if we want you to be successful with Kubernetes and AWS, whether using our managed service or running your own, or some third party service. Similarly, we worked with premetheus. We now have a managed premetheus service. And at reinvent last year, we announced the general availability of this thing called carpenter, which is a provisioning and auto-scaling engine for Kubernetes, which is also an open source project. But here's the beauty of carpenter. You don't have to be using EKS to use it. Anyone running Kubernetes on AWS can leverage it. We focus on the AWS provider, but we've built it in such a way that if you wanted to take carpenter and implemented on prem or another cloud provider, that'd be completely okay. That's how it's designed and what we anticipated people may want to do. I talked a little bit about BottleRocket it's our Linux-based open-source operating system. And the thing that we have done with BottleRocket is make sure that we focus on security and the needs of customers who want to run orchestrated container, very focused on that problem. So for example, BottleRocket only has essential software needed to run containers, se Linux. I just notice it says that's the lineups, but I'm sure that, you know, Lena Torvalds will be pretty happy. And seeing that SE linux is enabled by default, we use things like DM Verity, and it has a read only root file system, no shell, you can assess it. You can install it if you wanted to. We allowed it to create different bill types, variants as we call them, you can create a variant for a non AWS resource as well. If you have your own homegrown container orchestrator, you can create a variant for that. It's designed to be used in many different contexts and all of that is open sourced. And then we use the update framework to publish and secure repository and kind of how this transactional system way of updating the software. And it's something that we didn't invent, but we have embraced wholeheartedly. It's a bottle rockets, completely open source, you know, have partners like Aqua, where who develop security tools for containers. And for them, you know, something I bought in rocket is a natural partnership because people are running a container host operating system. You can use Aqua tooling to make sure that they have a secure Indiana environment. And we see many more examples like that. You may think so over us, it's all about AWS proprietary technology because Lambda is a proprietary service. But you know, if you look peek under the covers, that's not necessarily true. Lambda runs on top of firecracker, as we've talked about fact crackers and open-source projects. So the foundation of Lambda in many ways is open source. What it also allows people to do is because Lambda runs at such extreme scale. One of the things that firecracker is really good for is running at scale. So if you want to build your own firecracker base at scale service, you can have most of the confidence that as long as your workload fits the design parameters, a firecracker, the battle hardening the robustness is being proved out day-to-day by services at scale like Lambda and foggy. For those of you who don't know service support services, you know, in the end, our goal with serverless is to make sure that you don't think about all the infrastructure that your applications run on. We focus on business logic as much as you can. That's how we think about it. And serverless has become its own quote-unquote "Sort of environment." The number of partners and open-source frameworks and tools that are spun up around serverless. In which case mostly, I mean, Lambda, API gateway. So it says like that is pretty high. So, you know, number of open source projects like Zappa server serverless framework, there's so many that have come up that make it easier for our customers to consume AWS services like Lambda and API gateway. We've also done some of our own tooling and frameworks, a serverless application model, AWS jealous. If you're a Python developer, we have these open service runtimes for Lambda, rust dot other options. We have amount of number of tools that we opened source. So in general, you'll find that tooling that we do runtime will tend to be always be open-sourced. We will often take some of the guts of the things that we use to build our systems like firecracker and open-source them while the control plane, etc, AWS services may end up staying proprietary, which is the case in Lambda. Increasingly our customers build their applications and leverage the broader AWS partner network. The AWS partner network is a network of partnerships that we've built of trusted partners. when you go to the APN website and find a partner, they know that that partner meets a certain set of criteria that AWS has developed, and you can rely on those partners for your own business. So whether you're a little tiny business that wants some function fulfill that you don't have the resources for or large enterprise that wants all these applications that you've been using on prem for a long time, and want to keep leveraging them in the cloud, you can go to APN and find that partner and then bring their solution on as part of your cloud infrastructure and could even be a systems integrator, for example, to help you solve this specific development problem that you may have a need for. Increasingly, you know, one of the things we like to do is work with an apartment community that is full of open-source providers. So a great one, there's so many, and you have, we have a panel discussion with many other partners as well, who make it easier for you to build applications on AWS, all open source and built on open source. But I like to call it a couple of them. The first one of them is TIDELIFT. TIDELIFT, For those of you who don't know is a company that provides SAS based tools to curate track, manage open source catalogs. You know, they have a whole network of maintainers and providers. They help, if you're an independent open developer, or a smart team should probably get to know TIDELIFT. They provide you benefits and, you know, capabilities as a developer and maintainer that are pretty unique and really help. And I've seen a number of our open source community embraced TIDELIFT quite honestly, even before they were part of the APN. But as part of the partner network, they get to participate in things like ISP accelerate and they get to they're officially an advanced tier partner because they are, they migrated the SAS offering onto AWS. But in the end, if you're part of the open source supply chain, you're a maintainer, you are a developer. I would recommend working with TIDELIFT because their goal is making all of you who are developing open source solutions, especially on AWS, more successful. And that's why I enjoy this partnership with them. And I'm looking to do a lot more because I think as a company, we want to make sure that open source developers don't feel like they are not supported because all you have to do is read various forums. It's challenging often to be a maintainer, especially of a small project. So I think with helping with licensing license management, security identification remediation, helping these maintainers is a big part of what TIDELIFT to us and it was great to see them as part of a partner network. Another partner that I like to call sysdig. I actually got introduced to them many years ago when they first launched. And one of the things that happened where they were super interested in some of our serverless stuff. And we've been trying to figure out how we can work together because all of our customers are interested in the capabilities that cystic provides. And over the last few years, he found a number of areas where we can collaborate. So sysdig, I know them primarily in a security company. So people use cystic to secure the bills, detect, you know, do threat response, threat detection, completely continuously validate their posture, get this continuous analytics signal on how they're doing and monitor performance. At the end of it, it's a SAS platform. They have a very nice open source security stack. The one I'm most familiar with. And I think most of you are probably familiar with is Falco. You know, sysdig, a CNCF project has been super popular. It's just to go SSS what 3, 37, 40 million downloads by now. So that's pretty, pretty cool. And they have been a great partner because we've had to do make sure that their solution works at target, which is not a natural place for their software to run, but there was enough demand and interest from our customers that, you know, or both companies leaned in to make sure they can be successful. So last year sister got a security competency. We have a number of specific competencies that we for our partners, they have integration and security hub is great. partners are lean in the way cystic has onto making our customer successful. And working with us are the best partners that we have. And there's a number of open source companies out there built on open source where their entire portfolio is built on open source software or the active participants like we are that we love working with on a day to day basis. So, you know, I think the thing I would like to, as we wind this out in this presentation is, you know, AWS is constantly looking for partnerships because our partners enable our customers. They could be with companies like Redis with Mongo, confluent with Databricks customers. Your default reaction might be, "Hey, these are companies that maybe compete with AWS." but no, I mean, I think we are partners as well, like from somebody at the lower end of the spectrum where people run on top of the services that I own on Linux and containers are SE 2, For us, these partners are just as important customers as any AWS service or any third party, 20 external customer. And so it's not a zero sum game. We look forward to working with all these companies and open source projects from an AWS perspective, a big part of how, where my open source program spends its time is making it easy for our developers to contribute, to open source, making it easy for AWS teams to decide when to open source software or participate in open source projects. Over the last few years, we've made significant changes in how we reduce the friction. And I think you can see it in the results that I showed you earlier in this stock. And the last one is one of the most important things that I say and I'll keep saying that, that we do as AWS is carry the pager. There's a lot of open source projects out there, operationalizing them, running them at scale is not easy. It's not all for whatever reason. It may not have anything to do with the software itself. But our core competency is taking that and being really good at operating it and becoming experts at operating it. And then ideally taking that expertise and experience and operating that project, that software and contributing back upstream. Cause that makes it better for everybody. And I think you'll see us do a lot more of that going forward. We've been doing that for the last few years, you know, in the container space, we do it every day. And I'm excited about the possibilities. With that. Thank you very much. And I hope you enjoy the rest of the showcase. >> Okay. Welcome back. We have Deepak sing here. We just had the keynote closing keynote vice-president of compute services. Deepak. Great to a great keynote, great wisdom and insight from that session. A very notable highlights and cutting edge trends and product information. Thanks for sharing. >> No, anytime it's always good to be here. It's too bad that we still doing this virtually, but always good to talk to you, John. >> We'll get hopefully through this way pretty quickly, I want to jump right in. Cause we don't have a lot of time. I want to get some quick question. You've brought up a good things. Open source innovation. Okay. Going next level. You've seen the rise of super clouds and super apps developing at open source. You're seeing big companies contributing, you know, you mentioned Argo into it. You're seeing that dynamic where companies are forming around this. This is a rising tide. This is, this is actually real. It's not the old school of, okay, here's a project. And then someone manages support and commercialization of it. It's actually platform in cloud scale. This is next gen. >> Yeah. And actually I think it started a few years ago. We can talk about a company that, you know, you're very familiar with as part of this event, which is armory many years ago, Netflix spun off this project called Spinnaker. A Spinnaker is CISED you know, CSED system that was developed at Netflix for their own purposes, but they chose to open solicit. And since then, it's become very popular with customers who want to use it even on prem. And you have a company that spun up on it. I think what's making this world very unique is you have very large companies like Facebook that will build things for themselves like VITAS or Netflix with Spinnaker and open source them. And you can have a lot of discussion about why they chose to do so, etc. But increasingly that's becoming the default when Amazon or Netflix or Facebook or Mehta, I guess you call them these days, build something for themselves for their own needs. The first question we ask ourselves is, should it be opensource? And increasingly we are all saying yes. And here's what happens because of that. It gives an opportunity depending on how you open source it for innovation through commercial deployments, so that you get SaaS companies, you know, that are going to take that product and make it relevant and useful to a very broad number of customers. You build partnerships with cloud providers like AWS, because our customers love this open source project and they need help. And they may choose an AWS managed service, or they may end up working with this partner on a day-to-day basis. And we want to work with that partner because they're making our customers successful, which is one reason all of us are here. So you're having this set of innovation from large companies from, you know, whether they are just consumer companies like Metta infrastructure companies like us, or just random innovation that's happening in an open source project that which ends up in companies being spun up and that foster that innovative innovation and that flywheel that's happening right now. And I think you said that like, this is unique. I mean, you never saw this happen before from so many different directions. >> It really is a nice progression on the business model side as well. You mentioned Argo, which is a great organic thing that was Intuit developed. We just interviewed code fresh. They just presented here in the showcase as well. You seeing the formation around these projects develop now in the community at a different scale. I mean, look at code fresh. I mean, Intuit did it Argo and they're not just supporting it. They're building a platform. So you seeing the dynamics of tools and now emerging the platforms, you mentioned Lambda, okay. Which is proprietary for AWS and your talk powered by open source. So again, open source combined with cloud scale allows for new potential super applications or super clouds that are developing. This is a new phenomenon. This isn't just lift and shift and host on the cloud. This is actually a construction production developer workflow. >> Yeah. And you are seeing consumers, large companies, enterprises, startups, you know, it used to be that startups would be comfortable adopting some of these solutions, but now you see companies of all sizes doing so. And I said, it's not just software it's software, the services increasingly becoming the way these are given, delivered to customers. I actually think the innovation is just getting going, which is why we have this. We have so many partners here who are all in inventing and innovating on top of open source, whether it's developed by them or a broader community. >> Yeah. I liked, I liked the represent container. Do you guys have, did that drove that you've seen a lot of changes and again, with cloud scale and open source, you seeing the dynamics change, whether you're enabling that, and then you see kind of like real big change. So let's take snowflake, a big customer of AWS. They started out as a startup too, but they weren't a data warehouse. They were bringing data warehouse like functionality and then changing everything differently and making it consumable for the cloud. And hence they're huge. So that's a disruption into an incumbent leader or sector. Then you've got new capabilities emerging. What's your thoughts, Deepak? Can you share your vision on how you have the disruption to existing leaders, old guard, if you will, as you guys call them and then new capabilities as these new platforms emerge at a net new functionality, how do you see that emerging? >> Yeah. So I speak from my side of the world. I've lived in over the last few years, which has containers and serverless, right? There's a lot of, if you go to any enterprise and ask them, do you want to modernize the infrastructure? Do you want to take advantage of automated software delivery, continuous delivery infrastructure as code modern observability, all of them will say yes, but they also are still a large enterprise, which has these enterprise level requirements. I'm using the word enterprise a lot. And I usually it's a trigger word for me because so many customers have similar requirements, but I'm using it here as large company with a lot of existing software and existing practices. I think the innovation that's coming and I see a lot of companies doing that is saying, "Hey, we understand the problems you want to solve. We understand the world where you live in, which could be regulated." You want to use all these new modalities. How do we allow you to use all of them? Keep the advantages of switching to a Lambda or switching to, and a service running on far gate, but give you the same capabilities. And I think I'll bring up cystic here because we work so closely with them on Falco. As an example, I just talked about them in my keynote. They could have just said, "Oh no, we'll just support the SE2 and be done with it." They said, "No, we're going to make sure that serverless containers in particular are something that you're going to be really good at because our customers want to use them, but requires us to think differently. And then they ended up developing new things like Falco that are born in this new world, but understand the requirements of the old world. If you get what I'm saying. And I think that a real example. >> Yeah. Oh, well, I mean, first of all, they're smart. So that was pretty obvious for most people that know, sees that you can connect the dots on serverless, which is a great point, but not everyone can see that again, this is what's new and and systig was just found in his backyard. As I found out on my interview, a great, great founder, they would do a new thing. So it was a very easy to connect the dots there again, that's the trend. Well, I got to ask if they're doing that for serverless, you mentioned graviton in your speech and what came out of you mentioned graviton in your speech and what came out of re-invent this past year was all the innovation going on at the compute level with gravitron at many levels in the Silicon. How should companies and open source developers think about how to innovate with graviton? >> Yeah, I mean, you've seen examples from people blogging and tweeting about how fast their applications run and grab it on the price performance benefits that they get, whether it's on, you know, whether it's an observability or other places. something that AWS is going to embrace across a compute something that AWS is going to embrace across a compute portfolio. Obviously you can go find EC2 instances, the gravitron two instances and run on them and that'll be great. But we know that most of our customers, many of our customers are building new applications on serverless containers and serveless than even as containers increasingly with things like foggy, where they don't want to operate the underlying infrastructure. A big part of what we're doing is to make sure that graviton is available to you on every compute modality. You can run it on a C2 forever. You've been running, being able to use ECS and EKS and run and grab it on almost since launch. What do you want me to take it a step further? You elastic Beanstalk customers, elastic Beanstalk has been around for a decade, but you can now use it with graviton. people running ECS on for gate can now use graviton. Lambda customers can pick graviton as well. So we're taking this price performance benefits that you get So we're taking this price performance benefits that you get from graviton and basically putting it across the entire compute portfolio. What it means is every high level service that gets built on compute infrastructure. And you get the price performance benefits, you get the price performance benefits of the lower power consumption of arm processes. So I'm personally excited like crazy. And you know, this has graviton 2 graviton 3 is coming. >> That's incredible. It's an opportunity like serverless was it's pretty obvious. And I think hopefully everyone will jump on that final question as the time's ticking here. I want to get your thoughts quickly. If you look at what's happened with containers over the past say eight years since the original founding of the first Docker instance, if you will, to how that's evolved and then the introduction of Kubernetes and the cloud native wave we're seeing now, what is, how would you describe the relationship between the success Docker, seeing now with Kubernetes in the cloud native construct what's different and why is this combination so successful? >> Yeah. I often say that containers would have, let me rephrase that. what I say is that people would have adopted sort of the modern way of running applications, whether containers came around or not. But the fact that containers came around made that migration and that journey is so much more efficient for people. So right from, I still remember the first doc that Solomon gave Billy announced DACA and starting to use it on customers, starting to get interested all the way to the more sort of advanced orchestration that we have now for containers across the board. And there's so many examples of the way you can do that. Kubernetes being the most, most well-known one. Here's the thing that I think has changed. I think what Kubernetes or Docker, or the whole sort of modern way of building applications has done is it's taken people who would have taken years adopting these practices and by bringing it right to the fingertips and rebuilding it into the APIs. And in the case of Kubernetes building an entire sort of software world around it, the number of, I would say number of decisions people have to take has gone smaller in many ways. There's so many options, the number of decisions that become higher, but the com the speed at which they can get to a result and a production version of an application that works for them is way low. I have not seen anything like what I've seen in the last 6, 7, 8 years of how quickly the most you know, the most I would say is, you know, a company that you would think would never adopt modern technology has been able to go from, this is interesting to getting a production really quickly. And I think it's because the tooling makes it So, and the fact that you see the adoption that you see right and the fact that you see the adoption that you see right from the fact that you could do Docker run Docker, build Docker, you know, so easily back in the day, all the way to all the advanced orchestration you can do with container orchestrator is today. sort of taking all of that away as well. there's never been a better time to be a developer independent of whatever you're trying to build. And I think containers are a big central part of why that's happened. >> Like the recipe, the combination of cloud-scale, the timing of Kubernetes and the containerization concepts just explode as a beautiful thing. And it creates more opportunities and will challenges, which are opportunities that are net new, but it solves the automation piece that we're seeing this again, it's only makes things go faster. >> Yes. >> And that's the key trend. Deepak, thank you so much for coming on. We're seeing tons of open cloud innovations, thanks to the success of your team at AWS and being great participants in the community. We're seeing innovations from startups. You guys are helping enabling that. Of course, they want to live on their own and be successful and build their super clouds and super app. So thank you for spending the time with us. Appreciate. >> Yeah. Anytime. And thank you. And you know, this is a great event. So I look forward to people running software and building applications, using AWS services and all these wonderful partners that we have. >> Awesome, great stuff. Great startups, great next generation leaders emerging. When you see startups, when they get successful, they become the modern software applications platforms out there powering business and changing the world. This is the cube you're watching the AWS startup showcase. Season two episode one open cloud innovations on John Furrier your host, see you next time.

>> Announcer: From theCUBE studios in Palo Alto, in Boston, connecting with thought leaders all around the world. This is theCUBE conversation. >> Hi everyone, this is Dave Vellante and welcome to this CUBE conversation where we're going to dig in to this, the area of cloud databases. And Gartner just published a series of research in this space. And it's really a growing market, rapidly growing, a lot of new players, obviously the big three cloud players. And with me are three experts in the field, two long time industry analysts. Marc Staimer is the founder, president, and key principal at Dragon Slayer Consulting. And he's joined by David Floyer, the CTO of Wikibon. Gentlemen great to see you. Thanks for coming on theCUBE. >> Good to be here. >> Great to see you too Dave. >> Marc, coming from the great Northwest, I think first time on theCUBE, and so it's really great to have you. So let me set this up, as I said, you know, Gartner published these, you know, three giant tomes. These are, you know, publicly available documents on the web. I know you guys have been through them, you know, several hours of reading. And so, night... (Dave chuckles) Good night time reading. The three documents where they identify critical capabilities for cloud database management systems. And the first one we're going to talk about is, operational use cases. So we're talking about, you know, transaction oriented workloads, ERP financials. The second one was analytical use cases, sort of an emerging space to really try to, you know, the data warehouse space and the like. And, of course, the third is the famous Gartner Magic Quadrant, which we're going to talk about. So, Marc, let me start with you, you've dug into this research just at a high level, you know, what did you take away from it? >> Generally, if you look at all the players in the space they all have some basic good capabilities. What I mean by that is ultimately when you have, a transactional or an analytical database in the cloud, the goal is not to have to manage the database. Now they have different levels of where that goes to as how much you have to manage or what you have to manage. But ultimately, they all manage the basic administrative, or the pedantic tasks that DBAs have to do, the patching, the tuning, the upgrading, all of that is done by the service provider. So that's the number one thing they all aim at, from that point on every database has different capabilities and some will automate a whole bunch more than others, and will have different primary focuses. So it comes down to what you're looking for or what you need. And ultimately what I've learned from end users is what they think they need upfront, is not what they end up needing as they implement. >> David, anything you'd add to that, based on your reading of the Gartner work. >> Yes. It's a thorough piece of work. It's taking on a huge number of different types of uses and size of companies. And I think those are two parameters which really change how companies would look at it. If you're a Fortune 500 or Fortune 2000 type company, you're going to need a broader range of features, and you will need to deal with size and complexity in a much greater sense, and a lot of probably higher levels of availability, and reliability, and recoverability. Again, on the workload side, there are different types of workload and there're... There is as well as having the two transactional and analytic workloads, I think there's an emerging type of workload which is going to be very important for future applications where you want to combine transactional with analytic in real time, in order to automate business processes at a higher level, to make the business processes synchronous as opposed to asynchronous. And that degree of granularity, I think is missed, in a broader view of these companies and what they offer. It's in my view trying in some ways to not compare like with like from a customer point of view. So the very nuance, what you talked about, let's get into it, maybe that'll become clear to the audience. So like I said, these are very detailed research notes. There were several, I'll say analysts cooks in the kitchen, including Henry Cook, whom I don't know, but four other contributing analysts, two of whom are CUBE alum, Don Feinberg, and Merv Adrian, both really, you know, awesome researchers. And Rick Greenwald, along with Adam Ronthal. And these are public documents, you can go on the web and search for these. So I wonder if we could just look at some of the data and bring up... Guys, bring up the slide one here. And so we'll first look at the operational side and they broke it into four use cases. The traditional transaction use cases, the augmented transaction processing, stream/event processing and operational intelligence. And so we're going to show you there's a lot of data here. So what Gartner did is they essentially evaluated critical capabilities, or think of features and functions, and gave them a weighting, or a weighting, and then a rating. It was a weighting and rating methodology. On a s... The rating was on a scale of one to five, and then they weighted the importance of the features based on their assessment, and talking to the many customers they talk to. So you can see here on the first chart, we're showing both the traditional transactions and the augmented transactions and, you know, the thing... The first thing that jumps out at you guys is that, you know, Oracle with Autonomous is off the charts, far ahead of anybody else on this. And actually guys, if you just bring up slide number two, we'll take a look at the stream/event processing and operational intelligence use cases. And you can see, again, you know, Oracle has a big lead. And I don't want to necessarily go through every vendor here, but guys, if you don't mind going back to the first slide 'cause I think this is really, you know, the core of transaction processing. So let's look at this, you've got Oracle, you've got SAP HANA. You know, right there interestingly Amazon Web Services with the Aurora, you know, IBM Db2, which, you know, it goes back to the good old days, you know, down the list. But so, let me again start with Marc. So why is that? I mean, I guess this is no surprise, Oracle still owns the Mission-Critical for the database space. They earned that years ago. One that, you know, over the likes of Db2 and, you know, Informix and Sybase, and, you know, they emerged as number one there. But what do you make of this data Marc? >> If you look at this data in a vacuum, you're looking at specific functionality, I think you need to look at all the slides in total. And the reason I bring that up is because I agree with what David said earlier, in that the use case that's becoming more prevalent is the integration of transaction and analytics. And more importantly, it's not just your traditional data warehouse, but it's AI analytics. It's big data analytics. It's users are finding that they need more than just simple reporting. They need more in-depth analytics so that they can get more actionable insights into their data where they can react in real time. And so if you look at it just as a transaction, that's great. If you're going to just as a data warehouse, that's great, or analytics, that's fine. If you have a very narrow use case, yes. But I think today what we're looking at is... It's not so narrow. It's sort of like, if you bought a streaming device and it only streams Netflix and then you need to get another streaming device 'cause you want to watch Amazon Prime. You're not going to do that, you want one, that does all of it, and that's kind of what's missing from this data. So I agree that the data is good, but I don't think it's looking at it in a total encompassing manner. >> Well, so before we get off the horses on the track 'cause I love to do that. (Dave chuckles) I just kind of let's talk about that. So Marc, you're putting forth the... You guys seem to agree on that premise that the database that can do more than just one thing is of appeal to customers. I suppose that makes, certainly makes sense from a cost standpoint. But, you know, guys feel free to flip back and forth between slides one and two. But you can see SAP HANA, and I'm not sure what cloud that's running on, it's probably running on a combination of clouds, but, you know, scoring very strongly. I thought, you know, Aurora, you know, given AWS says it's one of the fastest growing services in history and they've got it ahead of Db2 just on functionality, which is pretty impressive. I love Google Spanner, you know, love the... What they're trying to accomplish there. You know, you go down to Microsoft is, they're kind of the... They're always good enough a database and that's how they succeed and et cetera, et cetera. But David, it sounds like you agree with Marc. I would say, I would think though, Amazon kind of doesn't agree 'cause they're like a horses for courses. >> I agree. >> Yeah, yeah. >> So I wonder if you could comment on that. >> Well, I want to comment on two vectors. The first vector is that the size of customer and, you know, a mid-sized customer versus a global $2,000 or global 500 customer. For the smaller customer that's the heart of AWS, and they are taking their applications and putting pretty well everything into their cloud, the one cloud, and Aurora is a good choice. But when you start to get to a requirements, as you do in larger companies have very high levels of availability, the functionality is not there. You're not comparing apples and... Apples with apples, it's two very different things. So from a tier one functionality point of view, IBM Db2 and Oracle have far greater capability for recovery and all the features that they've built in over there. >> Because of their... You mean 'cause of the maturity, right? maturity and... >> Because of their... Because of their focus on transaction and recovery, et cetera. >> So SAP though HANA, I mean, that's, you know... (David talks indistinctly) And then... >> Yeah, yeah. >> And then I wanted your comments on that, either of you or both of you. I mean, SAP, I think has a stated goal of basically getting its customers off Oracle that's, you know, there's always this urinary limping >> Yes, yes. >> between the two companies by 2024. Larry has said that ain't going to happen. You know, Amazon, we know still runs on Oracle. It's very hard to migrate Mission-Critical, David, you and I know this well, Marc you as well. So, you know, people often say, well, everybody wants to get off Oracle, it's too expensive, blah, blah, blah. But we talked to a lot of Oracle customers there, they're very happy with the reliability, availability, recoverability feature set. I mean, the core of Oracle seems pretty stable. >> Yes. >> But I wonder if you guys could comment on that, maybe Marc you go first. >> Sure. I've recently done some in-depth comparisons of Oracle and Aurora, and all their other RDS services and Snowflake and Google and a variety of them. And ultimately what surprised me is you made a statement it costs too much. It actually comes in half of Aurora for in most cases. And it comes in less than half of Snowflake in most cases, which surprised me. But no matter how you configure it, ultimately based on a couple of things, each vendor is focused on different aspects of what they do. Let's say Snowflake, for example, they're on the analytical side, they don't do any transaction processing. But... >> Yeah, so if I can... Sorry to interrupt. Guys if you could bring up the next slide that would be great. So that would be slide three, because now we get into the analytical piece Marc that you're talking about that's what Snowflake specialty is. So please carry on. >> Yeah, and what they're focused on is sharing data among customers. So if, for example, you're an automobile manufacturer and you've got a huge supply chain, you can supply... You can share the data without copying the data with any of your suppliers that are on Snowflake. Now, can you do that with the other data warehouses? Yes, you can. But the focal point is for Snowflake, that's where they're aiming it. And whereas let's say the focal point for Oracle is going to be performance. So their performance affects cost 'cause the higher the performance, the less you're paying for the performing part of the payment scale. Because you're paying per second for the CPUs that you're using. Same thing on Snowflake, but the performance is higher, therefore you use less. I mean, there's a whole bunch of things to come into this but at the end of the day what I've found is Oracle tends to be a lot less expensive than the prevailing wisdom. So let's talk value for a second because you said something, that yeah the other databases can do that, what Snowflake is doing there. But my understanding of what Snowflake is doing is they built this global data mesh across multiple clouds. So not only are they compatible with Google or AWS or Azure, but essentially you sign up for Snowflake and then you can share data with anybody else in the Snowflake cloud, that I think is unique. And I know, >> Marc: Yes. >> Redshift, for instance just announced, you know, Redshift data sharing, and I believe it's just within, you know, clusters within a customer, as opposed to across an ecosystem. And I think that's where the network effect is pretty compelling for Snowflake. So independent of costs, you and I can debate about costs and, you know, the tra... The lack of transparency of, because AWS you don't know what the bill is going to be at the end of the month. And that's the same thing with Snowflake, but I find that... And by the way guys, you can flip through slides three and four, because we've got... Let me just take a quick break and you have data warehouse, logical data warehouse. And then the next slide four you got data science, deep learning and operational intelligent use cases. And you can see, you know, Teradata, you know, law... Teradata came up in the mid 1980s and dominated in that space. Oracle does very well there. You can see Snowflake pop-up, SAP with the Data Warehouse, Amazon with Redshift. You know, Google with BigQuery gets a lot of high marks from people. You know, Cloud Data is in there, you know, so you see some of those names. But so Marc and David, to me, that's a different strategy. They're not trying to be just a better data warehouse, easier data warehouse. They're trying to create, Snowflake that is, an incremental opportunity as opposed to necessarily going after, for example, Oracle. David, your thoughts. >> Yeah, I absolutely agree. I mean, ease of use is a primary benefit for Snowflake. It enables you to do stuff very easily. It enables you to take data without ETL, without any of the complexity. It enables you to share a number of resources across many different users and know... And be able to bring in what that particular user wants or part of the company wants. So in terms of where they're focusing, they've got a tremendous ease of use, tremendous focus on what the customer wants. And you pointed out yourself the restrictions there are of doing that both within Oracle and AWS. So yes, they have really focused very, very hard on that. Again, for the future, they are bringing in a lot of additional functions. They're bringing in Python into it, not Python, JSON into the database. They can extend the database itself, whether they go the whole hog and put in transaction as well, that's probably something they may be thinking about but not at the moment. >> Well, but they, you know, they obviously have to have TAM expansion designs because Marc, I mean, you know, if they just get a 100% of the data warehouse market, they're probably at a third of their stock market valuation. So they had better have, you know, a roadmap and plans to extend there. But I want to come back Marc to this notion of, you know, the right tool for the right job, or, you know, best of breed for a specific, the right specific, you know horse for course, versus this kind of notion of all in one, I mean, they're two different ends of the spectrum. You're seeing, you know, Oracle obviously very successful based on these ratings and based on, you know their track record. And Amazon, I think I lost count of the number of data stores (Dave chuckles) with Redshift and Aurora and Dynamo, and, you know, on and on and on. (Marc talks indistinctly) So they clearly want to have that, you know, primitive, you know, different APIs for each access, completely different philosophies it's like Democrats or Republicans. Marc your thoughts as to who ultimately wins in the marketplace. >> Well, it's hard to say who is ultimately going to win, but if I look at Amazon, Amazon is an all-cart type of system. If you need time series, you go with their time series database. If you need a data warehouse, you go with Redshift. If you need transaction, you go with one of the RDS databases. If you need JSON, you go with a different database. Everything is a different, unique database. Moving data between these databases is far from simple. If you need to do a analytics on one database from another, you're going to use other services that cost money. So yeah, each one will do what they say it's going to do but it's going to end up costing you a lot of money when you do any kind of integration. And you're going to add complexity and you're going to have errors. There's all sorts of issues there. So if you need more than one, probably not your best route to go, but if you need just one, it's fine. And if, and on Snowflake, you raise the issue that they're going to have to add transactions, they're going to have to rewrite their database. They have no indexes whatsoever in Snowflake. I mean, part of the simplicity that David talked about is because they had to cut corners, which makes sense. If you're focused on the data warehouse you cut out the indexes, great. You don't need them. But if you're going to do transactions, you kind of need them. So you're going to have to do some more work there. So... >> Well... So, you know, I don't know. I have a different take on that guys. I think that, I'm not sure if Snowflake will add transactions. I think maybe, you know, their hope is that the market that they're creating is big enough. I mean, I have a different view of this in that, I think the data architecture is going to change over the next 10 years. As opposed to having a monolithic system where everything goes through that big data platform, the data warehouse and the data lake. I actually see what Snowflake is trying to do and, you know, I'm sure others will join them, is to put data in the hands of product builders, data product builders or data service builders. I think they're betting that that market is incremental and maybe they don't try to take on... I think it would maybe be a mistake to try to take on Oracle. Oracle is just too strong. I wonder David, if you could comment. So it's interesting to see how strong Gartner rated Oracle in cloud database, 'cause you don't... I mean, okay, Oracle has got OCI, but you know, you think a cloud, you think Google, or Amazon, Microsoft and Google. But if I have a transaction database running on Oracle, very risky to move that, right? And so we've seen that, it's interesting. Amazon's a big customer of Oracle, Salesforce is a big customer of Oracle. You know, Larry is very outspoken about those companies. SAP customers are many, most are using Oracle. I don't, you know, it's not likely that they're going anywhere. My question to you, David, is first of all, why do they want to go to the cloud? And if they do go to the cloud, is it logical that the least risky approach is to stay with Oracle, if you're an Oracle customer, or Db2, if you're an IBM customer, and then move those other workloads that can move whether it's more data warehouse oriented or incremental transaction work that could be done in a Aurora? >> I think the first point, why should Oracle go to the cloud? Why has it gone to the cloud? And if there is a... >> Moreso... Moreso why would customers of Oracle... >> Why would customers want to... >> That's really the question. >> Well, Oracle have got Oracle Cloud@Customer and that is a very powerful way of doing it. Where exactly the same Oracle system is running on premise or in the cloud. You can have it where you want, you can have them joined together. That's unique. That's unique in the marketplace. So that gives them a very special place in large customers that have data in many different places. The second point is that moving data is very expensive. Marc was making that point earlier on. Moving data from one place to another place between two different databases is a very expensive architecture. Having the data in one place where you don't have to move it where you can go directly to it, gives you enormous capabilities for a single database, single database type. And I'm sure that from a transact... From an analytic point of view, that's where Snowflake is going, to a large single database. But where Oracle is going to is where, you combine both the transactional and the other one. And as you say, the cost of migration of databases is incredibly high, especially transaction databases, especially large complex transaction databases. >> So... >> And it takes a long time. So at least a two year... And it took five years for Amazon to actually succeed in getting a lot of their stuff over. And five years they could have been doing an awful lot more with the people that they used to bring it over. So it was a marketing decision as opposed to a rational business decision. >> It's the holy grail of the vendors, they all want your data in their database. That's why Amazon puts so much effort into it. Oracle is, you know, in obviously a very strong position. It's got growth and it's new stuff, it's old stuff. It's, you know... The problem with Oracle it has like many of the legacy vendors, it's the size of the install base is so large and it's shrinking. And the new stuff is.... The legacy stuff is shrinking. The new stuff is growing very, very fast but it's not large enough yet to offset that, you see that in all the learnings. So very positive news on, you know, the cloud database, and they just got to work through that transition. Let's bring up slide number five, because Marc, this is to me the most interesting. So we've just shown all these detailed analysis from Gartner. And then you look at the Magic Quadrant for cloud databases. And, you know, despite Amazon being behind, you know, Oracle, or Teradata, or whomever in every one of these ratings, they're up to the right. Now, of course, Gartner will caveat this and say, it doesn't necessarily mean you're the best, but of course, everybody wants to be in the upper, right. We all know that, but it doesn't necessarily mean that you should go by that database, I agree with what Gartner is saying. But look at Amazon, Microsoft and Google are like one, two and three. And then of course, you've got Oracle up there and then, you know, the others. So that I found that very curious, it is like there was a dissonance between the hardcore ratings and then the positions in the Magic Quadrant. Why do you think that is Marc? >> It, you know, it didn't surprise me in the least because of the way that Gartner does its Magic Quadrants. The higher up you go in the vertical is very much tied to the amount of revenue you get in that specific category which they're doing the Magic Quadrant. It doesn't have to do with any of the revenue from anywhere else. Just that specific quadrant is with that specific type of market. So when I look at it, Oracle's revenue still a big chunk of the revenue comes from on-prem, not in the cloud. So you're looking just at the cloud revenue. Now on the right side, moving to the right of the quadrant that's based on functionality, capabilities, the resilience, other things other than revenue. So visionary says, hey how far are you on the visionary side? Now, how they weight that again comes down to Gartner's experts and how they want to weight it and what makes more sense to them. But from my point of view, the right side is as important as the vertical side, 'cause the vertical side doesn't measure the growth rate either. And if we look at these, some of these are growing much faster than the others. For example, Snowflake is growing incredibly fast, and that doesn't reflect in these numbers from my perspective. >> Dave: I agree. >> Oracle is growing incredibly fast in the cloud. As David pointed out earlier, it's not just in their cloud where they're growing, but it's Cloud@Customer, which is basically an extension of their cloud. I don't know if that's included these numbers or not in the revenue side. So there's... There're a number of factors... >> Should it be in your opinion, Marc, would you include that in your definition of cloud? >> Yeah. >> The things that are hybrid and on-prem would that cloud... >> Yes. >> Well especially... Well, again, it depends on the hybrid. For example, if you have your own license, in your own hardware, but it connects to the cloud, no, I wouldn't include that. If you have a subscription license and subscription hardware that you don't own, but it's owned by the cloud provider, but it connects with the cloud as well, that I would. >> Interesting. Well, you know, to your point about growth, you're right. I mean, it's probably looking at, you know, revenues looking, you know, backwards from guys like Snowflake, it will be double, you know, the next one of these. It's also interesting to me on the horizontal axis to see Cloud Data and Databricks further to the right, than Snowflake, because that's kind of the data lake cloud. >> It is. >> And then of course, you've got, you know, the other... I mean, database used to be boring, so... (David laughs) It's such a hot market space here. (Marc talks indistinctly) David, your final thoughts on all this stuff. What does the customer take away here? What should I... What should my cloud database management strategy be? >> Well, I was positive about Oracle, let's take some of the negatives of Oracle. First of all, they don't make it very easy to rum on other platforms. So they have put in terms and conditions which make it very difficult to run on AWS, for example, you get double counts on the licenses, et cetera. So they haven't played well... >> Those are negotiable by the way. Those... You bring it up on the customer. You can negotiate that one. >> Can be, yes, They can be. Yes. If you're big enough they are negotiable. But Aurora certainly hasn't made it easy to work with other plat... Other clouds. What they did very... >> How about Microsoft? >> Well, no, that is exactly what I was going to say. Oracle with adjacent workloads have been working very well with Microsoft and you can then use Microsoft Azure and use a database adjacent in the same data center, working with integrated very nicely indeed. And I think Oracle has got to do that with AWS, it's got to do that with Google as well. It's got to provide a service for people to run where they want to run things not just on the Oracle cloud. If they did that, that would in my term, and my my opinion be a very strong move and would make make the capabilities available in many more places. >> Right. Awesome. Hey Marc, thanks so much for coming to theCUBE. Thank you, David, as well, and thanks to Gartner for doing all this great research and making it public on the web. You can... If you just search critical capabilities for cloud database management systems for operational use cases, that's a mouthful, and then do the same for analytical use cases, and the Magic Quadrant. There's the third doc for cloud database management systems. You'll get about two hours of reading and I learned a lot and I learned a lot here too. I appreciate the context guys. Thanks so much. >> My pleasure. All right, thank you for watching everybody. This is Dave Vellante for theCUBE. We'll see you next time. (upbeat music)

>> Announcer: From around the globe, it's theCUBE, with digital coverage of AWS re:Invent 2020. Special coverage sponsored by AWS Worldwide Public Sector. >> Welcome to theCUBE Virtual and our coverage of AWS re:Invent 2020, the specialized programming for Worldwide Public Sector. I'm Lisa Martin. I'm joined by Nick Speece the chief federal technologist for Snowflake. Nick, welcome to theCUBE. >> Thank you, Lisa. It's great to be here. >> Likewise, chief federal technologist, that's the first time I've ever heard of that title. Tell me a little bit about that. >> It's probably the last time you'll hear it. So chief federal technologist is really somebody in the company who is focused on bringing the needs of the federal government back to our corporate headquarters, making sure that the product as it's developed and evolves has the federal requirements in mind. >> Excellent. So the last couple of months for Snowflake big, biggest software IPO and software history your market cap right now is at 66 billion 515 data workloads running on Snowflake's platform every day 250 petabytes of data under management, a lot is going on. Let's talk about Snowflake. You guys operate only in the cloud, why was that decision made and how does that impact businesses analysis of data? >> Yeah, so great question and the answer is actually in the opening that you gave for us and thank you for that reinforcement. Snowflake can't exist anywhere, but the cloud. Technology over the last five to 10 years has really seen a move from what the cloud originally was, which was I have a virtual machine in my data center, I'm going to run it on your stuff not mine, into more comprehensive service offerings like Snowflake. We can't reach the kind of scale that Snowflake operates at every day and that our customers demand without the technology of clouds like AWS. The technology has to be there, the underlying and underpinning architecture has to be there, otherwise our customers get left in the dark and we can't can't have that. >> And especially today as data volumes are massively increasing and we know that that's only going to go up. We know that IT is only going to be more complex but when we talk to businesses in any industry the value of the data is in the insights the ability to extract that data in real time glean insights from it so that businesses can make data-based decisions that pivot their business, especially critical during the year that we have now known as 2020. Talk to me a little bit about though digging into your marketing material, everyone, there's all these terms, right, that everyone uses and you guys use single source of truth. What does it actually mean for single source, for stuff like? >> Yeah, so we talk about cloud, we talk about single source of truth and when you're looking at data problems, the problem and the solution are the same thing. A massive amount of data is a raw resource, that's all it is. And trying to refine that raw resource into something that is insightful or something that is useful to a business process is a challenge that every customer in every market, in every region undergoes. And how you overcome that is critical. And one of the primary focuses of Snowflake is to evolve the data cloud. Snowflake platform is the underlying technology for the data cloud but the data cloud is where we're going. And what I mean by data cloud. If you have a data set, your internal data, that is your truth, but it might not be the truth. So in Snowflake we encourage our customers to collaborate on data sets. For example, if you want to know how many people are living in a certain borough in New York City you could go around with a clicker and count everyone, or you could just ask the Census Bureau. That's the nature of the data cloud and what we're talking about here. Going to the subject matter experts who have the data that you need, using our marketplace, using our private exchanges, using our data sharing to build your own data cloud and become part of the next gen architecture for data sharing and collaboration, to get to the source of the truth, to make better decisions, to gain better insights. It's great to combine your data with enrich data from other sources, especially when it comes to making federal decisions and governance decisions. >> Absolutely that's critical. That the biggest challenge customers have is being able to sort through all that and find. I like how you put this as their single source of truth. Can you give us some examples of some federal agencies maybe even just anonymously that are using the power of Snowflake to do just that? >> Absolutely. We've got customers in the healthcare space and in some of the law enforcement spaces and especially in public education that are trying to increase the awareness of the folks that are subscribing to their services, for example, folks that are looking for healthcare help. If you're filing claims for a certain healthcare providers or certain care facilities, we want to make sure that those claims that are forwarded to those entities are legitimate, first of all, for example, if you're filing a claim for knee surgery in Florida, you probably didn't have one in California, three hours later. So those kinds of enforcement activities, and not just trying to do audits but also to benefit everybody who's receiving care. There's a lot of push now about genetic sequencing, DNA and RNA vaccination is huge with COVID-19, getting access to massive amounts of data to do analysis against and figure out the best approach, that's critical for where we go in the next 10 to 15 years in healthcare. Snowflake is very, very honored and happy to be propelling that move in the healthcare space. >> It is that's going to be absolutely critical but we're also seeing it, you know, everywhere else, such as for universities and education, suddenly this need, the last few months for real-time learning. Talk to me about data analysis. Can Snowflake help companies, you talked about enriching data sets so not just companies sources of data but additional data sets that they can add in and evaluate and analyze to make great decisions, but from a historical real-time perspective, talk to me how Snowflake helps with that data analysis. >> Yeah, sure. Right. So Snowflake in and of itself can do some analysis work. We've got some great visualization tools in our new UI that was released recently on public preview. So there's some analysis tools built into Snowflake but really where the value comes from is in taking your tools that you already use today and connecting it to a data source or platform that can wrangle that data, that can move that data through automated pipelines to give you a model view of that data that's beneficial. For example, data scientists and data engineers spend 80% of their time, and I know a lot of statistics are made up on the spot, that was not a promise, but trying to move this data through and refine it and build features to get to the point where you can ask a question is 80% of these very valuable professionals time. Shortening those timelines is what Snowflake really aims to do in the analysis space. We're not trying to replace the analysis tools that you use today, we work fine with all of them. The big difference is presenting them with enough data volume to give you real insights and eliminate bias as much as we can in data sets. >> What are some of the things that differentiates Snowflake from data warehouses and other folks in the market? >> Yeah. Great question. The big difference is Snowflake was built natively for the cloud. We weren't adapted to the cloud, we didn't adopt the cloud at some point in the future, Snowflake was built from scratch to be in the cloud. And since this is the appropriate show to mention it the primary difference between us is we were built to use object storage foundationally underneath our technology. And I know that sounds really nerdy and it is, but it adds a tremendous amount of value. If you think about how we used to collaborate 10 years ago we'd have a spreadsheet that if I open that spreadsheet for my share drive and you tried to open it at the same time, you'd get locked out. You're told you couldn't have it. And if tradition stays true I would probably be on vacation for two weeks. Contrast that now with the massive Google Doc platform and Office 365, object storage has changed the way that we collaborate on the same kinds of documents. Multiple people interacting with one thing at one time without contention, that's the reason why Snowflake has to operate in the cloud. We bring that same paradigm, multiple actors on a single object and give you that source of truth the truth that you absolutely need to make decisions. >> And that's critical these days as we know. We're in living in uncertain times and one of the things I think we can expect is the uncertainty to continue, but also for many industries people to stay remote or some big percentage for quite a while. So the ability to have those collaboration tools and be able to collaborate in real time is table stakes for so many companies. But when we're talking about some of the things going on this year, security, we can't not talk about security. You know, all these folks from home accessing corporate networks, you know, maybe not through VPNs or behind firewalls, the cloud is paramount to that. How does Snowflake address the security issue? >> Absolutely. So I'll start by saying our security is inherited from the wonderful security platform that AWS has underneath it. So we inherit all the security around data storage the EC Compute, all of the different entities and end points that AWS already secures Snowflake takes the same precautions. More than that, we've also built and rolled this access control to ensure that people are getting access only to the data that they should be getting access to, we recently implemented data masking as well, so certain roles are not able to see unmasked data, but they can still do queries that use the underlying data to filter. So there's a lot of different capabilities built in, encryption at rest, encryption in flight, AES-256 encryption keys used in a hierarchial model. These are phenomenal security architectures that are paramount to the security of the folks that are using our platform. Because we know at the end of the day the first day we have a leak in Snowflake is probably our last day in business. We got to be good at that which is why it's our top priority. >> I didn't, to ever talk about security as an inherited, I must be a dominant trait if we're going to be talking about, you know, genetics and chromosomes and mRNA and things like that. So walk me through last question, a government organization, or say they're an AWS customer or they want to start using Snowflake, what's that process? How do they go about doing that to leverage those inherited security capabilities that you talked about? >> Well, thankfully AWS has helped us put a FedRAMP moderate certified Snowflake region together in AWS, East commercial, so we're very happy to have a FedRAMP moderate region. They can access Snowflake through the AWS Marketplace or from Snowflake.com, you can start a trial in just a couple of minutes. Our security is built into all of our regions although the FedRAMP regions are specialized in some of the encryption technology we use, but we always, always always protect our users' data, regardless of where it is. >> You make it sound easy, I got to say. (laughing) >> That's because it is. (laughing) Thank you cloud. >> That's good. And well, that's good and it should be, especially because there's so much complexity and uncertainty everywhere else in the world right now. Last question for you. As I mentioned in the beginning, the biggest IPO in software history, just a couple of months ago during probably one of the most strangest time of any of us have ever, and our relatives ever witnessed, what can we expect from Snowflake in 2021? Are you going to bring all the good vibes that we all need? (laughing) >> Well, good vibes is our business model. You know, Snowflake is a phenomenal platform. We've had a ton of success driven by the success of our cloud provider partners, driven by the success of our wonderful customers. We have over 4,000 people using Snowflake now to great effect. You can look for more features, you can look for more functions, but really the evolution of the data cloud, our big push is to help our customers get into the data cloud, get the truth out of their data and make better decisions every day. And you'll see more of that from us as time continues. >> One more question I wanted to sneak in, how did you work with those customers to evolve the data cloud? What's that feedback loop like? >> It's, a lot of it comes down to silos that the customers have built up over years and years and years of operation. That's the first step. In Snowflake there isn't such thing really as a data silo there's data put into Snowflake, everything is unified, you can do queries across databases, that's the first thing. The second thing is browsing our data marketplace. It's just like an App Store for your phone but instead it's data sets and the data sets are published by the experts who know that material better than anyone. I mentioned earlier bringing in everything from housing evaluation data to COVID-19 data from California and Boston, bringing World Health Organization data, John Hopkins University data, joining that with the data that you already use today along with weather and population counts, the main thing here, the strategy is almost endless. More and more data sets are being published over every day. We have over a hundred contributors in the marketplace now. >> That's exciting that we have the technology and the power like this to help the world re, you know, recover from such a crazy time. It's nice to know that, that there was the power of that behind that, and the smart folks like you chief federal technologists, helping to fine tune that and really ensure that organizations across the government can maximize the value of data and find their single source of truth. Nick, it's been a blast having you on theCUBE. Thank you for joining me. >> Thank you for having me. >> For next piece, I'm Lisa Martin. You're watching theCUBE Virtual. (upbeat music)

>>Welcome everyone. Good morning. Good evening to all of you around the world. I am so excited to welcome you to launch bad our annual conference for customers, for partners, for our own colleagues here at Mirandes. This is meant to be a forum for learning, for sharing for discovery. One of openness. We're incredibly excited. Do you have you here with us? I want to take a few minutes this morning and opened the conference and share with you first and foremost where we're going as a company. What is our vision then? I also want to share with you on update on what we have been up to you for the past year. Especially with two important acquisitions, Doc Enterprise and then container and lens. And what are some of the latest developments at Mirandes? And then I'll close also with an exciting announcement that we have today, which we hope is going to be interesting and valuable for all of you. But let me start with our mission. What are we here to Dio? It's very simple. We want to help you the ship code faster. This is something that we're very excited about, something that we have achieved for many of you around the world. And we just want thio double down on. We feel this is a mission that's very much worthwhile and relevant and important to you. Now, how do we do that? How do we help you ship code faster? There are three things we believe in. We believe in this world of cloud. Um, choice is incredibly important. We all know that developers want to use the latest tools. We all know that cloud technology is evolving very quickly and new innovations appear, um, very, very quickly, and we want to make them available to you. So choice is very important. At the same time, consuming choice can be difficult. So our mission is to make choice simple for you to give developers and operators simplicity and then finally underpinning everything that we dio is security. These are the three big things that we invest in and that we believe that choice, simplicity and security and the foundation technology that we're betting on to make that happen for you is kubernetes many of you, many of our customers use kubernetes from your aunties today and they use it at scale. And this is something we want to double down on the fundamental benefit. The our key promise we want to deliver for you is Speed. And we feel this is very relevant and important and and valuable in the world that we are in today. So you might also be interested in what have been our priorities since we acquired Doc Enterprise. What has happened for the past year at Miranda's And there are three very important things we focused on as a company. The first one is customer success. Um, when we acquired Doc Enterprise, the first thing we did is listen to you connect with the most important customers and find out what was your sentiment. What did you like? What were you concerned about? What needed to improve? How can we create more value and a better experience for you? So, customers success has been a top of our list of priorities ever since. And here is what we've heard here is what you've told us. You've told us that you very much appreciated the technology that you got a lot of value out of the technology, but that at the same time, there are some things that we can do better. Specifically, you wanted better. Sele's better support experience. You also wanted more clarity on the road map. You also wanted to have a deeper alignment and a deeper relationship between your needs and your requirements and our our technical development that keep people in our development organization are most important engineers. So those three things are were very, very important to you and they were very important to us here. So we've taken that to heart and over the past 12 months, we believe, as a team, we have dramatically improved the customer support experience. We introduced new SLS with prod care. We've rolled out a roadmap to many many of our customers. We've taken your requirements of the consideration and we've built better and deeper relationships with so many of you. And the evidence for that that we've actually made some progress is in a significant increase off the work clothes and in usage of all platforms. I was so fortunate that we were able to build better and stronger relationships and take you to the next level of growth for companies like Visa like soc T general, like nationwide, like Bosch, like Axa X l like GlaxoSmithKline, like standard and Poor's, like Apple A TNT. So many, many off you, Many of all customers around the world, I believe over the past 12 months have experienced better, better, better support strong s L. A s a deeper relationship and a lot more clarity on our roadmap and our vision forward. The second very big priority for us over the last year has been product innovation. This is something that we are very excited about that we've invested. Most of our resource is in, and we've delivered some strong proof points. Doc Enterprise 3.1 has been the first release that we have shipped. Um, as Mirant is as the unified company, Um, it's had some big innovative features or Windows support or a I and machine learning use cases and a significant number off improvements in stability and scalability earlier this year. We're very excited to have a quiet lens and container team, which is by far the most popular kubernetes. I'd, um, in the world today and every day, 600 new users are starting to use lens to manage the community's clusters to deploy applications on top of communities and to dramatically simplify the experience for communities for operators and developers alike. That is a very big step forward for us as a company. And then finally, this week at this conference, we announcing our latest product, which we believe is a huge step forward for Doc Enterprise and which we call Doc Enterprise, Container Cloud, and you will hear a lot more about that during this conference. The third vector of development, the third priority for us as a company over the past year was to become mawr and Mawr developer centric. As we've seen over the past 10 years, developers really move the world forward. They create innovation, they create new software. And while our platform is often managed and run and maybe even purchased by RT architects and operators and I T departments, the actual end users are developers. And we made it our mission a za company, to become closer and closer to developers to better understand their needs and to make our technology as easy and fast to consume as possible for developers. So as a company, we're becoming more and more developers centric, really. The two core products which fit together extremely well to make that happen, or lens, which is targeted squarely at a new breed off kubernetes developers sitting on the desktop and managing communities, environments and the applications on top on any cloud platform anywhere and then DACA enterprise contain a cloud which is a new and radically innovative, contain a platform which we're bringing to market this week. So with this a za background, what is the fundamental problem which we solve for you, for our customers? What is it that we feel are are your pain points that can help you resolve? We see too very, very big trends in the world today, which you are experiencing. On one side, we see the power of cloud emerging with more features mawr innovation, more capabilities coming to market every day. But with those new features and new innovations, there is also an exponential growth in cloud complexity and that cloud complexity is becoming increasingly difficult to navigate for developers and operators alike. And at the same time, we see the pace of change in the economy continuing to accelerate on bits in the economy and in the technology as well. So when you put these two things together on one hand, you have MAWR and Mawr complexity. On the other hand, you have fast and faster change. This makes for a very, very daunting task for enterprises, developers and operators to actually keep up and move with speed. And this is exactly the central problem that we want to solve for you. We want to empower you to move with speed in the middle off rising complexity and change and do it successfully and with confidence. So with that in mind, we are announcing this week at LAUNCHPAD a big and new concept to take the company forward and take you with us to create value for you. And we call this your cloud everywhere, which empowers you to ship code faster. Dr. Enterprise Container Cloud is a lynch bit off your cloud everywhere. It's a radical and new container platform, which gives you our customers a consistent experience on public clouds and private clouds alike, which enables you to ship code faster on any infrastructure, anywhere with a cohesive cloud fabric that meets your security standards that offers a choice or private and public clouds and offer you a offers you a simple, an extremely easy and powerful to use experience. for developers. All of this is, um, underpinned by kubernetes as the foundation technology we're betting on forward to help you achieve your goals at the same time. Lens kubernetes e. It's also very, very well into the real cloud. Every concept, and it's a second very strong linchpin to take us forward because it creates the developing experience. It supports developers directly on their desktop, enabling them Thio manage communities workloads to test, develop and run communities applications on any infrastructure anywhere. So Doc, Enterprise, Container, Cloud and Lens complement each other perfectly. So I'm very, very excited to share this with you today and opened the conference for you. And with this I want to turn it over to my colleague Adam Parker, who runs product development at Mirandes to share a lot more detail about Doc Enterprise Container Cloud. Why we're excited about it. Why we feel is a radical step forward to you and why we feel it can add so much value to your developers and operators who want to embrace the latest kubernetes technology and the latest container technology on any platform anywhere. I look forward to connecting with you during the conference and we should all the best. Bye bye. >>Thanks, Adrian. My name is Adam Parco, and I am vice president of engineering and product development at Mirant ISS. I'm extremely excited to be here today And to present to you Dr Enterprise Container Cloud Doc Enterprise Container Cloud is a major leap forward. It Turpal charges are platform. It is your cloud everywhere. It has been completely designed and built around helping you to ship code faster. The world is moving incredibly quick. We have seen unpredictable and rapid changes. It is the goal of Docker Enterprise Container Cloud to help navigate this insanity by focusing on speed and efficiency. To do this requires three major pillars choice, simplicity and security. The less time between a line of code being written and that line of code running in production the better. When you decrease that cycle, time developers are more productive, efficient and happy. The code is higher, quality contains less defects, and when bugs are found are fixed quicker and more easily. And in turn, your customers get more value sooner and more often. Increasing speed and improving developer efficiency is paramount. To do this, you need to be able to cycle through coding, running, testing, releasing and monitoring all without friction. We enabled us by offering containers as a service through a consistent, cloudlike experience. Developers can log into Dr Enterprise Container Cloud and, through self service, create a cluster No I T. Tickets. No industry specific experience required. Need a place to run. A workload simply created nothing quicker than that. The clusters air presented consistently no matter where they're created, integrate your pipelines and start deploying secure images everywhere. Instantly. You can't have cloud speed if you start to get bogged down by managing, so we offer fully automated lifecycle management. Let's jump into the details of how we achieve cloud speed. The first is cloud choice developers. Operators add mons users they all want. In fact, mandate choice choice is extremely important in efficiency, speed and ultimately the value created. You have cloud choice throughout the full stack. Choice allows developers and operators to use the tooling and services their most familiar with most efficient with or perhaps simply allows them to integrate with any existing tools and services already in use, allowing them to integrate and move on. Doc Enterprise Container Cloud isn't constructive. It's open and flexible. The next important choice we offer is an orchestration. We hear time and time again from our customers that they love swarm. That's simply enough for the majority of their applications. And that just works that they have skills and knowledge to effectively use it. They don't need to be or find coop experts to get immediate value, so we will absolutely continue to offer this choice and orchestration. Our existing customers could rest assure their workloads will continue to run. Great as always. On the other hand, we can't ignore the popularity that growth, the enthusiasm and community ecosystem that has exploded with communities. So we will also be including a fully conforming, tested and certified kubernetes going down the stock. You can't have choice or speed without your choice and operating system. This ties back to developer efficiency. We want developers to be able to leverage their operating system of choice, were initially supporting full stack lifecycle management for a bun, too, with other operating systems like red hat to follow shortly. Lastly, all the way down at the bottom of stack is your choice in infrastructure choice and infrastructure is in our DNA. We have always promoted no locking and flexibility to run where needed initially were supporting open stock AWS and full life cycle management of bare metal. We also have a road map for VM Ware and other public cloud providers. We know there's no single solution for the unique and complex requirements our customers have. This is why we're doubling down on being the most open platform. We want you to truly make this your cloud. If done wrong, all this choice at speed could have been extremely complex. This is where cloud simplification comes in. We offer a simple and consistent as a service cloud experience, from installation to day to ops clusters Air created using a single pane of glass no matter where they're created, giving a simple and consistent interface. Clusters can be created on bare metal and private data centers and, of course, on public cloud applications will always have specific operating requirements. For example, data protection, security, cost efficiency edge or leveraging specific services on public infrastructure. Being able to create a cluster on the infrastructure that makes the most sense while maintaining a consistent experience is incredibly powerful to developers and operators. This helps developers move quick by being able to leverage the infra and services of their choice and operators by leveraging, available, compute with the most efficient and for available. Now that we have users self creating clusters, we need centralized management to support this increase in scale. Doc Enterprise Container cloud use is the single pane of glass for observe ability and management of all your clusters. We have day to ops covered to keep things simple and new. Moving fast from this single pane of glass, you can manage the full stack lifecycle of your clusters from the infra up, including Dr Enterprise, as well as the fully automated deployment and management of all components deployed through it. What I'm most excited about is Doc Enterprise Container Cloud as a service. What do I mean by as a service doctor? Enterprise continue. Cloud is fully self managed and continuously delivered. It is always up to date, always security patched, always available new features and capabilities pushed often and directly to you truly as a service experience anywhere you want, it run. Security is of utmost importance to Miranda's and our customers. Security can't be an afterthought, and it can't be added later with Doctor and a price continued cloud, we're maintaining our leadership and security. We're doing this by leveraging the proven security and Dr Enterprise. Dr. Enterprise has the best and the most complete security certifications and compliance, such as Stig Oscar, How and Phipps 1 $40 to thes security certifications allows us to run in the world's most secure locations. We are proud and honored to have some of the most security conscious customers in the world from all industries into. She's like insurance, finance, health care as well as public, federal and government agencies. With Dr Enterprise Container Cloud. We put security as our top concern, but importantly, we do it with speed. You can't move fast with security in the way so they solve this. We've added what we're calling invisible security security enabled by default and configured for you as part of the platform. Dr Price Container Cloud is multi tenant with granular are back throughout. In conjunction with Doc Enterprise, Docker Trusted Registry and Dr Content Trust. We have a complete end to end secured software supply chain Onley run the images that have gone through the appropriate channels that you have authorized to run on the most secure container engine in the >>industry. >>Lastly, I want to quickly touch on scale. Today. Cluster sprawl is a very real thing. There are test clusters, staging clusters and, of course, production clusters. There's also different availability zones, different business units and so on. There's clusters everywhere. These clusters are also running all over the place. We have customers running Doc Enterprise on premise there, embracing public cloud and not just one cloud that might also have some bare metal. So cloud sprawl is also a very real thing. All these clusters on all these clouds is a maintenance and observe ability. Nightmare. This is a huge friction point to scaling Dr Price. Container Cloud solves these issues, lets you scale quicker and more easily. Little recap. What's new. We've added multi cluster management. Deploy and attach all your clusters wherever they are. Multi cloud, including public private and bare metal. Deploy your clusters to any infra self service cluster creation. No more I T. Tickets to get resources. Incredible speed. Automated Full stack Lifecycle management, including Dr Enterprise Container, cloud itself as a service from the in for up centralized observe ability with a single pane of glass for your clusters, their health, your APs and most importantly to our existing doc enterprise customers. You can, of course, add your existing D clusters to Dr Enterprise Container Cloud and start leveraging the many benefits it offers immediately. So that's it. Thank you so much for attending today's keynote. This was very much just a high level introduction to our exciting release. There is so much more to learn about and try out. I hope you are as excited as I am to get started today with Doc Enterprise. Continue, Cloud, please attend the tutorial tracks up Next is Miska, with the world's most popular Kubernetes E Lens. Thanks again, and I hope you enjoy the rest of our conference.

>>Hi, Oleg. So great of you to join us today. I'm really looking forward to our session. Eso Let's get started. So if I can get you to give a quick intro to yourself and then if you can share with us what you're going to be discussing today >>Hi, Jake. In my name is Oleg Elbow. I'm a product architect and the Doctor Enterprise Container Cloud team. Uh, today I'm going to talk about running kubernetes on bare metal with a container cloud. My goal is going to tell you about this exciting feature and why we think it's important and what we actually did to make it possible. >>Brilliant. Thank you very much. So let's get started. Eso from my understanding kubernetes clusters are typically run in virtual machines in clouds. So, for example, public cloud AWS or private cloud maybe open staff based or VM ware V sphere. So why why would you go off and run it on their mettle? >>Well, uh, the Doctor Enterprise container cloud already can run Coburn eighties in the cloud, as you know, and the idea behind the container clouds to enable us to manage multiple doctor enterprise clusters. But we want to bring innovation to kubernetes. And instead of spending a lot of resources on the hyper visor and virtual machines, we just go all in for kubernetes directly environmental. >>Fantastic. So it sounds like you're suggesting then to run kubernetes directly on their mettle. >>That's correct. >>Fantastic and without a hyper visor layer. >>Yes, we all know the reasons to run kubernetes and virtual machines it's in The first place is mutual mutual isolation off workloads, but virtualization. It comes with the performance, heat and additional complexity. Uh, another. And when Iran coordinated the director on the hardware, it's a perfect opportunity for developers. They can see performance boost up to 30% for certain container workloads. Uh, this is because the virtualization layer adds a lot off overhead, and even with things like enhanced placement awareness technologies like Numa or processor opinion, it's it's still another head. By skipping over the virtualization, we just remove this overhead and gained this boost. >>Excellent, though it sounds like 30% performance boost very appealing. Are there any other value points or positive points that you can pull out? >>Yes, Besides, the hyper visor over had virtual machines. They also have some static resource footprint. They take up the memory and CPU cycles and overall reintroduces the density of containers per host. Without virtual machines, you can run upto 16% more containers on the same host. >>Excellent. Really great numbers there. >>One more thing to point out directly. Use environmental makes it easier to use a special purpose hardware like graphic processors or virtual no virtual network functions for don't work interfaces or the field programmable gate arrays for custom circuits, Uh, and you can share them between containers more efficiently. >>Excellent. I mean, there's some really great value points you pulled out there. So 30% performance boost, 60% density boost on it could go off and support specialized hardware a lot easier. But let's talk about now. The applications. So what sort of applications do you think would benefit from this The most? >>Well, I'm thinking primarily high performance computations and deep learning will benefit, Uh, which is the more common than you might think of now they're artificial Intelligence is gripping into a lot off different applications. Uh, it really depends on memory capacity and performance, and they also use a special devices like F P G s for custom circuits widely sold. All of it is applicable to the machine learning. Really? >>And I mean, that whole ai piece is I mean, really exciting. And we're seeing this become more commonplace across a whole host of sectors. So you're telcos, farmers, banking, etcetera. And not just I t today. >>Yeah, that's indeed very exciting. Uh, but creating communities closer environmental, unfortunately, is not very easy. >>Hope so it sounds like there may be some challenges or complexities around it. Ondas this, I guess. The reason why there's not many products then out there today for kubernetes on their metal on baby I like. Could you talk to us then about some of the challenges that this might entail? >>Well, there are quite a few challenges first, and for most, there is no one way to manage governmental infrastructures Nowadays. Many vendors have their solutions that are not always compatible with each other and not necessarily cover all aspects off this. Um So we've worked an open source project called metal cube metal cooped and integrated it into the doctor Enterprise Container Cloud To do this unified bar middle management for us. >>And you mentioned it I hear you say is that open source? >>There is no project is open source. We had a lot of our special sauce to it. Um, what it does, Basically, it enables us to manage the hardware servers just like a cloud server Instances. >>And could you go? I mean, that's very interesting, but could you go into a bit more detail and specifically What do you mean? As cloud instances, >>of course they can. Generally, it means to manage them through some sort of a p I or programming interface. Uh, this interface has to cover all aspects off the several life cycle, like hardware configuration, operating system management network configuration storage configuration, Uh, with help off Metal cube. We extend the carbonated C p i to enable it to manage bare metal hosts. And aled these suspects off its life cycle. The mental que project that's uses open stack. Ironic on. Did it drops it in the Cuban. It s a P I. And ironic does all the heavy lifting off provisioned. It does it in a very cloud native way. Uh, it configures service using cloud they need, which is very familiar to anyone who deals with the cloud and the power is managed transparently through the i p my protocol on. But it does a lot to hide the differences between different hardware hosts from the user and in the Doctor Enterprise Container Cloud. We made everything so the user doesn't really feel the difference between bare metal server and cloud VM. >>So, Oleg, are you saying that you can actually take a machine that's turned off and turn it on using the commands? >>That's correct. That's the I. P M I. R Intelligent platform management interface. Uh, it gives you an ability to interact directly with the hardware. You can manager monitor things like power, consumption, temperature, voltage and so on. But what we use it for is to manage the food source and the actual power state of the server. So we have a group of service that are available and we can turn them on. And when we need them, just if we were spinning the VM >>Excellent. So that's how you get around the fact that while aled cloud the ends of the same, the hardware is all different. But I would assume you would have different server configurations in one environment So how would you get around that? >>Uh, yeah, that Zatz. Excellent questions. So some elements of the berm mental management the FBI that we developed, they are specifically to enable operators toe handle wider range of hardware configurations. For example, we make it possible to consider multiple network interfaces on the host. We support flexible partitioning off hard disks and other storage devices. We also make it possible thio boot remote live using the unified extended firmware interface for modern systems. Or just good old bias for for the legacy ones. >>Excellent. So yeah, thanks. Thanks for sharing that that. Now let's take a look at the rest of the infrastructure and eggs. So what about things like networking and storage house that managed >>Oh, Jakey, that's some important details. So from the networking standpoint, the most important thing for kubernetes is load balancing. We use some proven open source technologies such a Zengin ICS and met a little bit to handle. Handle that for us and for the storage. That's ah, a bit more tricky part. There are a lot off different stories. Solutions out. There s o. We decided to go with self and ah cooperator for self self is very much your and stable distributed stories system. It has incredible scalability. We actually run. Uh, pretty big clusters in production with chef and rock makes the life cycle management for self very robust and cloud native with health shaking and self correction. That kind of stuff. So any kubernetes cluster that Dr Underprice Container Cloud provision for environmental Potentially. You can have the self cluster installed self installed in this cluster and provide stories that is accessible from any node in the cluster to any port in the cluster. So that's, uh, called Native Storage components. Native storage. >>Wonderful. But would that then mean that you'd have to have additional hardware so mawr hardware for the storage cluster, then? >>Not at all. Actually, we use Converse storage architecture in the current price container cloud and the workloads and self. They share the same machines and actually managed by the same kubernetes cluster A. Some point in the future, we plan to add more fully, even more flexibility to this, uh, self configuration and enable is share self, where all communities cluster will use a single single self back, and that's that's not the way for us to optimize our very basically. >>Excellent. So thanks for covering the infrastructure part. What would be good is if we can get an understanding them for that kind of look and feel, then for the operators and the users of the system. So what can they say? >>Yeah, the case. We know Doc Enterprise Container Cloud provides a web based user interface that is, uh, but enables to manage clusters. And the bare metal management actually is integrated into this interface and provides provides very smooth user experience. A zone operator, you need to add or enrolled governmental hosts pretty much the same way you add cloud credentials for any other for any other providers for any other platforms. >>Excellent. I mean, Oleg, it sounds really interesting. Would you be able to share some kind of demo with us? It be great to see this in action. Of >>course. Let's let's see what we have here. So, >>uh, thank you. >>Uh, so, first of all, you take a bunch of governmental service and you prepare them, connect and connect them to the network is described in the dogs and bootstrap container cloud on top of these, uh, three of these bare metal servers. Uh, once you put through, you have the container cloud up and running. You log into the u I. Let's start here. And, uh, I'm using the generic operator user for now. Its's possible to integrate it with your in the entity system with the customer and the entity system and get real users there. Mhm. So first of all, let's create a project. It will hold all off our clusters. And once we created it, just switched to it. And the first step for an operator is to add some burr metal hosts of the project. As you see it empty, uh, toe at the berm. It'll host. You just need a few parameters. Uh, name that will allow you to identify the server later. Then it's, ah, user name and password to access the IBM. My controls off the server next on, and it's very important. It's the hardware address off the first Internet port. It will be used to remotely boot the server over network. Uh, finally, that Z the i p address off the i p m i n point and last, but not the least. It's the bucket, uh, toe Assign the governmental host to. It's a label that is assigned to it. And, uh, right now we offer just three default labels or buckets. It's, ah, manager, manager, hosts, worker hosts and storage hosts. And depending on the hardware configuration of the server, you assign it to one of these three groups. You will see how it's used later in the phone, so note that least six servers are required to deploy managed kubernetes cluster. Just as for for the cloud providers. Um, there is some information available now about the service is the result of inspection. By the way, you can look it up. Now we move. Want to create a cluster, so you need to provide the name for the cluster. Select the release off Dr Enterprise Engine and next next step is for provider specific information. You need to specify the address of the Class three guy and point here, and the range of feathers is for services that will be installed in the cluster. The user war close um kubernetes Network parameter school be changed as well, but the defaults are usually okay. Now you can enable or disable stack light the monitoring system for the Burnett's cluster and provide some parameters to eat custom parameters. Uh, finally you click create to create the cluster. It's an empty cluster that we need to add some machines to. So we need a least three manager notes. The form is very simple. You just select the roll off the community snowed. It's either manager of worker Onda. You need to select this label bucket from which the environmental hospital we picked. We go with the manager label for manager notes and work your label for the workers. Uh, while question is deploying, let's check out some machine information. The storage data here, the names off the disks are taken from the environmental host Harbor inspection data that we checked before. Now we wait for servers to be deployed. Uh, it includes ah, operating system, and the government is itself. So uh, yeah, that's that's our That's our you user interface. Um, if operators need to, they can actually use Dr Enterprise Container Container cloud FBI for some more sophisticated, sophisticated configurations or to integrate with an external system, for example, configuration database. Uh, all the burr mental tasks they just can be executed through the carbonated C. P. I and by changing the custom resources customer sources describing the burr mental notes and objects >>Mhm, brilliant. Well, thank you for bringing that life. It's always good. Thio See it in action. I guess from my understanding, it looks like the operators can use the same tools as develops or developers but for managing their infrastructure, then >>yes, Exactly. For example, if you're develops and you use lands, uh, to monitor and manage your cluster, uh, the governmental resources are just another set of custom resources for you. Uh, it is possible to visualize and configure them through lands or any other developer to for kubernetes. >>Excellent. So from what I can see, that really could bridge the gap, then between infrastructure operators on develops and developer teams. Which is which is a big thing? >>Yes, that's that's Ah, one of our aspirations is to unify the user experience because we've seen a lot of these situations when infrastructure is operated by one set of tools and the container platform uses agnostic off it end users and offers completely different set of tools. So as a develops, you have to be proficient in both, and that's not very sustainable for some developers. Team James. >>Sure. Okay, well, thanks for covering that. That's great. E mean, there's obviously other container platforms out there in the market today. It would be great if you could explain only one of some of the differences there and in how Dr Enterprise Container Cloud approaches bare metal. >>Yeah, that's that's a That's an excellent question, Jake. Thank you. So, uh, in container cloud in the container Cloud Burr Mental management Unlike another container platforms, Burr metal management is highly and is tightly integrated in the in the product. It's integrated on the U and the A p I, and on the back and implementation level. Uh, other platforms typically rely on the user to provision in the ber metal hosts before they can deploy kubernetes on it. Uh, this leaves the operating system management hardware configuration hardware management mostly with dedicated infrastructure greater steam. Uh, Dr Enterprise Container Cloud might help to reduce this burden and this infrastructure management costs by just automated and effectively removing the part of responsibility from the infrastructure operators. And that's because container cloud on bare metal is essentially full stack solution. It includes the hardware configuration covers, operating system lifecycle management, especially, especially the security updates or C e updates. Uh, right now, at this point, the only out of the box operating system that we support is you, Bhutto. We're looking to expand this, and, as you know, the doctor Enterprise engine. It makes it possible to run kubernetes on many different platforms, including even Windows. And we plan to leverage this flexibility in the doctor enterprise container cloud full extent to expand this range of operating systems that we support. >>Excellent. Well, Oleg, we're running out of time. Unfortunately, I mean, I've thoroughly enjoyed our conversation today. You've pulled out some excellent points you talked about potentially up to a 30% performance boost up to 60% density boost. Um, you've also talked about how it can help with specialized hardware and make this a lot easier. Um, we also talked about some of the challenges that you could solve, obviously, by using docker enterprise container clouds such as persistent storage and load balancing. There's obviously a lot here, but thank you so much for joining us today. It's been fantastic. And I hope that we've given some food for thoughts to go out and try and deployed kubernetes on Ben. It'll so thanks. So leg >>Thank you for coming. BJ Kim

>>this session will be reviewing the power benefits of implementing a secure software supply chain and how we can gain a cloud like experience with flexibility, speed and security off modern software delivery. Hi, I'm Matt Bentley, and I run our technical pre sales team here. Um Iran. Tous I spent the last six years working with customers on their container ization journey. One thing almost every one of my customers is focused on how they can leverage the speed and agility benefits of contain arising their applications while continuing to apply the same security controls. One of the most important things to remember is that we are all doing this for one reason, and that is for our applications. So now let's take a look at how we could provide flexibility all layers of the stack from the infrastructure on up to the application layer. When building a secure supply chain for container focus platforms, I generally see two different mindsets in terms of where the responsibilities lie between the developers of the applications and the operations teams who run the middleware platforms. Most organizations are looking to build a secure yet robust service that fits the organization's goals around how modern applications are built and delivered. Yeah. First, let's take a look at the developer or application team approach. This approach follows Mawr of the Dev ops philosophy, where a developer and application teams are the owners of their applications. From the development through their life cycle, all the way to production. I would refer this more of a self service model of application, delivery and promotion when deployed to a container platform. This is fairly common organizations where full stack responsibilities have been delegated to the application teams, even in organizations were full stack ownership doesn't exist. I see the self service application deployment model work very well in lab development or non production environments. This allows teams to experiment with newer technologies, which is one of the most effective benefits of utilizing containers and other organizations. There's a strong separation between responsibilities for developers and I T operations. This is often do the complex nature of controlled processes related to the compliance and regulatory needs. Developers are responsible for their application development. This can either include doctorate the development layer or b'more traditional throw it over the wall approach to application development. There's also quite a common experience around building a center of excellence with this approach, where we can take container platforms and be delivered as a service to other consumers inside of the I T organization. This is fairly prescriptive, in the manner of which application teams would consume it. When examining the two approaches, there are pros and cons to each process. Controls and appliance are often seen as inhibitors to speak. Self service creation, starting with the infrastructure layer, leads to inconsistency, security and control concerns, which leads to compliance issues. While self service is great without visibility into the utilization and optimization of those environments, it continues the cycles of inefficient resource utilization and the true infrastructure is a code. Experience requires Dev ops related coding skills that teams often have in pockets but maybe aren't ingrained in the company culture. Luckily for us, there is a middle ground for all of this Doc Enterprise Container Cloud provides the foundation for the cloud like experience on any infrastructure without all of the out of the box security and controls that are professional services Team and your operations team spend their time designing and implementing. This removes much of the additional work and worry Run, ensuring that your clusters and experiences are consistent while maintaining the ideal self service model, no matter if it is a full stack ownership or easing the needs of I T operations. We're also bringing the most natural kubernetes experience today with winds to allow for multi cluster visibility that is both developer and operator friendly. Let's provides immediate feedback for the health of your applications. Observe ability for your clusters. Fast context, switching between environments and allowing you to choose the best in tool for the task at hand. Whether is three graphical user interface or command line interface driven. Combining the cloud like experience with the efficiencies of a secure supply chain that meet your needs brings you the best of both worlds. You get Dave off speed with all the security controls to meet the regulations your business lives by. We're talking about more frequent deployments. Faster time to recover from application issues and better code quality, as you can see from our clusters we have worked with were able to tie these processes back to real cost savings, riel efficiency and faster adoption. This all adds up to delivering business value to end users in the overall perceived value. Now let's look at see how we're able to actually build a secure supply chain. Help deliver these sorts of initiatives in our example. Secure Supply chain. We're utilizing doctor desktop to help with consistency of developer experience. Get hub for our source Control Jenkins for a C A C D. Tooling the doctor trusted registry for our secure container registry in the universal control playing to provide us with our secure container run time with kubernetes and swarm. Providing a consistent experience no matter where are clusters are deployed. You work with our teams of developers and operators to design a system that provides a fast, consistent and secure experience for my developers that works for any application. Brownfield or Greenfield monolith or micro service on boarding teams could be simplified with integrations into enterprise authentication services. Calls to get help repositories. Jenkins Access and Jobs, Universal Control Plan and Dr Trusted registry teams and organizations. Cooper down his name space with access control, creating doctor trusted registry named spaces with access control, image scanning and promotion policies. So now let's take a look and see what it looks like from the C I c D process, including Jenkins. So let's start with Dr Desktop from the doctor desktop standpoint, what should be utilizing visual studio code and Dr Desktop to provide a consistent developer experience. So no matter if we have one developer or 100 we're gonna be able to walk through the consistent process through docker container utilization at the development layer. Once we've made our changes to our code will be able to check those into our source code repository in this case, abusing Get up. Then, when Jenkins picks up, it will check out that code from our source code repository, build our doctor containers, test the application that will build the image, and then it will take the image and push it toward doctor trusted registry. From there, we can scan the image and then make sure it doesn't have any vulnerabilities. Then we consign them. So once we signed our images, we've deployed our application to Dev. We can actually test their application deployed in our real environment. Jenkins will then test the deployed application, and if all tests show that is good, will promote the r R Dr and Mr Production. So now let's look at the process, beginning from the developer interaction. First of all, let's take a look at our application as is deployed today. Here, we can see that we have a change that we want to make on our application. So marketing Team says we need to change containerized injure next to something more Miranda's branded. So let's take a look at visual studio coat, which will be using for I D to change our application. So here's our application. We have our code loaded, and we're gonna be able to use Dr Desktop on our local environment with our doctor desktop plug in for visual studio code to be able to build our application inside of doctor without needing to run any command line. Specific tools here is our code will be able to interact with docker, make our changes, see it >>live and be able to quickly see if our changes actually made the impact that we're expecting our application. Let's find our updated tiles for application and let's go and change that to our Miranda sized into next. Instead of containerized in genetics, so will change in the title and on the front page of the application, so that we save. That changed our application. We can actually take a look at our code here in V s code. >>And as simple as this, we can right click on the docker file and build our application. We give it a name for our Docker image and V s code will take care of the automatic building of our application. So now we have a docker image that has everything we need in our application inside of that image. So here we can actually just right click on the image tag that we just created and do run this winter, actively run the container for us and then what's our containers running? We could just right click and open it up in a browser. So here we can see the change to our application as it exists live. So once we can actually verify that our applications working as expected, weaken, stop our container. And then from here, we can actually make that change live by pushing it to our source code repository. So here we're going to go ahead and make a commit message to say that we updated to our Mantis branding. We will commit that change and then we'll push it to our source code repository again. In this case we're using get Hub to be able to use our source code repository. So here in V s code will have that pushed here to our source code repository. And then we'll move on to our next environment, which is Jenkins. Jenkins is gonna be picking up those changes for our application, and it checked it out from our source code repository. So get Hub Notifies Jenkins. That there is a change checks out. The code builds our doctor image using the doctor file. So we're getting a consistent experience between the local development environment on our desktop and then and Jenkins or actually building our application, doing our tests, pushing in toward doctor trusted registry, scanning it and signing our image. And our doctor trusted registry, then 2.4 development environment. >>So let's actually take a look at that development environment as it's been deployed. So here we can see that our title has been updated on our application so we can verify that looks good and development. If we jump back here to Jenkins, will see that Jenkins go >>ahead and runs our integration tests for a development environment. Everything worked as expected, so it promoted that image for production repository and our doctor trusted registry. Where then we're going to also sign that image. So we're signing that. Yes, we have signed off that has made it through our integration tests, and it's deployed to production. So here in Jenkins, we could take a look at our deployed production environment where our application is live in production. We've made a change automated and very secure manner. >>So now let's take a look at our doctor trusted registry where we can see our game Space for application are simple in genetics repository. From here we will be able to see information about our application image that we've pushed into the registry, such as Thean Midge signature when it was pushed by who and then we'll also be able to see the scan results of our image. In this case, we can actually see that there are vulnerabilities for our image and we'll actually take a look at that. Dr Trusted registry does binary level scanning, so we get detailed information about our individual image layers. From here, these image layers give us details about where the vulnerabilities were located and what those vulnerabilities actually are. So if we click on the vulnerability, we can see specific information about that vulnerability to give us details around the severity and more information about what, exactly is vulnerable inside of our container. One of the challenges that you often face around vulnerabilities is how, exactly we would remediate that and secure supply chain. So let's take a look at that and the example that we were looking at the vulnerability is actually in the base layer of our image. In order to pull in a new base layer of our image, we need to actually find the source of that and updated. One of the ways that we can help secure that is a part of the supply chain is to actually take a look at where we get our base layers of our images. Dr. Help really >>provides a great source of content to start from, but opening up docker help within your organization opens up all sorts of security concerns around the origins of that content. Not all images are made equal when it comes to the security of those images. The official images from Docker, However, curated by docker, open source projects and other vendors, one of the most important use cases is around how you get base images into your environment. It is much easier to consume the base operating system layer images than building your own and also trying to maintain them instead of just blindly trusting the content from doctor. How we could take a set >>of content that we find useful, such as those base image layers or content from vendors, and pull that into our own Dr trusted registry using our rearing feature. Once the images have been mirrored into a staging area of our DACA trusted registry, we can then scan them to ensure that the images meet our security requirements and then, based off the scan result, promote the image toe a public repository where we can actually sign the images and make them available to our internal consumers to meet their needs. This allows us to provide a set of curated content that we know a secure and controlled within our environment. So from here we confined our updated doctor image in our doctor trust registry, where we can see that the vulnerabilities have been resolved from a developers point of view, that's about a smooth process gets. Now let's take a look at how we could provide that secure content for developers and our own Dr Trusted registry. So in this case, we're taking a look at our Alpine image that we've mirrored into our doctor trusted registry. Here we're looking at the staging area where the images get temporarily pulled because we have to pull them in order to actually be able to scan them. So here we set up nearing and we can quickly turn it on by making active. Then we can see that our image mirroring will pull our content from Dr Hub and then make it available in our doctor trusted registry in an automatic fashion. So from here, we can actually take a look at the promotions to be able to see how exactly we promote our images. In this case, we created a promotion policy within docker trusted registry that makes it so. That content gets promoted to a public repository for internal users to consume based off of the vulnerabilities that are found or not found inside of the docker image. So are actually users. How they would consume this content is by taking a look at the public to them official images that we've made available here again, Looking at our Alpine image, we can take a look at the tags that exist. We could see that we have our content that has been made available, so we've pulled in all sorts of content from Dr Hub. In this case, we have even pulled in the multi architectural images, which we can scan due to the binary level nature of our scanning solution. Now let's take a look at Len's. Lens provides capabilities to be able to give developers a quick, opinionated view that focuses around how they would want to view, manage and inspect applications to point to a Cooper Days cluster. Lindsay integrates natively out of the box with universal control playing clam bundles so you're automatically generated. Tell certificates from UCP. Just work inside our organization. We want to give our developers the ability to see their applications and a very easy to view manner. So in this case, let's actually filter down to the application that we just deployed to our development environment. Here we can see the pot for application and we click on that. We get instant, detailed feedback about the components and information that this pot is utilizing. We can also see here in Linz that it gives us the ability to quickly switch context between different clusters that we have access to. With that, we also have capabilities to be able to quickly deploy other types of components. One of those is helm charts. Helm charts are a great way to package of applications, especially those that may be more complex to make it much simpler to be able to consume inversion our applications. In this case, let's take a look at the application that we just built and deployed. This case are simple in genetics. Application has been bundled up as a helm chart and has made available through lens here. We can just click on that description of our application to be able to see more information about the helm chart so we can publish whatever information may be relevant about our application, and through one click, we can install our helm chart here. It will show us the actual details of the home charts. So before we install it, we can actually look at those individual components. So in this case, we could see that's created ingress rule. And then it's well, tell kubernetes how to create the specific components of our application. We just have to pick a name space to to employ it, too. And in this case, we're actually going to do a quick test here because in this case, we're trying to deploy the application from Dr Hub in our universal Control plane. We've turned on Dr Content Trust Policy Enforcement. So this is actually gonna fail to deploy because we're trying to deploy application from Dr Hub. The image hasn't been properly signed in our environment. So the doctor can to trust policy enforcement prevents us from deploying our doctor image from Dr Hub. In this case, we have to go through our approved process through our secure supply chain to be able to ensure that we know our image came from, and that meets our quality standards. So if we comment out the doctor Hub repository and comment in our doctor trusted registry repository and click install, it will then install the helm chart with our doctor image being pulled from our GTR, which then has a proper signature, we can see that our application has been successfully deployed through our home chart releases view. From here, we can see that simple in genetics application, and in this case we'll get details around the actual deploy and help chart. The nice thing is that Linds provides us this capability here with home. To be able to see all the components that make up our application from this view is giving us that single pane of glass into that specific application so that we know all the components that is created inside of kubernetes. There are specific details that can help us access the applications, such as that ingress world that we just talked about gives us the details of that. But it also gives us the resource is such as the service, the deployment in ingress that has been created within kubernetes to be able to actually have the application exist. So to recap, we've covered how we can offer all the benefits of a cloud like experience and offer flexibility around dev ups and operations controlled processes through the use of a secure supply chain, allowing our developers to spend more time developing and our operators mawr time designing systems that meet our security and compliance concerns

>>from around the globe. It's the Cube with digital coverage of Miranda's launchpad 2020 brought to you by more antis. >>Hi, I'm stupid man. And this is the cubes coverage of Miran Tous Launchpad 2020. Happy to welcome to the program First time guest William Do places. He's the head of customer success in operations with Miran Tous William. Thanks so much for joining us, >>Steve. Thanks for two. Thanks for having me. >>Yeah, why don't we start with a little bit? You know, customer success operations. Tell us what that's entail, What's what's under your purview, Right? >>So is everything basically, you know, post sales, right? So after a customer has portions, their their subscription, we basically take it from there Going forward, you know, looking after the relationship with the customer, ensure they you know, the whole, you know, subscription fulfillment element off it. Whether that is just bored with that is to cut the relationship management from a post sales perspective and so on, so forth. So that is basically into end from the point off purchase to the renewal face. Would would would fall with any supporting operations. >>Well, that's such an important piece of the whole cloud conversation. Of course, people, you know, we talked for such a long time cap ex op X. We talk about descriptions and manage services. Of course, has been a riel. You know, growth segment of the market place. Love to hear a little bit, you know, What are you hearing from your customers? And, you know, give us the lay of the land As to the various options that that that Miranda is offering today and we'll get into any of the new pieces also. >>Yeah. So the the the options that we're making available for our customers primary called Prod Care, which is a 24 7 mission critical support subscription. Andi Ops Care, which is a fully managed service offering. Um, what we hear from our customers is is, you know, the the the notion of having a development environment and a production environment with different, you know, sls and entitlements and so on. You know that that that notion is disappearing because your divots chain or pipeline is all connected. So you could just think for yourself. If you have a group of developers like 50 or 100 or 1000 developers that are basically standing there still, because they cannot push code because there's a problem or a new issue on the development cloud. But the development cloud is not. Beings is not seen or is treated as a mission critical platform. You know, those developers are standing date stole, so that is a very expensive problem for a customer at that point in time, so that the whole chain, the whole pipeline that makes part off your your develop cycle, should be seen as one entity. And that's what we've seen in the market at the moment that we're realizing with a large customers that are really embracing the kind of the approach to modern applications. Andi. This is why we're making these options available. Thio, our Doctor Enterprise customers We've been running with them for quite a while on the on the Miranda's cloud platform, which is our Infrastructures service offering on. We've had some great success with that, and we now in a position to make that available to our customers. So it's really providing a customer that true enterprise mission critical regardless of time off they the day of the week availability off support whether that is a my question or whether that is really an outage or a failure. You know, you know, you've got that safety net that is that is online and available for you. Thio to sort Whatever problem you have about, you know, that is from the support perspective, you know. And if we go over into the manage service offering we have for on up Skate that is a really hardened Eitel based, um infrastructure or platform as a service offering that we provide eso. We've had some great success. Like I said on the on the Miranda's cloud platform Peace. And we're now making that available for Doc Enterprise customers as well. So that is taking the whole the whole chain through. We look after the the whole platform for the customer and allow the customer to get on with what is important to them. You know, how do they develop their applications? You know, optimize that for their business instead, off spending their times and keep spending their time on keeping the lights on, so to speak, you know? So we take care of all of that. They have that responsibility over to us on DWI. We manage that as our own and we basically could become an extension of their business. So we have a fully integrated into the environment, the whole logging and not monitoring piece we take over the whole life cycle. Management off the environment. We take over, we do the whole change Management piece Incident Management Incident Management piece on. This whole process is truly transparent to the customer. At no point are they, you know, in the dark what's going on where we're going and we have the and the whole pieces wrapped around Bio customer success Manager which is bringing this whole sense off ownership Onda priority. That customer, you've got a single point of contact that is your business partner and that the only piece, the only metric that that individuals measured on is the success off that customer with our our product. So that in a nutshell, at a very high level what these are. But these offerings are all about >>well, we all know these days how important it is toe, you know, make your developers productive. It's funny listening to you, I think back to the Times where you talked about making sure that it's mission critical environment You know, years ago it was like, Oh, well, the developer just gets whatever old hardware we have, and they do it on their own. Now, of course, you know you want Dev in production toe have a very similar environment. And as you said, those manage services offering and be, you know, so important because we want to be able to shift left, let my platform let my vendors take care of some of the things that's gonna be able to enable me to build my new applications toe, respond to the business and do. In fact, I don't want my developers getting bogged down. So do you have any, You know, what are some of the successes there? How do your customers measure that? They Hey, I'm getting great value for going to manage service. Obviously, you know, you talked about that, That technical manager that helps them there. Anybody that's used, you know, enterprise offerings. There's certain times where it's like, Hey, I use it a lot. Other times it's it's just nice to be there, but, you know, why do you bring us in a little bit? Some of the customers, obviously anonymous. You need Teoh you know, how do they say, You know, this is phenomenal value for my business. >>Yes, it's all. It's all about the focus, right? So you're the customer. 100% focus on what is like I said, important to them, they are not being distracted at any point for, you know, on spending time on infrastructure related or platform related issues they purely focused on. Like I said, that is, that is important to their business. Andi, The successes that we see from that it is, is that we have this integration into into our customers like a seamless approach. We work with them is a true, transparent approach to work with our customers. There's a there's an active dialogue off what they developers want to see from the environment, what the customers want to see from from from the environment, what is working well, what we need to optimize. And that is really seeing ah, really good a approach from from from us and we're seeing some some great successes in it. But it all comes down to the customer is focusing on one thing, and that is on what is important to them on. But is there business instead off. You know, like you said, focusing on the stuff that shoot me, that that should be shift left. >>Yeah. And will, um, is there anything that really stands out when you talk about that? The monitoring that you in the reporting that you give the customers Is it all self serve? You know, how did they set that up and make sure that I'm getting valuable data. That's what what my company needs. >>Yes. So that is where your custom success manager comes in is really how to customize that approach to what fit for the customers. So we've got it in the background, very much automated, but we do the tweaks Thio customize it for for the customer that makes sense for them. Some customers want to see very granular details. Other customers just want a glance over it and look at the the high level metrics what they find important. So it is finding that balance and and understanding what your customer find important, and then put that in a way that makes sense for them Now. That might sound might sound kind of obvious, but it's more difficult than you think to put data from the customer That makes sense to them, uh, in their in their context. And then, you know, be in a position where you can take the information that you receive and give your customer the the runway to plan their the application. You know, where are they trending? So be able. Dutilleux. Look. 3452 quarters 345 months to quarters ahead to say this is where you're going to be. If you continue down this path, we might need to look at shifting direction or shift workload around or at Resource is or or, you know, depending on the situation. But it's all about having that insight going forward, looking forward. Rather, um, instead off, you know, playing things by year end, looking, looking at the year. And now because then that ISS that is done and dusted, really. So it's all about what is coming down the line for us and then be able to to plan for it and have an educated conversation of with with with your customer where they want to go. >>You mentioned that part of this offering is making this available for the Docker Enterprise base. Uh, maybe, if you could explain a little bit as to you know, what's gonna be compelling for for those customers. You know what Laurentis is has built specifically for that base? >>Yeah. So, like I said, this is an offering we have available on our Miranda's cloud platform for quite a while. You've seen some great success from it. Um, we're making it now available for the Doctor Enterprise customers. So it is really a true platform as a service offering, um, on your infrastructure of choice, whether that is on prim or whether that is on public cloud, we don't really care. We'll work with customers whichever way it is. And yeah, Like I said, just give that true platform as a service experience for our customers, Onda allow them to to focus on what's important to them. >>Alright, let me let you have the final word. Will tell us what you want your customers to understand about Iran tous when they leave launchpad this year. >>Yeah, So the main thing the main theme that I want to leave with is is that you know, the the we've made significant progress over the last 62 229 months on the doc enterprise side on. We're now in a position where we're taking the next step in making these offerings available for our customers, and we're really for the customers. That's the handful of custom that we have already. My greater to these offerings with getting some really good feedback from them on it is really helping them just thio thio just to expedite. They they, you know, wherever they're gonna go, whatever they want to want to achieve the, you know, expedite, think goals on bond. It is really there to ensure that we provide a customer or customers a true, um, you know, mission critical feeling, uh, giving them the support they need when they needed at the priority or the severity or the intensity that they need as well as they provide them. The ability to to focus on what is important to them on board. Let us look after the infrastructure and platform for them. >>Well, well, okay. Congratulations on Although the work that the team's done and definitely look forward to hearing more in the future. >>Excellent. Thank you very much for your time. >>Be sure to check out all the tracks for Miranda's launchpad 2020 of course. Powered by Cuba 3. 65. Got the infrastructure. The developers Lots of good content. Both live and on demand. And I'm still minimum. Thank you for watching. Thank you.

>> Narrator: From theCUBE Studios and Palo Alto in Boston. Connecting with thought leaders all around the world. This is a CUBE conversation. >> Hey, welcome back everybody. Jeff Frick here with theCUBE. We're at our Palo Alto studio as kind of our on going leadership coverage of what's happening with the COVID crisis, and really looking out into our community to find experts who can provide tips and tricks, and some guidance as everyone is kind of charting these uncharted waters if you will. And we've got a great cube alarm in our database. He's a fantastic resourcer. We're excited to get him on. Share the information with you. We'd like to welcome once again, Darren Murph. He is the Head of Remote for GitLab. Darren, great to see you. >> Absolutely, great to be here. Thanks for having me. >> Absolutely, so thank you and. First off, we had you on earlier this year, back when things were normal, in kind of a regular review. Who knew that you would be at the center of the work-from-home universe just a few short months later. I mean, you've been doing this for ever. So it's kind of a wile old veteran of the work-from-home, or not even from home, just work from some place else. What are some top level things that you can share for people that have never experienced this before? >> Yeah, on the working front. If you're one of the people that are working from home, I think there's a couple of things you can do to help acclimate, make your world a little bit better. The first is to try to create some sort of separation between your work life and your personal life. Now if you have a home big enough that you can dedicate a workspace to being your office, that's going to help a lot. Help from a focus standpoint and just. You don't want those lines between work and life to blur too much, that's where isolation kicks in. That's where burnout kicks in. You want to do whatever you can to avoid. You got to remember, when you're not physically walking out of a office and disconnecting from work. You have to replicate that and recreate that. I actually recommend for people that used to have a commute and now they don't. I would actually black something in your calendar, whether that's cooking, cleaning, spending time with your family. Resting more, anything so that you ramp into your day very deliberately and ramp out of very deliberately. Now on the team leading front. I'm going to say it may feel a little counter intuitive, but the further your team is from you, the more distributed they are. The more you really need to let go and allow them to have mechanism for feeding back to you. Managers job in a remote setting switches from just being a pure director, you're actually being an unblocker. A really active listener. And for people who have gotten to a certain point in their career through command and control, this is going to feel very strange, jarring and counter intuitive, but we've seen it time and time again. You need to trust that your workers are in a new environment. You have to give them a mechanism feeding back to you to help them unblock whatever it is. >> You know that's funny, we had someone on as part of this the other day, talking about leaders need to change their objectives that they're managing to, from kind of activity based, to deliverals based. And it actually floored me that someone is still writing in a blog in 2020, that people have to change their management deliverables from activity to deliverables. And it was so funny, you know, you had Martin Mikos on, we had him on too. My favorite comment was, "It's so easy to fake it in the office and look busy, "but when you're at home all you have is your deliverable." so it really, it seems like there's kind of a forcing function to get people to pay attention to the things they should be managing to anyway. >> You said it, forcing functions. I talk about this all the time, but there are so many forcing functions in remote that help you do remote well. But not only just do remote well, just run your business well. Even if you plan on going back to office. On some level there's a lot of things you can do now to help pave the infrastructure to creating a better and more effective team. And as a manager, if you have it in a writing down. The metrics or expectations for your direct reports in the office, now's the time to do it. Subjectivity is allowed to flourish in the office. You can praise or promote people just kind of how much you like them or how easy they are to work with. That really has nothing to do with metrics and results. I've often been asked, "How do you know if "someone's been working remotely?" And my response is, how do you know if they were working in the office. If you can't clearly answer that in the office, then you're not going to be able to answer it remotely. So frankly, in these times a lot of the burden falls more on the manager to actually take a hard look at what they're clarifying to their team. And if the metrics aren't laid out. It's on the manager to lay that out. It's not the responsibility of the direct report to figure out how to prove their worth. The manager has to be very articulant about what that value looks like. >> Right, and not only do they have to be articulate about what the deliverables are and what their expectations are, but. You guys have a remote play book GitLab has published, which is terrific. People should go online, it's 38 pages of dense, dense, dense material. It's a terrific resource, it's a open source, you got to love the open source, eat those. But one of the slides that jumped out to me, and it's consistent with a lot of these conversations that we're having, is that your frequency of communications when people are not in the same room together. Has to go up dramatically, which is a little counter intuitive, but what I found even more interesting was the variety of types of communication. Not just you kind of standard meeting, or you standard status on a project, or maybe a little bit of a look forward to some strategic stuff. But you outlined a whole variety of types of communication. Objectives or methods, or feel if you will, to help people stay connected and to help kind keep this team building going forward. >> So here's the thing about communication. You've got to be intentional about it in a remote setting. And in fact, you need to have more intentionality across the board in a remote setting. And communications is just a very obvious. So for a lot of companies, they leave a lot of things to spontaneity Inter-personal relationships and communications are two of the biggest ones. Where you may not actually lay out a plan for how work is communicated about, or what opportunities you give people to chat about their weekends, or sports, or anything like that. You just kind of put them in the same building and then people just kind of figure it out. In a remote setting that's unwise. You're going to get a lot of chaos and disfunction when people don't know how to communicate and on what channel. So at GitLab we're very prescriptive that work communication happens in a GitLab issue or a merge request. And then informal communication happens through Zoom calls or Slack. We actually expired our Slack messages after 90 days, specifically to force people not to do work in Slack. We want the work to begin where it needs to end up, and in that case it's a very, it's a tool, GitLab, that's built for asynchronous communication. We want to continue to encourage that bias towards asynchronous communication. So yeah, we write down everything about how we want people to communicate and through what channels. And that may sound like a lot of rules, but actually it's very much appreciated by our global team. We have over 1200 people, in more that 65 countries. And they all just need to know where communication is going to happen. And our team is really cohesive and on the same page because we're articulant about that. >> So I want to double down on that. On 'A secret is peace', 'cause you brought this up, or you and Stu brought it up in your conversation with Stu, and Stu raised an interesting point, right. Unfortunately in the day of email and connected phones, and this and that, there has grown an expectation that used to be business, okay was, "I'll get back to you within 24 hours "if you leave me a voicemail." And lord knows what it was when we were still typing letters and memos, and sticking stuff in the yellow envelop with the string, right, as multiple days. But somehow that all got changed to, "I need to hear back form you now." And often it feels like, if your trying to have just some uninterrupted work time, to get something done. It's like, why is your lack of planning suddenly my emergency. And you talked about, you can't operate that on a global, asynchronous team because everyone's in different timezones. And just by rule, there are going to be a lot of people that are not awake when you need the answer to that question. But that you've developed a culture that that's okay, and that that is kind of the flow and the pacing which A, forces people to ask in advance, not immediately when you need it. But also gives people unfettered time to actually plan to do work versus plan to answer communications. I wonder if you can dig into how did that evolve and how do you enforce that when somebody comes in from the outside world. >> The real key to that is something that might not be immediately apparent to everyone. Which is, at GitLab we try to shift as much burden as we possibly can humans to documentation. And this even starts at onboarding, where to get onboarded at GitLab, you get an onboarding issue within GitLab, with over 200 check boxes of things to read and knowledge assessments to take. And humans are a part of it, but very minimal compared to what most companies would do. And the thing that you just outlined was, we're talking about asking questions. Or tapping someone on the shoulder to fill in a knowledge gap. But at GitLab we want to write everything down in a very formalized structured way. We try to work handbook first. So we need to document all of our processes, protocols and solutions. Basically everything that we've ever seen or done, needs to be documented in the handbook. So it's not that GitLab team members just magically need less information, it's just that instead of having to ask someone on our team, we go ask the handbook. We go consult the documentation. And the more rich that your documentation is, the less you have to bother other people, and the less you need to rely on synchronicity. So for us it all starts with operating handbook first. That allows our humans to reserve their cycles for doing truly creative things, not just answering your question for the thousandth time. >> Right, another thing you covered, which I really enjoyed was getting senior executives to work from home for an extended period of time. Now obviously, before COVID that would probably be a lot harder to do. Well now COVID has forced that. And I think to your point about that is, it really forces the empathy for someone who had no interest in working from home. Didn't like to work from home. Loves going to the office, has their routine. Been doing it for decades, to kind of wake up to A, you need to have more empathy for what this is all about. And B, what's it all about by actually doing it. So I wonder, kind of your take in the movement to more of a work from anywhere future. Now that all the senior executives have been thrown into this work from home situation. >> Look Jeff, you never want to waste a crisis. We can't wish away the crisis that's in front of us, but we can choose how we respond to it. And this does present an opportunity to lay ground work, to lay infrastructure, to build a more remote organization. And I have absolutely advocated for companies to get their leadership teams out of the office for a meaningful amount of time. A month, ideally a quarter. So that they actually understand what the remote life is. They actually have some of those communication gaps and challenges so they can document what's happening. And then help fix it. But to your point, executives love going to the office because they're on a different playing field to begin with. They usually have an executive assistant. Things are just. There's less friction in general. So it behooves them to just kind of keep charging in that direction, but now what we have is a situation where all of those executives are remote. And I'm seeing a lot of them say, "You know what, I'm seeing the myths that I've perpetrated "break down in front of me." And this is even in the most suboptimal time ever to go remote. This isn't remote work, this is crisis induced work from home. We're all dealing with social isolation. Our parents are also doubling as homeschool teachers. We have a lot going on. And even on top of all of that, I'm amazed at how adaptable the human society has been. In just adjusting to this and figuring it out on the fly. And I think the companies that take this opportunity, to ask themselves the right question, and build this into their ongoing talent and operational strategy, will actually come out stronger on the other side. >> Yeah, as you said. This is as challenging as it's ever been. There was no planning ahead, you're spouse or significant other's also working from home. And has the same Zoom schedule as you do, for some strange reason, right. The kids are home as you said, and your homeschooling them. And they also have to get on Zoom to do their classes. So it's really suboptimal. But as you said, it's a forcing function and people are going to learn. One of the other things in your handbook is the kind of definitions. It's not just work from home or work at the office, but there's actually a continuum and a spectrum. And as people are doing this for weeks and months. And behaviors turn into habits. People are not going to want to go back to sitting on 101 for two hours every morning to go work on a laptop in the office. It just doesn't make sense. So as you kind of look forward. How do you see the evolution. How are people taking baby steps, if you will. To incorporate more of this learning as we go forward. And incorporate into more of their regular, everyday procedures. >> I'm really optimistic about the future because what I see happening here is people are unlocking their imaginations. So once they've kind of stabilized, they're starting to realize, "Hey, I'm getting a lot more time with my family. "I'm spending a lot less on gas. "I just feel better as a person because I don't show up "to work everyday with road rage. "So how can I keep this going." And I genuinely think what's going to happen in four or five months, we're going to have millions of people collectively look at each other and they say, "The boss just called me back into the office "but I just did my job from home. "Even in suboptimal conditions. "I saw my family more, I exercised more. "I had more time to cook and clean. "How about no, I'm not going to go back to the office "as my default location." And I think what's going to happen is the 80, 20 rule is going to flip. Right now people work from home only for a special occasion, like the cable company's coming or something like that. Going forward it think the offices are going to be the special occasion. You're only going to commute to the office, or fly to the office when you have a large contingent of people coming in and you need to wine and dine them, or something like that. And the second order of this is, people that are only living in expensive cities because of their location. When their lease comes up for renewal, they're going to cast a glance at places like Wyoming and Idaho, and Ohio. Maybe even Vietnam and Cambodia, or foreign places. Because now you have them thinking of, "What could life look like if I decouple geography at work. "I still want to work really hard "and contribute this knowledge. "But I can go to a place with better air quality, "better schools, better opportunity to actually "invest in a smaller community, "where I can see real impact." And I think that's just going to have massive, massive societal impacts. People are really taking this time to consider how tightly their identity has been woven into work. Now that they're home and they've become something more than just whatever the office life has defined them as. I think that's really healthy. I think a lot of people may have intertwined those two things too tightly in the past. And now it's a forcing function to really ask yourself, you aren't just your work, you're more than your work. And what can that look like when you can do that job from anywhere. >> Right, right. And as you said, there's so many kind of secondary benefits in terms of traffic and infrastructure, and the environment and all kinds of things. And the other thing I think that's interesting what you said, 80, 20 I think that was pretty generous. I wouldn't give it a 20 percent. But if people, even in this hybrid steps, do more once a week, twice a week. Once every two weeks, right. The impact on the infrastructure and peoples lives is going to be huge. But I wanted to drill on something as we go into kind of this hybrid mode at some point in time. And you talked about, and I thought it was fascinating, about the norms and really coming out from a work from home first, or a work from anywhere first. Your very good at specifying anywhere doesn't mean home. Could be the library, could be the coffee shop. Could be an office, could be a WeWork. Could be wherever. Because if you talked about the new norms and the one I thought was really interesting, which probably impacts a lot of teams, is when some of the team's in the office and some of the team isn't. The typical move, right, is to have everyone in the office go into the conference room. We sit around one big screen. So you get like five people sitting around one table and you got a bunch of heads on Zoom. And you said, "You know, no. "Let's all be remote. So if we just be happen to be sitting at our desk. If we happen to be in the office, that's okay. But really normalize. And like we saw the movement from Cloud got to Cloud-e to Cloud first, why not Cloud. And then you know, kind of mobile and does it work in a mobile. No, no, no it has to. It's mobile first. Really the shift to not, can it be done at home, but tell me why it shouldn't be done at home, a really different kind of opening position as to how people deploy resources and think about staffing and assigning teams. It's like turning the whole thing upside down. >> Completely upside down. I think remote first to your point, is going to be the default going forward. I think we're just one or two quarters away from major CEO's sitting on the hot seat on CNBC, when it's their turn for quarterly earnings. And they're going to have to justify why they're spending what they spend on real estate. Is if your spending a billion dollars a year on real estate, you could easily deploy that to more people, more R&D. Once that question is asked in mass, that is when you're going to see the next phase of this. Where you really have to justify, even from a cost stand point, why are you spending so much? Why are you tying so much of your business results to geography. The thing about remote first is that it's not a us versus them. A lot of what we've learned at GitLab, and how we operate so efficiently. They work really well for remote teams, and they are remote first. But they would work just as well in an office. We attach a Google doc agenda to every single business meeting that we have, so that there's always an artifact. There's always a documented thread on what happened in a meeting. Now this would work just as well in a co-located meeting. Who wouldn't want to have a meeting where it's not just in one ear and out the other. You're going to give the time to the meeting, you might as well get something out of it. And so a lot of these remote forced. Remote first forcing functions, they do help remote teams work well. But I think it's especially important for hybrid teams. Offices aren't going to vanish overnight. A lot of these companies are going to have some part of their company return to the office, when travel restrictions are lifted. It think the key here is that its going to be a lot more fluent. You're never going to know on a day to day basis, who is coming into the office, and who is not. So you need to optimize for everyone being out of the office. And if they just so happen to be there, they just so happen to be there. >> Right, right. So before we. I want to get into one little nitty gritty subject, in terms of investment into the home office. You know, we're doing 100% remote interviews now on theCUBE, we used to go to pretty much. Probably 80% of our business was at events, or at peoples offices, or facilities. Now it's all dial-in. You talked a lot about people need to flex a little bit on enabling people to invest in the little bits and pieces of infrastructure for their home office, that they just don't have the same set ups. You're talking about multiple monitors, a comfortable chair, a good light. That there's a few things you can invest in, not tremendous amounts of money. But a couple of hundred bucks here and there, to make a big difference on the home work environment. And how people should think about making that investment into a big monitor that they don't see. It's not sitting at the desk in the office. >> 100%, look if you're coming from a co-located space, you're probably sitting in a cube that costs five, 10, maybe 20 thousand dollars put together. You might not notice that, but it's not cheap to build cubicles in a high rise. And if you go to your home and you have nothing set up, I would say it's on the people group to think really hard about being more lax and more lenient about spending policy. People need multiple monitors. You need a decent webcam, you need a decent microphone. You need a chair that isn't going to kill your back. You want to help people create healthy ergonomics. Sustainable workspaces in their home. This is the kind of thing that will inevitably impact productivity. You force someone to just be hunched over on their couch, in front of a 13 inch laptop. I mean, what kind of productivity do you really expect from that. That's not a great long term solution. I think the people group actually has a higher burden to bare all the way around. You know when it comes to making sure teams feel like teams and they have the atmosphere to connect on a meaningful level. It comes down to the people group, to not letting that just go to spontaneity. You want to have a happy hour virtually, you're going to have to put a calendar invite on peoples calendar. You're going to create topical channels in Slack for people to talk about things other than work. Someone's going to have to do that. They don't just happen by default. So, from hardware all the way to communication. The people group really needs to use this opportunity to think about, "Okay, what can we unlock in this new world." >> Right, I'm glad you said the people group and not the resources group because they're not coal, or steel, or a factory. >> No, if anything COVID has humanized this in a way, and I think it's actually a really big silver lining, where we're all now peering into each others homes. And it is glaringly obvious, that we're all humans first, colleagues second. And of course that always been the case, but there's something about a sterile or co-located work environment. You check a piece of you at the door. And you just kind of get down to business. Why is that, we have technology at out fingertips. We can be humans with each other. And that going to actually encourage more empathy. As we've seen at GitLab, more empathy leads to better business results. It leads to more meaningful connections. I mean, I have people, friends, located all over the world that I feel like I have a closer bond with. A closer, more intimate connection with that a lot of people I've met in office. To some degree you don't know who they really are. You don't know what they really love and what makes them tick. >> Right, right. All right Darren, so before I let you go and again thank you for the time, the conversation. I'm sure everyone is calling you up and I just love the open source ETHOS and the sharing. It's made such a huge impact on the technology world and second order impacts that a lot of people take advantage. Again, give us the place that people can go for the playbook, so they can come and leverage some of the resources. And again, thank you guys for publishing 'em. >> Absolutely, so we're an open source. We try to open source all of our learnings on remote. So go to allremote.info that will redirect you right into the All Remote section of GitLab handbook. All of which is open source. Right at the top you can download the remote playbook, which is PDF that we talked about. Download that, it takes you through all of our best information on getting started and thriving as a remote team. Just under that there's a lot of comprehensive guides on how we think about everything. And how we operate synchronously. How we handle meeting, and even hiring and compensation. allremote.info and of course you're welcome to reach out to me on Twitter, I'm @darrenmurph. >> All right, well thanks a lot Darren. And I find it somewhat ironic that you have a jetliner over your shoulder. Waiting for the lockdown and the quarantine to end so you can get back on the airplane. And we're looking forward to that day. >> Can't wait man, I miss, I miss the airplanes. I told someone the other day, I never thought I'd say I miss having a middle seat at the very back of the airplane, with someone reclined into my nose. But honestly, I can't wait. Take me anywhere. >> I think you'll be fighting people for that seat in another month or so. All right, thanks a lot, Darren. >> Absolutely, take care all. >> All right, he's Darren. I'm Jeff, you're watching theCUBE, from our Palo Altos Studios. Thanks for watching, we'll see you next time. (upbeat music)