(gentle music playing) >> For centuries, we've been captivated by the concept of machines doing the job of humans. And over the past decade or so, we've really focused on AI and the possibility of intelligent machines that can perform cognitive tasks. Now in the past few years, with the popularity of machine learning models ranging from recent ChatGPT to Bert, we're starting to see how AI is changing the way we interact with the world. How is AI transforming the way we do business? And what does the future hold for us there. At theCube, we've covered Oracle's AI and ML strategy for years, which has really been used to drive automation into Oracle's autonomous database. We've talked a lot about MySQL HeatWave in database machine learning, and AI pushed into Oracle's business apps. Oracle, it tends to lead in AI, but not competing as a direct AI player per se, but rather embedding AI and machine learning into its portfolio to enhance its existing products, and bring new services and offerings to the market. Now, last October at Cloud World in Las Vegas, Oracle partnered with Nvidia, which is the go-to AI silicon provider for vendors. And they announced an investment, a pretty significant investment to deploy tens of thousands more Nvidia GPUs to OCI, the Oracle Cloud Infrastructure and build out Oracle's infrastructure for enterprise scale AI. Now, Oracle CEO, Safra Catz said something to the effect of this alliance is going to help customers across industries from healthcare, manufacturing, telecoms, and financial services to overcome the multitude of challenges they face. Presumably she was talking about just driving more automation and more productivity. Now, to learn more about Oracle's plans for AI, we'd like to welcome in Elad Ziklik, who's the vice president of AI services at Oracle. Elad, great to see you. Welcome to the show. >> Thank you. Thanks for having me. >> You're very welcome. So first let's talk about Oracle's path to AI. I mean, it's the hottest topic going for years you've been incorporating machine learning into your products and services, you know, could you tell us what you've been working on, how you got here? >> So great question. So as you mentioned, I think most of the original four-way into AI was on embedding AI and using AI to make our applications, and databases better. So inside mySQL HeatWave, inside our autonomous database in power, we've been driving AI, all of course are SaaS apps. So Fusion, our large enterprise business suite for HR applications and CRM and ELP, and whatnot has built in AI inside it. Most recently, NetSuite, our small medium business SaaS suite started using AI for things like automated invoice processing and whatnot. And most recently, over the last, I would say two years, we've started exposing and bringing these capabilities into the broader OCI Oracle Cloud infrastructure. So the developers, and ISVs and customers can start using our AI capabilities to make their apps better and their experiences and business workflow better, and not just consume these as embedded inside Oracle. And this recent partnership that you mentioned with Nvidia is another step in bringing the best AI infrastructure capabilities into this platform so you can actually build any type of machine learning workflow or AI model that you want on Oracle Cloud. >> So when I look at the market, I see companies out there like DataRobot or C3 AI, there's maybe a half dozen that sort of pop up on my radar anyway. And my premise has always been that most customers, they don't want to become AI experts, they want to buy applications and have AI embedded or they want AI to manage their infrastructure. So my question to you is, how does Oracle help its OCI customers support their business with AI? >> So it's a great question. So I think what most customers want is business AI. They want AI that works for the business. They want AI that works for the enterprise. I call it the last mile of AI. And they want this thing to work. The majority of them don't want to hire a large and expensive data science teams to go and build everything from scratch. They just want the business problem solved by applying AI to it. My best analogy is Lego. So if you think of Lego, Lego has these millions Lego blocks that you can use to build anything that you want. But the majority of people like me or like my kids, they want the Lego death style kit or the Lego Eiffel Tower thing. They want a thing that just works, and it's very easy to use. And still Lego blocks, you still need to build some things together, which just works for the scenario that you're looking for. So that's our focus. Our focus is making it easy for customers to apply AI where they need to, in the right business context. So whether it's embedding it inside the business applications, like adding forecasting capabilities to your supply chain management or financial planning software, whether it's adding chat bots into the line of business applications, integrating these things into your analytics dashboard, even all the way to, we have a new platform piece we call ML applications that allows you to take a machine learning model, and scale it for the thousands of tenants that you would be. 'Cause this is a big problem for most of the ML use cases. It's very easy to build something for a proof of concept or a pilot or a demo. But then if you need to take this and then deploy it across your thousands of customers or your thousands of regions or facilities, then it becomes messy. So this is where we spend our time making it easy to take these things into production in the context of your business application or your business use case that you're interested in right now. >> So you mentioned chat bots, and I want to talk about ChatGPT, but my question here is different, we'll talk about that in a minute. So when you think about these chat bots, the ones that are conversational, my experience anyway is they're just meh, they're not that great. But the ones that actually work pretty well, they have a conditioned response. Now they're limited, but they say, which of the following is your problem? And then if that's one of the following is your problem, you can maybe solve your problem. But this is clearly a trend and it helps the line of business. How does Oracle think about these use cases for your customers? >> Yeah, so I think the key here is exactly what you said. It's about task completion. The general purpose bots are interesting, but as you said, like are still limited. They're getting much better, I'm sure we'll talk about ChatGPT. But I think what most enterprises want is around task completion. I want to automate my expense report processing. So today inside Oracle we have a chat bot where I submit my expenses the bot ask a couple of question, I answer them, and then I'm done. Like I don't need to go to our fancy application, and manually submit an expense report. I do this via Slack. And the key is around managing the right expectations of what this thing is capable of doing. Like, I have a story from I think five, six years ago when technology was much inferior than it is today. Well, one of the telco providers I was working with wanted to roll a chat bot that does realtime translation. So it was for a support center for of the call centers. And what they wanted do is, Hey, we have English speaking employees, whatever, 24/7, if somebody's calling, and the native tongue is different like Hebrew in my case, or Chinese or whatnot, then we'll give them a chat bot that they will interact with and will translate this on the fly and everything would work. And when they rolled it out, the feedback from customers was horrendous. Customers said, the technology sucks. It's not good. I hate it, I hate your company, I hate your support. And what they've done is they've changed the narrative. Instead of, you go to a support center, and you assume you're going to talk to a human, and instead you get a crappy chat bot, they're like, Hey, if you want to talk to a Hebrew speaking person, there's a four hour wait, please leave your phone and we'll call you back. Or you can try a new amazing Hebrew speaking AI powered bot and it may help your use case. Do you want to try it out? And some people said, yeah, let's try it out. Plus one to try it out. And the feedback, even though it was the exact same technology was amazing. People were like, oh my God, this is so innovative, this is great. Even though it was the exact same experience that they hated a few weeks earlier on. So I think the key lesson that I picked from this experience is it's all about setting the right expectations, and working around the right use case. If you are replacing a human, the level is different than if you are just helping or augmenting something that otherwise would take a lot of time. And I think this is the focus that we are doing, picking up the tasks that people want to accomplish or that enterprise want to accomplish for the customers, for the employees. And using chat bots to make those specific ones better rather than, hey, this is going to replace all humans everywhere, and just be better than that. >> Yeah, I mean, to the point you mentioned expense reports. I'm in a Twitter thread and one guy says, my favorite part of business travel is filling out expense reports. It's an hour of excitement to figure out which receipts won't scan. We can all relate to that. It's just the worst. When you think about companies that are building custom AI driven apps, what can they do on OCI? What are the best options for them? Do they need to hire an army of machine intelligence experts and AI specialists? Help us understand your point of view there. >> So over the last, I would say the two or three years we've developed a full suite of machine learning and AI services for, I would say probably much every use case that you would expect right now from applying natural language processing to understanding customer support tickets or social media, or whatnot to computer vision platforms or computer vision services that can understand and detect objects, and count objects on shelves or detect cracks in the pipe or defecting parts, all the way to speech services. It can actually transcribe human speech. And most recently we've launched a new document AI service. That can actually look at unstructured documents like receipts or invoices or government IDs or even proprietary documents, loan application, student application forms, patient ingestion and whatnot and completely automate them using AI. So if you want to do one of the things that are, I would say common bread and butter for any industry, whether it's financial services or healthcare or manufacturing, we have a suite of services that any developer can go, and use easily customized with their own data. You don't need to be an expert in deep learning or large language models. You could just use our automobile capabilities, and build your own version of the models. Just go ahead and use them. And if you do have proprietary complex scenarios that you need customer from scratch, we actually have the most cost effective platform for that. So we have the OCI data science as well as built-in machine learning platform inside the databases inside the Oracle database, and mySQL HeatWave that allow data scientists, python welding people that actually like to build and tweak and control and improve, have everything that they need to go and build the machine learning models from scratch, deploy them, monitor and manage them at scale in production environment. And most of it is brand new. So we did not have these technologies four or five years ago and we've started building them and they're now at enterprise scale over the last couple of years. >> So what are some of the state-of-the-art tools, that AI specialists and data scientists need if they're going to go out and develop these new models? >> So I think it's on three layers. I think there's an infrastructure layer where the Nvidia's of the world come into play. For some of these things, you want massively efficient, massively scaled infrastructure place. So we are the most cost effective and performant large scale GPU training environment today. We're going to be first to onboard the new Nvidia H100s. These are the new super powerful GPU's for large language model training. So we have that covered for you in case you need this 'cause you want to build these ginormous things. You need a data science platform, a platform where you can open a Python notebook, and just use all these fancy open source frameworks and create the models that you want, and then click on a button and deploy it. And it infinitely scales wherever you need it. And in many cases you just need the, what I call the applied AI services. You need the Lego sets, the Lego death style, Lego Eiffel Tower. So we have a suite of these sets for typical scenarios, whether it's cognitive services of like, again, understanding images, or documents all the way to solving particular business problems. So an anomaly detection service, demand focusing service that will be the equivalent of these Lego sets. So if this is the business problem that you're looking to solve, we have services out there where we can bring your data, call an API, train a model, get the model and use it in your production environment. So wherever you want to play, all the way into embedding this thing, inside this applications, obviously, wherever you want to play, we have the tools for you to go and engage from infrastructure to SaaS at the top, and everything in the middle. >> So when you think about the data pipeline, and the data life cycle, and the specialized roles that came out of kind of the (indistinct) era if you will. I want to focus on two developers and data scientists. So the developers, they hate dealing with infrastructure and they got to deal with infrastructure. Now they're being asked to secure the infrastructure, they just want to write code. And a data scientist, they're spending all their time trying to figure out, okay, what's the data quality? And they're wrangling data and they don't spend enough time doing what they want to do. So there's been a lack of collaboration. Have you seen that change, are these approaches allowing collaboration between data scientists and developers on a single platform? Can you talk about that a little bit? >> Yeah, that is a great question. One of the biggest set of scars that I have on my back from for building these platforms in other companies is exactly that. Every persona had a set of tools, and these tools didn't talk to each other and the handoff was painful. And most of the machine learning things evaporate or die on the floor because of this problem. It's very rarely that they are unsuccessful because the algorithm wasn't good enough. In most cases it's somebody builds something, and then you can't take it to production, you can't integrate it into your business application. You can't take the data out, train, create an endpoint and integrate it back like it's too painful. So the way we are approaching this is focused on this problem exactly. We have a single set of tools that if you publish a model as a data scientist and developers, and even business analysts that are seeing a inside of business application could be able to consume it. We have a single model store, a single feature store, a single management experience across the various personas that need to play in this. And we spend a lot of time building, and borrowing a word that cellular folks used, and I really liked it, building inside highways to make it easier to bring these insights into where you need them inside applications, both inside our applications, inside our SaaS applications, but also inside custom third party and even first party applications. And this is where a lot of our focus goes to just because we have dealt with so much pain doing this inside our own SaaS that we now have built the tools, and we're making them available for others to make this process of building a machine learning outcome driven insight in your app easier. And it's not just the model development, and it's not just the deployment, it's the entire journey of taking the data, building the model, training it, deploying it, looking at the real data that comes from the app, and creating this feedback loop in a more efficient way. And that's our focus area. Exactly this problem. >> Well thank you for that. So, last week we had our super cloud two event, and I had Juan Loza on and he spent a lot of time talking about how open Oracle is in its philosophy, and I got a lot of feedback. They were like, Oracle open, I don't really think, but the truth is if you think about database Oracle database, it never met a hardware platform that it didn't like. So in that sense it's open. So, but my point is, a big part of of machine learning and AI is driven by open source tools, frameworks, what's your open source strategy? What do you support from an open source standpoint? >> So I'm a strong believer that you don't actually know, nobody knows where the next slip fog or the next industry shifting innovation in AI is going to come from. If you look six months ago, nobody foreseen Dali, the magical text to image generation and the exploding brought into just art and design type of experiences. If you look six weeks ago, I don't think anybody's seen ChatGPT, and what it can do for a whole bunch of industries. So to me, assuming that a customer or partner or developer would want to lock themselves into only the tools that a specific vendor can produce is ridiculous. 'Cause nobody knows, if anybody claims that they know where the innovation is going to come from in a year or two, let alone in five or 10, they're just wrong or lying. So our strategy for Oracle is to, I call this the Netflix of AI. So if you think about Netflix, they produced a bunch of high quality shows on their own. A few years ago it was House of Cards. Last month my wife and I binge watched Ginny and Georgie, but they also curated a lot of shows that they found around the world and bought them to their customers. So it started with things like Seinfeld or Friends and most recently it was Squid games and those are famous Israeli TV series called Founder that Netflix bought in, and they bought it as is and they gave it the Netflix value. So you have captioning and you have the ability to speed the movie and you have it inside your app, and you can download it and watch it offline and everything, but nobody Netflix was involved in the production of these first seasons. Now if these things hunt and they're great, then the third season or the fourth season will get the full Netflix production value, high value budget, high value location shooting or whatever. But you as a customer, you don't care whether the producer and director, and screenplay writing is a Netflix employee or is somebody else's employee. It is fulfilled by Netflix. I believe that we will become, or we are looking to become the Netflix of AI. We are building a bunch of AI in a bunch of places where we think it's important and we have some competitive advantage like healthcare with Acellular partnership or whatnot. But I want to bring the best AI software and hardware to OCI and do a fulfillment by Oracle on that. So you'll get the Oracle security and identity and single bill and everything you'd expect from a company like Oracle. But we don't have to be building the data science, and the models for everything. So this means both open source recently announced a partnership with Anaconda, the leading provider of Python distribution in the data science ecosystem where we are are doing a joint strategic partnership of bringing all the goodness into Oracle customers as well as in the process of doing the same with Nvidia, and all those software libraries, not just the Hubble, both for other stuff like Triton, but also for healthcare specific stuff as well as other ISVs, other AI leading ISVs that we are in the process of partnering with to get their stuff into OCI and into Oracle so that you can truly consume the best AI hardware, and the best AI software in the world on Oracle. 'Cause that is what I believe our customers would want the ability to choose from any open source engine, and honestly from any ISV type of solution that is AI powered and they want to use it in their experiences. >> So you mentioned ChatGPT, I want to talk about some of the innovations that are coming. As an AI expert, you see ChatGPT on the one hand, I'm sure you weren't surprised. On the other hand, maybe the reaction in the market, and the hype is somewhat surprising. You know, they say that we tend to under or over-hype things in the early stages and under hype them long term, you kind of use the internet as example. What's your take on that premise? >> So. I think that this type of technology is going to be an inflection point in how software is being developed. I truly believe this. I think this is an internet style moment, and the way software interfaces, software applications are being developed will dramatically change over the next year two or three because of this type of technologies. I think there will be industries that will be shifted. I think education is a good example. I saw this thing opened on my son's laptop. So I think education is going to be transformed. Design industry like images or whatever, it's already been transformed. But I think that for mass adoption, like beyond the hype, beyond the peak of inflected expectations, if I'm using Gartner terminology, I think certain things need to go and happen. One is this thing needs to become more reliable. So right now it is a complete black box that sometimes produce magic, and sometimes produce just nonsense. And it needs to have better explainability and better lineage to, how did you get to this answer? 'Cause I think enterprises are going to really care about the things that they surface with the customers or use internally. So I think that is one thing that's going to come out. And the other thing that's going to come out is I think it's going to come industry specific large language models or industry specific ChatGPTs. Something like how OpenAI did co-pilot for writing code. I think we will start seeing this type of apps solving for specific business problems, understanding contracts, understanding healthcare, writing doctor's notes on behalf of doctors so they don't have to spend time manually recording and analyzing conversations. And I think that would become the sweet spot of this thing. There will be companies, whether it's OpenAI or Microsoft or Google or hopefully Oracle that will use this type of technology to solve for specific very high value business needs. And I think this will change how interfaces happen. So going back to your expense report, the world of, I'm going to go into an app, and I'm going to click on seven buttons in order to get some job done like this world is gone. Like I'm going to say, hey, please do this and that. And I expect an answer to come out. I've seen a recent demo about, marketing in sales. So a customer sends an email that is interested in something and then a ChatGPT powered thing just produces the answer. I think this is how the world is going to evolve. Like yes, there's a ton of hype, yes, it looks like magic and right now it is magic, but it's not yet productive for most enterprise scenarios. But in the next 6, 12, 24 months, this will start getting more dependable, and it's going to change how these industries are being managed. Like I think it's an internet level revolution. That's my take. >> It's very interesting. And it's going to change the way in which we have. Instead of accessing the data center through APIs, we're going to access it through natural language processing and that opens up technology to a huge audience. Last question, is a two part question. And the first part is what you guys are working on from the futures, but the second part of the question is, we got data scientists and developers in our audience. They love the new shiny toy. So give us a little glimpse of what you're working on in the future, and what would you say to them to persuade them to check out Oracle's AI services? >> Yep. So I think there's two main things that we're doing, one is around healthcare. With a new recent acquisition, we are spending a significant effort around revolutionizing healthcare with AI. Of course many scenarios from patient care using computer vision and cameras through automating, and making better insurance claims to research and pharma. We are making the best models from leading organizations, and internal available for hospitals and researchers, and insurance providers everywhere. And we truly are looking to become the leader in AI for healthcare. So I think that's a huge focus area. And the second part is, again, going back to the enterprise AI angle. Like we want to, if you have a business problem that you want to apply here to solve, we want to be your platform. Like you could use others if you want to build everything complicated and whatnot. We have a platform for that as well. But like, if you want to apply AI to solve a business problem, we want to be your platform. We want to be the, again, the Netflix of AI kind of a thing where we are the place for the greatest AI innovations accessible to any developer, any business analyst, any user, any data scientist on Oracle Cloud. And we're making a significant effort on these two fronts as well as developing a lot of the missing pieces, and building blocks that we see are needed in this space to make truly like a great experience for developers and data scientists. And what would I recommend? Get started, try it out. We actually have a shameless sales plug here. We have a free deal for all of our AI services. So it typically cost you nothing. I would highly recommend to just go, and try these things out. Go play with it. If you are a python welding developer, and you want to try a little bit of auto mail, go down that path. If you're not even there and you're just like, hey, I have these customer feedback things and I want to try out, if I can understand them and apply AI and visualize, and do some cool stuff, we have services for that. My recommendation is, and I think ChatGPT got us 'cause I see people that have nothing to do with AI, and can't even spell AI going and trying it out. I think this is the time. Go play with these things, go play with these technologies and find what AI can do to you or for you. And I think Oracle is a great place to start playing with these things. >> Elad, thank you. Appreciate you sharing your vision of making Oracle the Netflix of AI. Love that and really appreciate your time. >> Awesome. Thank you. Thank you for having me. >> Okay. Thanks for watching this Cube conversation. This is Dave Vellante. We'll see you next time. (gentle music playing)

