>>Hey everyone. Welcome to this cube conversation. I'm your host, Lisa Martin Rajko same joins me now the chief product officer at elation. Raj. Great to have you on the cube. Welcome. >>It's great to be here, Lisa. And I've been a fan for a while and excited to have a chance to talk with you live. >>And we've got some exciting stuff to talk about elation in terms of the success in the enterprise market. I see more than 25% of the fortune 100 doing great. There is customers elation and snowflake. Before we get into your exciting news. Talk to me a little bit about the evolution of the partnership. >>Yeah, no, absolutely. So, you know, we've always been a, a close partner and integrator with snowflake and last year snowflake became an investor in elation and they participated in our series D round. And the thing I'm most excited about beyond that is we were announced in the snowflake summit back in June to be their data governance partner of the year for the second year running. And so we've always had a closer relationship with snowflake, both at the go to market level and at the product level. And you know, the stuff that we're about to talk about is a Testament to that. >>Absolutely. It is. So talk to us before we get into the announcement. What you're seeing in the market as organizations are really becoming much more serious about being data driven and building a data culture. What are you seeing with respect to enterprises as well as those smaller folks? >>Yeah, no, it, it, it's, it's a great question. I mean, you, you hear the T tropes data is the new oil data is like water it's essential. And we're seeing that very consistently across every customer, every segment, every geo that we, that we talk to, I, I think the challenges that organizations are seeing that are leading to the amazing growth that we've seen at elation are there's so much data. They don't know where it resides. You've got silos or islands of knowledge that exist across the, the enterprise. And they need a data intelligence platform to bring it all together, to help them make sense of it and ultimately build a data culture that, you know, it lets their employees make data driven decisions as opposed to relying on gut. And so those are some of the macro trends that we're seeing and with the migration of data to the cloud and in particular snowflake, it seemed like a huge opportunity for us to partner even more closely with, with snowflake. And we're, we're excited about the progress that we've seen with them thus far. >>All right, let's get right into it. So first of all, define a data culture and then talk to us about how elation and snowflake are helping organizations to really achieve that. >>Yeah. You know, it, it's interesting. The, the company vision that we have at elation is to empower a curious and rational world. And you know, what that really means is we want to deliver solutions that drive curiosity and drive rational behavior. So making, making decisions based on data and insights, as opposed to gut, or, you know, the, the highest paid, you know, person's opinion or what have you. And so delivering a data culture, building a data culture, which is something we hear from all the CDOs that we talk to is, Hey, elation, help us drive data literacy across the organization, provide that single source of reference. So if anybody has a question about, do we have data that answers this, or, you know, what kind of performance are we seeing in this product area? Give me a starting point for my data exploration journey. And that's really where elation and our data intelligence solutions kind of come into the play. >>So unpack elation cloud service for snowflake. Talk to us about what it is, why you're doing it, what the significance of this partnership and this solution is delivering. >>Absolutely. So the elation cloud service for snowflake is a brand new offering that we just brought to market. And the intent really was, you know, we've had massive success in the global 2000. You mentioned the, the progress that we've had with fortune 100 customers, we see the need for data, culture, and data literacy and governance in organizations, you know, that are massive global multinational enterprises all the way down to divisions of an organization, or even, you know, mid-market and SMB companies. And so we thought there was a huge opportunity to really drive data culture for those organizations that are adopting snowflake, but still need that data intelligence overlay across the, the data that's in the snowflake cloud. And so what we did is we launched the elation cloud service for snowflake as a free trial, and then, you know, low cost purchase solution that, you know, can be adopted for less than a hundred thousand dollars a year. >>Got it. So tar from a target market perspective that lower end of the market for, of course, you know, these days, Raj, as we talk about every company, regardless of size, regardless of industry and location has to be a data company getting there and, and, and, and really defining and going on a journey to get there is really complex. So you're going now down market to meet those customers where they are, how will elation cloud service for snowflake help those customers, those smaller customers really become data driven and, and, and adopt a data culture. >>Yeah. Yeah. It's, it's a great question. I, I think the biggest goal that we had was making it really simple and easy for them to begin this journey. So, you know, we are now live in the snowflake partner connect portal. And if someone wants to experience the power of elation cloud service for snowflake, they just need to go to that portal, click the elation tile. And literally within less than two minutes, a brand new instance of elation is spun up. Their snowflake data is automatically being cataloged as part of this trial. And they have 14 days to go through this experience and, and get a sense of the power of elation to give them insights into what's in their snowflake platform, what governance options they can layer on top of their snowflake data cloud and how the data is transforming across their organization. >>So talk to me about who you're talking to within a customer. I was looking at some data that elation provided to me, and I see that according to Gartner data culture is priority number one for chief data officers, but for those smaller organizations, do they have chief data officers? Is that responsibility line still with the CIO? Who are you engaging with? >>Yeah, it's very, very, really great question. I, I think the larger organizations that we sell to definitely have a, a CDO and, you know, CDO sometimes is the chief data and analytics officer in smaller organizations, or even in divisions of big companies that, that, you know, might be target customers for ACS, for snowflake could be a, a VP of analytics could be head of marketing. Operations could be a data engineering function, so that might roll up into the it. And so I think that's, what's interesting is we, we wanted to take the friction out of the, the experience process and the trial process, and whoever is responsible for the snowflake instance and, and leveraging snowflake for, for data and analytics, they can explore and understand what the, a power elation layered on top of snowflake can provide for them. >>Okay. So another, another thing that I uncovered in researching for this segment is McKenzie says data, culture is decision culture. I thought that was a really profound statement, but it's also such a challenge to get there is organizations of all sizes are on various points in their journey to become data driven. What does that mean? How, how well, how do elation and help customers really achieve that data culture so that they can really have that decision culture so they can make faster, better data based decisions? >>Yeah, it, so I, I think a huge part of it, like if we think about our, our, our big area of focus, how do we enable users to find, understand trust, govern, and use data within snowflake in this instance? And so step one to drive data culture is how, how do you provide a single source of reference a, a, a search box, frankly, you know, Google for your, for your data environment, so that you can actually find data, then how do you understand it? You know, what's in there. What does it mean? What are the relationships between these data objects? Can I trust this? Is this sandbox data, or is this production data that can be used for reporting and analytics? How do I govern the data? So I know who's using it, who should use it, what policies are there. And so if, if we go through the set of features that we've built into ation cloud service for snowflake, it enables us to deliver on that promise result at the very end, resulting in the ability to explore the data that exists in the snowflake platform as well. >>Let's go ahead and unpack that. Now, talk to me about some of the key capabilities of the solution and what it's enabling organizations to achieve. >>Yeah, so, you know, it starts with cataloging the data itself. You know, we, we, we are the data catalog company. We basically define that category. And so step one is how do we connect to snowflake and automatically ingest all the metadata that exists within that snowflake cloud, as well as extract the lineage relationships between tables. So you can understand how the data is transforming within the snowflake data cloud. And so that provides visibility to, to begin that fine journey. You know, how, how do I actually discover data on the understand and trust front? I think where things get really interesting is we've integrated deeply with Snowflake's new data governance features. So they've got data policies that provide things like row level security and, and data masking. We integrate directly with those policies, extract them, ingest them into elation so that they can be discovered, can be easily applied or added to other data sets within snowflake directly from the elation UI. >>So now you've got policies layered on top of your data environment. Snowflake's introduced, tagging and classification capabilities. We automatically extract and ingest those tags. They're surfaced in inhalation. So if somebody looks for a data set that they're not familiar with, they can see, oh, here are the policies that this data set is applied to. Here are the tags that are applied. And so snow elation actually becomes almost like a user interface to the data that exists within that snowflake platform. And then maybe just two other things with the lineage that we extract. One of the most important things that you can deliver for users is impact analysis. Hey, if I'm gonna deprecate this table, or if I'm gonna make a change to what this table definition is, what are the downstream objects and users that should know about that? So, Hey, if this table's going away and my Tableau report over here is gonna stop working, boy, it'd be great to be able to get visibility into that before that change is made, we can do that automatically within the elation UI and, and really just make it easier for somebody to govern and manage the data that exists within the snowflake data cloud. >>So easier to govern and manage the data. Let's go up a level or two. Sure. Talk to me about some of the business outcomes that this solution is gonna help organizations to achieve. We talked about every company these days has to be a data company. Consumers expect this very personalized, relevant experience. What are you thinking? Some of the outcomes are gonna be that this technology and this partnership is gonna unlock. >>Yeah, no, I, I, I think step one, and this has always been a huge area of focus for us is just simply driving business productivity. So, you know, the, the data that we see in talking to CDOs and CDOs is the onboarding and, and getting productive the time it takes to onboard and, and get a data analyst productive. It, it can be nine to 12 months. And, you know, we all know the battle for talent these days is significant. And so if we can provide a solution, and this is exactly what we do that enables an organization to get a data analyst productive in weeks instead of months, or, or, you know, potentially even a year, the value that that analyst can deliver to the organization goes up dramatically because they're spending less time looking for data and figuring out who knows what about the data. >>They can go to elation, get those insights and start answering business questions, as opposed to trying to wrangle or figure out does the data exist. And, and, and where does it exist? So that's, that's one key dimension. I'd say the other one that, that I'd highlight is just being able to have a governance program that is monitored managed and well understood. So that, you know, whether it's dealing with CCPA or GDPR, you know, some of the regulatory regimes, the, the ability for an organization to feel like they have control over their data, and they understand where it is who's using it and how it's being used. Those are hugely important business outcomes that CIOs and CDOs tell us they need. And that's why we built the lation cloud service for snowflake >>On the first front. One of the things that popped into my mind in terms of really enabling workforce productivity, workforce efficiency, getting analysts ramped up dramatically faster also seems to me to be something that your customers can leverage from a talent attraction and retention perspective, which in today's market is critical. >>I, I so glad you mentioned that that's, that's actually one of the key pillars that we highlight as well is like, if you give great tools to employees, they're gonna be happier. And, and you'll be a, a preferred employer and people are gonna feel like, oh, this is an organization that I wanna work at because they're making my job easier and they're making it easier for me to deliver value and be productive to the organization. And that's, it's absolutely critical this, this, this war for talent that everybody talks about. It's real and great self-service tools that are empowering to employees are the things that are gonna differentiate companies and allow them to, to unleash the power of data, >>Unleash the power of data, really use it to the competitive advantage that it can and should be used for. When we look at, when you look at customers that are on that journey, that data catalog journey, they, you probably see such a variety of, of locations about where they are in that journey. Do you see a common thread when you're in customer conversations? Is there kind of a common denominator that you, you speak to where you, you really know elation and snowflake here is absolutely the right thing. >>Yeah, no, it, it, it's a good question. I would actually say the fact that a customer is on snowflake. I they're already, you know, a step up on that maturity curve. You know, one of the big use cases that we see with customers that is, is leading to the need for data intelligence solutions that, you know, like that elation can deliver is digital transformation and, and, and cloud migration, you know, we've got legacy data. On-prem, we know we need to move to the cloud to get better agility, better scaling, you know, perhaps, you know, reduced costs, et cetera. And so I think step one, on that, that qualification criteria or that maturity journey is, Hey, if you're already in snowflake, that's a great sign because you're, you're recognizing the power of a data cloud platform and, and, and warehouse like snowflake. And so that's a, a, a great signal to us that this is a customer that wants to, you know, really better understand how they can get value out of, out of their solution. I think the next step on that journey is a recognition that they're not utilizing the data that they have as effectively as they can and should be, and they're not, and, and their employees are still struggling with, you know, where does the data exist? Can I trust it? It, you know, it, who do I know tends to be more important than do I have a tool that will help me understand the data. And so customers that are asking those sorts of questions are ideal customers for the elation cloud service for snowflake solution. >>So enabling those customers to get their hands on it, there's a free trial. Talk to us about that. And where can the audience go to actually click and try? >>Absolutely. So, you know, we'll, we'll be doing our usual marketing and, and promotion of this, but what I'm super excited about, you know, again, I mentioned earlier, you know, this is part of our, our cloud native multi 10 and architecture. We are live in the snowflake partner connect portal. And so if you are logged into snowflake and are an admin, you can go to the partner connect portal and you will see a tile. I think it's alphabetically, sorted and elation starts with a so pretty easy to find. I don't think you'll have to do too much searching. And literally all you have to do is click on that tile, answer a couple quick questions. And in the background in about two minutes, your elation instance will get spun up. We'll we will have sample data sets in there. There's some guided tours that you can walk through to kind of get a feel for the power of snowflake. >>So policy center lineage, you know, tags, our intelligent SQL tool that allows you to smartly query the snowflake data cloud and publish queries, share queries with others, collaborate on them for, for greater insights. And there's, you know, as you would expect with any, you know, online free trial, you know, we've got a built in chat bot. So if you have a question, wanna get a better sense of how a particular feature works or curious about how elation might work. In other areas, you can, you know, ask a question to the chat bot and we've got product specialists on the back end that can answer questions. So we really wanna make that journey as, as seamless and easy as, as possible. And hopefully that results in enough interests that the customer wants to, to, or the, the trial user wants to become a customer. And, and that's where our great sales organization will kind of take the Baton from there. >>And there's the, there's the objective there, and I'm sure Raj folks can find out about the free trial and access it. You, you mentioned through the marketplace, more information on elian.com. I imagine they can go there to access it as well, >>A hundred percent elation.com. We're on Twitter, we're on LinkedIn, but yeah, if you have any questions, you know, you can just search for elation cloud service for snowflake, or just go to the elation.com website. Absolutely. >>All right. Elation cloud service for snowflake. Congratulations on the launch to you and the entire elation team. We look forward to hearing customer success stories and really seeing those business outcomes realize in the next few months, Raj, thanks so much for your time. >>Thank you so much, Lisa. It's great to talk to you. >>Likewise, Raj gin. I'm Lisa Martin. Thank you for watching this cube conversation. Stay right here for more great action on the cube, the leader in live tech coverage.

>> From theCUBE studios in Palo Alto, in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vollante. >> The rise of Kubernetes came about through a combination of forces that were, in hindsight, quite a long shot. Amazon's dominance created momentum for Cloud native application development, and the need for newer and simpler experiences, beyond just easily spinning up computer as a service. This wave crashed into innovations from a startup named Docker, and a reluctant competitor in Google, that needed a way to change the game on Amazon and the Cloud. Now, add in the effort of Red Hat, which needed a new path beyond Enterprise Linux, and oh, by the way, it was just about to commit to a path of a Kubernetes alternative for OpenShift and figure out a governance structure to hurt all the cats and the ecosystem and you get the remarkable ascendancy of Kubernetes. Hello and welcome to this week's Wikibon CUBE Insights powered by ETR. In this breaking analysis, we tapped the back stories of a new documentary that explains the improbable events that led to the creation of Kubernetes. We'll share some new survey data from ETR and commentary from the many early the innovators who came on theCUBE during the exciting period since the founding of Docker in 2013, which marked a new era in computing, because we're talking about Kubernetes and developers today, the hoodie is on. And there's a new two part documentary that I just referenced, it's out and it was produced by Honeypot on Kubernetes, part one and part two, tells a story of how Kubernetes came to prominence and many of the players that made it happen. Now, a lot of these players, including Tim Hawkin Kelsey Hightower, Craig McLuckie, Joe Beda, Brian Grant Solomon Hykes, Jerry Chen and others came on theCUBE during formative years of containers going mainstream and the rise of Kubernetes. John Furrier and Stu Miniman were at the many shows we covered back then and they unpacked what was happening at the time. We'll share the commentary from the guests that they interviewed and try to add some context. Now let's start with the concept of developer defined structure, DDI. Jerry Chen was at VMware and he could see the trends that were evolving. He left VMware to become a venture capitalist at Greylock. Docker was his first investment. And he saw the future this way. >> What happens is when you define infrastructure software you can program it. You make it portable. And that the beauty of this cloud wave what I call DDI's. Now, to your point is every piece of infrastructure from storage, networking, to compute has an API, right? And, and AWS there was an early trend where S3, EBS, EC2 had API. >> As building blocks too. >> As building blocks, exactly. >> Not monolithic. >> Monolithic building blocks every little building bone block has it own API and just like Docker really is the API for this unit of the cloud enables developers to define how they want to build their applications, how to network them know as Wills talked about, and how you want to secure them and how you want to store them. And so the beauty of this generation is now developers are determining how apps are built, not just at the, you know, end user, you know, iPhone app layer the data layer, the storage layer, the networking layer. So every single level is being disrupted by this concept of a DDI and where, how you build use and actually purchase IT has changed. And you're seeing the incumbent vendors like Oracle, VMware Microsoft try to react but you're seeing a whole new generation startup. >> Now what Jerry was explaining is that this new abstraction layer that was being built here's some ETR data that quantifies that and shows where we are today. The chart shows net score or spending momentum on the vertical axis and market share which represents the pervasiveness in the survey set. So as Jerry and the innovators who created Docker saw the cloud was becoming prominent and you can see it still has spending velocity that's elevated above that 40% red line which is kind of a magic mark of momentum. And of course, it's very prominent on the X axis as well. And you see the low level infrastructure virtualization and that even floats above servers and storage and networking right. Back in 2013 the conversation with VMware. And by the way, I remember having this conversation deeply at the time with Chad Sakac was we're going to make this low level infrastructure invisible, and we intend to make virtualization invisible, IE simplified. And so, you see above the two arrows there related to containers, container orchestration and container platforms, which are abstraction layers and services above the underlying VMs and hardware. And you can see the momentum that they have right there with the cloud and AI and RPA. So you had these forces that Jerry described that were taking shape, and this picture kind of summarizes how they came together to form Kubernetes. And the upper left, Of course you see AWS and we inserted a picture from a post we did, right after the first reinvent in 2012, it was obvious to us at the time that the cloud gorilla was AWS and had all this momentum. Now, Solomon Hykes, the founder of Docker, you see there in the upper right. He saw the need to simplify the packaging of applications for cloud developers. Here's how he described it. Back in 2014 in theCUBE with John Furrier >> Container is a unit of deployment, right? It's the format in which you package your application all the files, all the executables libraries all the dependencies in one thing that you can move to any server and deploy in a repeatable way. So it's similar to how you would run an iOS app on an iPhone, for example. >> A Docker at the time was a 30% company and it just changed its name from .cloud. And back to the diagram you have Google with a red question mark. So why would you need more than what Docker had created. Craig McLuckie, who was a product manager at Google back then explains the need for yet another abstraction. >> We created the strong separation between infrastructure operations and application operations. And so, Docker has created a portable framework to take it, basically a binary and run it anywhere which is an amazing capability, but that's not enough. You also need to be able to manage that with a framework that can run anywhere. And so, the union of Docker and Kubernetes provides this framework where you're completely abstracted from the underlying infrastructure. You could use VMware, you could use Red Hat open stack deployment. You could run on another major cloud provider like rec. >> Now Google had this huge cloud infrastructure but no commercial cloud business compete with AWS. At least not one that was taken seriously at the time. So it needed a way to change the game. And it had this thing called Google Borg, which is a container management system and scheduler and Google looked at what was happening with virtualization and said, you know, we obviously could do better Joe Beda, who was with Google at the time explains their mindset going back to the beginning. >> Craig and I started up Google compute engine VM as a service. And the odd thing to recognize is that, nobody who had been in Google for a long time thought that there was anything to this VM stuff, right? Cause Google had been on containers for so long. That was their mindset board was the way that stuff was actually deployed. So, you know, my boss at the time, who's now at Cloudera booted up a VM for the first time, and anybody in the outside world be like, Hey, that's really cool. And his response was like, well now what? Right. You're sitting at a prompt. Like that's not super interesting. How do I run my app? Right. Which is, that's what everybody's been struggling with, with cloud is not how do I get a VM up? How do I actually run my code? >> Okay. So Google never really did virtualization. They were looking at the market and said, okay what can we do to make Google relevant in cloud. Here's Eric Brewer from Google. Talking on theCUBE about Google's thought process at the time. >> One interest things about Google is it essentially makes no use of virtual machines internally. And that's because Google started in 1998 which is the same year that VMware started was kind of brought the modern virtual machine to bear. And so Google infrastructure tends to be built really on kind of classic Unix processes and communication. And so scaling that up, you get a system that works a lot with just processes and containers. So kind of when I saw containers come along with Docker, we said, well, that's a good model for us. And we can take what we know internally which was called Borg a big scheduler. And we can turn that into Kubernetes and we'll open source it. And suddenly we have kind of a cloud version of Google that works the way we would like it to work. >> Now, Eric Brewer gave us the bumper sticker version of the story there. What he reveals in the documentary that I referenced earlier is that initially Google was like, why would we open source our secret sauce to help competitors? So folks like Tim Hockin and Brian Grant who were on the original Kubernetes team, went to management and pressed hard to convince them to bless open sourcing Kubernetes. Here's Hockin's explanation. >> When Docker landed, we saw the community building and building and building. I mean, that was a snowball of its own, right? And as it caught on we realized we know what this is going to we know once you embrace the Docker mindset that you very quickly need something to manage all of your Docker nodes, once you get beyond two or three of them, and we know how to build that, right? We got a ton of experience here. Like we went to our leadership and said, you know, please this is going to happen with us or without us. And I think it, the world would be better if we helped. >> So the open source strategy became more compelling as they studied the problem because it gave Google a way to neutralize AWS's advantage because with containers you could develop on AWS for example, and then run the application anywhere like Google's cloud. So it not only gave developers a path off of AWS. If Google could develop a strong service on GCP they could monetize that play. Now, focus your attention back to the diagram which shows this smiling, Alex Polvi from Core OS which was acquired by Red Hat in 2018. And he saw the need to bring Linux into the cloud. I mean, after all Linux was powering the internet it was the OS for enterprise apps. And he saw the need to extend its path into the cloud. Now here's how he described it at an OpenStack event in 2015. >> Similar to what happened with Linux. Like yes, there is still need for Linux and Windows and other OSs out there. But by and large on production, web infrastructure it's all Linux now. And you were able to get onto one stack. And how were you able to do that? It was, it was by having a truly open consistent API and a commitment into not breaking APIs and, so on. That allowed Linux to really become ubiquitous in the data center. Yes, there are other OSs, but Linux buy in large for production infrastructure, what is being used. And I think you'll see a similar phenomenon happen for this next level up cause we're treating the whole data center as a computer instead of trading one in visual instance is just the computer. And that's the stuff that Kubernetes to me and someone is doing. And I think there will be one that shakes out over time and we believe that'll be Kubernetes. >> So Alex saw the need for a dominant container orchestration platform. And you heard him, they made the right bet. It would be Kubernetes. Now Red Hat, Red Hat is been around since 1993. So it has a lot of on-prem. So it needed a future path to the cloud. So they rang up Google and said, hey. What do you guys have going on in this space? So Google, was kind of non-committal, but it did expose that they were thinking about doing something that was you know, pre Kubernetes. It was before it was called Kubernetes. But hey, we have this thing and we're thinking about open sourcing it, but Google's internal debates, and you know, some of the arm twisting from the engine engineers, it was taking too long. So Red Hat said, well, screw it. We got to move forward with OpenShift. So we'll do what Apple and Airbnb and Heroku are doing and we'll build on an alternative. And so they were ready to go with Mesos which was very much more sophisticated than Kubernetes at the time and much more mature, but then Google the last minute said, hey, let's do this. So Clayton Coleman with Red Hat, he was an architect. And he leaned in right away. He was one of the first outside committers outside of Google. But you still led these competing forces in the market. And internally there were debates. Do we go with simplicity or do we go with system scale? And Hen Goldberg from Google explains why they focus first on simplicity in getting that right. >> We had to defend of why we are only supporting 100 nodes in the first release of Kubernetes. And they explained that they know how to build for scale. They've done that. They know how to do it, but realistically most of users don't need large clusters. So why create this complexity? >> So Goldberg explains that rather than competing right away with say Mesos or Docker swarm, which were far more baked they made the bet to keep it simple and go for adoption and ubiquity, which obviously turned out to be the right choice. But the last piece of the puzzle was governance. Now Google promised to open source Kubernetes but when it started to open up to contributors outside of Google, the code was still controlled by Google and developers had to sign Google paper that said Google could still do whatever it wanted. It could sub license, et cetera. So Google had to pass the Baton to an independent entity and that's how CNCF was started. Kubernetes was its first project. And let's listen to Chris Aniszczyk of the CNCF explain >> CNCF is all about providing a neutral home for cloud native technology. And, you know, it's been about almost two years since our first board meeting. And the idea was, you know there's a certain set of technology out there, you know that are essentially microservice based that like live in containers that are essentially orchestrated by some process, right? That's essentially what we mean when we say cloud native right. And CNCF was seated with Kubernetes as its first project. And you know, as, as we've seen over the last couple years Kubernetes has grown, you know, quite well they have a large community a diverse con you know, contributor base and have done, you know, kind of extremely well. They're one of actually the fastest, you know highest velocity, open source projects out there, maybe. >> Okay. So this is how we got to where we are today. This ETR data shows container orchestration offerings. It's the same X Y graph that we showed earlier. And you can see where Kubernetes lands not we're standing that Kubernetes not a company but respondents, you know, they doing Kubernetes. They maybe don't know, you know, whose platform and it's hard with the ETR taxon economy as a fuzzy and survey data because Kubernetes is increasingly becoming embedded into cloud platforms. And IT pros, they may not even know which one specifically. And so the reason we've linked these two platforms Kubernetes and Red Hat OpenShift is because OpenShift right now is a dominant revenue player in the space and is increasingly popular PaaS layer. Yeah. You could download Kubernetes and do what you want with it. But if you're really building enterprise apps you're going to need support. And that's where OpenShift comes in. And there's not much data on this but we did find this chart from AMDA which show was the container software market, whatever that really is. And Red Hat has got 50% of it. This is revenue. And, you know, we know the muscle of IBM is behind OpenShift. So there's really not hard to believe. Now we've got some other data points that show how Kubernetes is becoming less visible and more embedded under of the hood. If you will, as this chart shows this is data from CNCF's annual survey they had 1800 respondents here, and the data showed that 79% of respondents use certified Kubernetes hosted platforms. Amazon elastic container service for Kubernetes was the most prominent 39% followed by Azure Kubernetes service at 23% in Azure AKS engine at 17%. With Google's GKE, Google Kubernetes engine behind those three. Now. You have to ask, okay, Google. Google's management Initially they had concerns. You know, why are we open sourcing such a key technology? And the premise was, it would level the playing field. And for sure it has, but you have to ask has it driven the monetization Google was after? And I would've to say no, it probably didn't. But think about where Google would've been. If it hadn't open source Kubernetes how relevant would it be in the cloud discussion. Despite its distant third position behind AWS and Microsoft or even fourth, if you include Alibaba without Kubernetes Google probably would be much less prominent or possibly even irrelevant in cloud, enterprise cloud. Okay. Let's wrap up with some comments on the state of Kubernetes and maybe a thought or two about, you know, where we're headed. So look, no shocker Kubernetes for all its improbable beginning has gone mainstream in the past year or so. We're seeing much more maturity and support for state full workloads and big ecosystem support with respect to better security and continued simplification. But you know, it's still pretty complex. It's getting better, but it's not VMware level of maturity. For example, of course. Now adoption has always been strong for Kubernetes, for cloud native companies who start with containers on day one, but we're seeing many more. IT organizations adopting Kubernetes as it matures. It's interesting, you know, Docker set out to be the system of the cloud and Kubernetes has really kind of become that. Docker desktop is where Docker's action really is. That's where Docker is thriving. It sold off Docker swarm to Mirantis has made some tweaks. Docker has made some tweaks to its licensing model to be able to continue to evolve its its business. To hear more about that at DockerCon. And as we said, years ago we expected Kubernetes to become less visible Stu Miniman and I talked about this in one of our predictions post and really become more embedded into other platforms. And that's exactly what's happening here but it's still complicated. Remember, remember the... Go back to the early and mid cycle of VMware understanding things like application performance you needed folks in lab coats to really remediate problems and dig in and peel the onion and scale the system you know, and in some ways you're seeing that dynamic repeated with Kubernetes, security performance scale recovery, when something goes wrong all are made more difficult by the rapid pace at which the ecosystem is evolving Kubernetes. But it's definitely headed in the right direction. So what's next for Kubernetes we would expect further simplification and you're going to see more abstractions. We live in this world of almost perpetual abstractions. Now, as Kubernetes improves support from multi cluster it will be begin to treat those clusters as a unified group. So kind of abstracting multiple clusters and treating them as, as one to be managed together. And this is going to create a lot of ecosystem focus on scaling globally. Okay, once you do that, you're going to have to worry about latency and then you're going to have to keep pace with security as you expand the, the threat area. And then of course recovery what happens when something goes wrong, more complexity, the harder it is to recover and that's going to require new services to share resources across clusters. So look for that. You also should expect more automation. It's going to be driven by the host cloud providers as Kubernetes supports more state full applications and begins to extend its cluster management. Cloud providers will inject as much automation as possible into the system. Now and finally, as these capabilities mature we would expect to see better support for data intensive workloads like, AI and Machine learning and inference. Schedule with these workloads becomes harder because they're so resource intensive and performance management becomes more complex. So that's going to have to evolve. I mean, frankly, many of the things that Kubernetes team way back when, you know they back burn it early on, for example, you saw in Docker swarm or Mesos they're going to start to enter the scene now with Kubernetes as they start to sort of prioritize some of those more complex functions. Now, the last thing I'll ask you to think about is what's next beyond Kubernetes, you know this isn't it right with serverless and IOT in the edge and new data, heavy workloads there's something that's going to disrupt Kubernetes. So in that, by the way, in that CNCF survey nearly 40% of respondents were using serverless and that's going to keep growing. So how is that going to change the development model? You know, Andy Jassy once famously said that if they had to start over with Amazon retail, they'd start with serverless. So let's keep an eye on the horizon to see what's coming next. All right, that's it for now. I want to thank my colleagues, Stephanie Chan who helped research this week's topics and Alex Myerson on the production team, who also manages the breaking analysis podcast, Kristin Martin and Cheryl Knight help get the word out on socials, so thanks to all of you. Remember these episodes, they're all available as podcasts wherever you listen, just search breaking analysis podcast. Don't forget to check out ETR website @etr.ai. We'll also publish. We publish a full report every week on wikibon.com and Silicon angle.com. You can get in touch with me, email me directly david.villane@Siliconangle.com or DM me at D Vollante. You can comment on our LinkedIn post. This is Dave Vollante for theCUBE insights powered by ETR. Have a great week, everybody. Thanks for watching. Stay safe, be well. And we'll see you next time. (upbeat music)

>>Okay, welcome back everyone. To the cubes coverage here, coop con cloud native con 2021 in person. The Cuba's here. I'm John farrier hosted the queue with Dave Nicholson, my cohost and cloud analyst, man. It's great to be back, uh, in person. We also have a hybrid event. We've got two great guests here, the founders of deep fence, sham, Krista Swami, C co-founder and CTO, and said deep line founder. It's great to have you on. This is a super important topic. As cloud native is crossed over. Everyone's talking about it mainstream, blah, blah, blah. But security is driving the agenda. You guys are in the middle of it. Cutting edge approach and news >>Like, like we were talking about John, we had operating at the intersection of the awesome desk, right? Open source security and cloud cloud native, essentially. Absolutely. And today's a super exciting day for us. We're launching something called track pepper, Apache V2, completely open source. Think of it as an x-ray or MRI scan for your cloud scan, you know, visualize this cloud at scale, all of the modalities, essentially, we look at cloud as a continuum. It's not a single modality it's containers. It's communities, it's William to settle we'll list all of them. Co-exist side by side. That's how we look at it and threat map. It essentially allows you to visualize all of this in real time, think of fed map, but as something that you, that, that takes over the Baton from the CIS unit, when the lift shift left gets over, that's when the threat pepper comes into picture. So yeah, super excited. >>It's like really gives that developer and the teams ops teams visibility into kind of health statistics of the cloud. But also, as you said, it's not just software mechanisms. The cloud is evolving, new sources being turned on and off. No one even knows what's going on. Sometimes this is a really hidden problem, right? Yeah, >>Absolutely. The basic problem is, I mean, I would just talk to, you know, a gentleman 70 of this morning is two 70 billion. Plus public cloud spent John two 70 billion plus even 3 billion, 30 billion they're saying right. Uh, projected revenue. And there is not even a single community tool to visualize all the clouds and all the cloud modalities at scale, let's start there. That's what we sort of decided, you know what, let's start with utilizing everything else there. And then look for known badness, which is the vulnerabilities, which still remains the biggest attack vector. >>Sure. Tell us about some of the hood. How does this all work cloud scale? Is it a cloud service managed service it's code? Take us out, take us through product. Absolutely. >>So, so, but before that, right, there's one small point that Sandeep mentioned. And Richard, I'd like to elaborate here, right? He spoke about the whole cloud spending such a large volume, right? If you look at the way people look at applications today, it's not just single clone anymore. It's multicloud multi regions across diverse plants, right? What does the solution to look at what my interests are to this point? That is a missing piece here. And that is what we're trying to tackle. And that is where we are going as open source. Coming back to your question, right? How does this whole thing work? So we have a completely on-prem model, right? Where customers can download the code today, install it. It can bill, we give binary stool and Shockley just as the exciting announcement that came out today, you're going to see somewhat exciting entrepreneurs. That's going to make a lot more easy for folks out there all day. Yeah, that's fine. >>So how does this, how does this all fit into security as a micro service and your, your vision of that? >>Absolutely. Absolutely. You know, I'll tell you, this has to do with the one of the continual conferences I would sort of when I was trying to get an idea, trying to shape the whole vision really? Right. Hey, what about syncretism? Microservice? I would go and ask people. They mentioned that sounds, that makes sense. Everything is becoming a microservice. Really. So what you're saying is you're going to deploy one more microservice, just like I deploy all of my other microservices. And that's going to look after my microservices. That compute back makes logical sense, essentially. That was the Genesis of that terminology. So defense essentially is deployed as a microservice. You go to scale, it's deployed, operated just like you to your microservices. So no code changes, no other tool chain changes. It just is yet another microservice. That's going to look after you talk about >>The, >>So there's one point I would like to add here, which is something very interesting, right? The whole concept of microservice came from, if you remember the memo from Jeff Bezos, that everybody's going to go, Microsoft would be fired. That gave rise to a very conventional unconditionally of thinking about their applications. Our deep friends, we believe that security should be. Now. You should bring the same unconventional way of thinking to security. Your security is all bottom up. No, it has to start popping up. So your applications on microservice, your security should also be a micro. >>So you need a microservice for a microservice security for the security. You're starting to get into a paradigm shift where you starting to see the API economy that bayzos and Amazon philosophy and their approach go Beanstream. So when I got to ask you, because this is a trend we've been watching and reporting on the actual application development processes, changing from the old school, you know, life cycle, software defined life cycle to now you've got machine learning and bots. You have AI. Now you have people are building apps differently. And the speed of which they want to code is high. And then other teams are slowing them down. So I've heard security teams just screw people over a couple of days. Oh my God, I can wait five days. No, it used to be five weeks. Now it's five days. They think that's progress. They want five minutes, the developers in real time. So this is a real deal optimum. >>Well, you know what? Shift left was a good thing. Instill a good thing. It helps you sort of figure out the issues early on in the development life cycle, essentially. Right? And so you started weaving in security early on and it stays with you. The problem is we are hydrating. So frequently you end up with a few hundred vulnerabilities every time you scan oftentimes few thousand and then you go to runtime and you can't really fix all these thousand one. You know? So this is where, so there is a little bit of a gap there. If you're saying, if look at the CIC cycle, the in financial cycle that they show you, right. You've got the far left, which is where you have the SAS tools, snake and all of that. And then you've got the center where, which is where you hand off this to ops. >>And then on the right side, you've got tech ops defense essentially starts in the middle and says, look, I know you've had thousand one abilities. Okay. But at run time, I see only one of those packages is loaded in memory. And only that is getting traffic. You go and fix that one because that's going to heart. You see what I'm saying? So that gap is what we're doing. So you start with the left, we come in in the middle and stay with you throughout, you know, till the whole, uh, she asks me. Yeah, well that >>Th that, that touches on a subject. What are the, what are the changes that we're seeing? What are the new threats that are associated with containerization and kind of coupled with that, look back on traditional security methods and how are our traditional security methods failing us with those new requirements that come out of the microservices and containerized world. And so, >>So having, having been at FireEye, I'll tell you I've worked on their windows products and Juniper, >>And very, very deeply involved in. >>And in fact, you know what I mean, at the company, we even sold a product to Palo Alto. So having been around the space, really, I think it's, it's, it's a, it's a foregone conclusion to say that attackers have become more sophisticated. Of course they have. Yeah. It's not a single attack vector, which gets you down anymore. It's not a script getting somewhere shooting who just sending one malicious HTP request exploiting, no, these are multi-vector multi-stage attacks. They, they evolve over time in space, you know? And then what happens is I could have shot a revolving with time and space, one notable cause of piling up. Right? And on the other side, you've got the infrastructure, which is getting fragmented. What I mean by fragmented is it's not one data center where everything would look and feel and smell similar it's containers and tuberosities and several lessons. All of that stuff is hackable, right? So you've got that big shift happening there. You've got attackers, how do you build visibility? So, in fact, initially we used to, we would go and speak with, uh, DevSecOps practitioner say, Hey, what is the coalition? Is it that you don't have enough scanners to scan? Is it that at runtime? What is the main problem? It's the lack of visibility, lack of observability throughout the life cycle, as well as through outage, it was an issue with allegation. >>And the fact that the attackers know that too, they're exploiting the fact that they can't see they're blind. And it's like, you know what? Trying to land a plane that flew yesterday and you think it's landing tomorrow. It's all like lagging. Right? Exactly. So I got to ask you, because this has comes up a lot, because remember when we're in our 11th season with the cube, and I remember conversations going back to 2010, a cloud's not secure. You know, this is before everyone realized shit, the club's better than on premises if you have it. Right. So a trend is emerged. I want to get your thoughts on this. What percentage of the hacks are because the attackers are lazier than the more sophisticated ones, because you see two buckets I'm going to get, I'm going to work hard to get this, or I'm going to go for the easy low-hanging fruit. Most people have just a setup that's just low hanging fruit for the hackers versus some sort of complex or thought through programmatic cloud system, because now is actually better if you do it. Right. So the more sophisticated the environment, the harder it is for the hackers, AK Bob wire, whatever you wanna call it, what level do we cross over? >>When does it go from the script periods to the, the, >>Katie's kind of like, okay, I want to go get the S3 bucket or whatever. There's like levels of like laziness. Yeah. Okay. I, yeah. Versus I'm really going to orchestrate Spearfish social engineer, the more sophisticated economy driven ones. Yeah. >>I think, you know what, this attackers, the hacks aren't being conducted the way they worked in the 10, five years ago, isn't saying that they been outsourced, there are sophisticated teams for building exploiters. This is the whole industry up there. Even the nation, it's an economy really. Right. So, um, the known badness or the known attacks, I think we have had tools. We have had their own tools, signature based tools, which would know, look for certain payloads and say, this is that I know it. Right. You get the stuff really starts sort of, uh, getting out of control when you have so many sort of different modalities running side by side. So much, so much moving attack surfaces, they will evolve. And you never know that you've scanned enough because you never happened because we just pushed the code. >>Yeah. So we've been covering the iron debt. Kim retired general, Keith Alexander, his company. They have this iron dome concept where there's more collective sharing. Um, how do you see that trend? Because I can almost imagine that the open-source man is going to love what you guys got. You're going to probably feed on it, like it's nobody's business, but then you start thinking, okay, we're going to be open. And you have a platform approach, not so much a tool based approach. So just give me tools. We all know that when does it, we cross over to the Nirvana of like real security sharing. Real-time telemetry data. >>And I want to answer this in two parts. The first part is really a lot of this wisdom is only in the community. It's a tribal knowledge. It's their informal feeds in from get up tickets. And you know, a lot of these things, what we're really doing with threat map, but as we are consolidating that and giving it out as a sort of platform that you can use, I like to go for free. This is the part you will never go to monetize this. And we are certain about disaster. What we are monetizing instead is you have, like I said, the x-ray or MRI scan of the cloud, which tells you what the pain points are. This is feel free. This is public collective good. This is a Patrick reader. This is for free. It's shocking. >>I took this long to get to that point, by the way, in this discussion. >>Yeah, >>This is this timing's perfect. >>Security is collective good. Right? And if you're doing open source, community-based, you know, programs like this is for the collector group. What we do look, this whole other set map is going to be open source. We going to make it a platform and our commercial version, which is called fetch Stryker, which is where we have our core IP, which is basically think about this way, right? If you figured out all the pain points and using tech map, or this was a free, and now you wanted the remedy for that pain feed to target a defense, we targeted quarantining of those statin workloads and all that stuff. And that's what our IP is. What we really do there is we said, look, you figured out the attack surface using tech fabric. Now I'm going to use threat Stryker to protect their attacks and stress >>Free. Not free to, or is that going to be Fort bang? >>Oh, that's for, okay. >>That's awesome. So you bring the goodness to the party, the goods to the party, again, share that collective, see where that goes. And the Stryker on top is how you guys monetize. >>And that's where we do some uniquely normal things. I would want to talk about that. If, if, if, if you know public probably for 30 seconds or so unique things we do in industry, which is basically being able to monitor what comes in, what goes out and what changes across time and space, because look, most of the modern attacks evolve over time and space, right? So you go to be able to see things like this. Here's a party structure, which has a vulnerability threats. Mapper told you that to strike. And what it does is it tells you a bunch of stress has a vulnerable again, know that somebody is sending a Melissa's HTP request, which has a malicious payload. And you know what, tomorrow there's a file system change. And there is outbound connection going to some funny place. That is the part that we're wanting this. >>Yeah. And you give away the tool to identify the threats and sell the hammer. >>That's giving you protection. >>Yeah. Yeah. Awesome. I love you guys love this product. I love how you're doing it. I got to ask you to define what is security as a microservice. >>So security is a microservice is a deployment modality for us. So defense, what defense has is one console. So defense is currently self posted by the customers within the infrastructure going forward. We'll also be launching a SAS version, the cloud version of it. But what happens as part of this deployment is they're running the management console, which is the gooey, and then a tiny sensor, which is collecting telemetric that is deployed as a microservice is what I'm saying. So you've got 10 containers running defenses level of container. That's, that's an eight or the Microsoft risk. And it utilizes, uh, EDP F you know, for tracing and all that stuff. Yeah. >>Awesome. Well, I think this is the beginning of a shift in the industry. You start to see dev ops and cloud native technologies become the operating model, not just dev dev ops are now in play and infrastructure as code, which is the ethos of a cloud generation is security is code. That's true. That's what you guys are doing. Thanks for coming on. Really appreciate it. Absolutely breaking news here in the queue, obviously great stuff. Open source continues to grow and win in the new model. Collaboration is the cube bringing you all the cover day one, the three days. I'm Jennifer, your host with Dave Nicholson. Thanks for watching.