>>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. >>Hey, welcome back to the cube at Lisa Martin with Steve men and men and we are coming to you alive from combo go 19 please to welcome to the cube, a gent from Microsoft Azure. We've got Ben call principal program manager. Ben, welcome. Thank you. Thanks for having me on. Thanks for coming on. So Microsoft combo, what's going on with the partnership? >>They wouldn't have have great storage pond is in data management space. We've been working with Convult for 20 years now in Microsoft and and they've been working with us on Azure for that as long as I can remember not being on that the Azure business for about seven years now. So just a long time in cloud terms like dog ears and it's sort of, they've been doing a huge amount there around getting customer data into the cloud, reducing costs, getting more resiliency and then also letting them do more with the data. So they're a pretty good partner to have and they make it much easy for their customers to to go and leverage cloud. >> So Ben, you know, in my career I've had lots of interactions with the Microsoft storage team. Things have changed a little bit when you're now talking about Azure compared to more, it was the interaction with the operating system or the business suite at had. >>So maybe bring us up to date as those people that might not have followed where kind of the storage positioning inside of Microsoft is now that when we talk about Azure and your title. Yeah, we, we sort of can just, just briefly, we worked very heavily with our own premises brethren, they are actually inside the O team is inside of the Azure engineering old male, which is kind of funny, but we do a load of things there. If he started looking at, firstly on that, that hybrid side, we have things like Azure files. It's a highly resilient as a service SMB NFS file Shafter a hundred terabytes, but that interacts directly with windows server to give you Azure file sync. So there is sort of synergies there as well. What I'm doing personally, my team, we work on scale storage. The big thing we have in there is owl is out blood storage technology, which really is the underpinning technology fault. >>Preapproval storage and Azure, which is an including our SAS offerings, which are hosted on Azure too. So disc is on blood storage of files on blood storage. You look at Xbox live, all these kind of stuff is a customer to us. So we build that out and we were doing work there and that's, that's really, really interesting. And how we do it. And that's not looking at going, we're gonna buy some compute, we're going to buy some storage, we're going to build it out, we're going to run windows or hyper V or maybe VM-ware with hoc with windows running on the VMware, whatever else. This is more a story about we're gonna provide you storage as a service. You didn't get a minimum of like 11 nines at your ability. And and be able to have that scale to petabytes of capacity in one logical namespace and give you multiple gigabytes, double digit gigabytes of throughput to that storage. >>And now we're even that about to multiple protocols. So rest API century. Today we've got Azure stack storage, EU API, she can go and use, but we give you that consistency of the actual backend storage and the objects and the data available via more than just one protocol. You can go and access that via HDFS API. We talk about data lakes all the time. For us, our blood storage is a data Lake. We turn on hierarchal namespace and you can go and access that via other protocols like as I mentioned HDFS as well. So that is a big story about what we want to do. We want to make that data available at crazy scale, have no limits in the end to the capacity or throughput or performance and over any protocol. That's kind of our lawn on the Hill about what we want to get to. >>And we've been talking to the Combolt team about some of the solutions that they are putting in the cloud. The new offering metallic that came out. They said if my customer has Azure storage or storage from that other cloud provider, you could just go ahead and use that. Maybe how familiar and how much I know you've been having about run metallic. >> We were working, we work pretty tightly with the product team over Convolt around this and my team as well around how do we design and how do we make it work the best and we're going to continue working to optimize as they get to beyond initial launch to go, wow, we've got data sets we we can analyze. We knew how to, we wanted out of tune it. Now really we love the solution particularly more because you know the default if you don't select the storage type where you want to go, you will run on Azure. >>So really sort of be cued off to the relationship there. They chose us as a first place we'll go to, but they've also done the choice for customers. So some customers may want to take it to another cloud. That's fine. It's reasonable. I mean we totally understand it's going to be a multicloud world and that's a reality for any large company. Our goal is to make sure we're growing faster than the competitors, not to knock out the competitors altogether because that just won't happen. So they've got that ability to go and, yeah, Hey, we'll use Azure as default because they feel we're offering the best support and the best solution there. But then if they have that customer, same customer wants to turn around and use a competitor of ours, fine as well. And I see people talking about that today where they may want to mitigate risks and say, I'm going to do, I'm doing off office three, six five on a, taken off this three 65 backup. It's cool. You use metallic, it'll take it maybe to a different region in Asia and they're backing up. They still going, well, I'm still all in on Microsoft. They may want to take it to another cloud or even take it back to on premise. So that does happen too because just in case of that moment we can get that data back in a different location. Something >>so metallic talking about that is this new venture is right. It's a Convolt venture and saw that the other day and thought that's interesting. So we dug into it a little bit yesterday and it's like a startup operating within a 20 year old company, which is very interesting. Not just from an incumbent customer perspective, but an incumbent partner perspective. How have you seen over the last few years and particularly bad in the last nine months with big leadership and GTM changes for condo? How has the partnership with Microsoft evolved as a result of those changes? >>Um, it's always been interesting. I guess when you start looking at adventure and everything seems to, things change a little bit. Priorities may change just to be fair, but we've had that tight relationship for a long time and a relationship level and an exec leadership level, nothing's really changed. But in the way they're building this platform, we, we sit down out of my team at the Azure engineering group and we'll sit down and do things like ideations. Like here's where we see gaps in the markets, here's what we believe could happen. And look back in July, we had inspire, which is our partner conference in Las Vegas and we sat down with their OT, our OT in a room, we'll talking about these kinds of things. And this is I think about two months after they may have started the initial development metallic from what I understand, but we're talking about exactly what they're doing with metallic offered as a service in Azure as, Hey, how about we do this? So we think it's really cool. It opens up a new market to convert I think too. I mean they're so strong in the enterprise, but they don't do much in the smaller businesses because with the full feature product, it also has inherent complexibility complexity around it. So by doing metallic, is it click, click, next done thing. They really opening I think new markets to them and also to us as a partner. >>I was going to add, you know, kind of click on that because they developed this very quickly. This is something that I think what student were here yesterday, metallic was kind of conceived, designed, built in about six months. So in terms of like acceleration, that's kind of a new area for Combolt. >>Yeah, and I think, I think they're really embracing the fact about let's release our code in production for, for products which are sort of getting the, getting to the, Hey, the product is at the viable stage now, not minimum viable, viable, let's release in production, let's find out how customers are using it and then let's keep optimizing and doing that constant iteration, taking that dev ops approach to let's get it out there, let's get it launched, and then let's do these small batches of changes based on customer need, based on tele telemetry. We can actually get in. We can't get the telemetry without having customers. So that's how it's going to keep working. So I think this initial product we see today, it's just going to keep evolving and improving as they get more data, as they get more information, more feedback, which is exactly what we want to see. >>Well, what will come to the cloud air or something you've been living in for a number of years. Ben, I'd love to hear you've been meeting with customers, they've been asking you questions, gives us some of the, you know, some of the things that, what's top of mind for some of the customers? What kinds of things did they come into Microsoft, Dawn, and how's that all fit together? >>There's many different conferences of interrelate, many different conversations and there'll be, we'll go from talking about, you know, Python machine learning or AI fits in PowerPoint. >>Yeah. >>It's a things like, you know, when are we gonna do incremental snapshots from the manage disks, get into the weeds on very infrastructure centric stuff. We're seeing range of conversations there. The big thing I think I see, keep seeing people call out and make assumptions of is that they're not going to be relevant because cloud, I don't know cloud yet. I don't know this whole coup cube thing, containers, I don't really understand that as well as I think I need to. And an AI, Oh my gosh, what do we even do there? Cause everyone's throwing the words and terms around. But to be honest, I think would still really evident is cloud is still is tiny fraction of enterprise workloads. So let's be honest, it's growing at a huge rate because it is that small fraction. So again, there's plenty of time for people to learn but they shouldn't go and try. >>And so it's not like you go and learn everything in the technology stack from networking to development to database management to, to running a data set of power and cooling. You learn the things that are applicable to what you're trying to do. And the same thing goes to cloud. Any of these technologies go and look at what you need to build for your business. Take it that step and then go and find out the details and levels you want to know. And as someone who's been on Azure for, like I said, almost seven years, which is crazy long. That was, that was literally like being in a startup instead of Microsoft when I joined and I wasn't sure if I wanted to join a licensing company. It's been very evident to me. I will not say I'm an Azure expert and I've been seven years in the platform. >>There are too many things for for me to be an expert in everything on, and I think people sort of just have to realize that anyone's saying that it's bravado. Nothing else. Oh, people. The goal is Microsoft as a platform provider. Hopefully you've got the software and the solution does make a lot of this easier for the customer, so hopefully they shouldn't need to become a Coobernetti's expert because it's baked into your platform. They shouldn't have to worry about some of these offerings because it's SAS. Most customers are there. Some things you need to learn between going from exchange to go into Oh three 65 absolutely. There's some nuances and things like that, but once you get over that initial hurdle, it should be a little easier. I think it's right and I think going back to that, sort of going back to bear principles going, what is the highest level of distraction that's viable for your business or that application or this workload has to always be done with everything. If it's like, well, class, not even viable, running on premises, don't, don't need to apologize for not running in cloud. If I as this, what's happening for you because of security, because of application architecture, run it that way. Don't feel the need and the pressure to have to push it that way. I think too many people get caught up in this shiny stuff up here, which is what you know 1% of people are doing versus the other 99% which is still happening in a lot of the areas we work and have challenges in today. >>That's a great point that you bring up because there is all the buzz words, right? AI, machine learning cloud. You've got to be cloud ready. You've got to be data-driven to customer. To your point going, I just need to make sure that what we have set up for our business is going to allow our business one to remain relevant, but to also be able to harness the power of the data that they have to extract new opportunities, new insights, and not get caught up with, shoot, should we be using automation? Should we be using AI? Everybody's talking about it. I liked that you brought up and I find it very respectfully, he said, Hey, I'm not an Azure expert. You'd been there seven, seven dog years like you said. And I think that's what customers probably gained confidence in is hearing the folks like you that they look to for that guidance and that leadership saying, no, I don't know everything to know. But giving them the confidence that their tribe, they're trusting you with that data and also helping look, trusting you to help them make the right decisions for their business. >>Yeah, and that's, we've got to do that. I mean, I as a tech guy, it's like I've, I've loved seeing the changes. When I joined Microsoft, I, I wasn't lying. I was almost there go enough. I really want to join this company. I was going to go join a startup instead and I got asked to one stage in an interview going, why do you want to join Microsoft? We see you've never applied to, I'd never wanted to. A friend told me to come in and it's just been amazing to see those changes and I'm pretty proud on that. So when we talk about those things we're doing, I mean, I think there is no shame going, I'm just going to lift and shift machines because cloud's about flexibility. If you're doing it just on cost, probably doing it for the wrong reason. It's about that flexibility to go and do something. >>Then change within months and slowly make steps to make things better and better as you find a need as you find the ability, whatever it may be. And some of the big things that we focus on right now with customers is we've got a product called Azure advisor. It'll go until people, when one, you don't build things in a resilient manner. Hey, do you know this has not ha because of this and you can do this. It's like, great. We'll also will tell you about security vulnerabilities that maybe should a gateway here for security. Maybe you should do this or this is not patched. But the big thing of that, it also goes and tells you, Hey, you're overspending. You don't need this much. It provisions, you provision like a Ferrari, you need a, you just need a Prius. Go and run a Prius because it's going to do what you need. >>I need a paler list and that's part of that trusted suit. Getting that understanding, and it's counterintuitive, but we're now like, it's coming out of mozzarella too, which is great. But seeing these guys were dropping contracts and licenses and basically, you know, once every three years I may call the customer, Hey, how about renewal? Now, go from that to now being focused on the customer's actual success. I've focused on their growth in Azure as a platform. Our services growth, like utilization not in sales has been a huge change. It scared some people away, but it's brought a lot more people in and and that sort of counterintuitive spend less money thing actually leads in the longterm to people using more. >>Absolutely. That's definitely not the shrink wrap software company of Microsoft that I remember from the 90s yeah. might be similar to, you know, just as to get Convolt to 2019 is not the same combo that many of us know from 15 years ago. A good >>mutual friend of ours, sort of Simon and myself before I took this job, he and I sat down, we're having a beer and discussing the merits, all not Yvette go to things like that. Same with Convolt there. They're changing such such a great deal with, you know, what they're putting in the cloud, what they're doing with the data, where they're trying to achieve with things like for data management across on premises and cloud with microservices applications and stuff going, Hey, this won't work like this anymore. When you now are doing it on premises and with containers, it's pretty good to see. I'm interested to see how they take that even further to their current audience, which is product predominantly. You know the it pro, the data center admin, storage manager. >>It's funny when you talked about just the choice that customers have and those saying, aye, we shouldn't be following the trends because they're the trends. We actually interviewed a couple of hours ago, one of customers that is all on prime healthcare company and said, he's like, I want to make a sticker that says no cloud and proud and it just what there was, we don't normally hear from them. We always talk about cloud, but for a company to sit down and look at what's best for our business, whether it's, you know, FedRAMP certification challenges or HIPAA or GDPR, other compelling requirements to keep it on prem, it was just refreshing to hear this customer say, >>yeah, I mean it's just appropriate for them. You do what's right for you. I, yeah, it's no shame in any of it. It's, I mean you don't, you definitely don't get fans by it by shaming people about not doing something right. And I mean I've, I'm personally very happy to fee fee, you know, see sort of hype around things like blockchain die down a little bit. So it's a slow database and we should use it for this specific case of that shared ledger. You know, things like that where people don't have to know blockchain. Now I have to know IOT. It's like, yeah, and that hype gets people there, but it also causes a lot of anxiety and it's good to see someone actually not be ashamed of it. And they agree the ones when they do take a step and use cloud citizen may be in the business already, they're probably going to do it appropriately because have a reason, not just because we think this would be cool, right? >>Well not. And how much inherit and complexity does that bring in if somebody is really feeling pressured to follow those trends. And maybe that's when you end up with this hodgepodge of technologies that don't work well together. You're spending way more in as as business it folks are consumers, you know, consumers in their personal lives, they expect things to be accessible, visible, but also cost efficient because they have so much choice. >>Yeah, the choice choice is hard. It's just a, just the conversation I was having recently, for example, just we'll take the storage cause of where we are, right? It's like I'm running something on Azure, I'm a, I'm using Souza, I want an NFS Mount point, which is available to me in Fs. Great, perfect. what do I use as like, well you can use any one of these seven options like that, but what's the right choice? And that's the thing about being a platform can be, we give you a lot of choices, but it's still up to you or up to app hotness. It can really help the customers as well to make the most appropriate choice. And, and I, I pushed back really hard in terms of best practices and things. I hate it because again, it's making the assumption this is the best thing to do. >>It's not. It's always about, you know, what are the patterns that have worked for other people? What are the anti-patterns and what's the appropriate path for me to take? And that's actually how we're building our docs now too. So we, we keep, we keep focusing on our Azure technology and we're bringing out some of the biggest things we've done is how we manage our documentation. It's all open sourced, it's all in markdown on get hub. So you can go in and read a document from someone like myself is doing product management going, this is how to use this product and you're actually, this bit's wrong, this bit needs to be like this and you can go in yourself even now, make a change and we can go, Oh yeah and take that committed in and dual this kind of stuff in that way. So we're constantly taking those documents in that way and getting realtime feedback from customers who are using it, not just ourself in an echo chamber. >>So you get this great insight and visibility that you never had before. Well, Ben, thank you, Georgie stew and me on the queue this afternoon. Excited to hear what's coming up next for Azure. Makes appreciate your time. Thank you for steam and event. I, Lisa Martin, you're watching the cue from Convault go 19.