>>Individuals create developers, translate ideas to code, to create great applications and great applications. Touch everyone. A Docker. We know that collaboration is key to your innovation sharing ideas, working together. Launching the most secure applications. Docker is with you wherever your team innovates, whether it be robots or autonomous cars, we're doing research to save lives during a pandemic, revolutionizing, how to buy and sell goods online, or even going into the unknown frontiers of space. Docker is launching innovation everywhere. Join us on the journey to build, share, run the future. >>Hello and welcome to Docker con 2021. We're incredibly excited to have more than 80,000 of you join us today from all over the world. As it was last year, this year at DockerCon is 100% virtual and 100% free. So as to enable as many community members as possible to join us now, 100%. Virtual is also an acknowledgement of the continuing global pandemic in particular, the ongoing tragedies in India and Brazil, the Docker community is a global one. And on behalf of all Dr. Khan attendees, we are donating $10,000 to UNICEF support efforts to fight the virus in those countries. Now, even in those regions of the world where the pandemic is being brought under control, virtual first is the new normal. It's been a challenging transition. This includes our team here at Docker. And we know from talking with many of you that you and your developer teams are challenged by this as well. So to help application development teams better collaborate and ship faster, we've been working on some powerful new features and we thought it would be fun to start off with a demo of those. How about it? Want to have a look? All right. Then no further delay. I'd like to introduce Youi Cal and Ben, gosh, over to you and Ben >>Morning, Ben, thanks for jumping on real quick. >>Have you seen the email from Scott? The one about updates and the docs landing page Smith, the doc combat and more prominence. >>Yeah. I've got something working on my local machine. I haven't committed anything yet. I was thinking we could try, um, that new Docker dev environments feature. >>Yeah, that's cool. So if you hit the share button, what I should do is it will take all of your code and the dependencies and the image you're basing it on and wrap that up as one image for me. And I can then just monitor all my machines that have been one click, like, and then have it side by side, along with the changes I've been looking at as well, because I was also having a bit of a look and then I can really see how it differs to what I'm doing. Maybe I can combine it to do the best of both worlds. >>Sounds good. Uh, let me get that over to you, >>Wilson. Yeah. If you pay with the image name, I'll get that started up. >>All right. Sen send it over >>Cheesy. Okay, great. Let's have a quick look at what you he was doing then. So I've been messing around similar to do with the batter. I've got movie at the top here and I think it looks pretty cool. Let's just grab that image from you. Pick out that started on a dev environment. What this is doing. It's just going to grab the image down, which you can take all of the code, the dependencies only get brunches working on and I'll get that opened up in my idea. Ready to use. It's a here close. We can see our environment as my Molly image, just coming down there and I've got my new idea. >>We'll load this up and it'll just connect to my dev environment. There we go. It's connected to the container. So we're working all in the container here and now give it a moment. What we'll do is we'll see what changes you've been making as well on the code. So it's like she's been working on a landing page as well, and it looks like she's been changing the banner as well. So let's get this running. Let's see what she's actually doing and how it looks. We'll set up our checklist and then we'll see how that works. >>Great. So that's now rolling. So let's just have a look at what you use doing what changes she had made. Compare those to mine just jumped back into my dev container UI, see that I've got both of those running side by side with my changes and news changes. Okay. So she's put Molly up there rather than mobi or somebody had the same idea. So I think in a way I can make us both happy. So if we just jumped back into what we'll do, just add Molly and Moby and here I'll save that. And what we can see is, cause I'm just working within the container rather than having to do sort of rebuild of everything or serve, or just reload my content. No, that's straight the page. So what I can then do is I can come up with my browser here. Once that's all refreshed, refresh the page once hopefully, maybe twice, we should then be able to see your refresh it or should be able to see that we get Malia mobi come up. So there we go, got Molly mobi. So what we'll do now is we'll describe that state. It sends us our image and then we'll just create one of those to share with URI or share. And we'll get a link for that. I guess we'll send that back over to you. >>So I've had a look at what you were doing and I'm actually going to change. I think that might work for both of us. I wondered if you could take a look at it. If I send it over. >>Sounds good. Let me grab the link. >>Yeah, it's a dev environment link again. So if you just open that back in the doc dashboard, it should be able to open up the code that I've changed and then just run it in the same way you normally do. And that shouldn't interrupt what you're already working on because there'll be able to run side by side with your other brunch. You already got, >>Got it. Got it. Loading here. Well, that's great. It's Molly and movie together. I love it. I think we should ship it. >>Awesome. I guess it's chip it and get on with the rest of.com. Wasn't that cool. Thank you Joey. Thanks Ben. Everyone we'll have more of this later in the keynote. So stay tuned. Let's say earlier, we've all been challenged by this past year, whether the COVID pandemic, the complete evaporation of customer demand in many industries, unemployment or business bankruptcies, we all been touched in some way. And yet, even to miss these tragedies last year, we saw multiple sources of hope and inspiration. For example, in response to COVID we saw global communities, including the tech community rapidly innovate solutions for analyzing the spread of the virus, sequencing its genes and visualizing infection rates. In fact, if all in teams collaborating on solutions for COVID have created more than 1,400 publicly shareable images on Docker hub. As another example, we all witnessed the historic landing and exploration of Mars by the perseverance Rover and its ingenuity drone. >>Now what's common in these examples, these innovative and ambitious accomplishments were made possible not by any single individual, but by teams of individuals collaborating together. The power of teams is why we've made development teams central to Docker's mission to build tools and content development teams love to help them get their ideas from code to cloud as quickly as possible. One of the frictions we've seen that can slow down to them in teams is that the path from code to cloud can be a confusing one, riddle with multiple point products, tools, and images that need to be integrated and maintained an automated pipeline in order for teams to be productive. That's why a year and a half ago we refocused Docker on helping development teams make sense of all this specifically, our goal is to provide development teams with the trusted content, the sharing capabilities and the pipeline integrations with best of breed third-party tools to help teams ship faster in short, to provide a collaborative application development platform. >>Everything a team needs to build. Sharon run create applications. Now, as I noted earlier, it's been a challenging year for everyone on our planet and has been similar for us here at Docker. Our team had to adapt to working from home local lockdowns caused by the pandemic and other challenges. And despite all this together with our community and ecosystem partners, we accomplished many exciting milestones. For example, in open source together with the community and our partners, we open sourced or made major contributions to many projects, including OCI distribution and the composed plugins building on these open source projects. We had powerful new capabilities to the Docker product, both free and subscription. For example, support for WSL two and apple, Silicon and Docker, desktop and vulnerability scanning audit logs and image management and Docker hub. >>And finally delivering an easy to use well-integrated development experience with best of breed tools and content is only possible through close collaboration with our ecosystem partners. For example, this last year we had over 100 commercialized fees, join our Docker verified publisher program and over 200 open source projects, join our Docker sponsored open source program. As a result of these efforts, we've seen some exciting growth in the Docker community in the 12 months since last year's Docker con for example, the number of registered developers grew 80% to over 8 million. These developers created many new images increasing the total by 56% to almost 11 million. And the images in all these repositories were pulled by more than 13 million monthly active IP addresses totaling 13 billion pulls a month. Now while the growth is exciting by Docker, we're even more excited about the stories we hear from you and your development teams about how you're using Docker and its impact on your businesses. For example, cancer researchers and their bioinformatics development team at the Washington university school of medicine needed a way to quickly analyze their clinical trial results and then share the models, the data and the analysis with other researchers they use Docker because it gives them the ease of use choice of pipeline tools and speed of sharing so critical to their research. And most importantly to the lives of their patients stay tuned for another powerful customer story later in the keynote from Matt fall, VP of engineering at Oracle insights. >>So with this last year behind us, what's next for Docker, but challenge you this last year of force changes in how development teams work, but we felt for years to come. And what we've learned in our discussions with you will have long lasting impact on our product roadmap. One of the biggest takeaways from those discussions that you and your development team want to be quicker to adapt, to changes in your environment so you can ship faster. So what is DACA doing to help with this first trusted content to own the teams that can focus their energies on what is unique to their businesses and spend as little time as possible on undifferentiated work are able to adapt more quickly and ship faster in order to do so. They need to be able to trust other components that make up their app together with our partners. >>Docker is doubling down and providing development teams with trusted content and the tools they need to use it in their applications. Second, remote collaboration on a development team, asking a coworker to take a look at your code used to be as easy as swiveling their chair around, but given what's happened in the last year, that's no longer the case. So as you even been hinted in the demo at the beginning, you'll see us deliver more capabilities for remote collaboration within a development team. And we're enabling development team to quickly adapt to any team configuration all on prem hybrid, all work from home, helping them remain productive and focused on shipping third ecosystem integrations, those development teams that can quickly take advantage of innovations throughout the ecosystem. Instead of getting locked into a single monolithic pipeline, there'll be the ones able to deliver amps, which impact their businesses faster. >>So together with our ecosystem partners, we are investing in more integrations with best of breed tools, right? Integrated automated app pipelines. Furthermore, we'll be writing more public API APIs and SDKs to enable ecosystem partners and development teams to roll their own integrations. We'll be sharing more details about remote collaboration and ecosystem integrations. Later in the keynote, I'd like to take a moment to share with Docker and our partners are doing for trusted content, providing development teams, access to content. They can trust, allows them to focus their coding efforts on what's unique and differentiated to that end Docker and our partners are bringing more and more trusted content to Docker hub Docker official images are 160 images of popular upstream open source projects that serve as foundational building blocks for any application. These include operating systems, programming, languages, databases, and more. Furthermore, these are updated patch scan and certified frequently. So I said, no image is older than 30 days. >>Docker verified publisher images are published by more than 100 commercialized feeds. The image Rebos are explicitly designated verify. So the developers searching for components for their app know that the ISV is actively maintaining the image. Docker sponsored open source projects announced late last year features images for more than 200 open source communities. Docker sponsors these communities through providing free storage and networking resources and offering their community members unrestricted access repos for businesses allow businesses to update and share their apps privately within their organizations using role-based access control and user authentication. No, and finally, public repos for communities enable community projects to be freely shared with anonymous and authenticated users alike. >>And for all these different types of content, we provide services for both development teams and ISP, for example, vulnerability scanning and digital signing for enhanced security search and filtering for discoverability packaging and updating services and analytics about how these products are being used. All this trusted content, we make available to develop teams for them directly to discover poll and integrate into their applications. Our goal is to meet development teams where they live. So for those organizations that prefer to manage their internal distribution of trusted content, we've collaborated with leading container registry partners. We announced our partnership with J frog late last year. And today we're very pleased to announce our partnerships with Amazon and Miranda's for providing an integrated seamless experience for joint for our joint customers. Lastly, the container images themselves and this end to end flow are built on open industry standards, which provided all the teams with flexibility and choice trusted content enables development teams to rapidly build. >>As I let them focus on their unique differentiated features and use trusted building blocks for the rest. We'll be talking more about trusted content as well as remote collaboration and ecosystem integrations later in the keynote. Now ecosystem partners are not only integral to the Docker experience for development teams. They're also integral to a great DockerCon experience, but please join me in thanking our Dr. Kent on sponsors and checking out their talks throughout the day. I also want to thank some others first up Docker team. Like all of you this last year has been extremely challenging for us, but the Docker team rose to the challenge and worked together to continue shipping great product, the Docker community of captains, community leaders, and contributors with your welcoming newcomers, enthusiasm for Docker and open exchanges of best practices and ideas talker, wouldn't be Docker without you. And finally, our development team customers. >>You trust us to help you build apps. Your businesses rely on. We don't take that trust for granted. Thank you. In closing, we often hear about the tenant's developer capable of great individual feeds that can transform project. But I wonder if we, as an industry have perhaps gotten this wrong by putting so much emphasis on weight, on the individual as discussed at the beginning, great accomplishments like innovative responses to COVID-19 like landing on Mars are more often the results of individuals collaborating together as a team, which is why our mission here at Docker is delivered tools and content developers love to help their team succeed and become 10 X teams. Thanks again for joining us, we look forward to having a great DockerCon with you today, as well as a great year ahead of us. Thanks and be well. >>Hi, I'm Dana Lawson, VP of engineering here at get hub. And my job is to enable this rich interconnected community of builders and makers to build even more and hopefully have a great time doing it in order to enable the best platform for developers, which I know is something we are all passionate about. We need to partner across the ecosystem to ensure that developers can have a great experience across get hub and all the tools that they want to use. No matter what they are. My team works to build the tools and relationships to make that possible. I am so excited to join Scott on this virtual stage to talk about increasing developer velocity. So let's dive in now, I know this may be hard for some of you to believe, but as a former CIS admin, some 21 years ago, working on sense spark workstations, we've come such a long way for random scripts and desperate systems that we've stitched together to this whole inclusive developer workflow experience being a CIS admin. >>Then you were just one piece of the siloed experience, but I didn't want to just push code to production. So I created scripts that did it for me. I taught myself how to code. I was the model lazy CIS admin that got dangerous and having pushed a little too far. I realized that working in production and building features is really a team sport that we had the opportunity, all of us to be customer obsessed today. As developers, we can go beyond the traditional dev ops mindset. We can really focus on adding value to the customer experience by ensuring that we have work that contributes to increasing uptime via and SLS all while being agile and productive. We get there. When we move from a pass the Baton system to now having an interconnected developer workflow that increases velocity in every part of the cycle, we get to work better and smarter. >>And honestly, in a way that is so much more enjoyable because we automate away all the mundane and manual and boring tasks. So we get to focus on what really matters shipping, the things that humans get to use and love. Docker has been a big part of enabling this transformation. 10, 20 years ago, we had Tomcat containers, which are not Docker containers. And for y'all hearing this the first time go Google it. But that was the way we built our applications. We had to segment them on the server and give them resources. Today. We have Docker containers, these little mini Oasys and Docker images. You can do it multiple times in an orchestrated manner with the power of actions enabled and Docker. It's just so incredible what you can do. And by the way, I'm showing you actions in Docker, which I hope you use because both are great and free for open source. >>But the key takeaway is really the workflow and the automation, which you certainly can do with other tools. Okay, I'm going to show you just how easy this is, because believe me, if this is something I can learn and do anybody out there can, and in this demo, I'll show you about the basic components needed to create and use a package, Docker container actions. And like I said, you won't believe how awesome the combination of Docker and actions is because you can enable your workflow to do no matter what you're trying to do in this super baby example. We're so small. You could take like 10 seconds. Like I am here creating an action due to a simple task, like pushing a message to your logs. And the cool thing is you can use it on any the bit on this one. Like I said, we're going to use push. >>You can do, uh, even to order a pizza every time you roll into production, if you wanted, but at get hub, that'd be a lot of pizzas. And the funny thing is somebody out there is actually tried this and written that action. If you haven't used Docker and actions together, check out the docs on either get hub or Docker to get you started. And a huge shout out to all those doc writers out there. I built this demo today using those instructions. And if I can do it, I know you can too, but enough yapping let's get started to save some time. And since a lot of us are Docker and get hub nerds, I've already created a repo with a Docker file. So we're going to skip that step. Next. I'm going to create an action's Yammel file. And if you don't Yammer, you know, actions, the metadata defines my important log stuff to capture and the input and my time out per parameter to pass and puts to the Docker container, get up a build image from your Docker file and run the commands in a new container. >>Using the Sigma image. The cool thing is, is you can use any Docker image in any language for your actions. It doesn't matter if it's go or whatever in today's I'm going to use a shell script and an input variable to print my important log stuff to file. And like I said, you know me, I love me some. So let's see this action in a workflow. When an action is in a private repo, like the one I demonstrating today, the action can only be used in workflows in the same repository, but public actions can be used by workflows in any repository. So unfortunately you won't get access to the super awesome action, but don't worry in the Guild marketplace, there are over 8,000 actions available, especially the most important one, that pizza action. So go try it out. Now you can do this in a couple of ways, whether you're doing it in your preferred ID or for today's demo, I'm just going to use the gooey. I'm going to navigate to my actions tab as I've done here. And I'm going to in my workflow, select new work, hello, probably load some workflows to Claire to get you started, but I'm using the one I've copied. Like I said, the lazy developer I am in. I'm going to replace it with my action. >>That's it. So now we're going to go and we're going to start our commitment new file. Now, if we go over to our actions tab, we can see the workflow in progress in my repository. I just click the actions tab. And because they wrote the actions on push, we can watch the visualization under jobs and click the job to see the important stuff we're logging in the input stamp in the printed log. And we'll just wait for this to run. Hello, Mona and boom. Just like that. It runs automatically within our action. We told it to go run as soon as the files updated because we're doing it on push merge. That's right. Folks in just a few minutes, I built an action that writes an entry to a log file every time I push. So I don't have to do it manually. In essence, with automation, you can be kind to your future self and save time and effort to focus on what really matters. >>Imagine what I could do with even a little more time, probably order all y'all pieces. That is the power of the interconnected workflow. And it's amazing. And I hope you all go try it out, but why do we care about all of that? Just like in the demo, I took a manual task with both tape, which both takes time and it's easy to forget and automated it. So I don't have to think about it. And it's executed every time consistently. That means less time for me to worry about my human errors and mistakes, and more time to focus on actually building the cool stuff that people want. Obviously, automation, developer productivity, but what is even more important to me is the developer happiness tools like BS, code actions, Docker, Heroku, and many others reduce manual work, which allows us to focus on building things that are awesome. >>And to get into that wonderful state that we call flow. According to research by UC Irvine in Humboldt university in Germany, it takes an average of 23 minutes to enter optimal creative state. What we call the flow or to reenter it after distraction like your dog on your office store. So staying in flow is so critical to developer productivity and as a developer, it just feels good to be cranking away at something with deep focus. I certainly know that I love that feeling intuitive collaboration and automation features we built in to get hub help developer, Sam flow, allowing you and your team to do so much more, to bring the benefits of automation into perspective in our annual October's report by Dr. Nicole, Forsgren. One of my buddies here at get hub, took a look at the developer productivity in the stork year. You know what we found? >>We found that public GitHub repositories that use the Automational pull requests, merge those pull requests. 1.2 times faster. And the number of pooled merged pull requests increased by 1.3 times, that is 34% more poor requests merged. And other words, automation can con can dramatically increase, but the speed and quantity of work completed in any role, just like an open source development, you'll work more efficiently with greater impact when you invest the bulk of your time in the work that adds the most value and eliminate or outsource the rest because you don't need to do it, make the machines by elaborate by leveraging automation in their workflows teams, minimize manual work and reclaim that time for innovation and maintain that state of flow with development and collaboration. More importantly, their work is more enjoyable because they're not wasting the time doing the things that the machines or robots can do for them. >>And I remember what I said at the beginning. Many of us want to be efficient, heck even lazy. So why would I spend my time doing something I can automate? Now you can read more about this research behind the art behind this at October set, get hub.com, which also includes a lot of other cool info about the open source ecosystem and how it's evolving. Speaking of the open source ecosystem we at get hub are so honored to be the home of more than 65 million developers who build software together for everywhere across the globe. Today, we're seeing software development taking shape as the world's largest team sport, where development teams collaborate, build and ship products. It's no longer a solo effort like it was for me. You don't have to take my word for it. Check out this globe. This globe shows real data. Every speck of light you see here represents a contribution to an open source project, somewhere on earth. >>These arts reach across continents, cultures, and other divides. It's distributed collaboration at its finest. 20 years ago, we had no concept of dev ops, SecOps and lots, or the new ops that are going to be happening. But today's development and ops teams are connected like ever before. This is only going to continue to evolve at a rapid pace, especially as we continue to empower the next hundred million developers, automation helps us focus on what's important and to greatly accelerate innovation. Just this past year, we saw some of the most groundbreaking technological advancements and achievements I'll say ever, including critical COVID-19 vaccine trials, as well as the first power flight on Mars. This past month, these breakthroughs were only possible because of the interconnected collaborative open source communities on get hub and the amazing tools and workflows that empower us all to create and innovate. Let's continue building, integrating, and automating. So we collectively can give developers the experience. They deserve all of the automation and beautiful eye UIs that we can muster so they can continue to build the things that truly do change the world. Thank you again for having me today, Dr. Khan, it has been a pleasure to be here with all you nerds. >>Hello. I'm Justin. Komack lovely to see you here. Talking to developers, their world is getting much more complex. Developers are being asked to do everything security ops on goal data analysis, all being put on the rockers. Software's eating the world. Of course, and this all make sense in that view, but they need help. One team. I told you it's shifted all our.net apps to run on Linux from windows, but their developers found the complexity of Docker files based on the Linux shell scripts really difficult has helped make these things easier for your teams. Your ones collaborate more in a virtual world, but you've asked us to make this simpler and more lightweight. You, the developers have asked for a paved road experience. You want things to just work with a simple options to be there, but it's not just the paved road. You also want to be able to go off-road and do interesting and different things. >>Use different components, experiments, innovate as well. We'll always offer you both those choices at different times. Different developers want different things. It may shift for ones the other paved road or off road. Sometimes you want reliability, dependability in the zone for day to day work, but sometimes you have to do something new, incorporate new things in your pipeline, build applications for new places. Then you knew those off-road abilities too. So you can really get under the hood and go and build something weird and wonderful and amazing. That gives you new options. Talk as an independent choice. We don't own the roads. We're not pushing you into any technology choices because we own them. We're really supporting and driving open standards, such as ISEI working opensource with the CNCF. We want to help you get your applications from your laptops, the clouds, and beyond, even into space. >>Let's talk about the key focus areas, that frame, what DACA is doing going forward. These are simplicity, sharing, flexibility, trusted content and care supply chain compared to building where the underlying kernel primitives like namespaces and Seagraves the original Docker CLI was just amazing Docker engine. It's a magical experience for everyone. It really brought those innovations and put them in a world where anyone would use that, but that's not enough. We need to continue to innovate. And it was trying to get more done faster all the time. And there's a lot more we can do. We're here to take complexity away from deeply complicated underlying things and give developers tools that are just amazing and magical. One of the area we haven't done enough and make things magical enough that we're really planning around now is that, you know, Docker images, uh, they're the key parts of your application, but you know, how do I do something with an image? How do I, where do I attach volumes with this image? What's the API. Whereas the SDK for this image, how do I find an example or docs in an API driven world? Every bit of software should have an API and an API description. And our vision is that every container should have this API description and the ability for you to understand how to use it. And it's all a seamless thing from, you know, from your code to the cloud local and remote, you can, you can use containers in this amazing and exciting way. >>One thing I really noticed in the last year is that companies that started off remote fast have constant collaboration. They have zoom calls, apron all day terminals, shattering that always working together. Other teams are really trying to learn how to do this style because they didn't start like that. We used to walk around to other people's desks or share services on the local office network. And it's very difficult to do that anymore. You want sharing to be really simple, lightweight, and informal. Let me try your container or just maybe let's collaborate on this together. Um, you know, fast collaboration on the analysts, fast iteration, fast working together, and he wants to share more. You want to share how to develop environments, not just an image. And we all work by seeing something someone else in our team is doing saying, how can I do that too? I can, I want to make that sharing really, really easy. Ben's going to talk about this more in the interest of one minute. >>We know how you're excited by apple. Silicon and gravis are not excited because there's a new architecture, but excited because it's faster, cooler, cheaper, better, and offers new possibilities. The M one support was the most asked for thing on our public roadmap, EFA, and we listened and share that we see really exciting possibilities, usership arm applications, all the way from desktop to production. We know that you all use different clouds and different bases have deployed to, um, you know, we work with AWS and Azure and Google and more, um, and we want to help you ship on prime as well. And we know that you use huge number of languages and the containers help build applications that use different languages for different parts of the application or for different applications, right? You can choose the best tool. You have JavaScript hat or everywhere go. And re-ask Python for data and ML, perhaps getting excited about WebAssembly after hearing about a cube con, you know, there's all sorts of things. >>So we need to make that as easier. We've been running the whole month of Python on the blog, and we're doing a month of JavaScript because we had one specific support about how do I best put this language into production of that language into production. That detail is important for you. GPS have been difficult to use. We've added GPS suppose in desktop for windows, but we know there's a lot more to do to make the, how multi architecture, multi hardware, multi accelerator world work better and also securely. Um, so there's a lot more work to do to support you in all these things you want to do. >>How do we start building a tenor has applications, but it turns out we're using existing images as components. I couldn't assist survey earlier this year, almost half of container image usage was public images rather than private images. And this is growing rapidly. Almost all software has open source components and maybe 85% of the average application is open source code. And what you're doing is taking whole container images as modules in your application. And this was always the model with Docker compose. And it's a model that you're already et cetera, writing you trust Docker, official images. We know that they might go to 25% of poles on Docker hub and Docker hub provides you the widest choice and the best support that trusted content. We're talking to people about how to make this more helpful. We know, for example, that winter 69 four is just showing us as support, but the image doesn't yet tell you that we're working with canonical to improve messaging from specific images about left lifecycle and support. >>We know that you need more images, regularly updated free of vulnerabilities, easy to use and discover, and Donnie and Marie neuro, going to talk about that more this last year, the solar winds attack has been in the, in the news. A lot, the software you're using and trusting could be compromised and might be all over your organization. We need to reduce the risk of using vital open-source components. We're seeing more software supply chain attacks being targeted as the supply chain, because it's often an easier place to attack and production software. We need to be able to use this external code safely. We need to, everyone needs to start from trusted sources like photography images. They need to scan for known vulnerabilities using Docker scan that we built in partnership with sneak and lost DockerCon last year, we need just keep updating base images and dependencies, and we'll, we're going to help you have the control and understanding about your images that you need to do this. >>And there's more, we're also working on the nursery V2 project in the CNCF to revamp container signings, or you can tell way or software comes from we're working on tooling to make updates easier, and to help you understand and manage all the principals carrier you're using security is a growing concern for all of us. It's really important. And we're going to help you work with security. We can't achieve all our dreams, whether that's space travel or amazing developer products ever see without deep partnerships with our community to cloud is RA and the cloud providers aware most of you ship your occasion production and simple routes that take your work and deploy it easily. Reliably and securely are really important. Just get into production simply and easily and securely. And we've done a bunch of work on that. And, um, but we know there's more to do. >>The CNCF on the open source cloud native community are an amazing ecosystem of creators and lovely people creating an amazing strong community and supporting a huge amount of innovation has its roots in the container ecosystem and his dreams beyond that much of the innovation is focused around operate experience so far, but developer experience is really a growing concern in that community as well. And we're really excited to work on that. We also uses appraiser tool. Then we know you do, and we know that you want it to be easier to use in your environment. We just shifted Docker hub to work on, um, Kubernetes fully. And, um, we're also using many of the other projects are Argo from atheists. We're spending a lot of time working with Microsoft, Amazon right now on getting natural UV to ready to ship in the next few. That's a really detailed piece of collaboration we've been working on for a long term. Long time is really important for our community as the scarcity of the container containers and, um, getting content for you, working together makes us stronger. Our community is made up of all of you have. Um, it's always amazing to be reminded of that as a huge open source community that we already proud to work with. It's an amazing amount of innovation that you're all creating and where perhaps it, what with you and share with you as well. Thank you very much. And thank you for being here. >>Really excited to talk to you today and share more about what Docker is doing to help make you faster, make your team faster and turn your application delivery into something that makes you a 10 X team. What we're hearing from you, the developers using Docker everyday fits across three common themes that we hear consistently over and over. We hear that your time is super important. It's critical, and you want to move faster. You want your tools to get out of your way, and instead to enable you to accelerate and focus on the things you want to be doing. And part of that is that finding great content, great application components that you can incorporate into your apps to move faster is really hard. It's hard to discover. It's hard to find high quality content that you can trust that, you know, passes your test and your configuration needs. >>And it's hard to create good content as well. And you're looking for more safety, more guardrails to help guide you along that way so that you can focus on creating value for your company. Secondly, you're telling us that it's a really far to collaborate effectively with your team and you want to do more, to work more effectively together to help your tools become more and more seamless to help you stay in sync, both with yourself across all of your development environments, as well as with your teammates so that you can more effectively collaborate together. Review each other's work, maintain things and keep them in sync. And finally, you want your applications to run consistently in every single environment, whether that's your local development environment, a cloud-based development environment, your CGI pipeline, or the cloud for production, and you want that micro service to provide that consistent experience everywhere you go so that you have similar tools, similar environments, and you don't need to worry about things getting in your way, but instead things make it easy for you to focus on what you wanna do and what Docker is doing to help solve all of these problems for you and your colleagues is creating a collaborative app dev platform. >>And this collaborative application development platform consists of multiple different pieces. I'm not going to walk through all of them today, but the overall view is that we're providing all the tooling you need from the development environment, to the container images, to the collaboration services, to the pipelines and integrations that enable you to focus on making your applications amazing and changing the world. If we start zooming on a one of those aspects, collaboration we hear from developers regularly is that they're challenged in synchronizing their own setups across environments. They want to be able to duplicate the setup of their teammates. Look, then they can easily get up and running with the same applications, the same tooling, the same version of the same libraries, the same frameworks. And they want to know if their applications are good before they're ready to share them in an official space. >>They want to collaborate on things before they're done, rather than feeling like they have to officially published something before they can effectively share it with others to work on it, to solve this. We're thrilled today to announce Docker, dev environments, Docker, dev environments, transform how your team collaborates. They make creating, sharing standardized development environments. As simple as a Docker poll, they make it easy to review your colleagues work without affecting your own work. And they increase the reproducibility of your own work and decreased production issues in doing so because you've got consistent environments all the way through. Now, I'm going to pass it off to our principal product manager, Ben Gotch to walk you through more detail on Docker dev environments. >>Hi, I'm Ben. I work as a principal program manager at DACA. One of the areas that doc has been looking at to see what's hard today for developers is sharing changes that you make from the inner loop where the inner loop is a better development, where you write code, test it, build it, run it, and ultimately get feedback on those changes before you merge them and try and actually ship them out to production. Most amount of us build this flow and get there still leaves a lot of challenges. People need to jump between branches to look at each other's work. Independence. Dependencies can be different when you're doing that and doing this in this new hybrid wall of work. Isn't any easier either the ability to just save someone, Hey, come and check this out. It's become much harder. People can't come and sit down at your desk or take your laptop away for 10 minutes to just grab and look at what you're doing. >>A lot of the reason that development is hard when you're remote, is that looking at changes and what's going on requires more than just code requires all the dependencies and everything you've got set up and that complete context of your development environment, to understand what you're doing and solving this in a remote first world is hard. We wanted to look at how we could make this better. Let's do that in a way that let you keep working the way you do today. Didn't want you to have to use a browser. We didn't want you to have to use a new idea. And we wanted to do this in a way that was application centric. We wanted to let you work with all the rest of the application already using C for all the services and all those dependencies you need as part of that. And with that, we're excited to talk more about docket developer environments, dev environments are new part of the Docker experience that makes it easier you to get started with your whole inner leap, working inside a container, then able to share and collaborate more than just the code. >>We want it to enable you to share your whole modern development environment, your whole setup from DACA, with your team on any operating system, we'll be launching a limited beta of dev environments in the coming month. And a GA dev environments will be ID agnostic and supporting composts. This means you'll be able to use an extend your existing composed files to create your own development environment in whatever idea, working in dev environments designed to be local. First, they work with Docker desktop and say your existing ID, and let you share that whole inner loop, that whole development context, all of your teammates in just one collect. This means if you want to get feedback on the working progress change or the PR it's as simple as opening another idea instance, and looking at what your team is working on because we're using compose. You can just extend your existing oppose file when you're already working with, to actually create this whole application and have it all working in the context of the rest of the services. >>So it's actually the whole environment you're working with module one service that doesn't really understand what it's doing alone. And with that, let's jump into a quick demo. So you can see here, two dev environments up and running. First one here is the same container dev environment. So if I want to go into that, let's see what's going on in the various code button here. If that one open, I can get straight into my application to start making changes inside that dev container. And I've got all my dependencies in here, so I can just run that straight in that second application I have here is one that's opened up in compose, and I can see that I've also got my backend, my front end and my database. So I've got all my services running here. So if I want, I can open one or more of these in a dev environment, meaning that that container has the context that dev environment has the context of the whole application. >>So I can get back into and connect to all the other services that I need to test this application properly, all of them, one unit. And then when I've made my changes and I'm ready to share, I can hit my share button type in the refund them on to share that too. And then give that image to someone to get going, pick that up and just start working with that code and all my dependencies, simple as putting an image, looking ahead, we're going to be expanding development environments, more of your dependencies for the whole developer worst space. We want to look at backing up and letting you share your volumes to make data science and database setups more repeatable and going. I'm still all of this under a single workspace for your team containing images, your dev environments, your volumes, and more we've really want to allow you to create a fully portable Linux development environment. >>So everyone you're working with on any operating system, as I said, our MVP we're coming next month. And that was for vs code using their dev container primitive and more support for other ideas. We'll follow to find out more about what's happening and what's coming up next in the future of this. And to actually get a bit of a deeper dive in the experience. Can we check out the talk I'm doing with Georgie and girl later on today? Thank you, Ben, amazing story about how Docker is helping to make developer teams more collaborative. Now I'd like to talk more about applications while the dev environment is like the workbench around what you're building. The application itself has all the different components, libraries, and frameworks, and other code that make up the application itself. And we hear developers saying all the time things like, how do they know if their images are good? >>How do they know if they're secure? How do they know if they're minimal? How do they make great images and great Docker files and how do they keep their images secure? And up-to-date on every one of those ties into how do I create more trust? How do I know that I'm building high quality applications to enable you to do this even more effectively than today? We are pleased to announce the DACA verified polisher program. This broadens trusted content by extending beyond Docker official images, to give you more and more trusted building blocks that you can incorporate into your applications. It gives you confidence that you're getting what you expect because Docker verifies every single one of these publishers to make sure they are who they say they are. This improves our secure supply chain story. And finally it simplifies your discovery of the best building blocks by making it easy for you to find things that you know, you can trust so that you can incorporate them into your applications and move on and on the right. You can see some examples of the publishers that are involved in Docker, official images and our Docker verified publisher program. Now I'm pleased to introduce you to marina. Kubicki our senior product manager who will walk you through more about what we're doing to create a better experience for you around trust. >>Thank you, Dani, >>Mario Andretti, who is a famous Italian sports car driver. One said that if everything feels under control, you're just not driving. You're not driving fast enough. Maya Andretti is not a software developer and a software developers. We know that no matter how fast we need to go in order to drive the innovation that we're working on, we can never allow our applications to spin out of control and a Docker. As we continue talking to our, to the developers, what we're realizing is that in order to reach that speed, the developers are the, the, the development community is looking for the building blocks and the tools that will, they will enable them to drive at the speed that they need to go and have the trust in those building blocks. And in those tools that they will be able to maintain control over their applications. So as we think about some of the things that we can do to, to address those concerns, uh, we're realizing that we can pursue them in a number of different venues, including creating reliable content, including creating partnerships that expands the options for the reliable content. >>Um, in order to, in a we're looking at creating integrations, no link security tools, talk about the reliable content. The first thing that comes to mind are the Docker official images, which is a program that we launched several years ago. And this is a set of curated, actively maintained, open source images that, uh, include, uh, operating systems and databases and programming languages. And it would become immensely popular for, for, for creating the base layers of, of the images of, of the different images, images, and applications. And would we realizing that, uh, many developers are, instead of creating something from scratch, basically start with one of the official images for their basis, and then build on top of that. And this program has become so popular that it now makes up a quarter of all of the, uh, Docker poles, which essentially ends up being several billion pulse every single month. >>As we look beyond what we can do for the open source. Uh, we're very ability on the open source, uh, spectrum. We are very excited to announce that we're launching the Docker verified publishers program, which is continuing providing the trust around the content, but now working with, uh, some of the industry leaders, uh, in multiple, in multiple verticals across the entire technology technical spec, it costs entire, uh, high tech in order to provide you with more options of the images that you can use for building your applications. And it still comes back to trust that when you are searching for content in Docker hub, and you see the verified publisher badge, you know, that this is, this is the content that, that is part of the, that comes from one of our partners. And you're not running the risk of pulling the malicious image from an employee master source. >>As we look beyond what we can do for, for providing the reliable content, we're also looking at some of the tools and the infrastructure that we can do, uh, to create a security around the content that you're creating. So last year at the last ad, the last year's DockerCon, we announced partnership with sneak. And later on last year, we launched our DACA, desktop and Docker hub vulnerability scans that allow you the options of writing scans in them along multiple points in your dev cycle. And in addition to providing you with information on the vulnerability on, on the vulnerabilities, in, in your code, uh, it also provides you with a guidance on how to re remediate those vulnerabilities. But as we look beyond the vulnerability scans, we're also looking at some of the other things that we can do, you know, to, to, to, uh, further ensure that the integrity and the security around your images, your images, and with that, uh, later on this year, we're looking to, uh, launch the scope, personal access tokens, and instead of talking about them, I will simply show you what they look like. >>So if you can see here, this is my page in Docker hub, where I've created a four, uh, tokens, uh, read-write delete, read, write, read only in public read in public creeper read only. So, uh, earlier today I went in and I, I logged in, uh, with my read only token. And when you see, when I'm going to pull an image, it's going to allow me to pull an image, not a problem success. And then when I do the next step, I'm going to ask to push an image into the same repo. Uh, would you see is that it's going to give me an error message saying that they access is denied, uh, because there is an additional authentication required. So these are the things that we're looking to add to our roadmap. As we continue thinking about the things that we can do to provide, um, to provide additional building blocks, content, building blocks, uh, and, and, and tools to build the trust so that our DACA developer and skinned code faster than Mario Andretti could ever imagine. Uh, thank you to >>Thank you, marina. It's amazing what you can do to improve the trusted content so that you can accelerate your development more and move more quickly, move more collaboratively and build upon the great work of others. Finally, we hear over and over as that developers are working on their applications that they're looking for, environments that are consistent, that are the same as production, and that they want their applications to really run anywhere, any environment, any architecture, any cloud one great example is the recent announcement of apple Silicon. We heard from developers on uproar that they needed Docker to be available for that architecture before they could add those to it and be successful. And we listened. And based on that, we are pleased to share with you Docker, desktop on apple Silicon. This enables you to run your apps consistently anywhere, whether that's developing on your team's latest dev hardware, deploying an ARM-based cloud environments and having a consistent architecture across your development and production or using multi-year architecture support, which enables your whole team to collaborate on its application, using private repositories on Docker hub, and thrilled to introduce you to Hughie cower, senior director for product management, who will walk you through more of what we're doing to create a great developer experience. >>Senior director of product management at Docker. And I'd like to jump straight into a demo. This is the Mac mini with the apple Silicon processor. And I want to show you how you can now do an end-to-end arm workflow from my M one Mac mini to raspberry PI. As you can see, we have vs code and Docker desktop installed on a, my, the Mac mini. I have a small example here, and I have a raspberry PI three with an led strip, and I want to turn those LEDs into a moving rainbow. This Dockerfile here, builds the application. We build the image with the Docker, build X command to make the image compatible for all raspberry pies with the arm. 64. Part of this build is built with the native power of the M one chip. I also add the push option to easily share the image with my team so they can give it a try to now Dr. >>Creates the local image with the application and uploads it to Docker hub after we've built and pushed the image. We can go to Docker hub and see the new image on Docker hub. You can also explore a variety of images that are compatible with arm processors. Now let's go to the raspberry PI. I have Docker already installed and it's running Ubuntu 64 bit with the Docker run command. I can run the application and let's see what will happen from there. You can see Docker is downloading the image automatically from Docker hub and when it's running, if it's works right, there are some nice colors. And with that, if we have an end-to-end workflow for arm, where continuing to invest into providing you a great developer experience, that's easy to install. Easy to get started with. As you saw in the demo, if you're interested in the new Mac, mini are interested in developing for our platforms in general, we've got you covered with the same experience you've come to expect from Docker with over 95,000 arm images on hub, including many Docker official images. >>We think you'll find what you're looking for. Thank you again to the community that helped us to test the tech previews. We're so delighted to hear when folks say that the new Docker desktop for apple Silicon, it just works for them, but that's not all we've been working on. As Dani mentioned, consistency of developer experience across environments is so important. We're introducing composed V2 that makes compose a first-class citizen in the Docker CLI you no longer need to install a separate composed biter in order to use composed, deploying to production is simpler than ever with the new compose integration that enables you to deploy directly to Amazon ECS or Azure ACI with the same methods you use to run your application locally. If you're interested in running slightly different services, when you're debugging versus testing or, um, just general development, you can manage that all in one place with the new composed service to hear more about what's new and Docker desktop, please join me in the three 15 breakout session this afternoon. >>And now I'd love to tell you a bit more about bill decks and convince you to try it. If you haven't already it's our next gen build command, and it's no longer experimental as shown in the demo with built X, you'll be able to do multi architecture builds, share those builds with your team and the community on Docker hub. With build X, you can speed up your build processes with remote caches or build all the targets in your composed file in parallel with build X bake. And there's so much more if you're using Docker, desktop or Docker, CE you can use build X checkout tonus is talk this afternoon at three 45 to learn more about build X. And with that, I hope everyone has a great Dr. Khan and back over to you, Donnie. >>Thank you UA. It's amazing to hear about what we're doing to create a better developer experience and make sure that Docker works everywhere you need to work. Finally, I'd like to wrap up by showing you everything that we've announced today and everything that we've done recently to make your lives better and give you more and more for the single price of your Docker subscription. We've announced the Docker verified publisher program we've announced scoped personal access tokens to make it easier for you to have a secure CCI pipeline. We've announced Docker dev environments to improve your collaboration with your team. Uh, we shared with you Docker, desktop and apple Silicon, to make sure that, you know, Docker runs everywhere. You need it to run. And we've announced Docker compose version two, finally making it a first-class citizen amongst all the other great Docker tools. And we've done so much more recently as well from audit logs to advanced image management, to compose service profiles, to improve where you can run Docker more easily. >>Finally, as we look forward, where we're headed in the upcoming year is continuing to invest in these themes of helping you build, share, and run modern apps more effectively. We're going to be doing more to help you create a secure supply chain with which only grows more and more important as time goes on. We're going to be optimizing your update experience to make sure that you can easily understand the current state of your application, all its components and keep them all current without worrying about breaking everything as you're doing. So we're going to make it easier for you to synchronize your work. Using cloud sync features. We're going to improve collaboration through dev environments and beyond, and we're going to do make it easy for you to run your microservice in your environments without worrying about things like architecture or differences between those environments. Thank you so much. I'm thrilled about what we're able to do to help make your lives better. And now you're going to be hearing from one of our customers about what they're doing to launch their business with Docker >>I'm Matt Falk, I'm the head of engineering and orbital insight. And today I want to talk to you a little bit about data from space. So who am I like many of you, I'm a software developer and a software developer about seven companies so far, and now I'm a head of engineering. So I spend most of my time doing meetings, but occasionally I'll still spend time doing design discussions, doing code reviews. And in my free time, I still like to dabble on things like project oiler. So who's Oberlin site. What do we do? Portal insight is a large data supplier and analytics provider where we take data geospatial data anywhere on the planet, any overhead sensor, and translate that into insights for the end customer. So specifically we have a suite of high performance, artificial intelligence and machine learning analytics that run on this geospatial data. >>And we build them to specifically determine natural and human service level activity anywhere on the planet. What that really means is we take any type of data associated with a latitude and longitude and we identify patterns so that we can, so we can detect anomalies. And that's everything that we do is all about identifying those patterns to detect anomalies. So more specifically, what type of problems do we solve? So supply chain intelligence, this is one of the use cases that we we'd like to talk about a lot. It's one of our main primary verticals that we go after right now. And as Scott mentioned earlier, this had a huge impact last year when COVID hit. So specifically supply chain intelligence is all about identifying movement patterns to and from operating facilities to identify changes in those supply chains. How do we do this? So for us, we can do things where we track the movement of trucks. >>So identifying trucks, moving from one location to another in aggregate, same thing we can do with foot traffic. We can do the same thing for looking at aggregate groups of people moving from one location to another and analyzing their patterns of life. We can look at two different locations to determine how people are moving from one location to another, or going back and forth. All of this is extremely valuable for detecting how a supply chain operates and then identifying the changes to that supply chain. As I said last year with COVID, everything changed in particular supply chains changed incredibly, and it was hugely important for customers to know where their goods or their products are coming from and where they were going, where there were disruptions in their supply chain and how that's affecting their overall supply and demand. So to use our platform, our suite of tools, you can start to gain a much better picture of where your suppliers or your distributors are going from coming from or going to. >>So what's our team look like? So my team is currently about 50 engineers. Um, we're spread into four different teams and the teams are structured like this. So the first team that we have is infrastructure engineering and this team largely deals with deploying our Dockers using Kubernetes. So this team is all about taking Dockers, built by other teams, sometimes building the Dockers themselves and putting them into our production system, our platform engineering team, they produce these microservices. So they produce microservice, Docker images. They develop and test with them locally. Their entire environments are dockerized. They produce these doctors, hand them over to him for infrastructure engineering to be deployed. Similarly, our product engineering team does the same thing. They develop and test with Dr. Locally. They also produce a suite of Docker images that the infrastructure team can then deploy. And lastly, we have our R and D team, and this team specifically produces machine learning algorithms using Nvidia Docker collectively, we've actually built 381 Docker repositories and 14 million. >>We've had 14 million Docker pools over the lifetime of the company, just a few stats about us. Um, but what I'm really getting to here is you can see actually doctors becoming almost a form of communication between these teams. So one of the paradigms in software engineering that you're probably familiar with encapsulation, it's really helpful for a lot of software engineering problems to break the problem down, isolate the different pieces of it and start building interfaces between the code. This allows you to scale different pieces of the platform or different pieces of your code in different ways that allows you to scale up certain pieces and keep others at a smaller level so that you can meet customer demands. And for us, one of the things that we can largely do now is use Dockers as that interface. So instead of having an entire platform where all teams are talking to each other, and everything's kind of, mishmashed in a monolithic application, we can now say this team is only able to talk to this team by passing over a particular Docker image that defines the interface of what needs to be built before it passes to the team and really allows us to scalp our development and be much more efficient. >>Also, I'd like to say we are hiring. Um, so we have a number of open roles. We have about 30 open roles in our engineering team that we're looking to fill by the end of this year. So if any of this sounds really interesting to you, please reach out after the presentation. >>So what does our platform do? Really? Our platform allows you to answer any geospatial question, and we do this at three different inputs. So first off, where do you want to look? So we did this as what we call an AOI or an area of interest larger. You can think of this as a polygon drawn on the map. So we have a curated data set of almost 4 million AOIs, which you can go and you can search and use for your analysis, but you're also free to build your own. Second question is what you want to look for. We do this with the more interesting part of our platform of our machine learning and AI capabilities. So we have a suite of algorithms that automatically allow you to identify trucks, buildings, hundreds of different types of aircraft, different types of land use, how many people are moving from one location to another different locations that people in a particular area are moving to or coming from all of these different analyses or all these different analytics are available at the click of a button, and then determine what you want to look for. >>Lastly, you determine when you want to find what you're looking for. So that's just, uh, you know, do you want to look for the next three hours? Do you want to look for the last week? Do you want to look every month for the past two, whatever the time cadence is, you decide that you hit go and out pops a time series, and that time series tells you specifically where you want it to look what you want it to look for and how many, or what percentage of the thing you're looking for appears in that area. Again, we do all of this to work towards patterns. So we use all this data to produce a time series from there. We can look at it, determine the patterns, and then specifically identify the anomalies. As I mentioned with supply chain, this is extremely valuable to identify where things change. So we can answer these questions, looking at a particular operating facility, looking at particular, what is happening with the level of activity is at that operating facility where people are coming from, where they're going to, after visiting that particular facility and identify when and where that changes here, you can just see it's a picture of our platform. It's actually showing all the devices in Manhattan, um, over a period of time. And it's more of a heat map view. So you can actually see the hotspots in the area. >>So really the, and this is the heart of the talk, but what happened in 2020? So for men, you know, like many of you, 2020 was a difficult year COVID hit. And that changed a lot of what we're doing, not from an engineering perspective, but also from an entire company perspective for us, the motivation really became to make sure that we were lowering our costs and increasing innovation simultaneously. Now those two things often compete with each other. A lot of times you want to increase innovation, that's going to increase your costs, but the challenge last year was how to do both simultaneously. So here's a few stats for you from our team. In Q1 of last year, we were spending almost $600,000 per month on compute costs prior to COVID happening. That wasn't hugely a concern for us. It was a lot of money, but it wasn't as critical as it was last year when we really needed to be much more efficient. >>Second one is flexibility for us. We were deployed on a single cloud environment while we were cloud thought ready, and that was great. We want it to be more flexible. We want it to be on more cloud environments so that we could reach more customers. And also eventually get onto class side networks, extending the base of our customers as well from a custom analytics perspective. This is where we get into our traction. So last year, over the entire year, we computed 54,000 custom analytics for different users. We wanted to make sure that this number was steadily increasing despite us trying to lower our costs. So we didn't want the lowering cost to come as the sacrifice of our user base. Lastly, of particular percentage here that I'll say definitely needs to be improved is 75% of our projects never fail. So this is where we start to get into a bit of stability of our platform. >>Now I'm not saying that 25% of our projects fail the way we measure this is if you have a particular project or computation that runs every day and any one of those runs sale account, that is a failure because from an end-user perspective, that's an issue. So this is something that we know we needed to improve on and we needed to grow and make our platform more stable. I'm going to something that we really focused on last year. So where are we now? So now coming out of the COVID valley, we are starting to soar again. Um, we had, uh, back in April of last year, we had the entire engineering team. We actually paused all development for about four weeks. You had everyone focused on reducing our compute costs in the cloud. We got it down to 200 K over the period of a few months. >>And for the next 12 months, we hit that number every month. This is huge for us. This is extremely important. Like I said, in the COVID time period where costs and operating efficiency was everything. So for us to do that, that was a huge accomplishment last year and something we'll keep going forward. One thing I would actually like to really highlight here, two is what allowed us to do that. So first off, being in the cloud, being able to migrate things like that, that was one thing. And we were able to use there's different cloud services in a more particular, in a more efficient way. We had a very detailed tracking of how we were spending things. We increased our data retention policies. We optimized our processing. However, one additional piece was switching to new technologies on, in particular, we migrated to get lab CICB. >>Um, and this is something that the costs we use Docker was extremely, extremely easy. We didn't have to go build new new code containers or repositories or change our code in order to do this. We were simply able to migrate the containers over and start using a new CIC so much. In fact, that we were able to do that migration with three engineers in just two weeks from a cloud environment and flexibility standpoint, we're now operating in two different clouds. We were able to last night, I've over the last nine months to operate in the second cloud environment. And again, this is something that Docker helped with incredibly. Um, we didn't have to go and build all new interfaces to all new, different services or all different tools in the next cloud provider. All we had to do was build a base cloud infrastructure that ups agnostic the way, all the different details of the cloud provider. >>And then our doctors just worked. We can move them to another environment up and running, and our platform was ready to go from a traction perspective. We're about a third of the way through the year. At this point, we've already exceeded the amount of customer analytics we produce last year. And this is thanks to a ton more albums, that whole suite of new analytics that we've been able to build over the past 12 months and we'll continue to build going forward. So this is really, really great outcome for us because we were able to show that our costs are staying down, but our analytics and our customer traction, honestly, from a stability perspective, we improved from 75% to 86%, not quite yet 99 or three nines or four nines, but we are getting there. Um, and this is actually thanks to really containerizing and modularizing different pieces of our platform so that we could scale up in different areas. This allowed us to increase that stability. This piece of the code works over here, toxin an interface to the rest of the system. We can scale this piece up separately from the rest of the system, and that allows us much more easily identify issues in the system, fix those and then correct the system overall. So basically this is a summary of where we were last year, where we are now and how much more successful we are now because of the issues that we went through last year and largely brought on by COVID. >>But that this is just a screenshot of the, our, our solution actually working on supply chain. So this is in particular, it is showing traceability of a distribution warehouse in salt lake city. It's right in the center of the screen here. You can see the nice kind of orange red center. That's a distribution warehouse and all the lines outside of that, all the dots outside of that are showing where people are, where trucks are moving from that location. So this is really helpful for supply chain companies because they can start to identify where their suppliers are, are coming from or where their distributors are going to. So with that, I want to say, thanks again for following along and enjoy the rest of DockerCon.

>>Live from Denver, Colorado. It's the cube covering com vault go 2019 brought to you by Combolt. >>Welcome to the cube. Lisa Martin with Stu Miniman. We are in Denver, Colorado, specifically Aurora, actually for the fourth annual comm vault. Go. Stu, I'm super excited to be back hosting with you again. Lisa, it's great to be with you our second year doing Convolt go last year. Keith Townsend with here with me and so glad you're here with me because you've got a little bit of background with this company I was with come out 10 years ago. It's scary to think that it's been 10 years that we're at the Gaylord Gaylord Rockies, which is one of their customers, massive conventions that aren't, as you said, the first conference that the Gaylord that probably heard that this, this convention center just opened up a couple of months ago. I think it holds like 1500 people, the 1500 rooms at the hotel and supposedly this is the first large event that they've done and this was planned last year. >>Last year we were in Nashville at the Gaylord the year before. I think they were in DC at the Gaylord and next year I know there'll be at another Gaylord, so definitely putting their customers first. Just like in the keynote this morning they had the state of Colorado opening up the event. We always love to hear a local customer welcoming us and talking about their partnership with the supplier. Absolutely agree with that. The state of Colorado, the statue share the highest number of micro breweries per capita and I don't know about you, I'm not a beer person. I would be super blown away if that, if I was there is the too much choice in beer. It used to be, you know, you'd go in and say, okay, here's the five or 10 beers I like. Now you go in and it's like, all right, there's a hundred new ones. I haven't tried that because they weren't here last time. >>So many beers here, a greater Denver. I've been to Boulder a couple of times. They say if you want to start a microbrewery, there's one that's ready to hand you over a place because they're going out of business. They just churn and go over and everything like that. So yeah, my first time actually hosting an event of the cube here in Colorado. Super excited for that. It's a great locale. And yeah, we're talking about, you know, so Convolt a 20 year old company, a lot of customers, but a lot of new faces. You look, we're going to be talking to the next two days. They run a whole new executive team. We knew this was coming last year. Our final guest in our two days is going to be Al Bunty, who is the CEO, was one of the original 20 years with the company. So we'll, we'll talk about the Baton and some of the changes in some of the things that are, are the same. >>So yeah. Interesting. You mentioned they started things off this morning with the customer at the state of Colorado. I too, like you always love to hear the voice of the customer. And I also really like it when customers talk about the challenges that they had. They talked about the Samsung attack and all of the exposures and vulnerabilities. I love that because that's what happens. We're seeing data protection as a service, the market positive trends in the market. There are a rise in cyber attacks. I love it when customers articulate, yep, nothing is perfect, but here's how working with Combalt we were able to recover quickly from something like that. A lot of big news, you mentioned a lot of new executive leadership. This is Sanjay merchant Donnie's first go. As CEO came in about nine months ago. He's a cube alumni, said we'll get to talk to him later this morning, but he came in after successfully leading puppet through many rounds of millions and venture funding. >>He took puppet worldwide, but he came into a company with declining revenues and one where folks said combat, you've got pressures to find alternative sources of growth. They said three things specifically. One, you need to upgrade your sales force. Two, you need to enhance your marketing, and three, we need to shift gears and expand your market share and there's been a whole bunch of news, not just yesterday, today, but in the last month or so, last few weeks actually where combo is making headway in all three of them. >> At least so right, because you look on paper and you look in the key, the keynote and say we have 20 years of experience. Here's all of the analyst reports that show us as the clear leader in this space. But then you look at it and say, Oh, 2018 to 2019 declining revenues. There are a lot of competitors both as some of the big stalwarts in technology as well as many startups. >>Heck, I'm even seeing the startups now. They're trying to call the last generation of startups that are going after con vault as the legacy. So if you're not fully cloud native microservice sass base architecture, you're the old way. And that's one of the news from Combolt already is they, they've done a couple of what they call Convult ventures. So the first one you were alluding to is they bought Hedvig, which was a software defined storage company. They just bought them back in September. What was their a two 40 $250 million, which was almost half of the cash that Combolt had sitting there. Hedvig company that had been around for a number of years. We're going to have Avinash who's the founder and CEO on the program here. He was on the keynote stage going through the demo. They kind of sat at this interesting line between software defined storage and actually hyperconverged infrastructure because you could in the early days do either storage only or fully converged environments, but massive scale. >>The customer that he talked about was a very large scale deployment. Those large scale deployments are really tough and can be challenging and they're not something that you just deploy everywhere. Unlike the other announcement that Convolt announced is metallic. If you go to metallic.io, they have this new sass based architecture. They built it in months from the ground up from the internal team. Part of me is sitting there saying, okay, wait, if they could do this and you know, six months or nine months or whatever it was, why hadn't they done it before? What has changed what Convolt technology is under there? It's great. It's working, you know, Azure and AWS as well as you can have a local copy in your environment. They call it SAS plus. Um, and we need to understand a little bit more of the technology. So a lot of exciting things. >>Definitely getting awareness, but both metallic and Hedvig they call Convolt ventures. So new areas, areas that they're looking to add some incremental growth. And one of the things Sandra said in his keynote is we want to, you know, rethink primary and secondary storage. So where is Convolt will they start dipping their toe into the primary storage? Does that line blur? We've got HP on the program, you know, NetApp is up on stage with them. They have partnerships. So changing landscape Convolt has long had a strong position in the market, but as things change they want to make sure that they make themselves relevant for the next era. >>Absolutely. And the Hedvig acquisition gives them a pretty significant, a much larger presence in the software defined space. But it also is going to give them a big Tam expansion. We look at metallic as you mentioned, the venture. I want to, I want to break that down. We've got Rob Kelly's, John Colussy, and on a little bit later, what is this Combolt venture, but also giving them, it sounds to me like giving customers in mid market more choice, but one of the things I mentioned that that analysts were saying is, Hey you guys, you gotta, you gotta expand your market share, you really gotta expand marketing. So we're seeing not just the technology announcements with Hedvig for the large scale enterprises of which I think most of their revenue, at least three quarters of combat revenue does come from that large space, metallic for mid market, but also some of the seals, leadership changes that they've made to are really positioning them. New initiatives, new partner initiatives, really focused on the largest global enterprises. We're gonna break some of that down today. So in terms of routes to market, you're seeing a lot of focus on mid-market and enterprise. >>Well, at least 80% of the convulse revenue comes from the partners. So that is hugely important. How does metallic fit in? Will that be as a SAS offering? Will that be direct? Will that go through the channel? Believe it's going to, you know, the channel's going to be able to be enabled. How do all of these pieces go together? One, one note on Hedvig you talk about Tam expansion. Hedwig was not a leader in the market when it comes to where they are. There's a lot of competition there. You know, they were not a, you know, a unicorn that had a road to $1 billion worth of actual revenue there. So they got bought at a very high multiple of what their actual revenue was. And the question was did they just not have the go to market to be able to bring that and maybe Convolt can bring them there where they miss positioned in the market. >>Should they not be really primary storage? Should they go more to secondary storage where partner closely with secondary storage, because I know some of Combolt's competitors did work with Hedvig. I've talked to a number of partners out there that liked Hedvig and was like, Oh it's a nice complimentary offering to what we have, whether they be a hardware or place. So we'll being in Convolt hyper charge that growth. Obviously they've got some smart team, smart team members, have an Ash, came from Amazon and Facebook and his team. But what will this do to accelerate what they're doing? How will there be hit the word but synergies between the two sides of the company. So Sanjay and team really laying out their vision for where they want to take the company and it's challenging to be, we're the trusted, reliable enterprise and we're going to go down to the lower end of the market and we're going to go on all these cool new spaces and everything. So Combalt only has limited resources just like any other company. And how will they maintain and grow their position going forward. >>We are going to hear from a number of their customers do today who been combo customers for 10 plus years. Some of them who have a number of Convolt competitors within, you know, disparate organizations. I love to hear from them, why are you running, you know, comm vault, the backup exec within these different departments. For example. AstraZeneca is one of them. And what makes Combalt in certain departments really ideal. So going to get a good picture of that, but also love to understand from these customers who've been using Combolt for years. Do you see a new combo in 20 in their fiscal year 2020 talked about the leadership changes. As you mentioned, this is a company that's not only 20 years old but at low run. Some stats by you that Sandra Mirchandani shared this morning, they've got 2.8 million. The virtual machines protected, they've got over 700 millions of petabytes. They're protecting in the cloud, 1.6 million servers on and on and on. How is con vault of fiscal year 2020 different and and really poised at this intersection of unified >>in? One of the answers for that that we'll dig into is it's about data. So while con vault does 45 million weekly backup jobs, we used to know backup is something that you just kind of had, but you didn't necessarily use it. Now it's not just having my data and making sure that it's relied on, but how can I leverage that data? It's, you know, data at the core and you know, Sandra said data is the heart of everything they're doing. So coming from puppet, Sanjay knows about dev ops and agile and he's going to bring some of that in. He's brought in a team that's going to infuse some change in the culture and we'll see. I expect Convolt to be moving a little, little faster. They definitely have made a number of changes in the short time that he has already been there and we'll get a little bit of a roadmap as to where we see them going. >>Yeah, there's certainly seems Stu to be moving quickly. You mentioned, you know, Sonjay being nine months metallic. You mentioned also being developed in house in a matter of months, announcing the Hedvig acquisition in September. It closed October 1st there Q2 earnings come out in just a couple of weeks right before Halloween. So it seems like a lot of momentum carrying into the Denver aura area. Is it going to be a trick or a treat? Ooh, I like that as a marketer, I'm jealous that you thought of that and I didn't, but I liked that. We'll go with that all these years on the cube. You gotta you gotta have the snappy comebacks, right? So, Steve, it's gonna be a great day today we are jam packed session interview after interview with combat executives, really dissecting what they're doing, what's new, what's positioning them to really kick the door wide open and really reverse those revenues, taking them positive and really not only meeting the endless expectations, but exceeding them. So I'm looking forward to an action packed two days in Aurora with use to, can't wait. All right, first two minute, man. I'm Lisa Martin. You're watching the cube from comm vault. Go 19 we'll be right back with our first guest.