>>Live from Denver, Colorado. It's the cube covering com vault go 2019 brought to you by Combolt. >>Hey, welcome back to the Q but Lisa Martin with men and men and we are coming to you alive from Conn logo 19 please to welcome to the cube, a gent from Microsoft Azure. We've got Ben Nichol, principal program manager. Ben, welcome. Thank you. Thanks for having me on. Thanks for coming on. So Microsoft combo, what's going on with the partnership? >>They wouldn't have have great storage pond is in data management space. We've been working with Convolt for 20 years now in Microsoft and and they've been working with us on Azure for about as long as I can remember not being on that the Azure business RET seven years now. So just a long time in cloud terms like doggies and it sort of, they'd been doing a huge amount of their around getting customer data into the cloud, reducing costs, getting more resiliency and then also letting them do more with the data. So they were a pretty good partner to have and they make it much easy for their customers to to go and leverage cloud. So Ben, you know, in my career I've had lots of interactions with the Microsoft storage team. Things have changed a little bit when you're now talking about Azure compared to, you know, more. >>It was the interaction with the operating system or the business suite had. So maybe bring us up to date as those people that might not have followed. You know, we're kind of the storage positioning inside of Microsoft is now that when we talk about Azure and your title. Yeah, we, we sort of look and just just briefly, we worked very heavily with our on premises brethren. They actually inside the O S team is inside of the Azure engineering old male, which is kind of funny, but we do a lot of things there. If he started looking at, firstly on that hybrid side, we have things like Azure files. It's a highly resilient as a service SMB NFS file share up to a hundred terabytes but that interacts directly with windows server to give you Azure file sync. So there is sort of synergies there as well. When I'm doing personally my team, we work on scale storage. >>The big thing we have in there is Al is out blood storage technology, which really is the underpinning technology, full Priya tool storage and Azure which is including our SAS offerings which are hosted on Azure too. So disc is on blood storage, our files on blood storage, you look at Xbox live, all these kinds of stuff is a customer to us. So we build that out and we, we are doing work there and that's really, really interesting and how we do it and that's not looking at going we're going to buy some compute, we're going to buy some storage, we're going to build it out, we're going to run windows or hyper V or maybe VMware with windows running on the VMware, whatever else. This is more a story about wigging to provide you storage as a service. You didn't get a minimum of like 11 nines at your ability and and be able to have that scale to petabytes of capacity in one logical namespace and give you multiple gigabytes, double digit gigabytes of throughput to that storage. >>And now we're even moving about to model multiple protocols. So rest API century today we've got Azure stack storage, you pay API, she can go and use, but we give me that consistency of the actual back end storage and the objects and the data available via more than just one protocol. You can go and access that via HDFS API. As we talk about data lakes all the time. For us, our blood storage is a data Lake. We turn on hierarchal namespace and you can go and access that via our other protocols like as I mentioned HDFS as well. So that is a big story about what we want to do. We want to make that data available at crazy scale, have no limits in the end to the capacity or throughput or performance and over any protocol. That's kind of our line in the Hill about what we want to get to. >>And we've been talking to vault team about some of the solutions that they are putting in the cloud. The new offering metallic that came out. They said if my customer has Azure storage or storage from that other cloud provider, you could just go ahead and use that. Maybe how familiar and how much, I know you've been having a run metallic. We were working, we were pretty tightly with the product team over Convolt around this and my team as well around how do we design and how do we make it work the best and we're going to continue working to optimize as they get beyond initial launch to go, wow, we've got data sets we can analyze, we know how to, we wanted out of tune it. Now really we love the solution particularly more because the default, if you don't select the storage type where you want to go, you will run on Azure. >>So really sort of be kudos to the relationship there. They chose us as a first place we'll go to, but they've also done the choice for customers. Say some customers may want to take it to another cloud. That's fine. It's reasonable. I mean, we totally understand it's going to be a multi-cloud world and that's a reality for any large company. Our goal is to make sure we're growing faster than the competitors, not to knock out the competitors all together because that just won't happen. So they've got that ability to go and yet, Hey, we'll use Azure as default because they feel that way, offering the best support and the best solution there. But then if they have that customer, same customer wants to turn around and use a competitor, Val's fine as well. And I see people talking about that today where they may want to mitigate risks and say, I'm going to do, I'm doing all of office three, six, five on a taken office, three, six, five backup. It's cool. Use metallic, it'll take it maybe to a different region in Asia and they're backing up and they still going, well I'm still all in on Microsoft. They may want to take it to another cloud or even take it back to on premises. So that does happen too because just in case of that moment we can get that data back in a different location. Something happens. >>So metallic talking about that is this new venture is right. It's a Combolt venture and saw that the other day and thought that's interesting. So we dug into it a little bit yesterday and it's like a startup operating within a 20 year old company, which is very interesting. Not just from an incumbent customer perspective, but an incumbent partner perspective. How have you seen over the last few years and particularly bad in the last nine months with big leadership and GTM changes for combo? How has the partnership with Microsoft evolved as a result of those changes? >>Um, it's always been interesting. I guess when you start looking at adventure and everything, since things change a little bit, priorities may change just to be fair, but we've had that tight relationship for a long time. At a relationship level and an exec leadership level, nothing's really changed. But in the way they're building this platform, we sit down out of my team, out of the Azure engineering group and we'll sit down and do things like ideations, like here's where we see gaps in the markets, here's what we believe could happen. And look back in July, we had inspire, which is our partner conference in Las Vegas. When we sat down with their OT, our OT in a room, we'll talking about these kinds of things and this is I think about two months after they may have started the initial development metallic from what I understand, but we will talking about exactly what they're doing with metallic offered as a service in Azure is, Hey, how bout we do this? So we think it's really cool. It opens up a new market to Convolt I think too. I mean they're so strong in the enterprise, but they don't do much in smaller businesses because with a full feature product, it also has inherent complexibility complexity around it. So by doing metallic, is it click, click, next done thing. They're really opening, I think, new markets to them and also to us as a partner. >>I was going to ask, you know, kind of click on that because they developed this very quickly. This is something that I think what student were here yesterday, metallic was kind of conceived design built in about six months. So in terms of like acceleration, that's kind of a new area for Combalt. >>Yeah, and I think, I think they're really embracing the fact about um, let's release our code in production for products, which are sort of getting, getting to the, Hey that product is at the viable stage now, not minimum viable, viable, let's release in production, let's find out how customers are using Atlin, let's keep optimizing and doing that constant iteration, taking that dev ops approach to let's get it out there, let's get it launched. And then let's do these small batches of changes based on customer need, based on tele telemetry. We can actually get in. We can't get the telemetry without having customers. So that's how it's going to keep working. So I think this initial product we see today, it's just going to keep evolving and improving as they get more data, as they get more information, more feedback. Which is exactly what we want to see. >>Well, what will come to the cloud air or something you've been living in for a number of years. Ben, I'd love to hear you've been meeting with customers. They've been asking you questions, gives us some of the, you know, some of the things that, what's top of mind for some of the customers? What kinds of things did they come into Microsoft, Dawn, and how's that all fit together? >>There's many different conferences of interrelate, many different conversations and they'll, we will go from talking about, you know, Python machine learning or AI PowerPoint. >>Yeah. >>It's a things like, you know, when are we going to do incremental snapshots from a manage disks? Get into the weeds on very infrastructure century staff. We're seeing range of conversations there. The big thing I think I see, keep seeing people call out and make assumptions of is that they're not going to be relevant because cloud, I don't know cloud yet. I don't know this whole coup cube thing. Containers. I don't, I don't really understand that as well as I think I need to. And an AI, Oh my gosh, what do I even do there? Because everyone's throwing the words and terms around. But to be honest, I think what's still really evident is cloud is still is tiny fraction of enterprise workloads. Let's be honest, it's growing at a huge rate because it is that small fraction. So again, there's plenty of time for people to learn, but they shouldn't go and try and slip. >>It's not like you're going to learn everything in a technology stack, from networking to development to database management to, to running a data set of power and cooling. You learn the things that are applicable to what you're trying to do. And the same thing goes to cloud. Any of these technologies, go and look at what you need to build for your business. Take it to that step and then go and find out the details and levels you want to know. And as someone who's been on Azure for like a cinema seven years, which is crazy long. That was a, that was literally like being in a startup instead of Microsoft when I joined and I wasn't sure if I wanted to join a licensing company. It's been very evident to me. I will not say I'm an Azure expert and I've been seven years in the platform. >>There are too many things throughout my for me to be an expert in everything on and I think people sort of just have to realize that anyone saying that it's bravado, nothing else. The goal is Microsoft as a platform provider. Hopefully you've got the software and the solution to make a lot of this easier for the customer, so hopefully they shouldn't need to become a Kubernetes expert because it's baked into your platform. They shouldn't have to worry about some of these offerings because it's SAS. Most customers are there some things you need to learn between going from, you know, exchange to go into oath bricks, these five. Absolutely. There are some nuances and things like that, but once you get over that initial hurdle, it should be a little easier. I think it's right and I think going back to that, sort of going back to bare principles going, what is the highest level of distraction that's viable for your business or that application or this workload has to always be done with everything. >>If it's like, well, class, not even viable, run it on premises. Don't, don't need to apologize for not running in cloud. If I as is what's happening for you because of security, because of application architecture, run it that way. Don't feel the need and the pressure to have to push it that way. I think too many people get caught up in the shiny stuff up here, which is what you know 1% of people are doing versus the other 99% which is still happening in a lot of the areas we work and have challenges in today. >>That's a great point that you bring up because there is all the buzz words, right? AI, machine learning cloud. You've got to be cloud ready. You've gotta be data-driven to customer, to your point going, I just need to make sure that what we have set up for our business is going to allow our business one to remain relevant, but to also be able to harness the power of the data that they have to extract new opportunities, new insights, and not get caught up with, shoot, should we be using automation? Should we be using AI? Everybody's talking about it. I liked that you brought up and I find it very respectfully, he said, Hey, I'm not an Azure expert. You'd been there seven, seven dog years like you said. And I think that's what customers probably gained confidence in is hearing the folks like you that they look to for that guidance and that leadership saying, no, I don't know everything. To know that giving them the confidence that they're true, they're trusting you with that data and also helping trusting you to help them make the right decisions for their business. >>Yeah. And that that's, we've got to do that. I mean, I, as a tech guy, it's like I've, I've loved seeing the changes. When I joined Microsoft, I, I wasn't lying. I was almost there go inf I really want to join this company. I was going to go join a startup instead. And I got asked to one stage in an interview going, why do you want to join Microsoft? We see you've never applied to that. I never wanted to, a friend told me to come in and it's just been amazing to see those changes and I'm pretty proud on that. Um, so when we talk about, you know, those, the things we're doing, I mean I think there is no shame going, I'm just going to lift and shift machines because cloud is about flexibility. If you're doing it just on cost, probably doing it for the wrong reason, it's about that flexibility to go and do something. >>Then change within months of slowly make steps to make things better and better as you find a need as you find the ability, whatever it may be. And some of the big things that we focus on right now with customers is we've got a product called Azure advisor. It'll go until people want one. You know, you don't build things in a resilient manner. Hey, do you know this is not ha because of this and you can do this. It's like great. Also will tell you about security vulnerabilities that maybe she had a gateway here for security. Maybe you should do this or this is not patched. But the big thing is that it also goes and tells you, Hey, you're overspending. You don't need this much. It provisions, you provision like a Ferrari, you need a, you just need a Prius, go and run a Prius because it's going to do what you need and need to pay a lot less. >>And that's part of that trust. Getting that understanding. And it's counterintuitive that we're now like it's coming out of my team a lot too, which is great. But seeing these guys were dropping contracts and licenses and basically, you know, once every three years I may call the customer, Hey, how bout a renewal now go from that to now being focused on the customer's actual success and focused on their growth in Azure as a platform of our vast services growth like utilization not in sales has been a huge change. It scared some people away but it's brought a lot more people in and and that sort of counterintuitive spin less money thing actually leads in the longterm to people using more. >>Absolutely. That's definitely not the shrink wrap software company of Microsoft that I remember from the 90s yeah, very might be similar to you know, just as volt to 2019 is not the same combo, but many of us know from with 15 >>years and a good mutual friend of ours, sort of Simon and myself before I took this job, he and I sat down, we're having a beer and discussing the merits, all the not evacuate and things like that. Same with. They are changing such, such a great deal with, you know, what they're putting in the cloud, what they're doing with the data, where they're trying to achieve with things like Hedvig for data management across on premises and cloud with microservices applications and stuff going, Hey, this won't work like this anymore. When you now are doing an on premises and we containers, it's pretty good to see. I'm interested to see how they take that even further to their current audience, which is product predominantly, you know, the it pro, the data center admin, storage manager. >>It's funny when you talked about, um, just the choice that customers have and those saying I, we shouldn't be following the trends because they're the trends. We actually interviewed a couple of hours ago, one of Combolt's customers that is all on prime healthcare company and said, he's like, I want to make a secret that says no cloud and proud and it just, what that was, we don't normally hear from them. We always talk about cloud, but for a company to sit down and look at what's best for our business, whether it's, you know, FedRAMP certification challenges or HIPAA or GDPR or other compelling requirements to keep it on prem, it was just refreshing to hear this customer say, >>yeah, I mean it's, it's appropriate for the do what's right for you. I, yeah, it's no shame in any of them. It's, I mean, you don't, you definitely don't get fans by, by shaming people and not doing something right. And I mean, I, I'm personally very happy with the feet, you know, see sort of hype around things like blockchain died down a little bit. So it's a slow database unless you're using for the specific case of that shared ledger, you know, things like that where people don't have to know blockchain. Now I have to know IOT. It's like, yeah. And that hype gets people there, but it also causes a lot of anxiety and it's good to see someone actually not be ashamed of and like, and they grade the ones when they do take a step and use cloud citizen may be in the business already. They're probably going to do it appropriately because have a reason, not just because we think this would be cool. >>Well not and how much inherent and complexity does that bring in if somebody is really feeling pressured to follow those trends and maybe that's when you end up with this hodgepodge of technologies that don't work well together, you're spending way more in as as business it folks are consumers, you know, consumers in their personal lives, they expect things to be accessible, visible, but also cost efficient because they have so much choice. >>Yeah, the choice choice is hard. It's just a, just the conversation is having recently, for example, just we'll take the storage cause of where we are, right? It's like I'm running something on Azure. I'm a, I'm using Souza. I want an office Mount point, which is available to me in Fs. Great. Perfect. what do I use? It's like, well you use any one of these seven options, like what's the right choice? And that's the thing about being a platform company. We give you a lot of choices but it's still up to you or up to harness. It can really help the customers as well to make the most appropriate choice. And I pushed back really hard on terms like best practices and things. I hate it because again, it's making the assumption this is the best thing to do. It's not. It's always about, you know, what are the patterns that have worked for other people, what are the anti-patterns and the appropriate path for me to take. >>And that's actually how we're building our docs now too. So we keep, we keep focusing at our Azure technology and we're bringing out some of the biggest things we've done is how we manage our documentation. It's all open sourced. It's all in markdown on get hub. So you can go and read a document from someone like myself is doing product management going, this is how to use this product and you're actually this bits wrong. This bit needs to be like this, and you can go in yourself, even now, make a change and we can go, Oh yeah, and take that committed in and do all this kind of stuff in that way. So we're constantly taking those documents in that way, in getting real time feedback from customers who are using it, not just ourself and an echo chamber. >>So you get this great insight and visibility that you never had before. Well, Ben, thank you, Georgie stew and me on the Q this afternoon. Excited to hear what's coming up next for Azure. May appreciate your time. Thank you for streaming event. I, Lisa Martin, you're watching the cue from convo. Go 19.