>>Bly from Boston, Massachusetts. It's the cube covering ifs world conference 2019 brought to you by ifs. >>Okay. We're back in Boston, Massachusetts ifs world day one. You walked into cube Dave Vellante with Paul Gillen boss Devoss is here. He's the director of ISF I F S labs and Bob Dico who's the vice president of AI and RPA at ifs jets. Welcome. Good to see you again. Good morning bossy. We're on last year. I'm talking about innovation ifs labs. First of all, tell us about ifs labs and what you've been up to in the last 12 months. Well, I have has Lapsis a functioning as the new technology incubator. Fire Fest writes over continuously looking at opportunities to bring innovation into, into product and help our customers take advantage of all the new things out there to yeah. To, to create better businesses. And one of the things I talked about last year is how we want to be close to our customers. And I think, uh, that's what we have been doing over the pasta pasta year. Really be close to our customers. So Bob, you got, you got the cool title, AI, RPA, all the hot cool topics. So help us understand what role you guys play as ifs. As a software developer, are you building AI? Are you building RPA? Are you integrating it? Yes, yes. Get your paint. >>I mean, our value to our customers comes from wrapping up the technology, the AI, the RPA, the IOT into product in a way that it's going to help their business. So it's going to be easy to use. They're not going to need to be a technical specialist to take advantage of it. It's going to be embedded in the product in a way they can take advantage of very easily that that's the key for us as a software developer. We don't want to offer them a platform that they can just go and do their own thing. We want to sort of control it, make it easier for them. >>So I presume it's not a coincidence that you guys are on together. So this stuff starts in the labs and then your job is to commercialize it. Right? So, so take machine intelligence for example. I mean it can be so many things to so many different people. Take us back to sort of, you know, the starting point, you know, within reason of your work on machine intelligence, what you were thinking at the time, maybe some of the experiments that you did and how it ends up in the product. Oh, very good question. Right? So I think we start at a, Oh, well first of all, I think ifs has been using a machine learning at, at various points in our products for many, many years of Trumbull in our dynamic scheduling engine. We have been using neural networks to optimize fuel serve scheduling for quite some many years. >>But I think, um, if we go back like two years, what we sold is that, uh, there, there's a real potential, um, in our products that if you will take machine learning algorithms inside of the product to actually, um, help ultimately certain decisions in there, um, that could potentially help our business quite a bit. And the role of ifs lapse back in the day as that we just started experimenting, right? So we went out to different customers. Uh, we started engaging with them to see, okay, what kind of data do we have, what kind of use cases are there? And basically based on that, we sort of developed a vision around AI and a division back in the day was based on on three important aspects, human machine interaction optimization and automation. And that kind of really lended well with our customer use case. We talked quite a bit about that or the previous world conference. >>So at that point we basically decided, okay, you know what, we need to make serious work of this, uh, experimenting as boots. But at a certain point you have to conclude that the experiments were successful, which we did. And at that point we decided to look at, okay, how can we make this into a product and how to normally go system. We started engaging with them more intensively and starting to hand over in this guys, we decided the most also a good moment to bring somebody on board that actually has even more experience and knowledge in AI and what we already had as hive as labs. But that could basically take over the Baton. And say, okay, now I am going to run with it and actually start commercializing and productizing that still in collaboration with IVIS laps. But yeah, taking that next step in the road and then then Bob came onboard. >>Christian Pedersen made the point during the keynote this morning that you have to avoid the, the appeal of technology for technology's sake. You have to have it. I start with the business use case. You are both very technology, very deep into the technology. How do you keep disciplined to avoid letting the technology lead your, your activities? >>Well, both. Yeah. So, so I think a good example is what we see this world's going fronts as well. It is staying closer to customer and, and, and accepting and realizing that there is no, um, there's no use in just creating technology for sake of technology as you say yourself. So what we did here for example, is that we showcase collaboration projects with, with customers. So, for example, we show showcase a woman chair pack, which um, as a, as a manufacturing of spouting pouches down here in Massachusetts actually, uh, and they wanted to invest in robotics to get our widows. So what we basically did is actually wind into their factory literally on the factory floor and start innovating there. So instead of just thinking about, okay, how do robotics and AI for subrogations or one of our older products work together, we set, let's experiment on the shop floor off a customer instead of inside of the ivory towers. Sometimes our competitors to them, they'll start to answer your question. >>Sure. I can pick up a little, a little feasible. Yeah. Well, so in, I think the really important thing, and again, Christian touched on it this morning is not the individual technologies themselves. It's how they work together. Um, we see a lot of the underlying technologies becoming more commoditized. That's not where companies are really starting to differentiate algorithms after a while become algorithms. There's a good way of doing things. They might evolve slightly over time, but effectively you can open source a lot of these things. You can take advantage, the value comes from that next layer up. How you take those technologies together, how you can create end to end processes. So if we take something like predictive, we would have an asset. We would have sensors on that asset that would be providing real time data, uh, to an IOT system. We can combine that with historical maintenance data stored within a classic ERP system. >>We can pull that together, use machine learning on it to make a prediction for when that machine is gonna break down. And based on that prediction, we can raise a work order and if we do that over enough assets, we can then optimize our technicians. So instead of having to wait for it to break down, we can know in advance, we can plan for people to be in the right the right place. It's that end to end process where the value is. We have to bring that together in a way that we can offer it to our customers. There's certainly, you know, a lot of talk in the press about machines replacing humans. Machine of all machines have always replaced humans. But for the first time in history, it's with cognitive functions. Now it's, people get freaked out. A little bit about that. I'm hearing a theme of, of augmentation, you know, at this event. >>But I wonder if you could share your thoughts with regard to things like AI automation, robotic process automation. How are customers, you know, adopting them? Is there sort of concern up front? I mean we've talked to a number of RPA customers that, you know, initially maybe are hesitant but then say, wow, I'm automating all those tasks that I hate and sort of lean in. But at the same time, you know, it's clear that this could have an effect on people's jobs and lives. What are your thoughts? Sure. Do you want to kick off on them? Yeah, I'll know. Yeah, absolutely. That's fine. So I think in terms of the, the automation, the low level tasks, as you say, that can free up people to focus on higher value activities. Something like RPA, those bots, they can work 24, seven, they can do it error free. >>Um, it's often doing work that people don't enjoy anyway. So that tends to actually raise morale, raise productivity, and allow you to do tasks faster. And the augmentation, I think is where it gets very interesting because you need to, you often don't want to automate all your decisions. You want people to have the final say, but you want to provide them more information, better, more pertinent ways of making that decision. And so it's very important. If you can do that, then you've got to build the trust with them. If you're going to give them an AI decision that's just out of a black box and just say, there's a 70% chance of this happening. And what I founded in my career is that people don't tend to believe that or they start questioning it and that's where you have difficulty. So this is where explainable AI comes in. >>I do to be able to state clearly why that prediction is being made, what are the key drivers going into it? Or if that's not possible, at least giving them the confidence to see, well, you're not sure about this prediction. You can play around with it. You can see I'm right, but I'm going to make you more comfortable and then hopefully you're going to understand and, and sort of move with it. And then it starts sort of finding its way more naturally into the workplace. So that's, I think the key to building up successful open sexually. What it is is it's sort of giving a human the, the, the parameters the and saying, okay, now you can make the call as to whether or not you want to place that bet or make a different decision or hold off and get more data. Is that right? >>Uh, yeah. I think a lot of it is about setting the threshold and the parameters with within which you want to operate. Often if a model is very confident, either you know, a yes or a no, you probably be quite happy to let it automate. Take that three, it's the borderline decision where it gets interesting. You probably would still want someone to look over it, but you want them to do it consistently. You want them to do it using all the information to hand and say that's what you do. You're presented to them. And to add to that, um, I think we also should not forget they said a lot of our customers, a lot of companies are, are actually struggling finding quality stuff, right? I mean aging of the workforce riots, we're, we're old. I'm retiring eventually. Right? So aging of the workforce is a potential issue. >>Funding, lack of quality. Stop. So if I go back to the chair pack example I was just talking about, um, and, and, and some of the benefits they get out of that robotics projects, um, um, is of course they're saving money right there. They're saving about one point $5 million a year on money on that project, but their most important benefits for them, it's actually the fact that I have been able to move the people from the work floor doing that into higher scope positions, effectively countering the labor shortage today. They were limited in their operations, but in fact, I had two few quality stuff. And by putting the robots in, they were able to reposition those people and that's for them the most important benefits. So I think there's always a little bit of a balance. Um, but I also think we eventually need robots. >>We need ultimation to also keep up with the work that needs to be done. Maybe you can speak to Bobby, you can speak to software robots. We've, Pete with people think of robots, they tend to think of machines, but in fact software robots are, where are the a, the real growth is right now, the greatest growth is right now. How pervasive will software robots be in the workplace do you think in the three to five years? >> I think the software robots as they are now within the RPA space, um, they fulfill a sort of part of the Avril automation picture, but they're never going to be the whole thing. I see them very much as bringing different systems together, moving data between systems, allowing them to interact more effectively. But, um, within systems themselves, uh, you know, the bots can only really scratched the surface. >>They're interacting with software in the same way a human would on the whole by clicking buttons going through, et cetera, beneath the surface. Uh, you know, for example, within the ifs products we have got data understanding how people interact with our products. We can use machine learning on that data to learn, to make recommendations to do things that our software but wouldn't be able to see. So I think it's a combination. There's software bots, they're kind of on the outside looking in, but they're very good at bringing things together. And then insight you've got that sort of deeper automation to take real advantage of the individual pieces of software. >> This may be a little out there, but you guys >>are, you guys are deep into, into the next generation lot to talk right now about quantum and how we could see workable quantum computers within the next two to two to three years. How, what do you think the, the outlook is there? How is that going to shake things up? So >>let me answer this. We were actually a having an active project and I for slabs currently could looking at quantum computing, right? Um, there's a lot of promise in it. Uh, there's also a lot of unfilled, unfulfilled problems in that, right? But if you look at the, the potential, I think where it really starts playing, um, into, uh, into benefits is if the larger the, the, the optimization problems, the larger the algorithms are that we have to run, the more benefits it actually starts bringing us. So if you're asking me for an for an outlook, I say there is potential definitely, especially in optimization problems. Right. Um, but I also think that the realistic outlook is quite far out. Uh, yes, we're all experimenting it and I think it's our responsibility as ifs or ciphers laps to also look on what it could potentially mean for applications as we FSI Fs. >>But my personal opinion is the odd Lucas. Yeah. So what comes five to 10 years out? What comes first? Quantum computing or fully autonomous driverless vehicles? Oh, that's a tricky question. I mean, I would say in terms of the practical commercial application, it's going to be the latter in that much so that's quite a ways off. Yeah, I think so. Of course. Question back on on RPA, what are you guys exactly doing on RPA? Are you developing your own robotic process automation software or are you integrating, doing both say within the products? We, you know, if we think of RPA as, as this means of interacting with the graphical user interface in a way that a human would within the product. Um, we, we're thinking more in terms of automating processes using the machine learning as I mentioned, to learn from experience, et cetera. Uh, in a way that will take advantage of things like our API eighth, an API APIs that are discussed on main stage today. >>RPA is very much our way of interacting with other systems, allowing other systems when trapped with ifs, allowing us to, to send messages out. So we need to make it as easy as possible for those bots to call us. Uh, you know, that can be by making our screens nice and accessible and easy to use. But I think the way that RPA is going, a lot of the major vendors are becoming orchestrators really. They're creating these, these studios where you can drag and drop different components into to do ACR, provide cognitive services and you know, elements that you could drag and drop in would be to say, ah, take data from a file and load it into ifs and put it in a purchase order. And you can just drag that in and then it doesn't really matter how it connects to YFS. It can do that via the API. And I think it probably will say it's creating the ability to talk to ifs. That's the most important thing for us. So you're making your products a RPA ready, friendly >>you, it sounds like you're using it for your own purposes, but you're not an RPA vendor per se. You know what I'm saying? Okay. Here's how you do an automation. You're gonna integrate that with other RPA leadership product. I think we would really take a more firm partner approach to it. Right? So if a customer, I mean, there's different ways of integrating systems to get our RPA as a Google on there. There's other ways as well, right? That if a customer actually, um, wants to integrate the systems together using RPA, very good choice, we make sure that our products are as ready as much for that as possible. Of course we will look at the partner ecosystem to make sure that we have sufficient and the right partners in there that a customer has as a choice in what we recommends. But basically we say where we want to be agnostic to what kind of RPA feminists sits in there that was standing there was obviously a lot of geopolitical stuff going on with tariffs and the like. >>So not withstanding that, do you feel as though things like automation, RPA, AI will swing the pendulum back to onshore manufacturing, whether it's Europe or, or U S or is the costs still so dramatically advantageous to, you know, manufacture in China? Well, that pendulum swing in your opinion as a result of automation? Um, I have a good, good question. Um, I'm not sure it's will completely swing, but it will definitely be influenced. Right. One of the examples I've seen in the RPA space ride wire a company before we would actually have an outsourcing project in India where people would just type over D uh, DDD, the purchase orders right now. Now in RPA bolts scans. I didn't, so they don't need the Indian North shore anymore. But it's always a balance between, you know, what's the benefit of what's the cost of developing technology and that's, and it's, and, and it's almost like a macro economical sort of discussion. >>One of the discussions I had with my colleagues in Sri Lanka, um, and, and maybe completely off topic example, we were talking about carwash, right? So us in the, in the Western world we have car wash where you drive your car through, right? They don't have them in Sri Lankan. All the car washes are by hands. But the difference is because labor is cheaper there that it's actually cheaper to have people washing your car while we'd also in the us for example, that's more expensive than actually having a machine doing it. Right. So it is a, it's a macro economical sort of question that is quite interesting to see how that develops over the next couple of years. All right, Jess. Well thanks very much for coming on the cube. Great discussion. Really appreciate it. Thank you very much. You're welcome. All right. I'll keep it right there, but he gave a latte. Paul Gillen moved back. Ifs world from Boston. You watch in the queue.

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019. Brought to you by VM Wear and its ecosystem partners. >> Welcome back, everyone. Day three Q coverage here in San Francisco for V emerald. 2019. I'm just for a student, Um, in here with David Lan. Take days free kick off. We have two sets wall to wall coverage. Guys, this is the time where we get to take a deep breath two days under our belts look and reflect on all the news we've covered in a dark to last analysis sessions but also kind of riff on. We got two nights in hallway conversations we learned a lot of the party means do. I learned a lot last night. Dave. I know you. You learned a lots, do you, Thomas? When things that the chatter Certainly twittersphere hashtag the emerald. A lot of action on there, but it's the hallway conversations. It's the party that people have a few cocktails in them day that you start to hear the truth. The real deal comes out, >> No doubt. And and again Jon Stewart, there's real concern over from the from the practitioners we talked to about this acquisition spree. Are they going to be integrated? Are they going to just throw all this stuff at us and keep jamming products and service is down our throats? Or is this going to be a coherent set of solutions that solves our problem? We also had a little little interesting side conversation about, you know, Snowflake, Frank's lumens new company and how basically Frank is bringing back the Pirates from Data Domain and from service. Now Mike Scarpelli is over there. He's a rock star. CFO Beth White is eventually is back over there. And Frank's Lupin. He's the guy who takes companies from, you know, 100 million to a billion, so that's gonna be >> very serious money making him going on there. >> We have been following his career for a number of years now. We watched him take data domain. We watched him pull that that rabbit out of his hat with the sale with net app, and then the emcee swooped in. And then we saw what he did service. Now we've documented this is an individual to watch, you know, >> he's a world class management team member I mean, he's executes. >> Oh, yeah, no doubt. And >> he has >> a formula that's been proven and in time and time again. And to me, the biggest testament salute Min is the success of the continued success of Data Domain. After he left Hey, he really helped clean up the emcees data protection mess. Um, and then the second thing is, look at service now is performance after he left, I haven't missed a beat. And, yeah, John Donahoe, great executive and all, but it's because Frank's Lubin had everything in place and that was a really well run >> dry. And they got a nice little oracle like business model. >> Yeah. No, you're right. They kind of, you know, the big complaint now as well. Your price is too high that Oracle. >> What have you learned? What you hear in the hallways? I mean, a lot of chatter. >> Yes, John, we We've been reflecting back a lot. It's 10 years in 10th year of the Cube here and back here in San Francisco. The new Mosconi, our third show that I've been at this year in Mosconi and we always track year to year. But since it's been what 45 years since we were here for VM World. When I talked to the average vendor. When I talk to you know, the analysts here were like, Oh, thank goodness we're not in Vegas. When I talked to the average attendee, they're like, Oh my God, what happened to San Francisco since last time we were here? It is too expensive. And the experience walking around San Francisco has really not nearly as nice as it might have been five or 10 years ago. And many of them we were talking to, Ah, woman that runs an event that has been Vegas in San Francisco. And she said, Oh, we did in San Francisco and got tremendous feedback. Don't do it there again. Brings back to Vegas both for costs and the enjoyment of being around the environment. >> Where was a shit show here in San Francisco is horrible right now, I got to say to your right eye was walking this morning from my hotel. Literally. A homeless person passed out the middle of the sidewalk. Um, your smells like urine. It's P, and it's It's just I mean, it's really bad this tense now. I mean City of San Francisco is gonna do some. Mosconi, by the way, has been rebuilt. Awesome. So, you know, in terms of the new Mosconi stew, that's a serious upgrade. Hotel rooms are scarce and just the homeless problem. It's just ridiculous. I don't know what they're >> doing. So one of the other big things when I was reflecting coming into here two years ago when VM wear really started down right before the war on AWS announcement, they made a big announcement. IBM because they had sold off the cloud air toe Oh, VH And for two years Oh, VH was a big partner, Talked about that transition, said we handed off this great asset over h isn't here at the show. I was like, Oh, my gosh, you know, that was, you know, such a big story and other companies like New >> 12. That's good. One lets someone who's not at the show and why. Yeah, oh, VH wired to hear >> They aren't here because, well, they've got customers. More of them are in Europe That was supposed to be a big entry into the United States. Obviously, it wasn't as valuable for them to be here, even though I'm sure they're still part of that service provider ecosystem. They have other big one for us, and we've had on the Cube Nutanix. You know, we've had Dheeraj Pandey. First time we had him on was that this show is still the majority of Nutanix. Customers are VM where customers I've talked to lots of Nutanix customers at the event, even part of the analyst event. Some of the customers I talked to were like, Oh, yeah, my hardware stacks Nutanix and amusing NSX. And I'm using other things there. But they are not here. They're not allowed to be at the show. And I >> mean, they were blatantly told they can't come. >> They can't come here. They can't come to the regional things. They can't do the partner things. So that that that relationship is definitely >> from red hat. What kind of presence have you seen from Red s? >> So their number companies like red Hat that they're kept at a lower level of sponsorship. So they're here. They participate, you know. Open shift, of course, is you know, big enemy for cloud native. Lots of open shift runs on V sphere. So many of those companies that are part of the ecosystem, but not the ones that they want to celebrate and put front and forward. So it's always interesting kind of walk around on those. Even Microsoft is an interesting relationship for, you know, decades with the M wear. You know, of course, azure they partner with. But hyper V was long a competitors. So, you know, we understand those competitive relationships >> could be interesting. Stew and Dave on the ecosystem Jerry Chan Day when we just doing my interview yesterday on the other set mentioned that the ecosystem reinvents itself the community. The question now is with Delhi emceeing Del Technologies obviously heard Michael Dell essentially laying out his plan, which is he's got. He's trying to keep people distracted, but the bottom line is going to top people putting together the cloud right well service provider model. So you know, that's what he's gonna be a big impact. VM wear the crown jewel of Del Technologies certainly is looking more and more like It's >> well and yesterday remember the first VM world we did in 2010? It was It was del I mean course and see only the time Who's Del? It was H p Yes, the emcee was there, but it was net app. I mean, everybody could've had equal standing yesterday at the keynotes. It was Project Dimension of V M, where cloud on Delhi emcee and long keynotes >> data protection into the VM were >> also it's It's all very heavily, you know, Jeff Clarke has his his thumb on, you know, the the deli emcee folks pushing that through Veum where Michael is orchestrating the whole thing. Pat obviously is allowing it. I was sitting in the audience Next next, Some folks from Netapp they're like, you know, this kind of a bummer. Calvin Sito from h p e tweeted Wow how to stick it in the face of your ecosystem partners. He then later went on Facebook saying, Hey, I love this ecosystem, so sort of balancing it out because, you know, he wants to be a good, good citizen, but clearly the ecosystem partners who basically brought VM where you know, to the the position where it's in through distribution, our little ruffled. Right now you can't blame him, But at the same time, the mandate is clear. Michael Dell is driving his products and his solutions through VM were period the end. And, you know, if you don't like it, leave >> right. They had such great success with V San and VX rail in that joint product development and go to market. If they can replicate that with a number of other solutions, they get that the synergies. If >> you don't like it, don't leave. That leave is worse than that. They say you don't like it, you know, invited you. But >> how about what Pat said yesterday in the Cube about when they announced on Gwen heavily leaned into V san. He said publicly that Joe Tucci was pissed and I hate her. They were going at it so that so that shows you the change, right? I mean, so so so e m. C. When it owned VM where was very cautious about allowing Veum wears a software company to drive value somewhere Now is just acting like a software company. >> Well, I think I mean, I learned last night's do, um and you can appreciate this. I learned that the top executives of'em where are looking heavily and working hard at understanding and drive them kubernetes cloud native thing because this is not a throwaway deal. This is not a you know, far anything that they are investing. They get their top brass tech execs on kubernetes fto. Two big players job. Ada, Craig McCaw calumnies. We know interviews since day one, but I think the cloud native thing is going to be interesting. And I think it's gonna be evolution. I think there's gonna be a very dynamic road thing's gonna be a series, of course, corrections, but directionally they're all in on. They're going for it, they're not. >> And actually, I had a, you know, good discussion with Chad Attack. It's a good friend of the program now working at GM, where for the first time, but came from AMC worked at Pivotal. He said, culturally, such a gap between VM wear don't have to touch your app, you know, move everything along lifted shift is nice and easy versus pivotal, you know must go completely You know, dual programming, you know, agile everything there, so bridging those because there's multiple paths and the rail pharaoh announcement is that would be cloud native stuff that won't necessarily go to the EMS. We're going to retool V EMS to now be a platform for kubernetes so that they have a few passed to bridge or to build towards the future. Here's the >> answer strategy. Discussion That and Rayo Farrell was now running Cloud native. Think this is just really >> ties in the interesting discussion that I had with some folks was that you've essentially got well, Jerry Chen brought this up last time we had him on it and reinventing because >> we have >> a conversation all the time about this Amazon have to go up the stack. And Jerry Chen made a really he said, Look, it they're not They're not gonna become an e r peace offer company. What they're gonna do is give tools to the builders so that they can disrupt Europea. They can disrupt service. Now they can disrupt Oracle. That's their strategy, at least for now. Okay, so what does that say? I think the strategy discussion inside of'em were and and l is about by whatever clouds gonna be 35 to 50% of the market. Fine. And the cloud native abs. Great. But you got this mission critical. E r p is an example. Database saps that are on Prem. What we have to do is keep them there. So we're going to sell to the incumbents and we're going to give them cloud native tools, toe modernize. Those APS have build new acts on Prem, and that's the that is the collision course that's coming. So the big question is, can the cloud native guys and AWS disrupt that >> huge? I've always said I'm is on and like the way they're coming in, a tsunami is coming in. And who's gonna build that sea wall to stop it right? And that's essentially only hope that these guys have. You look at all the competitive strategy. Was Oracle. Whoever just gotta stop it? You can't like >> the sea >> wall. That's a great building. A sea wall I was, I would say, is Is that you know, they're only hope at this point is to, you know, get in the game because see Amazon is the stack. They're not really moving up the stack. You hear that from Cisco and Dale and other people? That's where it's a game of musical chairs. Right now, the music's you know, there's still a lot of shares left, but soon chairs getting pulled away and Cisco Deli emcee VM, where they're all fighting for these big chairs. And one >> thing >> we talked about yesterday is that VM wears very directional, product driven. Otherwise they pick a direction, is a statement of direction and don't really have a lot of meat on the bone. In the product side, Sister is actually in market with service providers there in market with NETWORKINGS to this no vapor there that's installed basis and incumbent business. You have developers Esso Baton talks about suffered to find data center, suffer defined networking. I mean, come on, Really. I mean, they're getting there, but it didn't have the complete solution. Cisco >> Coming into this week, I expected here a bit more about the progress and all the customers of'em wear on AWS and feel like Vienna actually downplayed the AWS. We know what a strong partnership it is at every Amazon show we go to, and we got a lot of them Now there's a big presence there, and I can talk to customers that are starting to roll out and move there, but it felt like it was David's. You pointed out there are some messaging differences when you talk about multi cloud and how they're positioning it. So, you know, put those >> here Amazon. If your Amazon you're not happy with Microsoft Dell Technologies World The big announcement that was positioned a cloud foundation Although it wasn't a joint engineering, But the press picked it up as though the Amazon deal has been replicated with Microsoft and Google. I mean, you gotta be gotta be hurt if your Amazon >> So I've I've just been taking notes this this event, there's I've noted at least five major points of difference between a W s what they're saying and their philosophy and the anywhere so eight of us. We know they they don't talk multi cloud. They've told their partners, If you're doing joint marketing with us, you cannot say multi cloud aws that reinforce John. We saw this. Steven Schmidt said that this narrative that security is broken doesn't help the industry. Security's not broken, you know, we're doing great. The state of the nation is wonderful. Aws Matt. Not really. I agree. By the way. Uh, that's not the case. I agree with Pat saying Security's broken. It's a do over VM where wants to be the best infrastructure and developer software company. Who's the best infrastructure and software development platform. Eight of us. The M one wants to be the security cloud. Who's the security cloud? Eight of us. And then, uh, they talked about 10,000 cloud data Listeners are those really cloud data centers at Vienna. And the last one was this was a little nuanced Veum was talking about We know about migrating, modernize, lifted ship shift and then modernize The empire's not talking about modernize and then migrate. If you want to. I totally in conflict >> as a collision course. That's got Look, look, look at the data center was Look, it looks like we're going. We're going away, right to the data center. Staying. That's music to Michael Dell's VM. Where's years they live in the Data City? Do you pointed out yesterday? Data Senate goes away. So does begin. Where's business? >> One of things. I'm surprised. I'm wondering you both have talked to some of the service fighter telco pieces of'em, where they're doing that project dimension, which is the VM where stack on del that looks just like outposts on. And I know they had deployments on this for months. If I was them, you know, it's everybody's hearing about Outpost to talk about it, being more like we're already doing it in. This has you in that Amazon ecosystem. It might be a little strong for the Amazon story, but have you been hearing any about that this week? >> I think they keep a lot of cards close to the chest, but it's clear from the announces that they're doing certainly del the VM, where on Delhi Emcee Cloud or whatever it's called, it's not a cloud but their their infrastructure that is essentially a managed service. That's gonna be really strong for I t. People, because I think that the value proposition of going toe i t and saying we have this, you don't need to do anything. It's very strong, I mean, because I didn't want him >> and justified because this the project to mention it is that single, that thinner stack like what we saw on Outpost in the Amazon video, as opposed to Veum, where cloud on AWS, which is the full C i r h d. I stack. >> I haven't heard anything still on >> well, but the conversation I had from from Vienna, where standpoint, they could make money on that manage service. That's why it's the preferred partnership, right? And so that's their part of their cloud play. If you don't have a public cloud, I said this yesterday, you have to redefine Cloud and you have to get into cloud service. And that's what's happening. And that's exactly what's happening. And what I like about what V M where is doing is they are transitioning their model to a sass based model. Now it's only 12 and 1/2 percent of the revenues today. But both pivotal and carbon black are gonna add, you know, ah, $1,000,000,000 next year to that subscription based $3 billion in year two. Um, and so you know, Pat said the other day, I think we could get to 50 50. I don't necessarily think in the near term we're gonna go beyond that. It's not the Adobe >> way could be critical. Critical of'em were in some areas, but I gotta tell you their core strength that they went to a software operators on the data center friend of prices. That's been a great strategy. Focusing on their core building from there is Jerry 10 point out adding other products so their software company, So I think they're really got a good solution. And you? The data shows that people are increasing their spending, John. Just one based on >> that. Because I had a couple of really good conversation with customers, customers that would deploy VCF So they've got the full stack on there. So using H C I, but not necessarily on Dell hardware, could be Cisco Hardware. Could be HB hardware in the like or they're buying NSX. But the virtual ization team owns it, and they get kind of put in. A box storage team says That's not the array I'm used to buy. Well, maybe I'll put a pure storage box and put it in between. The networking team says I'm refreshing my Cisco hardware. You know, we're like, but we have NSX, and it's great. Well, you can use NSX over there. We're going to use a C I over here. So the term I heard from a number of customers is organizations still have hardware to find roles, and they're trying to figure out how to move to that software world. Which hurts me, cause I spent years trying to get beyond silos and helping people you know, move through those environments. And still, in 2019 it's a big challenge. That organizational shift is we know how tough that is. >> So just couple points in the data, because you're right. There are some countervailing trends, though. So, yes, people are spending Maurin VM where in the second half. But at the same time, the data shows that cloud is hurting VM wear spend. So this that's kind of gets interesting. Our containers gonna kill VM where? No, there's no evidence that container's air hurting VM where spend. But there's clearly risks there, you know, as we've talked about who's best position of multi cloud. Well, it turns out three guys with the public cloud are best positioned in multi Google and Microsoft on, and so and then the pivotal thing is interesting, and ties ties all this in so that the data is actually really interesting. It's like you're seeing tugs at both sides, and I think your your notion about the seawall is dead on. That's exactly what they're doing. >> You see that with Oracle's trying to stop jet. I just want they can't win this one to stop Amazon just on the tracks gave great data. Great reporting, Stoop. Good observations. Get all the day that night and parties we're gonna certainly keep doing that. Day three of wall to wall coverage here. You bringing to the insights and interviews here live from the Emerald Twin 19. Stay with us for more after this short break.

[Announcer] - Live from Washington D.C., it's theCUBE, covering .NEXT Conference brought to you by Nutanix. >> We're back in D.C., welcome to NextConf, this is day two of our wall-to-wall coverage and this is theCUBE, the leader in live tech coverage. My name is Dave Vellante with Stu Miniman. Dheeraj Pandey is here, he's the chairman and CEO of Nutanix. Long time CUBE alum. Great to see you again. >> Pleasure. >> So you know, I love your style, up on stage yesterday. Very philosophical, always have been humble. You sort of said, "I'm going to stay humble," and it appears that's the case. But yet, there's so much excitement around here, you have a lot to be very proud of. How do you feel? >> You know, there's no finish line in this company building, just like there's no finish line when you have a family, it never ends actually. Nutanix is a family, and we are trying to make it a bigger, happier family with more customers, more partners, more employees. I feel good, but I think this company is good right now, it's not a great company. We probably will have to spend another decade to make it a great company actually, so. >> How do you, as the chairman and CEO, how do you define "great company"? >> Great companies, for one, actually take really good care of their stakeholders. You think about employees and customers and partners and also Wall Street, so I think at the end of the day we have barely begun the journey in some of these things. Customers, sure, we have quite a few of them, but I think we can do so much more for them. At some level, even in the largest accounts, we're barely scratching the surface actually. Same thing with employees, you know, we have almost 3000 employees but still, we could do so much more for them as well in terms of wealth creation, in terms of building careers. Very early days. Same thing with Wall Street as well, very early days actually. >> Dheeraj, you're always opening to listening to feedback, but you mentioned, you've now got a lot of constituencies. I know I've interviewed you and said well you know, there's the 90-day shock clock but, we can't get distracted, we need to focus. How do you, you know, what is the filter, how do you, what do you take in and internalize to translate into the direction of the company? >> You know I talk about two things. There's delight, there's waste. Delight for main street and make sure you're cognizant of the waste with Wall Street, because if you keep growing they won't bother you. What they bother you with is waste. How are you growing, what does efficiency look like at scale? So I just learn "growth at any cost". I think these are all timely reminders for any company, so that it doesn't get too painful when recessions hit you, because there's highs and lows of any company that you have to go through. So I believe that waste is the larger ego of delight, and if you can do a really good job of delighting our customers, our partners, our employees and then figure out how to deal with all of this with waste in mind, I think we'll do a pretty good job. So what matters the most is delight, but not without figuring out what's waste-like. I think you have to keep looking at these "KPIs" and say how are we really doing at scale with respect to distribution, marketing, product development, product engineering. Now we have a pretty large engineering workforce as well. How can the company be delightful for them if you don't have "two-pizza teams", if you don't have APIs and microservices in which they actually talk to each other, still feel like they're the CTO of their company, because they all want to make independent decisions and design trade-offs and things of that nature. I think we talk about this thing which is a really important abstract thing, it's called the paradox of growth. I learned this from some of these folks who have done this book called The Founder's Mentality. Growth creates complexity and complexity kills growth, so just be aware of what you really vied for can kill you as well, and continue to release complexity to organizations in the way you deal with your customers, and I think those are the things that really matter. I look at employees as customers, I look at customers as customers, I look at partners as customers. If you have the customer-centric view, you'll probably continue to simplify things under the cover. >> One of the things that you see in great companies is early on they're able to articulate a vision, see that vision, execute on it obviously and continue to grow their team, I mean that's a big part of your job. You've dramatically, well first of all, the team that you started with was quite large. Cloud expands that enormously. So maybe talk about your vision and how you're seeing that through. >> Well I think from very early on, the mission was invisible infrastructure. And that is an infinite mission because again, no finish line actually. You can make things invisible and then probably say we still aren't invisible enough and you have to make it more invisible. When you have downer to four clicks you have to say how about three and two and one click? And finally get rid of the click because machine learning can come in and automate more things as well. So how more and more things go from humans to machines and how the human-man-machine interface becomes less frictioned is the vision of this company. Now, all of this is not just graphical UI because the systems have to work, they have to be scalable, stable, reliable, available. So the back-end has to be very robust but then without a front-end it's really the same as a man-machine interface. Also the machine-machine interface, because APIs match for a lot as well, you know. If you're only thinking about man-machine, then you've lost a lot of this automation and machine learning capability as well, actually. >> I think back to some of our earliest conversations, you always talked about Nutanix is a software company and the challenge of our day is building distributed systems. The tooling and the way we build things today are very different from when you started the company. If you were starting from a bare sheet today, would you be born in the cloud, you know, how would things like containers and microservices change the way, or, and how are you taking from where you are today, which it started out in virtualization, is that a core, you've got AHV driving a lot of the pieces, versus some of those who are models? >> Yeah, I mean, look, VMware was building an operating system, but they needed a shield of EMC to go sell and distribute that. We had the compute virtualization piece that came a little bit later, but the storage virtualization, the control plane pieces, we needed to shield them, and we shield them in appliance, and that became our form factor the could give us the control of our own destiny, and that's what the appliance did to us. But you always knew you were building software, actually. And many people told us early on, just don't build appliances at all, and we would've been killed, we probably would have to sell this company early on, because it's really hard to build an OS company early on when you don't have a brand and nobody's willing to support you and customers are like, you know, if nobody else is willing to support you, how do you really build an operating system, actually? So I think if there's a method to the madness, we always knew we had to be hardware-agnostic, that's why we never built NVRAMs and FBGAs and things like that. And over time when Dell came forward and said look, you should OEM your product, I think it was a very natural decision for us two and a half, three years ago. I think there's been this controlled release of goodness of this operating system that basically not mean like oh we never thought about it, we always thought about hardware-agnosticism, hypervisor-agnosticism, all those things were there from day one in this company. But you know the question of whether we would start in the cloud today? Honestly, all companies have to start where they are in order to make money, and continue to navigate the shifting sands of time actually. I mean, you sell books, then realize it's not good enough, you go and sell, you know goods with e-commerce, and that's not good enough, you sell computing. We started an office productivity company, go and do a desktop operating system, then you go and do databases and server operating system and then all sorts of things for the family room and so on and then finally do a cloud. I think there's no, you know, change is the only constant you know, if you were to think about it, and companies that actually survive and thrive, they start someplace, and their thing, every three, four years, you just find the adjacencies, and keep navigating, you know, how the market is actually shifting and changing. >> There's a strange aura around your company. Now maybe it's the allure of the product, I don't know, but you have a lot of companies now coming into this ecosystem. We have Chad on next from Dell EMC, you know, arguably one of your larger competitors, okay, but they're here and they're happy to be here. So, it's, I say, maybe it's product, but it's also part cultural. And I'm guessing that your philosophy is it can't be a zero sum game. It's got to be a win-win for the partner, so I wonder if you could add any color to that. >> Yeah, that's a great point by the way, bring up this idea that you can be all things to all people. Somebody asked me in this analyst meetup, how about just go and build a firewall? We can, there's too deep a space in there for us to go build everything, so we need to have open APIs, where others also make money. And by the way, when you have a really flourishing ecosystem, the word of mouth, that they're also making money, the word builds a larger ecosystem, a larger operating system and so on. That's what Apple 2.0 was, because in 1.0 they were all about it's me, it's mine, no one else can do anything, and then they saw Microsoft, and how it was really building this burgeoning ecosystem with APIs, APIs, and more APIs. 90 was Microsoft's decade because of APIs actually, and partners and ecosystems, and Apple learned from them by the way, so when they came out and said we built a device, they said no no no, we've also got to build iTunes, because that's ecosystem, and then they built iCloud and app store and things like that. So I think there are lessons galore in the last 20, 25 years where if you're not a good API-driven company, you're probably not a long-lasting company actually. And the idea of a platform is incomplete without those APIs and the ecosystem itself. >> There's a change in accountant coming which is going to make you, I guess, to restate the software that you've sold through the OEMs will probably have Wall Street look at you a little bit differently. We've talked in the past before about how much you want to sell as Nutanix, how much you want to sell with partners. What's that mix that you see today going forward? How much of your product will you see, hardware, software, services, what's a good mix for you? >> Yeah, I think it's a, it's a good opportunity for the company to really think about revenue 2.0, because revenue 1.0 was what we had sort of planned out four, five years ago and 2.0 is a time when we have different form factors. We have ELAs that we started doing in the last 12 months. We're selling software in CISCO and now software in HP. Obviously Zai will happen in subscription as well. Now we have markable routes to market, you know, obviously the OEMs have actually matured, both OEMs have matured. So the question is of how do we really make it simple one more time? Because obviously there's more routes to market, so as a company we're saying now we can sell more software, and with a new accounting change, which is called ASC 606, software will have to be recognized in the same quarter, we can't defer it arbitrarily. And in some ways it's a good thing, in some ways it's bad because it takes away our goodness of the waterfall, because we could have deferred more revenue, as a company we've deferred a lot, I mean, folks know we have about $465,000,000 of deferred revenue right now, because of how good we were in actually postponing this instant gratification of cutted quarter and so on. So I think some of that will have to be brought into the current quarter but in some sense it's a good thing because we can then take the gross margin of that software and sell more appliances, so I think there's some mixing that'll happen with different margin profiles that'll have to come and kind of work with each other to say can we still grow as a company beyond a billion. >> But these are income statement gymnastics, not that you're playing, but that you're able to- >> Well, there's something about guard rails of the gross margin, because Amazon, what did Amazon say, look, your gross margin, my opportunity, right? So if you just let unbridled software go and sell itself, then our gross margins will be starting to creep up, but what if you kept it within the guard rails of around 60%, and then went and sold more appliances, because the software gave us the luxury to buy growth? I think those are the kind of architectures we are actually looking at right now. >> And the knobs that you might choose to turn, but it will have an impact on the income statement from an operating profit standpoint, I mean, right? If you're going to recognize all that deferred revenue up front you know- >> Just in subscription, we can actually do one-year terms and things like that, but obviously we don't want to completely throw the baby out of the bathwater, because a lot of subscription is a good thing, and Zai will provide subscription. Hopefully as we do this Cisco and HP on software, we can do one-year terms. >> It doesn't seem like these are distractions to you, I mean, Michael Dell always talks about the 90-day shock clock. With you, you sat down with Stu after the IPO, I was struck by your comments of "look, I'm not going to get all wound up about the stock price", you know, you're not going to obsess over it. Now it's easy not to obsess when you're growing at 60, 65% a year, but it doesn't seem like it's been a big distraction for you. >> Yeah, I think it's, just like a growing customer base can be a distraction, can be a strength, you know, because you could say, well, they're asking me not to innovate at all, and have the brute force figure out a way to have velocity and quality, because existing customers want quality, because they don't know what else you can be, like, give me a faster horse, right? And then you know from within the area we innovate that's where velocity matters. Same thing is true for Wall Street as well. Main Street wants both, Wall Street is saying look, as long as you can keep growing and grow wisely, I'm not going to touch you, actually. >> I want to ask you about your customers. We've had some great customers on. Most of the customers I've talked to that are Nutanix are what I'd call, you know, they're in the early part of the adoption, they're people that, they're taking some risks, we heard NASDAQ talk you know, forget about the fear, you've got to go forward. As you grow, how do you stop, you know, the enterprise buyer from trying to shift you, change your model? I loved that you're doing things like, you know, many companies are trying to switch to, you know, consumption models to pay as you grow, but as you try to grow that customer base, how do you pull them ahead or how do they not, you know, hold you back? >> Well I think as long as we have an authentic product, customer service, sales motion relationship they'll like us. And I think obviously there are different kind of sub-functions in the customer itself like procurement versus ID versus the business user and so on, and it's a constant hussle, there's no, again way to say that it's going to be a perfect world one day. If you can keep building great products, have great customer service, and we know that our sales motion is easy because it can, it can be a really good product and have really good customer support, but customers might hate transacting with you. I think that's the last piece that matters, and I think as computing becomes a real consumer market, that's what's happening you know with cloud, you can go and buy a computer like the way you used to buy your toothpaste or mouthwash or shampoo. I think it's becoming even more customer-centric, even more customer service-focused and so on. So I think the changing landscape of computing keeps a lot of vendors honest actually. Now, that doesn't mean that everybody will innovate, enough of them will say look, I'm done, and I think one of the things we've done well in the last five years is that the thesis of the product market fit. Like well, we know this is the product direction, this is the vision of the company, it has actually stuck. You know, people have said "I like what you guys are saying," actually. Over and over and over again, I mean, combos and acquisition, people are like "I love this". HP was one of those really audacious ideas, people said "I love this, now that I see it, I love it, when I didn't see it, I was skeptical". So I think a lot of the thesis of the company around innovation have worked in our favor. I think if we keep having that luck with ourselves, good things will happen. >> So Dheeraj, your positioning of the company has usually been a little bit ahead of the market, you know, for years it was like, ah, what, that HEI thing is a niche, and it's not really much that different, oh, enterprise cloud is nothing more than, you know, kind of vapor you know, what are the misperceptions you see today that you'd want to clarify for the market as to who Nutanix is today and where you're going? >> Well the first one is that we are a hardware company, because we are a hardware company, even though we sell a lot of software within the hardware and obviously we do a lot more software these days. And the fact that HEI's the destination, where HEIs basically was a mere milestone like five years ago or something, you know, we talk about I'd say about five years ago imagine a lot of the competition is talking about SEI today, when people are saying the compute storage form factor is interesting but not that interesting because I need to figure out how to converge clouds now, not just converge devices within my data center, I need to figure out OPEX and CAPEX, how do I meld those things, how do I burst, and things like that, you know. So the story keeps evolving because the consumers, the customers, and the competitors continue to evolve the market as well actually. So I would say that people have to look at us as an OS company, and the more they try us the more they realize why we are an OS company. They look at our networking R&D, they look at our security pieces together, storage, hypervisor, and now Zai, I think, you know, good things will happen. >> I inferred from your keynote yesterday that you're on a mission to change the operating model. Certainly Amazon has changed the operating model as we well know and it's translated into their operating profit, you know, their marginal economics as we've talked about in the past are compelling, software-like for services. As you change that operate- first of all, did I get that right? Are you on that- >> I call it a consumption model. >> Consumption model, great. So where do you see that going for customers? They're obviously taking labor costs out, how far can they take that- how much can you sort of automate in that process for your own company, taking those labor costs out to drive your margin? >> I think again, now going back to this idea of invisible infrastructure, just like it has no finish line, automation has no finish line. We used to automate 50 years ago as well. Automation as a word has existed for 200 years you know, since the industrial revolution actually. So again, there's no finish line in automation, there's no finish line for what machines can do compared to humans and I think they've constantly evolved, I mean, 200 years ago we were primarily agrarian, we would do agriculture and nothing more, and today we are doing a lot more things with our brain and I think we're becoming a more evolved species actually. So I think as machines do more, humans will also figure out a way to continue to do higher level things, so I think the best part about this company is that what we have chosen has no end to it, and the more we think we automate, the more we'll have to automate some more actually. And not just within the realm of compute, virtualization, or storage or networking or security, but also migration, portability, you know, what does it mean to really look at things on and off premise and things like that, so a lot of work is around that. Application automation is a big part of it as well. >> When I hear you say there's no finish line, it reminds me of Jeff Bezos, he says, "there is no day two, we will always be in day one". The two concerns I have, that is, number one, you can't have your employees constantly be charging, you know they run to the point where they're going to burn out and I hear Amazon is a challenging company to work for. Secondly, every customer I talk to, like, boy, they can't keep up with the six week release cycles that are coming at that, you know, remember when it used to be 18 to 24 months, you know, that was nice, we could do upgrade cycles when we want. How do you internally and with customers manage that pace of change and avoid burnout or over-complicating the environment for your customers? >> That's a great point actually, because obviously, if you don't have delighted work, it's hard. For them right now their delight, for Amazon employees, it's stock pricing. That's the only delight they have. But I look at it as a marathon of strengths. You basically have to sprint, take some rest, like after this we'll rest a little, and then say let's go and do another sprint, because NIS is another sprint, you know, and then reading all this stuff is another sprint, so I think if we can keep looking at that, and plus even do a little bit of baton-passing that'll happen, you know, I think as a company, we were all in San Jose and now some of the baton has passed to Seattle, some of the baton has passed to RDP Durham and Bangalore. We build this distributed workforce where different teams are coming in and saying "now I can run with it as well", like Bangalore could not have run with this six, seven, eight years ago, because everything was here. You know, RDP and Seattle were too small for us so I think there's critical mass emerging where the overall morale of the workforce is actually just as good as it was like five, six, seven years ago. Now, people talk about burnout a lot, but I also believe that a lot of this is choice. People who are saying "I know how to blend work and life". It's becoming hybrid, there's no such thing as work separate, life separate, it's melding into each other right now, and it's really becoming like this where people who are working smarter saying "I can figure out what that means in terms of balance". And millenials are again one of those who were born with all these things from day one. So the devices have been with them from day one, actually. They're saying "well, I can't not interact with the machine some time or the other". So I think that a lot of this is evolution for us, I mean, the eight to five way of looking at work, which is "batch processing", is now becoming multitasking and so on, so what happened to operating systems 30, 40 years ago is what's happening to humans as well actually. >> You know, we're out of time, but I wanted to share with our audience, one of the unique things about this conference is that you have advisors. A lot of people hire McKinsey and it all stays, you know, behind closed doors. Condi Rice, Robert Gates, Stephen Hadley, Deepak Malhotra, these are advisors to your company and we've met them all, many have been on theCUBE. You share with your community, your advisors, and you put them in front of your community and it's great content. I've really not seen a company be that transparent with its advisors before. Deliberate? Just sort of happens? >> It's always been like that actually, you know because the more a company learns from them, honestly, the more we've gotten out of them in turns of ROI, if you just think of it from a left wing point of view, but the right wing is that people want to build careers, not just wealth, they want to build careers, they want to actually be with folks that they can look up to you know, when the going gets tough. How do you remember somebody's words? Not just in books, but you know, in flesh and blood, you're like, wow, I talked to Condi Rice, I talked to Bob Gates, I talked to Steve Hadley, these people told me exactly what they went through, and I think there's no substitute to experience actually. To me, people like Mark Templeton and Frank Slootman, they all are great sources of energy and aspiration and ambition as well. >> Outstanding. >> No compression I've heard on experience, right Dave? >> That's right. Dheeraj, I feel calm just hanging out with you here, so thanks very much for coming back on theCUBE, it's always a pleasure to see you, and thanks for having us. Alright, keep it right there everybody, Stu and I will be back with our next guest. We're live from .Next, be right back. (electronic music)