hey welcome back to vmworld 2013 this is the cube our flagship program out the advanced extracted from the noise I'm John furry the founders SiliconANGLE my co-host Dave allante co-founder Wikibon or go to Wikibon org for free content go to slipping the angle for the reference point for tech innovation and go to SiliconANGLE com for all the footage also go to youtube.com slash SiliconANGLE for all the replays i'm showing with my co-host hi everybody i'm dafe a lot a leak as well as here is the vice president virtualization product group that fusion-io we welcome back to the cube thank you very much it's great to be here see you guys again this venue is terrific yeah you here in a new role actually I a new company new role is very exciting to us I'm going for you how many vm Rose have you been to oh yes it's all right yeah you Jen your veteran exactly so you have seen a lot of change and that you know since virtualization I mean flash is the next big exciting thing is 0 10 years I mean a lot to change first five years just give us your perspectives you worked at VMware right five years and second five years what's just what's a summary what's the bumper sticker you know when we started off the back in like two thousand we basically like to say well what are we going to virtualize first and it was the easy stuff right take all the applications that were running that weren't very i/o intensive it wasn't the Oracle databases we want to go put on virtualization now we've got what seventy eighty percent of workloads being virtualized what's left well all the hard stuff right and that's where flash is coming in is how do we go and take the hard applications and make those sing in a virtual environment so I've seen you're at heading up the virtualization team at fusion is that correct that's the roles that's the official title yes so what's the big news for you guys this week you know we've got some very exciting deliverables that we've shown we have a technology demonstration we're doing on a new product called I ovd i Iove I basically solves the problem of how you get performance into virtual desktops without breaking persistent storage and giving you a cost that's less than a physical desktop which is what everybody wanted from the start so you have to solve the cost problem solve the performance problem I ovd I is that that's the latest port now the latest implementation of our i/o turbine software so it's a very interesting way to go and say we'll take all the benefits of the i/o memory flash platform which you know I've been you know the basics of fusion-io success so you and I had you and I had a chance to chat on last week prior to the embargo of the new yet but one of the things we were talking about and then I was I went Dave about earlier they say was that everything at the top of the stack has always been this elusive dream right when Palmer its laid out the original vision you know 2010 it was really laid out we called the software mainframe what everyone want to call it it was a stack at the top of the stack e with apps being where I tried to her hand at that now pivotal's out outside and still there was a lot of work to do in the middle ground right so yes I would say it got stalled a little bit mainly because the hypervisor stuff a lot of the middle where big data hit the scene storage virtualization network virtualization all kind of started to happen yes so with that what's happening above the stack so stuff starting to commodify the infrastructure service platform deserves but then the apps data fabrics are there so what's your at the top of the thing you got to look up what's the view and what's the trends there well one of the aspects of virtualizing flash is that we're looking at basic hypervisor level virtualization first and this was the phase one of what I owe turbine had to develop which is how do we go and solve the i/o blender problem so any virtual virtual appliances or virtual machines have to go and look carefully at how we're going to go take what looks like now a random workload and how do we accelerate that that was phase one now we have with IO vdi a very interesting way to run in the guest and add more intelligence and so the intelligence now could be paying a desktop environment how do I take advantage of common files to speed up boot times how do I take advantage of the fact that there's a substantial amount of desktop rights that actually never matter remember your desktop even that drive goes on you're like what's it doing that's all data that doesn't ever have to go to this and we could take advantage of this now intelligently at the guest and do some very interesting work to speed up acceleration make sure desktops are working fast and that's the sort of intelligence you look at and it's all based on applications and solution knowledge one of the things that I've been working on it at fusion-io so I got to ask you leave I've been coming to vmworld now probably auto six or seven years and and my remember my first vmworld I said oh my gosh storage is good to get killed right and it was everybody's complaining about storage and and so so then we started down this path of integration you know via a I and Vasa and the Lycan right and every year Wikibon does this evaluation of the integration points and we rank oh you know who's got wat and I'm looking at the other day and I'm saying all this stuff is designed to sort of minimize the the spinning disk penalty mm-hmm and I've look at the integration points that relate to flash and it's like a handful of them mm-hmm so to the extent we get to that vision it seems to be is coming soon we're all my active data we talked about this with Gary earlier well my active data is served out of flash all those other integrations that I just spent all this time and money on kind of become irrelevant that was my take so the first time I've articulated that I wonder you know you're an expert in this area and products is that a fair characterization yet for years the disk drive has been doing a dual service it's been providing both performance which it's not very good at and capacity which is very good at right and so what's happening is it as you look at flash right now this is one of the reasons fusion-io is so successful early on is a single pci card serves the performance delivery of over 200 drives and so what's happening now is there's this radical split happening where wherever you can take the performance and disaggregate it from the capacity needs now that's changing extremely fast and so we're seeing that overall or I'm going to use a disc for a relatively cold store anywhere I can provide acceleration the software stack is how we do that yeah well if I could do that through an API call right right based on some kind of policy so so where are we in terms of being able to do that and what role does fusion-io play in that regard yeah very good question we've done some very interesting things with IO control for example this is an acquisition we had recently where we're now applying quality of service across as a policy across application environments so if you want to have a sand and basically run multiple applications how do I go make sure that I've got I've got performance now that I can allocate so that I can make sure that i'm getting the performance i need for the applications i care about allocating not just baseline performance but quality of service becomes a very important differentiator that fusion-io is driving okay and i can do that through an API call that's why I can open the API yes and you can go and actually allocate this on a policy-based by your application then I can change that pretty much on the fly on the fly yes it's one way of thinking that it's not just raw performance that users care about it turns out what users care about and you know this from your own experience waiting for that look that little life you know the hourglass to change what you care about is you care about persistent or seek consistent performance as much as you care about vegetable consistent performance right yeah the one thing that drives users nuts is if they don't know when something's gonna complete right and if it's too slow then they'll throw it out and get a new one but if it's consistent and predictable and I know what's coming one of the build processes around it here's one of the area's we've spending a lot of time on we are so early with flash we spend a lot of time on solutions so if you look at what are the key solutions at flash accelerates today well its databases server virtualization VDI big data if you take those as a group we have a set of customers that have deployed and seen successful the acceleration in the field and we're just going to show other customers here's how you can do this we've stripped out all the risk of making this work in the field so talk a little bit more about the the customers and how use cases are expanding kind of where they started and where you see them going and I know that's if there's a wide variety but I wonder if we can generalize especially as your product line has begun more more robust well we've taken a mapping right now of whether you're on a server side are you on the storage side with caching are you going to basically try and bridge the gap between these and the applications look like this so within databases databases love block storage and they love fast response times you can service more customers you can save costs you can consolidate infrastructure these are terrific benefits now for how flash can make a difference in server virtualization we've got the ability to go and run more VMs more consistently that's a huge driver of getting more virtual workloads going personal desktops got that same same concept of how do I make sure that users get that level of consistent response times and then lastly in big data big data is all about processing no data is deleted anymore the data that you have is just processed over and over and over again and that processing is all consistent with high-performance flash so big daddy talking about extending in-memory analytics potentially persisting in-memory analytics right every yeah we have some is Hannah crazy but Hannah Healy persistent data we've been doing a lot of work on Hannah lately his eats it's great I mean I love we love the concept but but you talk to Hannah users and they keep telling you what goes down a lot so well we need to persist it I know you guys are working on part on helping us ap out with that problem well there's some very interesting applications we announced Spotify as a customer for example streaming music is an ideal case of how do you have very fast performance over latency sensitive applications these types of things and how you go and manage things like playlists right become very important for businesses that want to take all of the effort they were doing on managing i/o take those developers off that work put them on developing new applications or new features that you're going to use to competing as your you know your competition that's how you've changed the game right now is I don't have to actually worry about managing io because we have thousands of I ops to work with hundreds of thousands of I ops the all of a sudden what was a scarce resource in the past now you've got a lot of it so think about riorca texting that's the that's the sort of you know cathartic change we're going through right now Lee how do you talk to guys first of all there's two there's two professions to this one first one is Silicon Valley is always a new stars coming on so like are there any seats left at the table in the i/o gain we'll get to that one to say but I watch this or the second one first which is if you're an IT guy you get all the storage laying around yes you know Nass and gas and all of its laying around usually tied to some app by going server-side talk about the dynamics that you guys get in there is it a rip and replace is an extension you guys commoditize it is it just you treat storage as a a resource that can be commoditized I mean how you view that what's the solution it's very interesting one thing we're finding is that there's so much extra capacity now because customers into buying discs to deliver performance that element right if having to buy so you know 15k SAS drive gives you a hundred and fifty I ops it costs seven dollars to get that level of performance flash is relatively inexpensive at a nickel so you can all of a sudden now you can free up all of this capacity so one of the things we're seeing first off is what drives buying decisions is how do I consolidate the infrastructure I have we're consolidating physical infrastructure we're consolidating licenses as well by having this level of performance so that's one dynamic customers are come in different shapes and sizes some customers want to buy server-side flash some customers want to buy storage side flash we're delivering both we have with our eye on products and IO control products if you want to buy storage we have some very interesting ways to deploy it that way if you want to buy servers we got the fastest in the industry on the server side so you know our metal our Metro right now is that you know however you want to consume it we're going to supply the economics is you can come in and maximize pre existing investments same time get that flash data center built out is that kind of like yeah let me describe one one way we're doing that with IO vdi which is new for virtual desktops we're coming in saying we're taking all the performance dependencies from the sand and basically moving them into the server side so by having it on the server side now you can say well I'll just tap into the sand for capacity which is really what you wanted in the first place huh I just wanted to add sand for data protection and so the sand administrators is great this is what I was hoping to do in the first place give you a few terabytes you're off and running I deploy this on server side deployments basically gets you back into that seamless increments of deployment well we saw a lot of action today in the news violin filed to go possible that so competition there was always new startups coming out so what are you back to the start of a question is always a new startup iOS hot so you have some innovation what are you seeing on the on the startup scene and are there any seats left at the table well who knew storage was going to be so sexy we did I guess you guys did right shopper come on Georgie day really yeah head Jojo Jojo G of storage a sexy I'll tell you what you know he got enough expected when he turns out he's gonna taught yeah it's funny mate if there's a lot of room for innovation left this is what you know we're we're seeing you know flash by itself is one way to go and deploy this there will be others right over time what what we're looking at is once you take any imperfect media and flash like disc is an imperfect media you have to start thinking about hey how do i how do i basically overcome some of the limitations there's reliability considerations i got to make it reliable right there's density how do i go and aggregate it together there's protection i mean all of these things and so all of that tends to lead towards software innovation right software innovation is where we're putting the bulk of our effort right now on making flash more more social so everybody wants a piece of you I mean you guys came out you had like a four-year lease on the industry and you did the side because oh wow maybe yeah the flash in the pan and so so it now all these big guys investing buying you back etc so you said software is where the innovation is is that how you keep your regiment if we could talk about that a little bit and help us understand you know what we can expect generally yeah that's that's a really good question there's no doubt and I've had experience in the past at one time my career I was selling some silicon to Intel for 69 margins and the question was so how did you get away with that rest of the day thank you me too and the answer was C 45 the value prop was not about this so yeah right listen item at what's not about the silicon itself who is how did you prove out things like compatibility software value add and in our case at fusion-io solutions what we've done and what we offer to customers is it's not so much about like raw acceleration because anybody can pull a number off a data sheet and say hey we're faster in this one case what we can show is we've made these customers this much more successful in the field and so our value right now is to show that we're going to accelerate your success with flash not just accelerate some portion of your data so what are those solutions we talked about him briefly before but so what talking about in generic terms database you know I abetik stuff it was interesting actually looking we have a luxury it from a marketing standpoint of saying they're actually fairly definable so within the database case Microsoft sequel server we've got Oracle both for rack for Oracle 11 12 X my sequel if you look there when you look into virtualization well clearly we've got VMware today and then moving to hyper-v right within VDI so it's both VMware for view and Citrix and then within big data we see some very interesting we're some work there not like to comment on that for a minute because because of our success on flash just showing the raw performance then we had application developer saying hey I'd like to rewrite the applications now and so we've had some very good success with companies like sky sequel Maria DB percona of rewriting the applications now to take advantage of the native the native benefits of flash yeah so that's two orders of magnitude performance it's a very interesting dynamic right so so okay so that's that's always been fundamental to your strategy and a big part of it has mediation and you guys are kind of unique in that area I think you got it well at some point there we're moving from the early adopters so early adopters right they like words like visionary disruptive groundbreaking this is going to be de like well to the later adopters right the CIO of a grain company in the Midwest like that sounds pretty scary so what we've done now is we've reduced the risk saying hey you get these / benefits and one of the things we have we have a theme st. same planet different world and that is designed around the aha moment that occurs when people realize are you kidding me forty percent of our customers see more than 10x performance in their applications 10x in the field from our surveys 10x performance can you imagine the moment where you go really seriously I could do that while the norm is to get that low latency you know feel like hey no disc at all but you know I think that's the key so I want to ask you two final questions we wrap up the place what's so you guys also you're doing great and we were talking earlier with Gary orenstein and some other folks the stuff under the under the hood is where all the actions in the data center so yeah so I'm gonna find data centers not just one thing it's that it's a bunch of parts yeah flashes is a big part of it yeah what is the big takeaway for folks out there shares I'll give you the last word share with them in your own words what's going on with flash this year at vmworld is 10th anniversary so flash the benefits of flash are so compelling it's going to be deployed everywhere where disk has been deployed when you think about it that way all of a sudden you look at the server side you look at the storage side and you look at how you bridge the gap in between we're going to see flash come on than everyone and what fusion-io has done is said we're going to be able to give you solutions however you want to consume it will give an offering there that you can go and say the advantages that we've developed and hardware and software take that and deploy it at low risk final question please add one more you've been at vmware veteran your industry vet been on the block you've seen at the movie a few times kids going to college our kids going to college so yeah but you've been all the vm worlds what what can you share the folks from the beginning of the first vmworld to now ten years what has happened how big has it become what's your giving the order of magnitude share some perspective or experiences sure you know in the early days the question was hey there was a customer question of virtualization is it safe right just to start off with like will my data like will my apps run and so you go through that first phase right of jumping in the pool like am I going to jump it is it okay right and then you jump in and you're like wow that was pretty good right one of my experiences early on was that the first benefit was about consolidation because that drove cost improvement and then the subsequent value was around high availability and management we're seeing the same thing in flash right now and you're seeing everyone get in the act the first element is hey is it safe is it going to work how can I consolidate infrastructure we're going through that we've gone through that phase now it's how do I manage this how do I make sure it works in the applications how do i get a che how do I support vmotion these are the questions customers are asking it's an integration question we think we're in a great position to capitalize on that the castle is fusion-io thanks for me on the cube we right back with wrap up after this short break day 1 i'm john forward day volante this is silicon angles the cube here live at vmworld in San Francisco we right back after this short break