(light music) >> Narrator: theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat music) >> Welcome back to Spain everyone. Lisa Martin here with theCUBE Dave Vellante, my co-host for the next four days. We're live in Barcelona, covering MWC23. This is only day one, but I'll tell you the theme of this conference this year is velocity. And I don't know about you Dave, but this day is flying by already. This is ecosystem day. We're going to have a great discussion on the ecosystem next. >> Well we're seeing the disaggregation of the hardened telco stack, and that necessitates an ecosystem open- we're going to talk about Open RAN, we've been talking about even leading up to the show. It's a critical technology enabler and it's compulsory to have an ecosystem to support that. >> Absolutely compulsory. We've got two guests here joining us, Gautam Bhagra, Vice President partnerships at Dell, and Scott Walker, Vice President of global Telco ecosystem at Wind River. Guys, welcome to the program. >> Nice to be here. >> Thanks For having us. >> Thanks for having us. >> So you've got some news, this is day one of the conference, there's some news, Gautam, and let's start with you, unpack it. >> Yeah, well there's a lot of news, as you know, on Dell World. One of the things we are very excited to announce today is the launch of the Open Telecom Ecosystems Community. I think Dave, as you mentioned, getting into an Open RAN world is a challenge. And we know some of the challenges that our customers face. To help solve for those challenges, Dell wants to work with like-minded partners and customers to build innovative solutions, and join go-to-market. So we are launching that today. Wind River is one of our flagship partners for that, and I'm excited to be here to talk about that as well. >> Can you guys talk a little bit about the partnership, maybe a little bit about Wind River so the audience gets that context? >> Sure, absolutely, and the theme of the show, Velocity, is what this partnership is all about. We create velocity for operators if they want to adopt Open RAN, right? We simplify it. Wind River as a company has been around for 40 years. We were part of Intel at one point, and now we're independent, owned by a company called Aptiv. And with that we get another round of investment to help continue our acceleration into this market. So, the Dell partnership is about, like I said, velocity, accelerating the adoption. When we talk to operators, they have told us there are many roadblocks that they face, right? Like systems integration, operating at scale. 'Cause when you buy a traditional radio access network solution from a single supplier, it's very easy. It's works, it's been tested. When you break these components apart and disaggregate 'em, as we talked about David, it creates integration points and support issues, right? And what Dell and Wind River have done together is created a cloud infrastructure solution that could host a variety of RAN workloads, and essentially create a two layer cake. What we're, overall, what we're trying to do is create a traditional RAN experience, with the innovation agility and flexibility of Open RAN. And that's really what this partnership does. >> So these work, this workload innovation is interesting to me because you've got now developers, you know, the, you know, what's the telco developer look like, you know, is to be defined, right? I mean it's like this white sheet of paper that can create all this innovation. And to do that, you've got to have, as I said earlier, an ecosystem. But you've got now, I'm interested in your Open RAN agenda and how you see that sort of maturity model taking place. 'Cause today, you got disruptors that are going to lean right in say "Hey, yeah, that's great." The traditional carriers, they have to have a, you know, they have to migrate, they have to have a hybrid world. We know that takes time. So what's that look like in the marketplace today? >> Yeah, so I mean, I can start, right? So from a Dell's perspective, what we see in the market is yes, there is a drive towards, everyone understands the benefits of being open, right? There's the agility piece, the innovation piece. That's a no-brainer. The question is how do we get there? And I think that's where partnerships become critical to get there, right? So we've been working with partners like Wind River to build solutions that make it easier for customers to start adopting some of the foundational elements of an open network. The, one of the purposes in the agenda of building this community is to bring like-minded developers, like you said like we want those guys to come and work with the customers to create new solutions, and come up with something creative, which no one's even thought about, that accelerates your option even quicker, right? So that's exactly what we want to do as well. And that's one of the reasons why we launched the community. >> Yeah, and what we find with a lot of carriers, they are used to buying, like I said, traditional RAN solutions which are provided from a single provider like Erickson or Nokia and others, right? And we break this apart, and you cloudify that network infrastructure, there's usually a skills gap we see at the operator level, right? And so from a developer standpoint, they struggle with having the expertise in order to execute on that. Wind River helps them, working with companies like Dell, simplify that bottom portion of the stack, the infrastructure stack. So, and we lifecycle manage it, we test- we're continually testing it, and integrating it, so that the operator doesn't have to do that. In addition to that, wind River also has a history and legacy of working with different RAN vendors, both disruptors like Mavenir and Parallel Wireless, as well as traditional RAN providers like Samsung, Erickson, and others soon to be announced. So what we're doing on the northbound side is making it easy by integrating that, and on the southbound side with Dell, so that again, instead of four or five solutions that you need to put together, it's simply two. >> And you think about today how we- how you consume telco services are like there's these fixed blocks of services that you can buy, that has to change. It's more like the, the app stores. It's got to be an open marketplace, and that's where the innovation's going to come in, you know, from the developers, you know, top down maybe. I don't know, how do you see that maturity model evolving? People want to know how long it's going to take. So many questions, when will Open RAN be as reliable. Does it even have to be? You know, so many interesting dynamics going on. >> Yeah, and I think that's something we at Dell are also trying to find out, right? So we have been doing a lot of good work here to help our customers move in that direction. The work with Dish is an example of that. But I think we do understand the challenges as well in terms of getting, adopting the technologies, and adopting the innovation that's being driven by Open. So one of the agendas that we have as a company this year is to work with the community to drive this a lot further, right? We want to have customers adopt the technology more broadly with the tier one, tier two telcos globally. And our sales organizations are going to be working together with Wind Rivers to figure out who's the right set of customers to have these conversations with, so we can drop, drive, start driving this agenda a lot quicker than what we've seen historically. >> And where are you having those customer conversations? Is that at the operator level, is it higher, is it both? >> Well, all operators are deploying 5G in preparation for 6G, right? And we're all looking for those killer use cases which will drive top line revenue and not just make it a TCO discussion. And that starts at a very basic level today by doing things like integrating with Juniper, for their cloud router. So instead of at the far edge cell site, having a separate device that's doing the routing function, right? We take that and we cloudify that application, run it on the same server that's hosting the RAN applications, so you eliminate a device and reduce TCO. Now with Aptiv, which is primarily known as an automotive company, we're having lots of conversations, including with Dell and Intel and others about vehicle to vehicle communication, vehicle to anything communication. And although that's a little bit futuristic, there are shorter term use cases that, like, vehicle to vehicle accident avoidance, which are going to be much nearer term than autonomous driving, for example, which will help drive traffic and new revenue streams for operators. >> So, oh, that's, wow. So many other things (Scott laughs) that's just opened up there too. But I want to come back to, sort of, the Open RAN adoption. And I think you're right, there's a lot of questions that that still have to be determined. But my question is this, based on your knowledge so far does it have to be as hardened and reliable, obviously has to be low latency as existing networks, or can flexibility, like the cloud when it first came out, wasn't better than enterprise IT, it was just more flexible and faster, and you could rent it. And, is there a similar dynamic here where it doesn't have to replicate the hardened stack, it can bring in new benefits that drive adoption, what are your thoughts on that? >> Well there's a couple of things on that, because Wind River, as you know, where our legacy and history is in embedded devices like F-15 fighter jets, right? Or the Mars Rover or the James Web telescope, all run Wind River software. So, we know about can't fail ultra reliable systems, and operators are not letting us off the hook whatsoever. It has to be as hardened and locked down, as secure as a traditional RAN environment. Otherwise they will (indistinct). >> That's table stakes. >> That's table stakes that gets us there. And when River, with our legacy and history, and having operator experience running live commercial networks with a disaggregated stack in the tens of thousands of nodes, understand what this is like because they're running live commercial traffic with live customers. So we can't fail, right? And with that, they want their cake and eat it too, right? Which is, I want ultra reliable, I want what I have today, but I want the agility and flexibility to onboard third party apps. Like for example, this JCNR, this Juniper Cloud-Native Router. You cannot do something as simple as that on a traditional RAN Appliance. In an open ecosystem you can take that workload and onboard it because it is an open ecosystem, and that's really one of the true benefits. >> So they want the mainframe, but they want (Scott laughs) the flexibility of the developer cloud, right? >> That's right. >> They want their, have their cake eat it too and not gain weight. (group laughs) >> Yeah I mean David, I come from the public cloud world. >> We all don't want to do that. >> I used to work with a public cloud company, and nine years ago, public cloud was in the same stage, where you would go to a bank, and they would be like, we don't trust the cloud. It's not secure, it's not safe. It was the digital natives that adopted it, and that that drove the industry forward, right? And that's where the enterprises that realized that they're losing business because of all these innovative new companies that came out. That's what I saw over the last nine years in the cloud space. I think in the telco space also, something similar might happen, right? So a lot of this, I mean a lot of the new age telcos are understanding the value, are looking to innovate are adopting the open technologies, but there's still some inertia and hesitancy, for the reasons as Scott mentioned, to go there so quickly. So we just have to work through and balance between both sides. >> Yeah, well with that said, if there's still some inertia, but there's a theme of velocity, how do you help organizations balance that so they trust evolving? >> Yeah, and I think this is where our solution, like infrastructure block, is a foundational pillar to make that happen, right? So if we can take away the concerns that the organizations have in terms of security, reliability from the fundamental elements that build their infrastructure, by working with partners like Wind River, but Dell takes the ownership end-to-end to make sure that service works and we have those telco grade SLAs, then the telcos can start focusing on what's next. The applications and the customer services on the top. >> Customer service customer experience. >> You know, that's an interesting point Gautam brings up, too, because support is an issue too. We all talk about when you break these things apart, it creates integration points that you need to manage, right? But there's also, so the support aspect of it. So imagine if you will, you had one vendor, you have an outage, you call that one vendor, one necktie to choke, right, for accountability for the network. Now you have four or five vendors that you have to work. You get a lot of finger pointing. So at least at the infrastructure layer, right? Dell takes first call support for both the hardware infrastructure and the Wind River cloud infrastructure for both. And we are training and spinning them up to support, but we're always behind them of course as well. >> Can you give us a favorite customer example of- that really articulates the value of the partnership and the technologies that it's delivering to customers? >> Well, Infra Block- >> (indistinct) >> Is quite new, and we do have our first customer which is LG U plus, which was announced yesterday. Out of Korea, small customer, but a very important one. Okay, and I think they saw the value of the integrated system. They don't have the (indistinct) expertise and they're leveraging Dell and Wind River in order to make that happen. But I always also say historically before this new offering was Vodafone, right? Vodafone is a leader in Europe in terms of Open RAN, been very- Yago and Paco have been very vocal about what they're doing in Open RAN, and Dell and Wind River have been there with them every step of the way. And that's what I would say, kind of, led up to where we are today. We learned from engagements like Vodafone and I think KDDI as well. And it got us where we are today and understanding what the operators need and what the impediments are. And this directly addresses that. >> Those are two very different examples. You were talking about TCO before. I mean, so the earlier example is, that's an example to me of a disruptor. They'll take some chances, you know, maybe not as focused on TCO, of course they're concerned about it. Vodafone I would think very concerned about TCO. But I'm inferring from your comments that you're trying to get the industry, you're trying to check the TCO box, get there. And then move on to higher levels of value monetization. The TCO is going to come down to how many humans it takes to run the network, is it not, is that- >> Well a lot of, okay- >> Or is it devices- >> So the big one now, particularly with Vodafone, is energy cost, right? >> Of course, greening the network. >> Two-thirds of the energy consumption in RAN is the the Radio Access Network. Okay, the OPEX, right? So any reductions, even if they're 5% or 10%, can save tens or hundreds of millions of dollars. So we do things creatively with Dell to understand if there's a lot of traffic at the cell site and if it's not, we will change the C state or P state of the server, which basically spins it down, so it's not consuming power. But that's just at the infrastructure layer. Where this gets really powerful is working with the RAN vendors like Samsung and Ericson and others, and taking data from the traffic information there, applying algorithms to that in AI to shut it down and spin it back up as needed. 'Cause the idea is you don't want that thing powered up if there's no traffic on it. >> Well there's a sustainability, ESG, benefit to that, right? >> Yes. >> And, and it's very compute intensive. >> A hundred percent. >> Which is great for Dell. But at the same time, if you're not able to manage that power consumption, the whole thing fails. I mean it's, because there's going to be so much data, and such a intense requirement. So this is a huge issue. Okay, so Scott, you're saying that in the TCO equation, a big chunk is energy consumption? >> On the OPEX piece. Now there's also the CapEx, right? And Open RAN solutions are now, what we've heard from our customers today, are they're roughly at parity. 'Cause you can do things like repurpose servers after the useful life for a lower demand application which helps the TCO, right? Then you have situations like Juniper, where you can take, now software that runs on the same device, eliminating at a whole other device at the cell site. So we're not just taking a server and software point of view, we're taking a whole cell site point of view as it relates to both CapEx and OPEX. >> And then once that infrastructure it really gets adopted, that's when the innovation occurs. The ecosystem comes in. Developers now start to think of new applications that we haven't thought of yet. >> Gautam: Exactly. >> And that's where, that's going to force the traditional carriers to respond. They're responding, but they're doing so very carefully right now, it's understandable why. >> Yeah, and I think you're already seeing some news in the, I mean Nokia's announcement yesterday with the rebranding, et cetera. That's all positive momentum in my opinion, right? >> What'd you think of the logo? >> I love the logo. >> I liked it too. (group laughs) >> It was beautiful. >> I thought it was good. You had the connectivity down below, You need pipes, right? >> Exactly. >> But you had this sort of cool letters, and then the the pink horizon or pinkish, it was like (Scott laughs) endless opportunity. It was good, I thought it was well thought out. >> Exactly. >> Well, you pick up on an interesting point there, and what we're seeing, like advanced carriers like Dish, who has one of the true Open RAN networks, publishing APIs for programmers to build in their 5G network as part of the application. But we're also seeing the network equipment providers also enable carriers do that, 'cause carriers historically have not been advanced in that way. So there is a real recognition that in order for these networks to monetize new use cases, they need to be programmable, and they need to publish standard APIs, so you can access the 5G network capabilities through software. >> Yeah, and the problem from the carriers, there's not enough APIs that the carriers have produced yet. So that's where the ecosystem comes in, is going to >> A hundred percent >> I think there's eight APIs that are published out of the traditional carriers, which is, I mean there's got to be 8,000 for a marketplace. So that's where the open ecosystem really has the advantage. >> That's right. >> That's right. >> That's right. >> Yeah. >> So it all makes sense on paper, now you just, you got a lot of work to do. >> We got to deliver. Yeah, we launched it today. We got to get some like-minded partners and customers to come together. You'll start seeing results coming out of this hopefully soon, and we'll talk more about it over time. >> Dave: Great Awesome, thanks for sharing with us. >> Excellent. Guys, thank you for sharing, stopping by, sharing what's going on with Dell and Wind River, and why the opportunity's in it for customers and the technological evolution. We appreciate it, you'll have to come back, give us an update. >> Our pleasure, thanks for having us. (Group talks over each other) >> All right, thanks guys >> Appreciate it. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE, Live from MWC23 in Barcelona. theCUBE is the leader in live tech coverage. (upbeat music)

(upbeat music) >> Welcome everyone to theCUBE's presentation of the AWS Startup Showcase. Topic is MarTech: Emerging Cloud-Scale Experience. This is season two, episode three of the ongoing series covering the exciting startups from the AWS ecosystem. Talk about their value proposition and their company and all the good stuff that's going on. I'm your host, John Furrier. And today we're excited to be joined by Manyam Mallela who's the co-founder and head of AI at Blueshift. Great to have you on here to talk about the Blueshift-Intelligent Customer Engagement, Made Simple. Thanks for joining us today. >> Thank you, John. Thank you for having me. >> So last time we did our intro video. We put it out in the web. Got great feedback. One of the things that we talked about, which is resonating out there in the viral Twitter sphere and in the thought leadership circles is this concept that you mentioned called 10X marketer. That idea that you have a solution that can provide 10X value. Kind of a riff on the 10X engineer in the DevOps cloud world. What does it mean? And how does someone get there? >> Yeah, fantastic. I think that's a great way to start our discussion. I think a lot of organizations, especially as of this current economic environment are looking to say, I have limited resources, limited budgets, how do I actually achieve digital and customer engagement that helps move the needle for my key metrics, whether it's average revenue per user, lifetime value of the user and frequent interactions. Above all, the more frequently a brand is able to interact with their customers, the better they understand them, the better they can actually engage them. And that usually leads to long term good outcomes for both customer and the brand and the organizations. So the way I see 10X marketer is that you need to have tools that give you that speed and agility without hindering your ability to activate any of the campaigns or experience that you want to create. And I see the roadblocks usually for many organizations, is that kind of threefold. One is your data silos. Usually data that is on your sites, does not talk to your app data, does not talk to your social data, does not talk to your CRM data and so forth. So how do I break those silos? The second is channel silos. I actually have customers who are only engaging on email or some are on email and mobile apps. Some are on email and mobile apps and maybe the OTT TV in a Roku or one of the connected TV experiences, or maybe in the future, another Web3 environments. How do I actually break those channel silos so that I get a comprehensive view of the customer and my marketing team can engage with all of them in respect to the channel? So break the channel silos. And the last part, what I call like some of the little talked about is I call the inside silo, which is that, not only do you need to have the data, but you also have to have a common language to share and talk about within your organizations. What are we learning from our customers? What do we translate our learning and insight on this common data platform or fabric into an action? And that requires the shared language of how do I actually know my customers and what do I do with them? Like either the inside silo as well. I think a lot of times organizations do get into this habit like each one speaks their own language, but they don't actually are talking the common language of what did we actually know about the real customer there. >> Yeah, and I think that's a great conversation because there's two, when you hear 10X marketer or 10X conversations, it implies a couple things. One is you're breaking an old way and bringing in something new. And the new is a force multiplier, in this case, 10X marketer. But this is the cloud scale so marketing executives, chiefs, staffs, chiefs of staffs of CMOs and their staffs. They want to get that scale. So marketing at scale is now the table stakes. Now budget constraints are there as well. So you're starting to see, okay, I need to do more with less. Now the big question comes up is ROI. So I want to have AI. I want to have all these force multipliers. What do I got to do with the old? How do I handle that? How do I bring the new in and operationalize it? And if that's the case, I'm making a change. So I have to ask you, what's your view on the ROI of AI marketing, because this is a key component 'cause you've got scale factor here. You've got to force multiplier opportunity. How do you get that ROI on the table? >> I think that as you rightly said, it's table stakes. And I think the ROI of AI marketing starts with one very key simple premise that today some of the tools allow you to do things one at a time. So I can actually say, "can I run this campaign today?" And you can scramble your team, hustle your way, get everybody involved and run that campaign. And then tomorrow I'd say like, Hey, I looked at the results. Can I do this again? And they're like, oh, we just asked for all of us to get that done. How do I do it tomorrow? How do I do it next week? How do I do it for every single week for the rest of the year? That's where I think the AI marketing is essentially taking your insight, taking your creativity, and creating a platform and a tool that allows you to run this every single day. And that's agility at scale. That is not only a scale of the customer base, but scale across time. And that AI-based automation is the key ROI piece for a lot of AI marketing practitioners. So Forrester, for example, did a comprehensive total economic impact study with our customers. And what they found out was actually the 781% ROI that they reported in that particular report is based on three key factors. One is being able to do experiences that are intelligent at scale, day in and day out. So do your targeting, do your recommendations. Not just one day, but do it every single day. And don't hold back yourself on being able to do that. >> I think they got to get the return. They got to get the sales too. This is the numbers. >> That's right. They actually have real dollars, real numbers attached to it. They have a calculator. You can actually go in and plug your own numbers and get what you might expect from your existing customer base. The second is that once you have a unified platform like ours, the 10X marketer that we're talking about is actually able to do more. It's sometimes actually, it's kind of counterintuitive to think that a smaller team does more. But in reality, what we have seen, that is the case. When you actually have the right tools, the smaller teams actually achieve more. And that's the redundant operations, conflicting insights that go away into something more coherent and comprehensive. And that's the second insight that they found. And the third is just having reporting and all of the things in one place means that you can amplify it. You can amplify it across your paid media channels. You can amplify it across your promotions programs and other partnerships that you're running. >> That's the key thing about platforms that people don't understand is that you have a platform and it enables a lot of value. In this case, force multiplier value. It enables more value than you pay for it. But the key is it enables customers to do things without a line of code, meaning it's a platform. They're innovating on top of it. And that's, I think, where the ROI comes in and this leads me where the next question is. I wanted to ask you is, not to throw a wet blanket on the MarTech industry, but I got to think of when I hear marketing automation, I kind of think old. I think old, inadequate antiquated technologies. I think email blasting and just some boring stuff that just gets siloed or it's bespoke from something else. Are marketing automation tools created equal? Does something like, what you guys are doing with SmartHub? Change that, and can you just talk about that 'cause it's not going to go away. It's just another level that's going to be abstracted away under the coverage. >> Yeah, great question. Certainly, email marketing has been practiced for two or three decades now and in some form or another. I think we went from essentially what people call list-based marketing. I have a list, let me keep blasting the same message to everybody and then hopefully something will come out of it. A little bit more of saying, then they can, okay, maybe now I have CRM database and can I do database marketing, which they will call like, "Hey, Hi John. Hi Manyam", which is the first name. And that's all they think will get the customer excited about because you'll call them by name, which is certainly helpful, but not enough. I think now what we call like, the new age that we live in is that we call it graph-based marketing. And the way we materialize that is that every single user is interacting with a brand with their offerings. So that this interaction graph that's happening across millions of customers, across thousands of content articles, videos, shows, products, items, and that graph actually has much richer knowledge of what the customer wants than the first names or list-based ones. So I think the next evolution of marketing automation, even though the industry has been there a while, there is a step change in what can actually be done at scale. And which is taking that interaction graph and making that a part of the experience for the customer, and that's what we enable. That's why we do think of that as a big step change from how people are being practicing list-based marketing. And within that, certainly there is a relation of curve as to how people approach AI marketing and they are in a different spectrum. Some people are still at list-based marketing. Some people are database marketing. And hopefully will move them to this new interaction graph-based marketing. >> Yeah and I think the context is key. I like how you bring up the graph angle on this because the graph databases imply there's a lot of different optionality around what's happened contextually both over time and currently and it adds to it. Makes it smarter. It's not just siloed, just one dimensional. It feels like it's got a lot there. This is clearly I'm a big fan of and I think this is the way to go. As you get more personalization, you get more data. Graphic database makes a lot of sense. So I have to ask you, this is a really cutting edge value proposition, who are the primary buyers and users in an organization that you guys are working with? >> Yeah, great question. So we typically have CMO organizations approaching us with this problem and they usually talk to their CIO organizations, their counterparts, and the chief information officers have been investing in data fabrics, data lakes, data warehouses for the better part of last decade or two, and have some very cutting edge technology that goes into organizing all this data. But that doesn't still solve the problem of how do I take this data and make a meaningful, relevant, authentic experience for the customer. That's the CMO problem. And CMO are now challenge with creating product level experience with every interaction and that's where we coming. So the CMO are the buyers of our SmartHub CDP platform. And we're looking for consolidating hundreds of tools that they had in the past and making that one or two channel marketers. Actually, the 10X marketer that we talk about. And you need the right tool on top of your data lakes and data warehouses to be able to do that. So CMO are also the real drivers of using this technology. >> I think that also place the ROI equation around ROI and having that unified platform. Great call out there. I got to ask you the question here 'cause this comes up a lot and when I hear you talking, I think, okay, all the great stuff you guys have there. But if I'm a company, I want to make my core competencies mine. I don't really want to outsource or buy something that's going to be core to my business. But at the same time as market shifts, the business changes. And sometimes people don't even know what business they're in at the end of the day. And as it gets more complicated too, by the way. So the question comes up with companies and I can see this clearly, do I buy it? Do I build it? When it comes to AI because that's a core competency. Wait a minute, AI. I'm going to maybe buy some chatbot technology. That's not really AI, but it feels like AI, but I'm a company, I want to buy it or build it. That's a choice. What do you see there? 'Cause you guys have a very comprehensive platform. It's hard to replicate, imitates, inimitable. So what's your customers doing with respect buy and build? And where do they get the core competency? What do they get to have as a core competency? >> Fantastic. I think certainly, AI as it applies to at the organization level, I've seen this at my previous organization that I was part of, and there will be product and financial applications that are using AI for the service of that organization. So we do see, depending upon the size of the organization having in-house AI and data science teams. They are focused on these long term problems that they are doing as part of their product itself. Adjacent to that, the CMO organization gets some resources, but not certainly a lot. I think the CMO organization is usually challenged with the task, but not given the hundred people data science and engineering team to be able to go solve that. So what we see among our customer base is that they need agile platform to do most of the things that they need to do on a day to day basis, but augmented with what our in-house data science they have. So we are an extensible platform. What we have seen is that half of our customers use us solely for the AI needs. The other half certainly uses both AI modules that we provide and are actually augmented with things that they've already built. And we do not have a fight in that ring. But we do acknowledge and we do provide the right hooks for getting the data out of our system and bringing their AI back into our system. And we think that at the end of the day, if you want agility for the CMO, there should not be any barriers. >> It's like they're in the data business and that's the focus. So I think with what I hear you saying is that with your technology and platform, you're enabling to get them to be in the data business as fast as possible. >> That's right. >> Versus algorithm business, which they could add to over time. >> Certainly they could add to. But I think the bulk of competencies for the CMO are on the creative side. And certainly wrangling with data pipelines day in and day out and wondering what actually happened to a pipeline in the middle of the night is not probably what they would want to focus on. >> Not their core confidence. Yeah, I got that. >> That's right. >> You can do all the heavy lifting. I love that. I got to ask you on the Blueshift side on customer experience consumption. how can someone experience the product before buying? Is there a trial or POC? What's the scale and scope of operationalizing and getting the Blueshift value proposition in them? >> Yeah, great. So we actually recently released a fantastic way to experience our product. So if you go to our website, there's only one call-to-action saying, explore Blueshift. And if you click on that, without asking, anything other than your business email address, you're shown the full product. You're given a guided tour of all the possibilities. So you can actually experience what your marketing team would be doing in the product. And they call it Project Rover. We launched it very recently and we are seeing fantastic reception to that. I think a lot of times, as you said, there is that question mark of like, I have a marketing team that is already doing X, Y, Z. Now you are asking me to implement Blueshift. How would they actually experience the product? And now they can go in and experience the product. It's a great way to get the gist of the product in 10 clicks. Much more than going through any number of videos or articles. I think people really want to say, let me do those 10 clicks. And I know what impression that I can get from platform. So we do think that's a great way to experience the product and it's easily available from the main website. >> It's in the value proposition. It isn't always a straight line. And you got that technology. And I got to ask from between your experience with the customers that you're talking to, prospects, and customers, where do you see yourself winning deals on Customer Engagement, Made Simple because the word customer engagement's been around for a while, and it's become, I won't say cliche, but there's been different generational evolutions of technology that made that possible. Obviously, we're living in an era of high velocity Omni-Channel, a lot of data, the graph databases you mentioned are in there, big part of it. Where are you winning deals? Where are customers pain points where you are solving that specifically? >> Yeah, great question. So the organizations that come to us usually have one of the dimensions of either they have offering complexity, which is what catalog of content or videos or items do they offer to the customers. And on the data complexity on the other side is to what the scale of customer base that I usually target. And that problem has not gone away. I think the customer engagement, even though has been around for a while, the problem of engaging those customers at scale hasn't gone away and it only is getting harder and harder and organizations that have, especially on what we call the business-to-consumer side where the bulk of what marketing organizations in a B2C segments are doing. I have tens to millions of customers and how do I engage them day in and day out. And I think that all that problem is only getting harder because consumer preferences keeps shifting all the time. >> And where's your sweet spot for your customer? What size? Can you just share the target organization? Is it medium enterprise, large B2C, B2B2C? What's the focus area? >> Yeah, great question. So we have seen like startups that are in Silicon Valley. I have now half a million monthly active users, how do I actually engage them to customers and clients like LendingTree and PayPal and Discovery and BBC who have been in the business for multiple decades, have tens of millions of customers that they're engaging with. So that's kind of our sweet spot. We are certainly not maybe for small shop with maybe a hundred plus customers. But as you reach the scale of tens of thousands of customers, you start seeing this problem. And then you start to look out for solutions that are beyond, especially list-based marketing and email blast. >> So as the scale, you can dial up and down, but you have to have some enough scale to get the data pattern. >> That's right. >> If I can connect the dots there. >> I would probably say, looking at a hundred thousand or more monthly active customer base, and then you're trying to ramp up your own growth based on what you're learning and to engage those customers. >> It's like a bulldozer. You need the heavy equipment. Great conversation. For the last minute we have here Manyam, give you a plug for the company. What's going on? What are you guys doing? What's new? Give some success stories, your latest achievements. Take a minute to give a plug for the company. >> Yeah, great. We have been recognized by Deloitte as the fastest growth startup two years in a row and continuing to be on that streak. We have released currently integrations with AWS partners and Snowflake partners and data lake partners that allow implementing Blueshift a much streamlined experience with bidirectional integrations. We have now hundred plus data connectors and data integrations in our system and that takes care of many of our needs. And now, I think organizations that have been budget constraint and are trying to achieve a lot with a small team are actually going to look at these solutions and say, "Can I get there?" and "Can I become that 10X marketing organization? And as you have said, agility at scale is very, very hard to achieve. Being able to take your marketing team and achieve 10X requires the right platform and the right solution. We are ready for it. >> And every company's in the data business that's the asset. You guys make that sing for them. It's good stuff. Love the 10X. Love the scale. Manyam Mallela, thanks for coming on. Co-founder, Head of AI at Blueshift. This is the AWS Startup Showcase season two, episode three of the ongoing series covering the exciting startups from the AWS ecosystem. I'm John Furrier, your host. Thanks for watching. >> Thank you, John. (upbeat music)

(upbeat music) >> Okay, welcome back everyone. CUBE's coverage of re:MARS, here in Las Vegas, in person. I'm John Furrier, host of theCUBE. This is the analyst panel wrap up analysis of the keynote, the show, past one and a half days. We got two great guests here. We got Andy Thurai, Vice President, Principal Consultant, Constellation Research. Larry Carvalho, Principal Consultant at RobustCloud LLC. Congratulations going out on your own. >> Thank you. >> Andy, great to see you. >> Great to see you as well. >> Guys, thanks for coming out. So this is the session where we break down and analyze, you guys are analysts, industry analysts, you go to all the shows, we see each other. You guys are analyzing the landscape. What does this show mean to you guys? 'Cause this is not obvious to the normal tech follower. The insiders see the confluence of robotics, space, automation and machine learning. Obviously, it's IoTs, industrials, it's a bunch of things. But there's some dots to connect. Let's start with you, Larry. What do you see here happening at this show? >> So you got to see how Amazon started, right? When AWS started. When AWS started, it primarily took the compute storage, networking of Amazon.com and put it as a cloud service, as a service, and started selling the heck out of it. This is a stage later now that Amazon.com has done a lot of physical activity, and using AIML and the robotics, et cetera, it's now the second phase of innovation, which is beyond digital transformation of back office processes, to the transformation of physical processes where people are now actually delivering remotely and it's an amazing area. >> So back office's IT data center kind of vibe. >> Yeah. >> You're saying front end, industrial life. >> Yes. >> Life as we know it. >> Right, right. I mean, I just stopped at a booth here and they have something that helps anybody who's stuck in the house who cannot move around. But with Alexa, order some water to bring them wherever they are in the house where they're stuck in their bed. But look at the innovation that's going on there right at the edge. So I think those are... >> John: And you got the Lunar, got the sex appeal of the space, Lunar Outpost interview, >> Yes. >> those guys. They got Rover on Mars. They're going to have be colonizing the moon. >> Yes. >> I made a joke, I'm like, "Well, I left a part back on earth, I'll be right back." (Larry and Andy laugh) >> You can't drive back to the office. So a lot of challenges. Andy, what's your take of the show? Take us your analysis. What's the vibe, what's your analysis so far? >> It's a great show. So, as Larry was saying, one of the thing was that when Amazon started, right? So they were more about cloud computing. So, which means is they try to commoditize more of data center components or compute components. So that was working really well for what I call it as a compute economy, right? >> John: Mm hmm. >> And I call the newer economy as more of a AIML-based data economy. So when you move from a compute economy into a data economy, there are things that come into the forefront that never existed before, never popular before. Things like your AIML model creation, model training, model movement, model influencing, all of the above, right? And then of course the robotics has come long way since then. And then some of what they do at the store, or the charging, the whole nine yards. So, the whole concept of all of these components, when you put them on re:Invent, such a big show, it was getting lost. So that's why they don't have it for a couple of years. They had it one year. And now all of a sudden they woke up and say, "You know what? We got to do this!" >> John: Yeah. >> To bring out this critical components that we have, that's ripe, mature for the world to next component. So that's why- I think they're pretty good stuff. And some of the robotics things I saw in there, like one of them I posted on my Twitter, it's about the robot dog, sniffing out the robot rover, which I thought was pretty hilarious. (All laugh) >> Yeah, this is the thing. You're seeing like the pandemic put everything on hold on the last re:Mars, and then the whole world was upside down. But a lot of stuff pulled forward. You saw the call center stuff booming. You saw the Zoomification of our workplace. And I think a lot of people got to the realization that this hybrid, steady-state's here. And so, okay. That settles that. But the digital transformation of actually physical work? >> Andy: Yeah. >> Location, the walk in and out store right over here we've seen that's the ghost store in Seattle. We've all been there. In fact, I was kind of challenged, try to steal something. I'm like, okay- (Larry laughs) I'm pulling all my best New Jersey moves on everyone. You know? >> Andy: You'll get charged for it. >> I couldn't get away with it. Two double packs, drop it, it's smart as hell. Can't beat the system. But, you bring that to where the AI machine learning, and the robotics meet, robots. I mean, we had robots here on theCUBE. So, I think this robotics piece is a huge IoT, 'cause we've been covering industrial IoT for how many years, guys? And you could know what's going on there. Huge cyber threats. >> Mm hmm. >> Huge challenges, old antiquated OT technology. So I see a confluence in the collision between that OT getting decimated, to your point. And so, do you guys see that? I mean, am I just kind of seeing mirage? >> I don't see it'll get decimated, it'll get replaced with a newer- >> John: Dave would call me out on that. (Larry laughs) >> Decimated- >> Microsoft's going to get killed. >> I think it's going to have to be reworked. And just right now, you want do anything in a shop floor, you have to have a physical wire connected to it. Now you think about 5G coming in, and without a wire, you get minute details, you get low latency, high bandwidth. And the possibilities are endless at the edge. And I think with AWS, they got Outposts, they got Snowcone. >> John: There's a threat to them at the edge. Outpost is not doing well. You talk to anyone out there, it's like, you can't find success stories. >> Larry: Yeah. >> I'm going to get hammered by Amazon people, "Oh, what're you're saying that?" You know, EKS for example, with serverless is kicking ass too. So, I mean I'm not saying Outpost was wrong answer, it was a right at the time, what, four years ago that came out? >> Yeah. >> Okay, so, but that doesn't mean it's just theirs. You got Dell Technologies want some edge action. >> Yeah. >> So does HPE. >> Yes. >> So you got a competitive edge situation. >> I agree with that and I think that's definitely not Amazon's strong point, but like everything, they try to make it easy to use. >> John: Yeah. >> You know, you look at the AIML and they got Canvas. So Canvas says, hey, anybody can do AIML. If they can do that for the physical robotic processes, or even like with Outpost and Snowcone, that'll be good. I don't think they're there yet, and they don't have the presence in the market, >> John: Yeah. >> like HPE and, >> John: Well, let me ask you guys this question, because I think this brings up the next point. Will the best technology win or will the best solution win? Because if cloud's a platform and all software's open source, which you can make those assumptions, you then say, hey, they got this killer robotics thing going on with Artemis and Moonshot, they're trying to colonize the moon, but oh, they discovered a killer way to solve a big problem. Does something fall out of this kind of re:Mars environment, that cracks the code and radically changes and disrupts the IoT game? That's my open question. I don't know the answer. I'd love to get your take on what might be possible, what wild card's out there around, disrupting the edge. >> So one thing I see the way, so when IoT came into the world of play, it's when you're digitizing the physical world, it's IoT that does digitalization part of that actually, right? >> But then it has its own set of problems. >> John: Yeah. >> You're talking about you installing sensor everywhere, right? And not only installing your own sensor, but also you're installing competitor sensors. So in a given square feet how many sensors can you accommodate? So there are physical limitations on liabilities of bandwidth and networking all of that. >> John: And integration. >> As well. >> John: Your point. >> Right? So when that became an issue, this is where I was talking to the robotic guys here, a couple of companies, and one of the use cases they were talking about, which I thought was pretty cool, is, rather than going the sensor route, you go the robot route. So if you have either a factor that you want to map out, you put as many sensors on your robot, whatever that is, and then you make it go around, map the whole thing, and then you also do a surveillance in the whole nine yards. So, you can either have a fixed sensors or you can have moving sensors. So you can have three or four robots. So initially, when I was asking them about the price of it, when they were saying about a hundred thousand dollars, I was like, "Who would buy that?" (John and Larry laugh) >> When they then explained that, this is the use case, oh, that makes sense, because if you had to install, entire factory floor sensors, you're talking about millions of dollars. >> John: Yeah. >> But if you do the moveable sensors in this way, it's a lot cheaper. >> John: Yeah, yeah. >> So it's based on your use case, what are your use cases? What are you trying to achieve? >> The general purpose is over. >> Yeah. >> Which you're getting at, and that the enablement, this is again, this is the cloud scale open question- >> Yep. >> it's, okay, the differentiations isn't going to be open source software. That's open. >> It's going to be in the, how you configure it. >> Yes. >> What workflows you might have, the data streams. >> I think, John, you're bringing up a very good point about general purpose versus special purpose. Yesterday Zoox was on the stage and when they talked about their vehicle, it's made just for self-driving. You walk around in Vegas, over here, you see a bunch of old fashioned cars, whether they're Ford or GM- >> and they put all these devices around it, but you're still driving the same car. >> John: Yeah, exactly. >> You can retrofit those, but I don't think that kind of IoT is going to work. But if you redo the whole thing, we are going to see a significant change in how IoT delivers value all the way from the industrial to home, to healthcare, mining, agriculture, it's going to have to redo. I'll go back to the OT question. There are some OT guys, I know Rockwell and Siemens, some of them are innovating faster. The ones who innovate faster to keep up with the IT side, as well as the MLAI model are going to be the winners on that one. >> John: Yeah, I agree. Andy, your thoughts on manufacturing, you brought up the sensor thing. Robotics ultimately is, end of the day, an opportunity there. Obviously machine learning, we know what that does. As we move into these more autonomous builds, what does that look like? And is Amazon positioned well there? Obviously they have big manufacturers. Some are saying that they might want to get out of that business too, that Jassy's evaluating that some are saying. So, where does this all lead for that robotics manufacturing lifestyle, walk in, grab my food? 'Cause it's all robotics and AI at the end of the day, I got sensors, I got cameras, I got non-humans moving heavy lifting stuff, fixing the moon will be done by robots, not humans. So it's all coming. What's your analysis? >> Well, so, the point about robotics is on how far it has come, it is unbelievable, right? Couple of examples. One was that I was just talking to somebody, was explaining to them, to see that robot dog over there at the Boston Dynamics one- >> John: Yeah. >> climbing up and down the stairs. >> Larry: Yeah. >> That's more like the dinosaur movie opening the doors scene. (John and Larry laugh) It's like that for me, because the coordinated things, it is able to go walk up and down, that's unbelievable. But okay, it does that, and then there was also another video which is going on viral on the internet. This guy kicks the dog, robot dog, and then it falls down and it gets back up, and the sentiment that people were feeling for the dog, (Larry laughs) >> you can't, it's a robot, but people, it just comes at that level- >> John: Empathy, for a non-human. >> Yeah. >> But you see him, hey you, get off my lawn, you know? It's like, where are we? >> It has come to that level that people are able to kind of not look at that as a robot, but as more like a functioning, almost like a pet-level, human-level being. >> John: Yeah. >> And you saw that the human-like walking robot there as well. But to an extent, in my view, they are all still in an experimentation, innovation phase. It doesn't made it in the industrial terms yet. >> John: Yeah, not yet, it's coming. >> But, the problem- >> John: It's coming fast. That's what I'm trying to figure out is where you guys see Amazon and the industry relative to what from the fantasy coming reality- >> Right. >> of space in Mars, which is, it's intoxicating, let's face it. People love this. The nerds are all here. The geeks are all here. It's a celebration. James Hamilton's here- >> Yep. >> trying to get him on theCUBE. And he's here as a civilian. Jeff Barr, same thing. I'm here, not for Amazon, I bought a ticket. No, you didn't buy a ticket. (Larry laughs) >> I'm going to check on that. But, he's geeking out. >> Yeah. >> They're there because they want to be here. >> Yeah. >> Not because they have to work here. >> Well, I mean, the thing is, the innovation velocity has increased, because, in the past, remember, the smaller companies couldn't innovate because they don't have the platform. Now Compute is a platform available at the scale you want, AI is available at the scale. Every one of them is available at the scale you want. So if you have an idea, it's easy to innovate. The innovation velocity is high. But where I see most of the companies failing, whether startup or big company, is that you don't find the appropriate use case to solve, and then don't sell it to the right people to buy that. So if you don't find the right use case or don't sell the right value proposition to the actual buyer, >> John: Mm hmm. >> then why are you here? What are you doing? (John laughs) I mean, you're not just an invention, >> John: Eh, yeah. >> like a telephone kind of thing. >> Now, let's get into next talk track. I want to get your thoughts on the experience here at re:Mars. Obviously AWS and the Amazon people kind of combined effort between their teams. The event team does a great job. I thought the event, personally, was first class. The coffee didn't come in late today, I was complaining about that, (Larry laughs) >> people complaining out there, at CUBE reviews. But world class, high bar on the quality of the event. But you guys were involved in the analyst program. You've been through the walkthrough, some of the briefings. I couldn't do that 'cause I'm doing theCUBE interviews. What would you guys learn? What were some of the key walkaways, impressions? Amazon's putting all new teams together, seems on the analyst relations. >> Larry: Yeah. >> They got their mojo booming. They got three shows now, re:Mars, re:inforce, re:invent. >> Andy: Yeah. >> Which will be at theCUBE at all three. Now we got that coverage going, what's it like? What was the experience like? Did you feel it was good? Where do they need to improve? How would you grade the Amazon team? >> I think they did a great job over here in just bringing all the physical elements of the show. Even on the stage, where they had robots in there. It made it real and it's not just fake stuff. And every, or most of the booths out there are actually having- >> John: High quality demos. >> high quality demos. (John laughs) >> John: Not vaporware. >> Yeah, exactly. Not vaporware. >> John: I won't say the name of the company. (all laugh) >> And even the sessions were very good. They went through details. One thing that stood out, which is good, and I cover Low Code/No Code, and Low Code/No Code goes across everything. You know, you got DevOps No Low-Code Low-Code. You got AI Low Code/No Code. You got application development Low Code/No Code. What they have done with AI with Low Code/No Code is very powerful with Canvas. And I think that has really grown the adoption of AI. Because you don't have to go and train people what to do. And then, people are just saying, Hey, let me kick the tires, let me use it. Let me try it. >> John: It's going to be very interesting to see how Amazon, on that point, handles this, AWS handles this data tsunami. It's cause of Snowflake. Snowflake especially running the table >> Larry: Yeah. >> on the old Hadoop world. I think Dave had a great analysis with other colleagues last week at Snowflake Summit. But still, just scratching the surface. >> Larry: Yeah. >> The question is, how shared that ecosystem, how will that morph? 'Cause right now you've got Data Bricks, you've got Snowflake and a handful of others. Teradata's got some new chops going on there and a bunch of other folks. Some are going to win and lose in this downturn, but still, the scale that's needed is massive. >> So you got data growing so much, you were talking earlier about the growth of data and they were talking about the growth. That is a big pie and the pie can be shared by a lot of folks. I don't think- >> John: And snowflake pays AWS, remember that? >> Right, I get it. (John laughs) >> I get it. But they got very unique capabilities, just like Netflix has very unique capabilities. >> John: Yeah. >> They also pay AWS. >> John: Yeah. >> Right? But they're competing on prime. So I really think the cooperation is going to be there. >> John: Yeah. >> The pie is so big >> John: Yeah. >> that there's not going to be losers, but everybody could be winners. >> John: I'd be interested to follow up with you guys after next time we have an event together, we'll get you back on and figure out how do you measure this transitions? You went to IDC, so they had all kinds of ways to measure shipments. >> Larry: Yep. >> Even Gartner had fumbled for years, the Magic Quadrant on IaaS and PaaS when they had the market share. (Larry laughs) And then they finally bundled PaaS and IaaS together after years of my suggesting, thank you very much Gartner. (Larry laughs) But that just performs as the landscape changes so does the scoreboard. >> Yep. >> Right so, how do you measure who's winning and who's losing? How can we be critical of Amazon so they can get better? I mean, Andy Jassy always said to me, and Adam Salassi same way, we want to hear how bad we're doing so we can get better. >> Yeah. >> So they're open-minded to feedback. I mean, not (beep) posting on them, but they're open to critical feedback. What do you guys, what feedback would you give Amazon? Are they winning? I see them number one clearly over Azure, by miles. And even though Azure's kicking ass and taking names, getting back in the game, Microsoft's still behind, by a long ways, in some areas. >> Andy: Yes. In some ways. >> So, the scoreboard's changing. What's your thoughts on that? >> So, look, I mean, at the end of the day, when it comes to compute, right, Amazon is a clear winner. I mean, there are others who are catching up to it, but still, they are the established leader. And it comes with its own advantages because when you're trying to do innovation, when you're trying to do anything else, whether it's a data collection, we were talking about the data sensors, the amount of data they are collecting, whether it's the store, that self-serving store or other innovation projects, what they have going on. The storage compute and process of that requires a ton of compute. And they have that advantage with them. And, as I mentioned in my last article, one of my articles, when it comes to AIML and data programs, there is a rich and there is a poor. And the rich always gets richer because they, they have one leg up already. >> John: Yeah. >> I mean the amount of model training they have done, the billion or trillion dollar trillion parametrization, fine tuning of the model training and everything. They could do it faster. >> John: Yeah. >> Which means they have a leg up to begin with. So unless you are given an opportunity as a smaller, mid-size company to compete at them at the same level, you're going to start at the negative level to begin with. You have a lot of catch up to do. So, the other thing about Amazon is that they, when it comes to a lot of areas, they admit that they have to improve in certain areas and they're open and willing and listen to the people. >> Where are you, let's get critical. Let's do some critical analysis. Where does Amazon Websters need to get better? In your opinion, what criticism would you, in a constructive way, share? >> I think on the open source side, they need to be more proactive in, they are already, but they got to get even better than what they are. They got to engage with the community. They got to be able to talk on the open source side, hey, what are we doing? Maybe on the hardware side, can they do some open-sourcing of that? They got graviton. They got a lot of stuff. Will they be able to share the wealth with other folks, other than just being on an Amazon site, on the edge with their partners. >> John: Got it. >> If they can now take that, like you said, compute with what they have with a very end-to-end solution, the full stack. And if they can extend it, that's going to be really beneficial for them. >> Awesome. Andy, final word here. >> So one area where I think they could improve, which would be a game changer would be, right now, if you look at all of their solutions, if you look at the way they suggest implementation, the innovations, everything that comes out, comes out across very techy-oriented. The persona is very techy-oriented. Very rarely their solutions are built to the business audience or to the decision makers. So if I'm, say, an analyst, if I want to build, a business analyst rather, if I want to build a model, and then I want to deploy that or do some sort of application, mobile application, or what have you, it's a little bit hard. It's more techy-oriented. >> John: Yeah, yeah. >> So, if they could appeal or build a higher level abstraction of how to build and deploy applications for business users, or even build something industry specific, that's where a lot of the legacy companies succeeded. >> John: Yeah. >> Go after manufacturing specific or education. >> Well, we coined the term 'Supercloud' last re:Invent, and that's what we see. And Jerry Chen at Greylock calls it Castles in the Cloud, you can create these moats >> Yep. >> on top of the CapEx >> Yep. >> of Amazon. >> Exactly. >> And ride their back. >> Yep. >> And the difference in what you're paying and what you're charging, if you're good, like a Snowflake or a Mongo. I mean, Mongo's, they're just as big as Snow, if not bigger on Amazon than Snowflake is. 'Cause they use a lot of compute. No one turns off their database. (John laughs) >> Snowflake a little bit different, a little nuanced point, but, this is the new thing. You see Goldman Sachs, you got Capital One. They're building their own kind of, I call them sub clouds, but Dave Vellante says it's a Supercloud. And that essentially is the model. And then once you have a Supercloud, you say, great, I'm going to make sure it works on Azure and Google. >> Andy: Yep. >> And Alibaba if I have to. So, we're kind of seeing a playbook. >> Andy: Mm hmm. >> But you can't get it wrong 'cause it scales. >> Larry: Yeah, yeah. >> You can't scale the wrong answer. >> Andy: Yeah. >> So that seems to be what I'm watching is, who gets it right? Product market fit. Then if they roll it out to the cloud, then it becomes a Supercloud, and that's pure product market fit. So I think that's something that I've seen some people trying to figure out. And then, are you a supplier to the Superclouds? Like a Dell? Or you become an enabler? >> Andy: Yeah. >> You know, what's Dell Technologies do? >> Larry: Yeah. >> I mean, how do the box movers compete? >> Larry: I, the whole thing is now hybrid and you're going to have to see just, you said. (Larry laughs) >> John: Hybrid's a steady-state. I don't need to. >> Andy: I mean, >> By the way we're (indistinct), we can't get the chips, cause Broadcom and Apple bought 'em all. (Larry laughs) I mean there's a huge chip problem going on. >> Yes. I agree. >> Right now. >> I agree. >> I mean all these problems when you attract to a much higher level, a lot of those problems go away because you don't care about what they're using underlying as long as you deliver my solution. >> Larry: Yes. >> Yeah, it could be significantly, a little bit faster than what it used to be. But at the end of the day, are you solving my specific use case? >> John: Yeah. >> Then I'm willing to wait a little bit longer. >> John: Yeah. Time's on our side and now they're getting the right answers. Larry, Andy, thanks for coming on. This great analyst session turned into more of a podcast vibe, but you know what? (Larry laughs) To chill here at re:Mars, thanks for coming on, and we unpacked a lot. Thanks for sharing. >> Both: Thank you. >> Appreciate it. We'll get you back on. We'll get you in the rotation. We'll take it virtual. Do a panel. Do a panel, do some panels around this. >> Larry: Absolutely. >> Andy: Oh this not virtual, this physical. >> No we're live right now! (all laugh) We get back to Palo Alto. You guys are influencers. Thanks for coming on. You guys are moving the market, congratulations. Take a minute, quick minute each to plug any work you're doing for the people watching. Larry, what are you working on? Andy? You go after Larry, what you're working on. >> Yeah. So since I started my company, RobustCloud, since I left IDC about a year ago, I'm focused on edge computing, cloud-native technologies, and Low Code/No Code. And basically I help companies put their business value together. >> All right, Andy, what are you working on? >> I do a lot of work on the AIML areas. Particularly, last few of my reports are in the AI Ops incident management and ML Ops areas of how to generally improve your operations. >> John: Got it, yeah. >> In other words, how do you use the AIML to improve your IT operations? How do you use IT Ops to improve your AIML efficiency? So those are the- >> John: The real hardcore business transformation. >> Yep. >> All right. Guys, thanks so much for coming on the analyst session. We do keynote review, breaking down re:Mars after day two. We got a full day tomorrow. I'm John Furrier with theCUBE. See you next time. (pleasant music)

>>Okay, welcome back everyone. This is the Cube's coverage here in Las Vegas. Back at events re Mars, Amazon re Mars. I'm your host, John fur with the cube. Mars stands for machine learning, automation, robotics, and space. It's great event brings together a lot of the industrial space machine learning and all the new changes in scaling up from going on the moon to, you know, doing great machine learning. And we've got two great guests here with kinda called lunar outpost, Justin Sears, CEO, Lauren, man. He's the co-founder and chief strategy officer lunar outpost. They're right next to us, watching their booth. Love the name, gentlemen. Welcome to the cube. >>Yeah. Thanks for having us, John. >>All right. So lunar outpost, I get the clues here. Tell us what you guys do. Start with that. >>Absolutely. So lunar outpost, we're a company based outta Colorado that has two missions headed to the moon over the course of the next 24 months. We're currently operating on Mars, which forest will tell you a little bit more about here in a second. And we're really pushing out towards expanding the infrastructure on the lunar surface. And then we're gonna utilize that to provide sustainable access to other planetary bodies. >>All right, far as teeing it up for you. Go, how cool is this? We don't, we wanna use every minute. What's the lunar surface look like? What's the infrastructure roads. You gonna pave it down. You what's going on. Well, >>Where we're going. No one has ever been. So, um, our first mission is going to Shackleton connecting Ridge on the south pole, the moon, and that's ripe to add infrastructure such as landing pads and other things. But our first Rover will be primarily driving across the surface, uh, exploring, uh, what the material looks like, prospecting for resources and testing new technologies. >>And you have a lot of technology involved. You're getting data in, you're just doing surveillance. What's the tech involved there. >>Yeah. So the primary technology that we're demonstrating is a 4g network for NOK. Um, we're providing them mobility services, which is basically like the old Verizon commercial. Can you hear me now? Uh, where the Rover drives farther and farther away from the Lander to test their signal strength, and then we're gonna have some other payloads ride sharing along with us for the ride >>Reminds me the old days of wifi. We used to call it war drive and you go around and try to find someone's wifi hotspot <laugh> inside the thing, but no, this is kind of cool. It brings up the whole thing. Now on lunar outpost, how big is the company? What's how what's to some of the stats heres some of the stats. >>Absolutely. So lunar outpost, 58 people, uh, growing quite quickly on track to double. So any of you watching, you want a job, please apply <laugh>. But with lunar outpost, uh, very similar to how launch companies provide people access to different parts of space. Lunar outpost provides people access to different spots on planetary bodies, whether it's the moon, Mars or beyond. So that's really where we're starting. >>So it's kinda like a managed service for all kinds of space utilities. If you kind of think about it, you're gonna provide services. Yeah, >>Absolutely. Yeah. It, it's definitely starting there and, and we're pushing towards building that infrastructure and that long term vision of utilizing space resources. But I can talk about that a little bit more here in a sec. >>Let's get into that. Let's talk about Mars first. You guys said what's going on with >>Mars. Absolutely. >>Yeah. So right now, uh, lunar outpost is part of the science team for, uh, Moxi, which is an instrument on the perseverance Rover. Yeah. Moxi is the first demonstration of space resource utilization on another planet. And what space resource utilization is basically taking resources on another planet, turning them into something useful. What Moxi does is it takes the CO2 from the atmosphere of Mars and atmosphere of Mars is mostly CO2 and it uses a process called solid oxide electrolysis to basically strip oxygen off of that CO2 to produce oh two and carbon monoxide. >>So it's what you need to self sustain on the surface. >>Exactly. It's not just sustaining, um, the astronauts, but also for producing oxygen for propellant. So it'll actually produce, um, it's a, it's a technology that'll produce a propellant for return rockets, um, to come back for Mars. So >>This is the real wildcard and all this, this, this exploration is how fast can the discoveries invent the new science to provide the life and the habitat on the surface. And that seems to be the real focus in the, in the conversations I heard on the keynote as well, get the infrastructure up so you can kinda land and, and we'll pull back and forth. Um, where are we on progress? You guys have the peg from one zero to 10, 10 being we're going, my grandmother's going, everyone's going to zero. Nothing's moving. >>We're making pretty rapid >>Progress. A three six, >>You know, I'll, I'll put it on an eight, John an >>Eight, I'll put it on >>Eight. This is why the mission force was just talking about that's launching within the next 12 months. This is no longer 10 years out. This is no longer 20 years away, 12 months. And then we have mission two shortly after, and that's just the beginning. We have over a dozen Landers that are headed to line surface this decade alone and heavy lift Landers and launchers, uh, start going to the moon and coming back by 2025. >>So, and you guys are from Colorado. You mentioned before you came on camera, right with the swap offices. So you got some space in Colorado, then the rovers to move around. You get, you get weird looks when people drive by and see the space gear. >>Oh yeah, definitely. So we have, um, you know, we have our facility in golden and our Nevada Colorado, and we'll take the vehicles out for strolls and you'll see construction workers, building stuff, and looking over and saying, what's >>Good place to work too. So you're, you're hiring great. You're doubling on the business model side. I can see a lot of demand. It's cheaper to launch stuff now in space. Is there becoming any rules of engagement relative to space? I don't wanna say verified, but like, you know, yet somehow get to the point where, I mean, I could launch a satellite, I could launch something for a couple hundred grand that might interfere with something legitimate. Do you see that on the radar because you guys are having ease of use so smaller, faster, cheaper to get out there. Now you gotta refine the infrastructure, get the services going. Is there threats from just random launches? >>It's a, it's a really interesting question. I mean, current state of the art people who have put rovers on other planetary bodies, you're talking like $3 billion, uh, for the March perseverance Rover. So historically there hasn't been that threat, but when you start talking about lowering the cost and the access to some of these different locations, I do think we'll get to the point where there might be folks that interfere with large scale operations. And that's something that's not very well defined in international law and something you won't really probably get any of the major space powers to agree to. So it's gonna be up to commercial companies to operate responsibly so we can make that space sustainable. And if there is a bad actor, I think it they'll weed themselves out over time. >>Yeah. It's gonna be of self govern, I think in the short term. Good point. Yeah. What about the technology? Where are we in the technology? What are some of the big, uh, challenges that we're overcoming now and what's that next 20 M stare in terms of the next milestone? Yeah, a tech perspective. >>Yeah. So the big technology technological hurdle that has been identified by many is the ability to survive the LUN night. Um, it gets exceptionally cold, uh, when the sun on the moon and that happens every 14 days for another, for, you know, for 14 days. So these long, cold lunar nights, uh, can destroy circuit boards and batteries and different components. So lunar outpost has invested in developing thermal technologies to overcome this, um, both in our offices, in the United States, but we also have opened a new office in, uh, Luxembourg in Europe. That's focusing specifically on thermal technologies to survive the lunar night, not just for rovers, but all sorts of space assets. >>Yeah. Huge. That's a hardware, you know, five, nine kind of like meantime between failure conversation, right. >><laugh> and it's, it gets fun, right? Because you talk five nines and it's such like, uh, you know, ingrained part of the aerospace community. But what we're pitching is we can send a dozen rovers for the cost of one of these historical rovers. So even if 25% of 'em fail, you still have eight rovers for the cost of one of the old rovers. And that's just the, economy's a scale. >>I saw James Hamilton here walking around. He's one of the legendary Amazonians who built out the data center. You might come by the cube. That's just like what they did with servers. Hey, if one breaks throw it away. Yeah. Why buy the big mainframe? Yeah. That's the new model. All right. So now about, uh, space space, that's a not space space, but like room to move around when you start getting some of these habitats going, um, how does space factor into the size of the location? Um, cuz you got the, to live there, solve some of the thermal problems. How do I live on space? I gotta have, you know, how many people gonna be there? What's your forecast? You think from a mission standpoint where there'll be dozens of people or is it still gonna be small teams? >>Yeah. >>Uh, what's that look like? >>I mean you >>Can guess it's okay. >>I mean, my vision's thousands of people. Yep. Uh, living and working in space because it's gonna be, especially the moon I think is a destination that's gonna grow, uh, for tourism. There's an insane drive from people to go visit a new destination. And the moon is one of the most unique experiences you could imagine. Yep. Um, in the near term for Artis, we're gonna start by supporting the Artis astronauts, which are gonna be small crews of astronauts. Um, you know, two to six in the near term. >>And to answer your question, uh, you know, in a different way, the habitat that we're actually gonna build, it's gonna take dozens of these robotic systems to build and maintain over time. And when we're actually talking, timelines, force talks, thousands of people living and working in space, I think that's gonna happen within the next 10 to 15 years. The first few folks are gonna be on the moon by 2025. And we're pushing towards having dozens of people living and working in space and by 2030. >>Yeah. I think it's an awesome goal. And I think it's doable question I'll have for you is the role of software in all this. I had a conversation with, uh, space nerd and we were talking and, and I said open sources everywhere now in the software. Yeah. How do you repair in space? Does you know, you don't want to have a firmware be down. So send down backhoe back to the United States. The us, wait a minute, it's the planet. I gotta go back to earth. Yeah. To get apart. So how does break fix work in space? How, how do you guys see that problem? >>So this one's actually quite fun. I mean, currently we don't have astronauts that can pick up a or change a tire. Uh, so you have to make robots that are really reliable, right. That can continuously operate for years at a time. But when you're talking about long-term repairs, there's some really cool ideas and concepts about standardization of some of these parts, you know, just like Lu knots on your car, right? Yeah. If everyone has the same Lu knots on their wheel, great. Now I can go change it out. I can switch off different parts that are available on the line surface. So I think we're moving towards, uh, that in the long >>Term you guys got a great company. Love the mission. Final question for both of you is I noticed that there's a huge community development around Mars, living on Mars, living on the moon. I mean, there's not a chat group that clubhouse app used, used to be around just kind of dying. But now it's when the Twitter spaces Reddit, you name it, there's a fanatical fan base that loves to talk about an engineer and kind of a collective intelligence, not, may not be official engineering, but they just love to talk about it. So there's a huge fan base for space. How does someone get involved if they really want to dive in and then how do you nurture that audience? How does that, is it developing? What's your take on this whole movement? It's it's beyond just being interested. It's it's become, I won't say cult-like but it's been, there's very, a lot of people in young people interested in space. >>Yeah. >>Yeah. There's, there's a whole, lots of places to get involved. There's, you know, societies, right? Like the Mar society there's technical committees, um, there's, you know, even potentially learning about these, you know, taking a space, resources master program and getting into the field and, and joining the company. So, um, we really, uh, thrive on that energy from the community and it really helps press us forward. And we hope to, uh, have a way to take everyone with us on the mission. And so stay tuned, follow our website. We'll be announcing some of that stuff soon. >>Awesome. And just one last, uh, quick pitch for you, John, I'll leave you with one thought. There are two things that space has an infinite amount of the first is power and the second is resources. And if we can find a way to access either of those, we can fundamentally change the way humanity operates. Yeah. So when you're talking about living on Mars long term, we're gonna need to access the resource from Mars. And then long term, once we get the transportation infrastructure in place, we can start bringing those resources back here to earth. So of course there are gonna be those people that sign up for that first mission out to Mars with SpaceX. But, uh, we'd love for folks to join on with us at lunar outpost and be a part of that kind of next leap accessing those resources. >>I love the mission, as always said, once in the cube, everything in star Trek will be invented someday. <laugh>, we're almost there except for the, the, uh, the transporter room. We don't have that done yet, but almost soon be there. All right. Well, thanks for coming. I, I really appreciate Justin for us for sharing. Great story. Final minute. Give a plug for the company. What are you guys looking for? You said hiring. Yep. Anything else you'd like to share? Put a plug in for lunar outpost. >>Absolutely. So we're hiring across the board, aerospace engineering, robotics engineering, sales marketing. Doesn't really matter. Uh, we're doubling as a company currently around 58 people, as we said, and we're looking for the top people that want to make an impact in aerospace. This is truly a unique moment. First time we've ever had continuous reliable operations. First time NASA is pushing really hard on the public private partnerships for commercial companies like ours to go out and create this sustainable presence on the moon. So whether you wanna work with us, our partner with us, we'd be excited to talk to you and, uh, yeah. Please contact us at info. Lunar outpost.com. >>We'll certainly follow up. Thanks for coming. I love the mission we're behind you and everyone else is too. You can see the energy it's gonna happen. It's the cube coverage from re Mars new actions happening in space on the ground, in the, on the moon you name it's happening right here in Vegas. I'm John furrier. Thanks for watching.

>>Yeah. Hello and welcome back to the cubes coverage of AWS public sector summit here in Washington D. C. We're live on the ground for two days. Face to face conference and expo hall and everything here but keith brooks who is the director and head of technical business development for a dress government Govcloud selling brains 10th birthday. Congratulations. Welcome to the cube. Thank you john happy to be E. C. 2 15 S three is 9.5 or no, that maybe they're 10 because that's the same day as sqs So Govcloud. 10 years, 20 years. What time >>flies? 10 years? >>Big milestone. Congratulations. A lot of history involved in Govcloud. Yes. Take us through what's the current situation? >>Yeah. So um let's start with what it is just for the viewers that may not be familiar. So AWS Govcloud is isolated. AWS cloud infrastructure and services that were purposely built for our U. S. Government customers that had highly sensitive data or highly regulated data or applications and workloads that they wanted to move to the cloud. So we gave customers the ability to do that with AWS Govcloud. It is subject to the fed ramp I and D O D S R G I L four L five baselines. It gives customers the ability to address ITAR requirements as well as Seaga's N'est ce MMC and Phipps requirements and gives customers a multi region architecture that allows them to also designed for disaster recovery and high availability in terms of why we built it. It starts with our customers. It was pretty clear from the government that they needed a highly secure and highly compliant cloud infrastructure to innovate ahead of demand and that's what we delivered. So back in august of 2011 we launched AWS GovCloud which gave customers the best of breed in terms of high technology, high security, high compliance in the cloud to allow them to innovate for their mission critical workloads. Who >>was some of the early customers when you guys launched after the C. I. A deal intelligence community is a big one but some of the early customers. >>So the Department of Health and Human Services, the Department of Veterans Affairs, the Department of Justice and the Department of Defense were all early users of AWS GovCloud. But one of our earliest lighthouse customers was the Nasa jet propulsion laboratory and Nasa Jpl used AWS GovCloud to procure Procure resources ahead of demand which allowed them to save money and also take advantage of being efficient and only paying for what they needed. But they went beyond just I. T. Operations. They also looked at how do they use the cloud and specifically GovCloud for their mission programs. So if you think back to all the way to 2012 with the mars curiosity rover, Nasa Jpl actually streamed and processed and stored that data from the curiosity rover on AWS Govcloud They actually streamed over 150 terabytes of data responded to over 80,000 requests per second and took it beyond just imagery. They actually did high performance compute and data analytics on the data as well. That led to additional efficiencies for future. Over there >>were entire kicking they were actually >>hard core missing into it. Mission critical workloads that also adhere to itar compliance which is why they used AWS GovCloud. >>All these compliance. So there's also these levels. I remember when I was working on the jetty uh stories that were out there was always like level for those different classifications. What does all that mean like? And then this highly available data and highly high availability all these words mean something in these top secret clouds. Can you take us through kind of meetings >>of those? Yeah absolutely. So it starts with the federal compliance program and the two most popular programs are Fed ramp and Dodi srg fed ramp is more general for federal government agencies. There are three levels low moderate and high in the short and skinny of those levels is how they align to the fisma requirements of the government. So there's fisma low fisma moderate fisma high depending on the sensitivity of the government data you will have to align to those levels of Fed ramp to use workloads and store data in the cloud. Similar story for D. O. D. With srg impact levels to 45 and six uh impacts levels to four and five are all for unclassified data. Level two is for less sensitive public defense data levels. Four and five cover more sensitive defense data to include mission critical national security systems and impact level six is for classified information. So those form the basis of security and compliance, luckily with AWS GovCloud celebrating our 10th anniversary, we address Fed ramp high for our customers that require that and D. O. D impact levels to four and five for a sensitive defense guy. >>And that was a real nuanced point and a lot of the competition can't do that. That's real people don't understand, you know, this company, which is that company and all the lobbying and all the mudslinging that goes on. We've seen that in the industry. It's unfortunate, but it happens. Um, I do want to ask you about the Fed ramp because what I'm seeing on the commercial side in the cloud ecosystem, a lot of companies that aren't quote targeting public sector are coming in on the Fed ramp. So there's some good traction there. You guys have done a lot of work to accelerate that. Any new, any new information to share their. >>Yes. So we've been committed to supporting the federal government compliance requirements effectively since the launch of GovCloud. And we've demonstrated our commitment to Fed ramp over the last number of years and GovCloud specifically, we've taken dozens of services through Fed ramp high and we're 100% committed to it because we have great relationships with the Fed ramp, Jabor the joint authorization board. We work with individual government agencies to secure agency A. T. O. S. And in fact we actually have more agency A. T. O. S. With AWS GovCloud than any other cloud provider. And the short and skinny is that represents the baseline for cloud security to address sensitive government workloads and sensitive government data. And what we're seeing from industry and specifically highly regulated industries is the standard that the U. S. Government set means that they have the assurance to run control and classified information or other levels of highly sensitive data on the cloud as well. So Fed ramp set that standard. It's interesting >>that the cloud, this is the ecosystem within an ecosystem again within crossover section. So for instance um the impact of not getting Fed ramp certified is basically money. Right. If you're a supplier vendor uh software developer or whatever used to being a miracle, no one no one would know right bed ramp. I'm gonna have to hire a whole department right now. You guys have a really easy, this is a key value proposition, isn't it? >>Correct. And you see it with a number of I. S. V. S. And software as the service providers. If you visit the federal marketplace website, you'll see dozens of providers that have Fed ramp authorized third party SAAS products running on GovCloud industry leading SAAS companies like Salesforce dot com driven technology Splunk essay PNS to effectively they're bringing their best of breed capabilities, building on top of AWS GovCloud and offering those highly compliant fed ramp, moderate fed ramp high capabilities to customers both in government and private industry that need that level of compliance. >>Just as an aside, I saw they've got a nice tweet from Teresa Carlson now it's plunk Govcloud yesterday. That was a nice little positive gesture uh, for you guys at GovCloud, what other areas are you guys moving the needle on because architecturally this is a big deal. What are some areas that you're moving the needle on for the GovCloud? >>Well, when I look back across the last 10 years, there were some pretty important developments that stand out. The first is us launching the second Govcloud infrastructure region in 2018 And that gave customers that use GovCloud specifically customers that have highly sensitive data and high levels of compliance. The ability to build fault tolerant, highly available and mission critical workloads in the cloud in a region that also gives them an additional three availability zones. So the launch of GovCloud East, which is named AWS GovCloud Us East gave customers to regions a total of six availability zones that allowed them accelerate and build more scalable solutions in the cloud. More recently, there is an emergence of another D O D program called the cybersecurity maturity model, C M M C and C M M C is something where we looked around the corner and said we need to Innovate to help our customers, particularly defense customers and the defense industrial based customers address see MMC requirements in the cloud. So with Govcloud back in December of 2020, we actually launched the AWS compliant framework for federal defense workloads, which gives customers a turnkey capability and tooling and resources to spin up environments that are configured to meet see MMC controls and D. O. D. Srg control. So those things represent some of the >>evolution keith. I'm interested also in your thoughts on how you see the progression of Govcloud outside the United States. Tactical Edge get wavelength coming on board. How does how do you guys look at that? Obviously us is global, it's not just the jet, I think it's more of in general. Edge deployments, sovereignty is also going to be world's flat, Right? I mean, so how does that >>work? So it starts back with customer requirements and I tie it back to the first question effectively we built Govcloud to respond to our U. S. Government customers and are highly regulated industry customers that had highly sensitive data and a high bar to meet in terms of regulatory compliance and that's the foundation of it. So as we look to other customers to include those outside of the US. It starts with those requirements. You mentioned things like edge and hybrid and a good example of how we marry the two is when we launched a W. S. Outpost in Govcloud last year. So outpost brings the power of the AWS cloud to on premises environments of our customers, whether it's their data centers or Coehlo environments by bringing AWS services, a. P. I. S and service and points to the customer's on premises facilities >>even outside the United States. >>Well, for Govcloud is focused on us right now. Outside of the U. S. Customers also have availability to use outpost. It's just for us customers, it's focused on outpost availability, geography >>right now us. Right. But other governments gonna want their Govcloud too. Right, Right, that's what you're getting at, >>Right? And it starts with the data. Right? So we we we spent a lot of time working with government agencies across the globe to understand their regulations and their requirements and we use that to drive our decisions. And again, just like we started with govcloud 10 years ago, it starts with our customer requirements and we innovate from there. Well, >>I've been, I love the D. O. D. S vision on this. I know jet I didn't come through and kind of went scuttled, got thrown under the bus or whatever however you want to call it. But that whole idea of a tactical edge, it was pretty brilliant idea. Um so I'm looking forward to seeing more of that. That's where I was supposed to come in, get snowball, snowmobile, little snow snow products as well, how are they doing? And because they're all part of the family to, >>they are and they're available in Govcloud and they're also authorized that fed ramp and Gov srg levels and it's really, it's really fascinating to see D. O. D innovate with the cloud. Right. So you mentioned tactical edge. So whether it's snowball devices or using outposts in the future, I think the D. O. D. And our defense customers are going to continue to innovate. And quite frankly for us, it represents our commitment to the space we want to make sure our defense customers and the defense industrial base defense contractors have access to the best debris capabilities like those edge devices and edge capable. I >>think about the impact of certification, which is good because I just thought of a clean crows. We've got aerospace coming in now you've got D O. D, a little bit of a cross colonization if you will. So nice to have that flexibility. I got to ask you about just how you view just in general, the intelligence community a lot of uptake since the CIA deal with amazon Just overall good health for eight of his gum cloud. >>Absolutely. And again, it starts with our commitment to our customers. We want to make sure that our national security customers are defense customers and all of the customers and the federal government that have a responsibility for securing the country have access to the best of breed capability. So whether it's the intelligence community, the Department of Defense are the federal agencies and quite frankly we see them innovating and driving things forward to include with their sensitive workloads that run in Govcloud, >>what's your strategy for partnerships as you work on the ecosystem? You do a lot with strategy. Go to market partnerships. Um, it's got its public sector pretty much people all know each other. Our new firms popping up new brands. What's the, what's the ecosystem looks like? >>Yeah, it's pretty diverse. So for Govcloud specifically, if you look at partners in the defense community, we work with aerospace companies like Lockheed martin and Raytheon Technologies to help them build I tar compliant E. R. P. Application, software development environments etcetera. We work with software companies I mentioned salesforce dot com. Splunk and S. A. P. And S. To uh and then even at the state and local government level, there's a company called Pay It that actually worked with the state of Kansas to develop the Icann app, which is pretty fascinating. It's a app that is the official app of the state of Kansas that allow citizens to interact with citizens services. That's all through a partner. So we continue to work with our partner uh broad the AWS partner network to bring those type of people >>You got a lot of MST is that are doing good work here. I saw someone out here uh 10 years. Congratulations. What's the coolest thing uh you've done or seen. >>Oh wow, it's hard to name anything in particular. I just think for us it's just seeing the customers and the federal government innovate right? And, and tie that innovation to mission critical workloads that are highly important. Again, it reflects our commitment to give these government customers and the government contractors the best of breed capabilities and some of the innovation we just see coming from the federal government leveraging the count now. It's just super cool. So hard to pinpoint one specific thing. But I love the innovation and it's hard to pick a favorite >>Child that we always say. It's kind of a trick question I do have to ask you about just in general, the just in 10 years. Just look at the agility. Yeah, I mean if you told me 10 years ago the government would be moving at any, any agile anything. They were a glacier in terms of change, right? Procure Man, you name it. It's just like, it's a racket. It's a racket. So, so, but they weren't, they were slow and money now. Pandemic hits this year. Last year, everything's up for grabs. The script has been flipped >>exactly. And you know what, what's interesting is there were actually a few federal government agencies that really paved the way for what you're seeing today. I'll give you some examples. So the Department of Veterans Affairs, they were an early Govcloud user and way back in 2015 they launched vets dot gov on gov cloud, which is an online platform that gave veterans the ability to apply for manage and track their benefits. Those type of initiatives paved the way for what you're seeing today, even as soon as last year with the U. S. Census, right? They brought the decennial count online for the first time in history last year, during 2020 during the pandemic and the Census Bureau was able to use Govcloud to launch and run 2020 census dot gov in the cloud at scale to secure that data. So those are examples of federal agencies that really kind of paved the way and leading to what you're saying is it's kind >>of an awakening. It is and I think one of the things that no one's reporting is kind of a cultural revolution is the talent underneath that way, the younger people like finally like and so it's cooler. It is when you go fast and you can make things change, skeptics turned into naysayers turned into like out of a job or they don't transform so like that whole blocker mentality gets exposed just like shelf where software you don't know what it does until the cloud is not performing, its not good. Right, right. >>Right. Into that point. That's why we spend a lot of time focused on education programs and up skilling the workforce to, because we want to ensure that as our customers mature and as they innovate, we're providing the right training and resources to help them along their journey, >>keith brooks great conversation, great insight and historian to taking us to the early days of Govcloud. Thanks for coming on the cube. Thanks thanks for having me cubes coverage here and address public sector summit. We'll be back with more coverage after this short break. Mhm. Mhm mm.

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

>>From around the globe. It's the queue with digital coverage of dev ops virtual forum brought to you by Broadcom. >>Hi, Lisa Martin here covering the Broadcom dev ops virtual forum. I'm very pleased to be joined today by a cube alumni, Jeffrey Hammond, the vice president and principal analyst serving CIO is at Forester. Jeffrey. Nice to talk with you today. >>Good morning. It's good to be here. Yeah. >>So a virtual forum, great opportunity to engage with our audiences so much has changed in the last it's an understatement, right? Or it's an overstated thing, but it's an obvious, so much has changed when we think of dev ops. One of the things that we think of is speed, you know, enabling organizations to be able to better serve customers or adapt to changing markets like we're in now, speaking of the need to adapt, talk to us about what you're seeing with respect to dev ops and agile in the age of COVID, what are things looking like? >>Yeah, I think that, um, for most organizations, we're in a, uh, a period of adjustment, uh, when we initially started, it was essentially a sprint, you know, you run as hard as you can for as fast as you can for as long as you can and you just kind of power through it. And, and that's actually what, um, the folks that get hub saw in may when they ran an analysis of how developers, uh, commit times and a level of work that they were committing and how they were working, uh, in the first couple of months of COVID was, was progressing. They found that developers, at least in the Pacific time zone were actually increasing their work volume, maybe because they didn't have two hour commutes or maybe because they were stuck away in their homes, but for whatever reason, they were doing more work. >>And it's almost like, you know, if you've ever run a marathon the first mile or two in the marathon, you feel great and you just want to run and you want to power through it and you want to go hard. And if you do that by the time you get to mile 18 or 19, you're going to be gassed. It's sucking for wind. Uh, and, and that's, I think where we're starting to hit. So as we start to, um, gear our development chops out for the reality that most of us won't be returning into an office until 2021 at the earliest and many organizations will, will be fundamentally changing, uh, their remote workforce, uh, policies. We have to make sure that the agile processes that we use and the dev ops processes and tools that we use to support these teams are essentially aligned to help developers run that marathon instead of just kind of power through. >>So, um, let me give you a couple of specifics for many organizations, they have been in an environment where they will, um, tolerate Rover remote work and what I would call remote work around the edges like developers can be remote, but product managers and, um, you know, essentially scrum masters and all the administrators that are running the, uh, uh, the SCM repositories and, and the dev ops pipelines are all in the office. And it's essentially centralized work. That's not, we are anymore. We're moving from remote workers at the edge to remote workers at the center of what we do. And so one of the implications of that is that, um, we have to think about all the activities that you need to do from a dev ops perspective or from an agile perspective, they have to be remote people. One of the things I found with some of the organizations I talked to early on was there were things that administrators had to do that required them to go into the office to reboot the SCM server as an example, or to make sure that the final approvals for production, uh, were made. >>And so the code could be moved into the production environment. And so it actually was a little bit difficult because they had to get specific approval from the HR organizations to actually be allowed to go into the office in some States. And so one of the, the results of that is that while we've traditionally said, you know, tools are important, but they're not as important as culture as structure as organization as process. I think we have to rethink that a little bit because to the extent that tools enable us to be more digitally organized and to hiring, you know, achieve higher levels of digitization in our processes and be able to support the idea of remote workers in the center. They're now on an equal footing with so many of the other levers, uh, that, that, um, uh, that organizations have at their disposal. Um, I'll give you another example for years. >>We've said that the key to success with agile at the team level is cross-functional co located teams that are working together physically co located. It's the easiest way to show agile success. We can't do that anymore. We can't be physically located at least for the foreseeable future. So, you know, how do you take the low hanging fruits of an agile transformation and apply it in, in, in, in the time of COVID? Well, I think what you have to do is that you have to look at what physical co-location has enabled in the past and understand that it's not so much the fact that we're together looking at each other across the table. It's the fact that we're able to get into a shared mindspace, uh, from, um, uh, from a measurement perspective, we can have shared purpose. We can engage in high bandwidth communications. It's the spiritual aspect of that physical co-location that is actually important. So one of the biggest things that organizations need to start to ask themselves is how do we achieve spiritual colocation with our agile teams? Because we don't have the, the ease of physical co-location available to us anymore? >>Well, the spiritual co-location is such an interesting kind of provocative phrase there, but something that probably was a challenge here, we are seven, eight months in for many organizations, as you say, going from, you know, physical workspaces, co-location being able to collaborate face to face to a, a light switch flip overnight. And this undefined period of time where all we were living with with was uncertainty, how does spiritual, what do you, when you talk about spiritual co-location in terms of collaboration and processes and technology help us unpack that, and how are you seeing organizations adopted? >>Yeah, it's, it's, um, it's a great question. And, and I think it goes to the very root of how organizations are trying to transform themselves to be more agile and to embrace dev ops. Um, if you go all the way back to the, to the original, uh, agile manifesto, you know, there were four principles that were espoused individuals and interactions over processes and tools. That's still important. Individuals and interactions are at the core of software development, processes and tools that support those individual and interact. Uh, those individuals in those interactions are more important than ever working software over comprehensive documentation. Working software is still more important, but when you are trying to onboard employees and they can't come into the office and they can't do the two day training session and kind of understand how things work and they can't just holler over the cube, uh, to ask a question, you may need to invest a little bit more in documentation to help that onboarding process be successful in a remote context, uh, customer collaboration over contract negotiation. >>Absolutely still important, but employee collaboration is equally as important if you want to be spiritually, spiritually co-located. And if you want to have a shared purpose and then, um, responding to change over following a plan. I think one of the things that's happened in a lot of organizations is we have focused so much of our dev ops effort around velocity getting faster. We need to run as fast as we can like that sprinter. Okay. You know, trying to just power through it as quickly as possible. But as we shift to, to the, to the marathon way of thinking, um, velocity is still important, but agility becomes even more important. So when you have to create an application in three weeks to do track and trace for your employees, agility is more important. Um, and then just flat out velocity. Um, and so changing some of the ways that we think about dev ops practices, um, is, is important to make sure that that agility is there for one thing, you have to defer decisions as far down the chain to the team level as possible. >>So those teams have to be empowered to make decisions because you can't have a program level meeting of six or seven teams and one large hall and say, here's the lay of the land. Here's what we're going to do here are our processes. And here are our guardrails. Those teams have to make decisions much more quickly that developers are actually developing code in smaller chunks of flow. They have to be able to take two hours here or 50 minutes there and do something useful. And so the tools that support us have to become tolerant of the reality of, of, of, of how we're working. So if they work in a way that it allows the team together to take as much autonomy as they can handle, um, to, uh, allow them to communicate in a way that, that, that delivers shared purpose and allows them to adapt and master new technologies, then they're in the zone in their spiritual, they'll get spiritually connected. I hope that makes sense. >>It does. I think we all could use some of that, but, you know, you talked about in the beginning and I've, I've talked to numerous companies during the pandemic on the cube about the productivity, or rather the number of hours of work has gone way up for many roles, you know, and, and, and times that they normally late at night on the weekends. So, but it's a cultural, it's a mind shift to your point about dev ops focused on velocity, sprints, sprints, sprints, and now we have to, so that cultural shift is not an easy one for developers. And even at this folks to flip so quickly, what have you seen in terms of the velocity at which businesses are able to get more of that balance between the velocity, the sprint and the agility? >>I think, I think at the core, this really comes down to management sensitivity. Um, when everybody was in the office, you could kind of see the mental health of development teams by, by watching how they work. You know, you call it management by walking around, right. We can't do that. Managers have to, um, to, to be more aware of what their teams are doing, because they're not going to see that, that developer doing a check-in at 9:00 PM on a Friday, uh, because that's what they had to do, uh, to meet the objectives. And, um, and, and they're going to have to, to, um, to find new ways to measure engagement and also potential burnout. Um, friend of mine once had, uh, had a great metric that he called the parking lot metric. It was helpful as the parking lot at nine. And how full was it at five? >>And that gives you an indication of how engaged your developers are. Um, what's the digital equivalent equivalent to the parking lot metric in the time of COVID it's commit stats, it's commit rates. It's, um, you know, the, uh, the turn rate, uh, that we have in our code. So we have this information, we may not be collecting it, but then the next question becomes, how do we use that information? Do we use that information to say, well, this team isn't delivering as at the same level of productivity as another team, do we weaponize that data or do we use that data to identify impedances in the process? Um, why isn't a team working effectively? Is it because they have higher levels of family obligations and they've got kids that, that are at home? Um, is it because they're working with, um, you know, hardware technology, and guess what, they, it's not easy to get the hardware technology into their home office because it's in the lab at the, uh, at the corporate office, uh, or they're trying to communicate, uh, you know, halfway around the world. >>And, uh, they're communicating with a, with an office lab that is also shut down and, and, and the bandwidth just doesn't enable the, the level of high bandwidth communications. So from a dev ops perspective, managers have to get much more sensitive to the, the exhaust that the dev ops tools are throwing off, but also how they're going to use that in a constructive way to, to prevent burnout. And then they also need to, if they're not already managing or monitoring or measuring the level of developer engagement, they have, they really need to start whether that's surveys around developer satisfaction, um, whether it's, you know, more regular social events, uh, where developers can kind of just get together and drink a beer and talk about what's going on in the project, uh, and monitoring who checks in and who doesn't, uh, they have to, to, um, work harder, I think, than they ever have before. >>Well, and you mentioned burnout, and that's something that I think we've all faced in this time at varying levels and it changes. And it's a real, there's a tension in the air, regardless of where you are. There's a challenge, as you mentioned, people having, you know, coworker, their kids as coworkers and fighting for bandwidth, because everyone is forced in this situation. I'd love to get your perspective on some businesses that are, that have done this well, this adaptation, what can you share in terms of some real-world examples that might inspire the audience? >>Yeah. Uh, I'll start with, uh, stack overflow. Uh, they recently published a piece in the journal of the ACM around some of the things that they had discovered. Um, you know, first of all, just a cultural philosophy. If one person is remote, everybody is remote. And you just think that way from an executive level, um, social spaces. One of the things that they talk about doing is leaving a video conference room open at a team level all day long, and the team members, you know, we'll go on mute, you know, so that they don't have to, that they don't necessarily have to be there with somebody else listening to them. But if they have a question, they can just pop off mute really quickly and ask the question. And if anybody else knows the answer, it's kind of like being in that virtual pod. Uh, if you, uh, if you will, um, even here at Forrester, one of the things that we've done is we've invested in social ceremonies. >>We've actually moved our to our team meetings on, on my analyst team from, from once every two weeks to weekly. And we have built more time in for social Ajay socialization, just so we can see, uh, how, how, how we're doing. Um, I think Microsoft has really made some good, uh, information available in how they've managed things like the onboarding process. I think I'm Amanda silver over there mentioned that a couple of weeks ago when, uh, uh, a presentation they did that, uh, uh, Microsoft onboarded over 150,000 people since the start of COVID, if you don't have good remote onboarding processes, that's going to be a disaster. Now they're not all developers, but if you think about it, um, everything from how you do the interviewing process, uh, to how you get people, their badges, to how they get their equipment. Um, security is a, is another issue that they called out typically, uh, it security, um, the security of, of developers machines ends at, at, at the corporate desktop. >>But, you know, since we're increasingly using our own machines, our own hardware, um, security organizations kind of have to extend their security policies to cover, uh, employee devices, and that's caused them to scramble a little bit. Uh, so, so the examples are out there. It's not a lot of, like, we have to do everything completely differently, but it's a lot of subtle changes that, that have to be made. Um, I'll give you another example. Um, one of the things that, that we are seeing is that, um, more and more organizations to deal with the challenges around agility, with respect to delivering software, embracing low-code tools. In fact, uh, we see about 50% of firms are using low-code tools right now. We predict it's going to be 75% by the end of next year. So figuring out how your dev ops processes support an organization that might be using Mendix or OutSystems, or, you know, the power platform building the front end of an application, like a track and trace application really, really quickly, but then hooking it up to your backend infrastructure. Does that happen completely outside the dev ops investments that you're making and the agile processes that you're making, or do you adapt your organization? Um, our hybrid teams now teams that not just have professional developers, but also have business users that are doing some development with a low-code tool. Those are the kinds of things that we have to be, um, willing to, um, to entertain in order to shift the focus a little bit more toward the agility side, I think >>Lot of obstacles, but also a lot of opportunities for businesses to really learn, pay attention here, pivot and grow, and hopefully some good opportunities for the developers and the business folks to just get better at what they're doing and learning to embrace spiritual co-location Jeffrey, thank you so much for joining us on the program today. Very insightful conversation. >>My pleasure. It's it's, it's an important thing. Just remember if you're going to run that marathon, break it into 26, 10 minute runs, take a walk break in between each and you'll find that you'll get there. >>Digestible components, wise advice. Jeffery Hammond. Thank you so much for joining for Jeffrey I'm Lisa Martin, you're watching Broadcom's dev ops virtual forum >>From around the globe. It's the queue with digital coverage of dev ops virtual forum brought to you by Broadcom, >>Continuing our conversations here at Broadcom's dev ops virtual forum. Lisa Martin here, please. To welcome back to the program, Serge Lucio, the general manager of the enterprise software division at Broadcom. Hey, Serge. Welcome. Thank you. Good to be here. So I know you were just, uh, participating with the biz ops manifesto that just happened recently. I just had the chance to talk with Jeffrey Hammond and he unlocked this really interesting concept, but I wanted to get your thoughts on spiritual co-location as really a necessity for biz ops to succeed in this unusual time in which we're living. What are your thoughts on spiritual colocation in terms of cultural change versus adoption of technologies? >>Yeah, it's a, it's, it's quite interesting, right? When we, when we think about the major impediments for, uh, for dev ops implementation, it's all about culture, right? And swore over the last 20 years, we've been talking about silos. We'd be talking about the paradox for these teams to when it went to align in many ways, it's not so much about these teams aligning, but about being in the same car in the same books, right? It's really about fusing those teams around kind of the common purpose, a common objective. So to me, the, this, this is really about kind of changing this culture where people start to look at a kind of OKR is instead of the key objective, um, that, that drives the entire team. Now, what it means in practice is really that's, uh, we need to change a lot of behaviors, right? It's not about the Yarki, it's not about roles. It's about, you know, who can do what and when, and, uh, you know, driving a bias towards action. It also means that we need, I mean, especially in this school times, it becomes very difficult, right? To drive kind of a kind of collaboration between these teams. And so I think there there's a significant role that especially tools can play in terms of providing this complex feedback from teams to, uh, to be in that preface spiritual qualification. >>Well, and it talked about culture being, it's something that, you know, we're so used to talking about dev ops with respect to velocity, all about speed here. But of course this time everything changed so quickly, but going from the physical spaces to everybody being remote really does take it. It's very different than you can't replicate it digitally, but there are collaboration tools that can kind of really be essential to help that cultural shift. Right? >>Yeah. So 2020, we, we touch to talk about collaboration in a very mundane way. Like, of course we can use zoom. We can all get into, into the same room. But the point when I think when Jeff says spiritual, co-location, it's really about, we all share the same objective. Do we, do we have a niece who, for instance, our pipeline, right? When you talk about dev ops, probably we all started thinking about this continuous delivery pipeline that basically drives the automation, the orchestration across the team, but just thinking about a pipeline, right, at the end of the day, it's all about what is the meantime to beat back to these teams. If I'm a developer and a commit code, I don't, does it take where, you know, that code to be processed through pipeline pushy? Can I get feedback if I am a finance person who is funding a product or a project, what is my meantime to beat back? >>And so a lot of, kind of a, when we think about the pipeline, I think what's been really inspiring to me in the last year or so is that there is much more of an adoption of the Dora metrics. There is way more of a focus around value stream management. And to me, this is really when we talk about collaboration, it's really a balance. How do you provide the feedback to the different stakeholders across the life cycle in a very timely matter? And that's what we would need to get to in terms of kind of this, this notion of collaboration. It's not so much about people being in the same physical space. It's about, you know, when I checked in code, you know, to do I guess the system to automatically identify what I'm going to break. If I'm about to release some allegation, how can the system help me reduce my change pillar rates? Because it's, it's able to predict that some issue was introduced in the outpatient or work product. Um, so I think there's, there's a great role of technology and AI candidate Lynch to, to actually provide that new level of collaboration. >>So we'll get to AI in a second, but I'm curious, what are some of the, of the metrics you think that really matter right now is organizations are still in some form of transformation to this new almost 100% remote workforce. >>So I'll just say first, I'm not a big fan of metrics. Um, and the reason being that, you know, you can look at a change killer rate, right, or a lead time or cycle time. And those are, those are interesting metrics, right? The trend on metric is absolutely critical, but what's more important is you get to the root cause what is taught to you lean to that metric to degrade or improve or time. And so I'm much more interested and we, you know, fruit for Broadcom. Are we more interested in understanding what are the patterns that contribute to this? So I'll give you a very mundane example. You know, we know that cycle time is heavily influenced by, um, organizational boundaries. So, you know, we talk a lot about silos, but, uh, we we've worked with many of our customers doing value stream mapping. And oftentimes what you see is that really the boundaries of your organization creates a lot of idle time, right? So to me, it's less about the metrics. I think the door metrics are a pretty, you know, valid set metrics, but what's way more important is to understand what are the antiperspirants, what are the things that we can detect through the data that actually are affecting those metrics. And, uh, I mean, over the last 10, 20 years, we've learned a lot about kind of what are, what are the antiperspirants within our large enterprise customers. And there are plenty of them. >>What are some of the things that you're seeing now with respect to patterns that have developed over the last seven to eight months? >>So I think the two areas which clearly are evolving very quickly are on kind of the front end of the life cycle, where DevOps is more and more embracing value stream management value stream mapping. Um, and I think what's interesting is that in many ways the product is becoming the new silo. Uh, the notion of a product is very difficult by itself to actually define people are starting to recognize that a value stream is not its own little kind of Island. That in reality, when I define a product, this product, oftentimes as dependencies on our products and that in fact, you're looking at kind of a network of value streams, if you will. So, so even on that, and there is clearly kind of a new sets, if you will, of anti-patterns where products are being defined as a set of OTRs, they have interdependencies and you have have a new set of silos on the operands, uh, the Abra key movement to Israel and the SRE space where, um, I think there is a cultural clash while the dev ops side is very much embracing this notion of OTRs and value stream mapping and Belgium management. >>On the other end, you have the it operations teams. We still think business services, right? For them, they think about configure items, think about infrastructure. And so, you know, it's not uncommon to see, you know, teams where, you know, the operations team is still thinking about hundreds of thousands, tens of thousands of business services. And so the, the, there is there's this boundary where, um, I think, well, SRE is being put in place. And there's lots of thinking about what kind of metrics can be fined. I think, you know, going back to culture, I think there's a lot of cultural evolution that's still required for true operations team. >>And that's a hard thing. Cultural transformation in any industry pandemic or not is a challenging thing. You talked about, uh, AI and automation of minutes ago. How do you think those technologies can be leveraged by DevOps leaders to influence their successes and their ability to collaborate, maybe see eye to eye with the SRS? >>Yeah. Um, so th you're kind of too. So even for myself, as a leader of a, you know, 1500 people organization, there's a number of things I don't see right. On a daily basis. And, um, I think the, the, the, the technologies that we have at our disposal today from the AI are able to mind a lot of data and expose a lot of, uh, issues that's as leaders we may not be aware of. And some of the, some of these are pretty kind of easy to understand, right? We all think we're agile. And yet when you, when you start to understand, for instance, uh, what is the, what is the working progress right to during the sprint? Um, when you start to analyze the data you can detect, for instance, that maybe the teams are over committed, that there is too much work in progress. >>You can start to identify kind of, interdepencies either from a technology, from a people point of view, which were hidden, uh, you can start to understand maybe the change filler rates he's he is dragging. So I believe that there is a, there's a fundamental role to be played by the tools to, to expose again, these anti parents, to, to make these things visible to the teams, to be able to even compare teams. Right. One of the things that's, that's, uh, that's amazing is now we have access to tons of data, not just from a given customer, but across a large number of customers. And so we start to compare all of these teams kind of operate, and what's working, what's not working >>Thoughts on AI and automation as, as a facilitator of spiritual co-location. >>Yeah, absolutely. Absolutely. It's um, you know, th there's, uh, the problem we all face is the unknown, right? The, the law city, but volume variety of the data, uh, everyday we don't really necessarily completely appreciate what is the impact of our actions, right? And so, um, AI can really act as a safety net that enables us to, to understand what is the impact of our actions. Um, and so, yeah, in many ways, the ability to be informed in a timely matter to be able to interact with people on the basis of data, um, and collaborate on the data. And the actual matter, I think is, is a, is a very powerful enabler, uh, on, in that respect. I mean, I, I've seen, um, I've seen countless of times that, uh, for instance, at the SRE boundary, um, to basically show that we'll turn the quality attributes, so an incoming release, right. And exposing that to, uh, an operations person and a sorry person, and enabling that collaboration dialogue through data is a very, very powerful tool. >>Do you have any recommendations for how teams can use, you know, the SRE folks, the dev ops says can use AI and automation in the right ways to be successful rather than some ways that aren't going to be nonproductive. >>Yeah. So to me, the th there, there's a part of the question really is when, when we talk about data, there are there different ways you can use data, right? Um, so you can, you can do a lot of an analytics, predictive analytics. So I think there is a, there's a tendency, uh, to look at, let's say a, um, a specific KPI, like a, an availability KPI, or change filler rate, and to basically do a regression analysis and projecting all these things, going to happen in the future. To me, that that's, that's a, that's a bad approach. The reason why I fundamentally think it's a better approach is because we are systems. The way we develop software is, is a, is a non-leader kind of system, right? Software development is not linear nature. And so I think there's a D this is probably the worst approach is to actually focus on metrics on the other end. >>Um, if you, if you start to actually understand at a more granular level, what har, uh, which are the things which are contributing to this, right? So if you start to understand, for instance, that whenever maybe, you know, you affect a specific part of the application that translates into production issues. So we, we have, I've actually, uh, a customer who, uh, identified that, uh, over 50% of their unplanned outages were related to specific components in your architecture. And whenever these components were changed, this resulted in these plant outages. So if you start to be able to basically establish causality, right, cause an effect between kind of data across the last cycle. I think, I think this is the right way to, uh, to, to use AI. And so pharma to be, I think it's way more God could have a classification problem. What are the classes of problems that do exist and affect things as opposed to analytics, predictive, which I don't think is as powerful. >>So I mentioned in the beginning of our conversation, that just came off the biz ops manifesto. You're one of the authors of that. I want to get your thoughts on dev ops and biz ops overlapping, complimenting each other, what, from a, the biz ops perspective, what does it mean to the future of dev ops? >>Yeah, so, so it's interesting, right? If you think about DevOps, um, there's no felony document, right? Can we, we can refer to the Phoenix project. I mean, there are a set of documents which have been written, but in many ways, there's no clear definition of what dev ops is. Uh, if you go to the dev ops Institute today, you'll see that they are specific, um, trainings for instance, on value management on SRE. And so in many ways, the problem we have as an industry is that, um, there are set practices between agile dev ops, SRE Valley should management. I told, right. And we all basically talk about the same things, right. We all talk about essentially, um, accelerating in the meantime fee to feedback, but yet we don't have the common framework to talk about that. The other key thing is that we add to wait, uh, for, uh, for jeans, Jean Kim's Lascaux, um, to, uh, to really start to get into the business aspect, right? >>And for value stream mapping to start to emerge for us to start as an industry, right. It, to start to think about what is our connection with the business aspect, what's our purpose, right? And ultimately it's all about driving these business outcomes. And so to me, these ops is really about kind of, uh, putting a lens on this critical element that it's not business and it, that we in fact need to fuse business 19 that I need needs to transform itself to recognize that it's, it's this value generator, right. It's not a cost center. And so the relationship to me, it's more than BizOps provides kind of this Oliver or kind of framework, if you will. That set the context for what is the reason, uh, for it to exist. What's part of the core values and principles that it needs to embrace to, again, change from a cost center to a value center. And then we need to start to use this as a way to start to unify some of the, again, the core practices, whether it's agile, DevOps value, stream mapping SRE. Um, so, so I think over time, my hope is that we start to optimize a lot of our practices, language, um, and, uh, and cultural elements. >>Last question surgeon, the last few seconds we have here talking about this, the relation between biz ops and dev ops, um, what do you think as DevOps evolves? And as you talked to circle some of your insights, what should our audience keep their eyes on in the next six to 12 months? >>So to me, the key, the key, um, challenge for, for the industry is really around. So we were seeing a very rapid shift towards kind of, uh, product to product, right. Which we don't want to do is to recreate kind of these new silos, these hard silos. Um, so that, that's one of the big changes, uh, that I think we need to be, uh, to be really careful about, um, because it is ultimately, it is about culture. It's not about, uh, it's not about, um, kind of how we segment the work, right. And, uh, any true culture that we can overcome kind of silos. So back to, I guess, with Jeffrey's concept of, um, kind of the spiritual co-location, I think it's, it's really about that too. It's really about kind of, uh, uh, focusing on the business outcomes on kind of aligning on driving engagement across the teams, but, but not for create a, kind of a new set of silos, which instead of being vertical are going to be these horizontal products >>Crazy by surge that looking at culture as kind of a way of really, uh, uh, addressing and helping to, uh, re re reduce, replace challenges. We thank you so much for sharing your insights and your time at today's DevOps virtual forum. >>Thank you. Thanks for your time. >>I'll be right back >>From around the globe it's the cube with digital coverage of devops virtual forum brought to you by Broadcom. >>Welcome to Broadcom's DevOps virtual forum, I'm Lisa Martin, and I'm joined by another Martin, very socially distanced from me all the way coming from Birmingham, England is Glynn Martin, the head of QA transformation at BT. Glynn, it's great to have you on the program. Thank you, Lisa. I'm looking forward to it. As we said before, we went live to Martins for the person one in one segment. So this is going to be an interesting segment guys, what we're going to do is Glynn's going to give us a really kind of deep inside out view of devops from an evolution perspective. So Glynn, let's start. Transformation is at the heart of what you do. It's obviously been a very transformative year. How have the events of this year affected the >> transformation that you are still responsible for driving? Yeah. Thank you, Lisa. I mean, yeah, it has been a difficult year. >>Um, and although working for BT, which is a global telecommunications company, um, I'm relatively resilient, I suppose, as a, an industry, um, through COVID obviously still has been affected and has got its challenges. And if anything, it's actually caused us to accelerate our transformation journey. Um, you know, we had to do some great things during this time around, um, you know, in the UK for our emergency and, um, health workers give them unlimited data and for vulnerable people to support them. And that's spent that we've had to deliver changes quickly. Um, but what we want to be able to do is deliver those kinds of changes quickly, but sustainably for everything that we do, not just because there's an emergency. Um, so we were already on the kind of journey to agile, but ever more important now that we are, we are able to do those, that kind of work, do it more quickly. >>Um, and that it works because the, the implications of it not working is, can be terrible in terms of you know, we've been supporting testing centers,  new hospitals to treat COVID patients. So we need to get it right. And then therefore the coverage of what we do, the quality of what we do and how quickly we do it really has taken on a new scale and what was already a very competitive market within the telco industry within the UK. Um, you know, what I would say is that, you know, we are under pressure to deliver more value, but we have small cost challenges. We have to obviously, um, deal with the fact that, you know, COVID 19 has hit most industries kind of revenues and profits. So we've got this kind of paradox between having less costs, but having to deliver more value quicker and  to higher quality. So yeah, certainly the finances is, um, on our minds and that's why we need flexible models, cost models that allow us to kind of do growth, but we get that growth by showing that we're delivering value. Um, especially in these times when there are financial challenges on companies. So one of the things that I want to ask you about, I'm again, looking at DevOps from the inside >>Out and the evolution that you've seen, you talked about the speed of things really accelerating in this last nine months or so. When we think dev ops, we think speed. But one of the things I'd love to get your perspective on is we've talked about in a number of the segments that we've done for this event is cultural change. What are some of the things that you've seen there as, as needing to get, as you said, get things right, but done so quickly to support essential businesses, essential workers. How have you seen that cultural shift? >>Yeah, I think, you know, before test teams for themselves at this part of the software delivery cycle, um, and actually now really our customers are expecting that quality and to deliver for our customers what they want, quality has to be ingrained throughout the life cycle. Obviously, you know, there's lots of buzzwords like shift left. Um, how do we do shift left testing? Um, but for me, that's really instilling quality and given capabilities shared capabilities throughout the life cycle that drive automation, drive improvements. I always say that, you know, you're only as good as your lowest common denominator. And one thing that we were finding on our dev ops journey was that we  would be trying to do certain things quick, we had automated build, automated tests. But if we were taking a weeks to create test scripts, or we were taking weeks to manually craft data, and even then when we had taken so long to do it, that the coverage was quite poor and that led to lots of defects later on in the life cycle, or even in our production environment, we just couldn't afford to do that. >>And actually, focusing on continuous testing over the last nine to 12 months has really given us the ability to deliver quickly across the whole life cycle. And therefore actually go from doing a kind of semi agile kind of thing, where we did the user stories, we did a few of the kind of agile ceremonies, but we weren't really deploying any quicker into production because our stakeholders were scared that we didn't have the same control that we had when we had more waterfall releases. And, you know, when we didn't think of ourselves. So we've done a lot of work on every aspect, um, especially from a testing point of view, every aspect of every activity, rather than just looking at automated tests, you know, whether it is actually creating the test in the first place, whether it's doing security testing earlier in the lot and performance testing in the life cycle, et cetera. So, yeah,  it's been a real key thing that for CT, for us to drive DevOps, >>Talk to me a little bit about your team. What are some of the shifts in terms of expectations that you're experiencing and how your team interacts with the internal folks from pipeline through life cycle? >>Yeah, we've done a lot of work on this. Um, you know, there's a thing that I think people will probably call it a customer experience gap, and it reminds me of a Gilbert cartoon, where we start with the requirements here and you're almost like a Chinese whisper effects and what we deliver is completely different. So we think the testing team or the delivery teams, um, know in our teeth has done a great job. This is what it said in the acceptance criteria, but then our customers are saying, well, actually that's not working this isn't working and there's this kind of gap. Um, we had a great launch this year of agile requirements, it's one of the Broadcom tools. And that was the first time in, ever since I remember actually working within BT, I had customers saying to me, wow, you know, we want more of this. >>We want more projects to have extra requirements design on it because it allowed us to actually work with the business collaboratively. I mean, we talk about collaboration, but how do we actually, you know, do that and have something that both the business and technical people can understand. And we've actually been working with the business , using agile requirements designer to really look at what the requirements are, tease out requirements we hadn't even thought of and making sure that we've got high levels of test coverage. And what we actually deliver at the end of it, not only have we been able to generate tests more quickly, but we've got much higher test coverage and also can more smartly, using the kind of AI within the tool and then some of the other kinds of pipeline tools, actually deliver to choose the right tasks, and actually doing a risk based testing approach. So that's been a great launch this year, but just the start of many kinds of things that we're doing >>Well, what I hear in that, Glynn is a lot of positives that have come out of a very challenging situation. Talk to me about it. And I liked that perspective. This is a very challenging time for everybody in the world, but it sounds like from a collaboration perspective you're right, we talk about that a lot critical with devops. But those challenges there, you guys were able to overcome those pretty quickly. What other challenges did you face and figure out quickly enough to be able to pivot so fast? >>I mean, you talked about culture. You know, BT is like most companies  So it's very siloed. You know we're still trying to work to become closer as a company. So I think there's a lot of challenges around how would you integrate with other tools? How would you integrate with the various different technologies. And BT, we have 58 different IT stacks. That's not systems, that's stacks, all of those stacks can have hundreds of systems. And we're trying to, we've got a drive at the moment, a simplified program where we're trying to you know, reduce that number to 14 stacks. And even then there'll be complexity behind the scenes that we will be challenged more and more as we go forward. How do we actually highlight that to our users? And as an it organization, how do we make ourselves leaner, so that even when we've still got some of that legacy, and we'll never fully get rid of it and that's the kind of trade off that we have to make, how do we actually deal with that and hide that from our users and drive those programs, so we can, as I say, accelerate change,  reduce that kind of waste and that kind of legacy costs out of our business. You know, the other thing as well, I'm sure telecoms is probably no different to insurance or finance. When you take the number of products that we do, and then you combine them, the permutations are tens and hundreds of thousands of products. So we, as a business are trying to simplify, we are trying to do that in an agile way. >>And haven't tried to do agile in the proper way and really actually work at pace, really deliver value. So I think what we're looking more and more at the moment is actually  more value focused. Before we used to deliver changes sometimes into production. Someone had a great idea, or it was a great idea nine months ago or 12 months ago, but actually then we ended up deploying it and then we'd look at the users, the usage of that product or that application or whatever it is, and it's not being used for six months. So we haven't got, you know, the cost of the last 12 months. We certainly haven't gotten room for that kind of waste and, you know, for not really understanding the value of changes that we are doing. So I think that's the most important thing of the moment, it's really taking that waste out. You know, there's lots of focus on things like flow management, what bits of our process are actually taking too long. And we've started on that journey, but we've got a hell of a long way to go. But that involves looking at every aspect of the software delivery cycle. >> Going from, what 58 IT stacks down to 14 or whatever it's going to be, simplifying sounds magical to everybody. It's a big challenge. What are some of the core technology capabilities that you see really as kind of essential for enabling that with this new way that you're working? >>Yeah. I mean, I think we were started on a continuous testing journey, and I think that's just the start. I mean as I say, looking at every aspect of, you know, from a QA point of view is every aspect of what we do. And it's also looking at, you know, we've started to branch into more like AI, uh, AI ops and, you know, really the full life cycle. Um, and you know, that's just a stepping stone to, you know, I think autonomics is the way forward, right. You know, all of this kind of stuff that happens, um, you know, monitoring, uh, you know, watching the systems what's happening in production, how do we feed that back? How'd you get to a point where actually we think about change and then suddenly it's in production safely, or if it's not going to safety, it's automatically backing out. So, you know, it's a very, very long journey, but if we want to, you know, in a world where the pace is in ever-increasing and the demands for the team, and, you know, with the pressures on, at the moment where we're being asked to do things, uh, you know, more efficiently and as lean as possible, we need to be thinking about every part of the process and how we put the kind of stepping stones in place to lead us to a more automated kind of, um, you know, um, the future. >>Do you feel that that planned outcomes are starting to align with what's delivered, given this massive shift that you're experiencing? >>I think it's starting to, and I think, you know, as I say, as we look at more of a value based approach, um, and, um, you know, as I say, print, this was a kind of flow management. I think that that will become ever, uh, ever more important. So, um, I think it starting to people certainly realize that, you know, teams need to work together, you know, the kind of the cousin between business and it, especially as we go to more kind of SAS based solutions, low code solutions, you know, there's not such a gap anymore, actually, some of our business partners that expense to be much more tech savvy. Um, so I think, you know, this is what we have to kind of appreciate what is its role, how do we give the capabilities, um, become more of a centers of excellence rather than actually doing mounds amounts of work. And for me, and from a testing point of view, you know, mounds and mounds of testing, actually, how do we automate that? How do we actually generate that instead of, um, create it? I think that's the kind of challenge going forward. >>What are some, as we look forward, what are some of the things that you would like to see implemented or deployed in the next, say six to 12 months as we hopefully round a corner with this pandemic? >>Yeah, I think, um, you know, certainly for, for where we are as a company from a QA perspective, we are, um, you let's start in bits that we do well, you know, we've started creating, um, continuous delivery and DevOps pipelines. Um, there's still manual aspects of that. So, you know, certainly for me, I I've challenged my team with saying how do we do an automated journey? So if I put a requirement in JIRA or rally or wherever it is and why then click a button and, you know, with either zero touch for one such, then put that into production and have confidence that, that has been done safely and that it works and what happens if it doesn't work. So, you know, that's, that's the next, um, the next few months, that's what our concentration, um, is, is about. But it's also about decision-making, you know, how do you actually understand those value judgments? >>And I think there's lots of the things dev ops, AI ops, kind of that always ask aspects of business operations. I think it's about having the information in one place to make those kinds of decisions. How does it all try and tie it together? As I say, even still with kind of dev ops, we've still got elements within my company where we've got lots of different organizations doing some, doing similar kinds of things, but they're all kind of working in silos. So I think having AI ops as it comes more and more to the fore as we go to cloud, and that's what we need to, you know, we're still very early on in our cloud journey, you know, so we need to make sure the technologies work with cloud as well as you can have, um, legacy systems, but it's about bringing that all together and having a full, visible pipeline, um, that everybody can see and make decisions. >>You said the word confidence, which jumped out at me right away, because absolutely you've got to have be able to have confidence in what your team is delivering and how it's impacting the business and those customers. Last question then for you is how would you advise your peers in a similar situation to leverage technology automation, for example, dev ops, to be able to gain the confidence that they're making the right decisions for their business? >>I think the, the, the, the, the approach that we've taken actually is not started with technology. Um, we've actually taken a human centered design, uh, as a core principle of what we do, um, within the it part of BT. So by using human centered design, that means we talk to our customers, we understand their pain points, we map out their current processes. Um, and then when we mapped out what this process does, it also understand their aspirations as well, you know? Um, and where do they want to be in six months? You know, do they want it to be, um, more agile and, you know, or do they want to, you know, is, is this a part of their business that they want to do one better? We actually then looked at why that's not running well, and then see what, what solutions are out there. >>We've been lucky that, you know, with our partnership, with Broadcom within the payer line, lots of the tools and the PLA have directly answered some of the business's problems. But I think by having those conversations and actually engaging with the business, um, you know, especially if the business hold the purse strings, which in, in, uh, you know, in some companies include not as they do there is that kind of, you know, almost by understanding their, their pain points and then starting, this is how we can solve your problem. Um, is we've, we've tended to be much more successful than trying to impose something and say, well, here's the technology that they don't quite understand. It doesn't really understand how it kind of resonates with their problems. So I think that's the heart of it. It's really about, you know, getting, looking at the data, looking at the processes, looking at where the kind of waste is. >>And then actually then looking at the right solutions. Then, as I say, continuous testing is massive for us. We've also got a good relationship with Apple towards looking at visual AI. And actually there's a common theme through that. And I mean, AI is becoming more and more prevalent. And I know, you know, sometimes what is AI and people have kind of this semantics of, is it true AI or not, but it's certainly, you know, AI machine learning is becoming more and more prevalent in the way that we work. And it's allowing us to be much more effective, be quicker in what we do and be more accurate. And, you know, whether it's finding defects running the right tests or, um, you know, being able to anticipate problems before they're happening in a production environment. >>Well, thank you so much for giving us this sort of insight outlook at dev ops sharing the successes that you're having, taking those challenges, converting them to opportunities and forgiving folks who might be in your shoes, or maybe slightly behind advice enter. They appreciate it. We appreciate your time. >>Well, it's been an absolute pleasure, really. Thank you for inviting me. I have a extremely enjoyed it. So thank you ever so much. >>Excellent. Me too. I've learned a lot for Glenn Martin. I'm Lisa Martin. You're watching the cube >>Driving revenue today means getting better, more valuable software features into the hands of your customers. If you don't do it quickly, your competitors as well, but going faster without quality creates risks that can damage your brand destroy customer loyalty and cost millions to fix dev ops from Broadcom is a complete solution for balancing speed and risk, allowing you to accelerate the flow of value while minimizing the risk and severity of critical issues with Broadcom quality becomes integrated across the entire DevOps pipeline from planning to production, actionable insights, including our unique readiness score, provide a three 60 degree view of software quality giving you visibility into potential issues before they become disasters. Dev ops leaders can manage these risks with tools like Canary deployments tested on a small subset of users, or immediately roll back to limit the impact of defects for subsequent cycles. Dev ops from Broadcom makes innovation improvement easier with integrated planning and continuous testing tools that accelerate the flow of value product requirements are used to automatically generate tests to ensure complete quality coverage and tests are easily updated. >>As requirements change developers can perform unit testing without ever leaving their preferred environment, improving efficiency and productivity for the ultimate in shift left testing the platform also integrates virtual services and test data on demand. Eliminating two common roadblocks to fast and complete continuous testing. When software is ready for the CIC CD pipeline, only DevOps from Broadcom uses AI to prioritize the most critical and relevant tests dramatically improving feedback speed with no decrease in quality. This release is ready to go wherever you are in your DevOps journey. Broadcom helps maximize innovation velocity while managing risk. So you can deploy ideas into production faster and release with more confidence from around the globe. It's the queue with digital coverage of dev ops virtual forum brought to you by Broadcom. >>Hi guys. Welcome back. So we have discussed the current state and the near future state of dev ops and how it's going to evolve from three unique perspectives. In this last segment, we're going to open up the floor and see if we can come to a shared understanding of where dev ops needs to go in order to be successful next year. So our guests today are, you've seen them all before Jeffrey Hammond is here. The VP and principal analyst serving CIO is at Forester. We've also Serge Lucio, the GM of Broadcom's enterprise software division and Glenn Martin, the head of QA transformation at BT guys. Welcome back. Great to have you all three together >>To be here. >>All right. So we're very, we're all very socially distanced as we've talked about before. Great to have this conversation. So let's, let's start with one of the topics that we kicked off the forum with Jeff. We're going to start with you spiritual co-location that's a really interesting topic that we've we've uncovered, but how much of the challenge is truly cultural and what can we solve through technology? Jeff, we'll start with you then search then Glen Jeff, take it away. >>Yeah, I think fundamentally you can have all the technology in the world and if you don't make the right investments in the cultural practices in your development organization, you still won't be effective. Um, almost 10 years ago, I wrote a piece, um, where I did a bunch of research around what made high-performance teams, software delivery teams, high performance. And one of the things that came out as part of that was that these teams have a high level of autonomy. And that's one of the things that you see coming out of the agile manifesto. Let's take that to today where developers are on their own in their own offices. If you've got teams where the team itself had a high level of autonomy, um, and they know how to work, they can make decisions. They can move forward. They're not waiting for management to tell them what to do. >>And so what we have seen is that organizations that embraced autonomy, uh, and got their teams in the right place and their teams had the information that they needed to make the right decisions have actually been able to operate pretty well, even as they've been remote. And it's turned out to be things like, well, how do we actually push the software that we've created into production that would become the challenge is not, are we writing the right software? And that's why I think the term spiritual co-location is so important because even though we may be physically distant, we're on the same plane, we're connected from a, from, from a, a shared purpose. Um, you know, surgeon, I worked together a long, long time ago. So it's been what almost 15, 16 years since we were at the same place. And yet I would say there's probably still a certain level of spiritual co-location between us, uh, because of the shared purposes that we've had in the past and what we've seen in the industry. And that's a really powerful tool, uh, to build on. So what do tools play as part of that, to the extent that tools make information available, to build shared purpose on to the extent that they enable communication so that we can build that spiritual co-location to the extent that they reinforce the culture that we want to put in place, they can be incredibly valuable, especially when, when we don't have the luxury of physical locate physical co-location. Okay. That makes sense. >>It does. I shouldn't have introduced us. This last segment is we're all spiritually co-located or it's a surge, clearly you're still spiritually co located with jump. Talk to me about what your thoughts are about spiritual of co-location the cultural impact and how technology can move it forward. >>Yeah. So I think, well, I'm going to sound very similar to Jeff in that respect. I think, you know, it starts with kind of a shared purpose and the other understanding, Oh, individuals teams, uh, contributed to kind of a business outcome, what is our shared goal or shared vision? What's what is it we're trying to achieve collectively and keeping it kind of aligned to that? Um, and so, so it's really starts with that now, now the big challenge, always these over the last 20 years, especially in large organization, there's been specialization of roles and functions. And so we, we all that started to basically measure which we do, uh, on a daily basis using metrics, which oftentimes are completely disconnected from kind of a business outcome or purpose. We, we kind of reverted back to, okay, what is my database all the time? What is my cycle time? >>Right. And, and I think, you know, which we can do or where we really should be focused as an industry is to start to basically provide a lens or these different stakeholders to look at what they're doing in the context of kind of these business outcomes. So, um, you know, probably one of my, um, favorites experience was to actually weakness at one of a large financial institution. Um, you know, Tuesday Golder's unquote development and operations staring at the same data, right. Which was related to, you know, in calming changes, um, test execution results, you know, Coverity coverage, um, official liabilities and all the all ran. It could have a direction level links. And that's when you start to put these things in context and represent that to you in a way that these different stakeholders can, can look at from their different lens. And, uh, and it can start to basically communicate and, and understand have they joined our company to, uh, to, to that kind of common view or objective. >>And Glen, we talked a lot about transformation with you last time. What are your thoughts on spiritual colocation and the cultural part, the technology impact? >>Yeah, I mean, I agree with Jeffrey that, you know, um, the people and culture, the most important thing, actually, that's why it's really important when you're transforming to have partners who have the same vision as you, um, who, who you can work with, have the same end goal in mind. And w I've certainly found that with our, um, you know, continuing relationship with Broadcom, what it also does though, is although, you know, tools can accelerate what you're doing and can join consistency. You know, we've seen within simplify, which is BTS flagship transformation program, where we're trying to, as it can, it says simplify the number of systems stacks that we have, the number of products that we have actually at the moment, we've got different value streams within that program who have got organizational silos. We were trying to rewrite, rewrite the wheel, um, who are still doing things manually. >>So in order to try and bring that consistency, we need the right tools that actually are at an enterprise grade, which can be flexible to work with in BT, which is such a complex and very dev, uh, different environments, depending on what area of BT you're in, whether it's a consumer, whether it's a mobile area, whether it's large global or government organizations, you know, we found that we need tools that can, um, drive that consistency, but also flex to Greenfield brownfield kind of technologies as well. So it's really important that as I say, for a number of different aspects, that you have the right partner, um, to drive the right culture, I've got the same vision, but also who have the tool sets to help you accelerate. They can't do that on their own, but they can help accelerate what it is you're trying to do in it. >>And a really good example of that is we're trying to shift left, which is probably a, quite a bit of a buzz phrase in their kind of testing world at the moment. But, you know, I could talk about things like continuous delivery direct to when a ball comes tools and it has many different features to it, but very simply on its own, it allows us to give the visibility of what the teams are doing. And once we have that visibility, then we can talk to the teams, um, around, you know, could they be doing better component testing? Could they be using some virtualized services here or there? And that's not even the main purpose of continuous delivery director, but it's just a reason that tools themselves can just give greater visibility of have much more intuitive and insightful conversations with other teams and reduce those organizational silos. >>Thanks, Ben. So we'd kind of sum it up, autonomy collaboration tools that facilitate that. So let's talk now about metrics from your perspectives. What are the metrics that matter? Jeff, >>I'm going to go right back to what Glenn said about data that provides visibility that enables us to, to make decisions, um, with shared purpose. And so business value has to be one of the first things that we look at. Um, how do we assess whether we have built something that is valuable, you know, that could be sales revenue, it could be net promoter score. Uh, if you're not selling what you've built, it could even be what the level of reuse is within your organization or other teams picking up the services, uh, that you've created. Um, one of the things that I've begun to see organizations do is to align value streams with customer journeys and then to align teams with those value streams. So that's one of the ways that you get to a shared purpose, cause we're all trying to deliver around that customer journey, the value with it. >>And we're all measured on that. Um, there are flow metrics which are really important. How long does it take us to get a new feature out from the time that we conceive it to the time that we can run our first experiments with it? There are quality metrics, um, you know, some of the classics or maybe things like defect, density, or meantime to response. Um, one of my favorites came from a, um, a company called ultimate software where they looked at the ratio of defects found in production to defects found in pre production and their developers were in fact measured on that ratio. It told them that guess what quality is your job to not just the test, uh, departments, a group, the fourth level that I think is really important, uh, in, in the current, uh, situation that we're in is the level of engagement in your development organization. >>We used to joke that we measured this with the parking lot metric helpful was the parking lot at nine. And how full was it at five o'clock. I can't do that anymore since we're not physically co-located, but what you can do is you can look at how folks are delivering. You can look at your metrics in your SCM environment. You can look at, uh, the relative rates of churn. Uh, you can look at things like, well, are our developers delivering, uh, during longer periods earlier in the morning, later in the evening, are they delivering, uh, you know, on the weekends as well? Are those signs that we might be heading toward a burnout because folks are still running at sprint levels instead of marathon levels. Uh, so all of those in combination, uh, business value, uh, flow engagement in quality, I think form the backbone of any sort of, of metrics, uh, a program. >>The second thing that I think you need to look at is what are we going to do with the data and the philosophy behind the data is critical. Um, unfortunately I see organizations where they weaponize the data and that's completely the wrong way to look at it. What you need to do is you need to say, you need to say, how is this data helping us to identify the blockers? The things that aren't allowing us to provide the right context for people to do the right thing. And then what do we do to remove those blockers, uh, to make sure that we're giving these autonomous teams the context that they need to do their job, uh, in a way that creates the most value for the customers. >>Great advice stuff, Glenn, over to your metrics that matter to you that really make a big impact. And, and, and also how do you measure quality kind of following onto the advice that Jeff provided? >>That's some great advice. Actually, he talks about value. He talks about flow. Both of those things are very much on my mind at the moment. Um, but there was this, I listened to a speaker, uh, called me Kirsten a couple of months ago. It taught very much around how important flow management is and removing, you know, and using that to remove waste, to understand in terms of, you know, making software changes, um, what is it that's causing us to do it longer than we need to. So where are those areas where it takes long? So I think that's a very important thing for us. It's even more basic than that at the moment, we're on a journey from moving from kind of a waterfall to agile. Um, and the problem with moving from waterfall to agile is with waterfall, the, the business had a kind of comfort that, you know, everything was tested together and therefore it's safer. >>Um, and with agile, there's that kind of, you know, how do we make sure that, you know, if we're doing things quick and we're getting stuff out the door that we give that confidence, um, that that's ready to go, or if there's a risk that we're able to truly articulate what that risk is. So there's a bit about release confidence, um, and some of the metrics around that and how, how healthy those releases are, and actually saying, you know, we spend a lot of money, um, um, an investment setting up our teams, training our teams, are we actually seeing them deliver more quickly and are we actually seeing them deliver more value quickly? So yeah, those are the two main things for me at the moment, but I think it's also about, you know, generally bringing it all together, the dev ops, you know, we've got the kind of value ops AI ops, how do we actually bring that together to so we can make quick decisions and making sure that we are, um, delivering the biggest bang for our buck, absolutely biggest bang for the buck, surge, your thoughts. >>Yeah. So I think we all agree, right? It starts with business metrics, flow metrics. Um, these are kind of the most important metrics. And ultimately, I mean, one of the things that's very common across a highly functional teams is engagements, right? When, when you see a team that's highly functioning, that's agile, that practices DevOps every day, they are highly engaged. Um, that that's, that's definitely true. Now the, you know, back to, I think, uh, Jeff's point on weaponization of metrics. One of the key challenges we see is that, um, organizations traditionally have been kind of, uh, you know, setting up benchmarks, right? So what is a good cycle time? What is a good lead time? What is a good meantime to repair? The, the problem is that this is very contextual, right? It varies. It's going to vary quite a bit, depending on the nature of application and system. >>And so one of the things that we really need to evolve, um, as an industry is to understand that it's not so much about those flow metrics is about our, these four metrics ultimately contribute to the business metric to the business outcome. So that's one thing. The second aspect, I think that's oftentimes misunderstood is that, you know, when you have a bad cycle time or, or, or what you perceive as being a buy cycle time or better quality, the problem is oftentimes like all, do you go and explore why, right. What is the root cause of this? And I think one of the key challenges is that we tend to focus a lot of time on metrics and not on the eye type patterns, which are pretty common across the industry. Um, you know, if you look at, for instance, things like lead time, for instance, it's very common that, uh, organizational boundaries are going to be a key contributor to badly time. >>And so I think that there is, you know, the only the metrics there is, I think a lot of work that we need to do in terms of classifying, descend type patterns, um, you know, back to you, Jeff, I think you're one of the cool offers of waterscrumfall as a, as, as a key pattern, the industry or anti-spatter. Um, but waterscrumfall right is a key one, right? And you will detect that through kind of a defect arrival rates. That's where that looks like an S-curve. And so I think it's beyond kind of the, the metrics is what do you do with those metrics? >>Right? I'll tell you a search. One of the things that is really interesting to me in that space is I think those of us had been in industry for a long time. We know the anti-patterns cause we've seen them in our career maybe in multiple times. And one of the things that I think you could see tooling do is perhaps provide some notification of anti-patterns based on the telemetry that comes in. I think it would be a really interesting place to apply, uh, machine learning and reinforcement learning techniques. Um, so hopefully something that we'd see in the future with dev ops tools, because, you know, as a manager that, that, you know, may be only a 10 year veteran or 15 year veteran, you may be seeing these anti-patterns for the first time. And it would sure be nice to know what to do, uh, when they start to pop up, >>That would right. Insight, always helpful. All right, guys, I would like to get your final thoughts on this. The one thing that you believe our audience really needs to be on the lookout for and to put on our agendas for the next 12 months, Jeff will go back to you. Okay. >>I would say look for the opportunities that this disruption presents. And there are a couple that I see, first of all, uh, as we shift to remote central working, uh, we're unlocking new pools of talent, uh, we're, it's possible to implement, uh, more geographic diversity. So, so look to that as part of your strategy. Number two, look for new types of tools. We've seen a lot of interest in usage of low-code tools to very quickly develop applications. That's potentially part of a mainstream strategy as we go into 2021. Finally, make sure that you embrace this idea that you are supporting creative workers that agile and dev ops are the peanut butter and chocolate to support creative, uh, workers with algorithmic capabilities, >>Peanut butter and chocolate Glen, where do we go from there? What are, what's the one silver bullet that you think folks to be on the lookout for now? I, I certainly agree that, um, low, low code is, uh, next year. We'll see much more low code we'd already started going, moving towards a more of a SAS based world, but low code also. Um, I think as well for me, um, we've still got one foot in the kind of cow camp. Um, you know, we'll be fully trying to explore what that means going into the next year and exploiting the capabilities of cloud. But I think the last, um, the last thing for me is how do you really instill quality throughout the kind of, um, the, the life cycle, um, where, when I heard the word scrum fall, it kind of made me shut it because I know that's a problem. That's where we're at with some of our things at the moment we need to get beyond that. We need >>To be releasing, um, changes more frequently into production and actually being a bit more brave and having the confidence to actually do more testing in production and go straight to production itself. So expect to see much more of that next year. Um, yeah. Thank you. I haven't got any food analogies. Unfortunately we all need some peanut butter and chocolate. All right. It starts to take us home. That's what's that nugget you think everyone needs to have on their agendas? >>That's interesting. Right. So a couple of days ago we had kind of a latest state of the DevOps report, right? And if you read through the report, it's all about the lost city, but it's all about sweet. We still are receiving DevOps as being all about speed. And so to me, the key advice is in order to create kind of a spiritual collocation in order to foster engagement, we have to go back to what is it we're trying to do collectively. We have to go back to tie everything to the business outcome. And so for me, it's absolutely imperative for organizations to start to plot their value streams, to understand how they're delivering value into aligning everything they do from a metrics to deliver it, to flow to those metrics. And only with that, I think, are we going to be able to actually start to really start to align kind of all these roles across the organizations and drive, not just speed, but business outcomes, >>All about business outcomes. I think you guys, the three of you could write a book together. So I'll give you that as food for thought. Thank you all so much for joining me today and our guests. I think this was an incredibly valuable fruitful conversation, and we appreciate all of you taking the time to spiritually co-located with us today, guys. Thank you. Thank you, Lisa. Thank you. Thank you for Jeff Hammond serves Lucio and Glen Martin. I'm Lisa Martin. Thank you for watching the broad cops Broadcom dev ops virtual forum.

(upbeat music) >> Facilitator: From theCUBE studios in Palo Alto in Boston, connecting with other leaders all around the world. This is a CUBE conversation. >> Java is the world's most popular programming language. And it remains the leading application development platform. But what's the status of Java? What a customers doing? And very importantly, what is Oracle's and the community strategy with respect to Java? Welcome everybody to this Java power panel on theCUBE. I'm your host, Dave Vellante. Manish Gupta here, he's the Vice President of Global Marketing at Java for Oracle, Donald Smith is also on the panel, and he's the Senior Director of Product Management at Oracle and we're joined by David Floyd who is a CTO of Wikibon Research and has done a number of research activities on this very topic. Gentlemen, welcome to theCUBE, great to see you. >> Thank you. >> Thank you. >> Manish, I want to start with you. Can you help us understand really what dig into Oracle strategy with respect to Java. The technology, the licensing, the support. How has that evolved over time? Take us through that. >> Dave, with 51 billion JVMs deployed worldwide, Java has truly cemented its position as the language of innovation and the technology world. There's no question about that. In fact, I like to say it's really the language of empowerment. Given the the impact it has had numerous applications ranging from the Mars Rover to genomics and everything in between. As Oracle acquired sign over 10 years ago, it's really kept it front of mind, two aspects of what we want to do with the technology and the platform. The first one was to ensure there was broad accessibility to the technology and the platform for anybody that wanted to benefit from it. And the second one was to ensure that the ecosystem remained vibrant and thriving throughout. I managed to do both. And underpinning these two objectives were really three pillars of our strategy. The first one was around trust, ensuring that openness and transparency of the technology was as was before continued to be the case going forward. The second element of that within the trust pillar was to ensure that as enterprises invested in the technology that investment was protected, it was not, you invest and you lose over a period of time in a backward compatibility, interoperability, certifications, were all foundational to the platform itself to the features, to the innovation moving forward. And more recently as we have rethought to the support, the licensing and the overall structure of the pricing that we have ensured that ultimately the trust comes along in those dimensions as well. So the launch of the Java subscription came along with, pay as you go model, it's a transparent pricing structure and discuss structure published on the website. So you can go and see what it would cost for the desktop on servers or cloud deployment. So those were the things that made kind of the first pillar happen. The second one was Dunno innovation. Over the last 25 years, Java has stood the test of time. It has delivered the needs of today while preparing for the future. And that remains the case. It is not something that has sort of focused on the fat of the day and the hot thing for the day, but really more important that it is prepared to deal with the mission critical, massive scale deployments that can run for years, for decades, in some cases. And keeping that in mind, Oracle has continued to put more and more technology into the open source world with every release that comes out, you can see 80 plus percent of the contributions come from Oracle. So that's the second pillar around innovation. And the third piece of the strategy has been around predictability. Ensuring that Java, the technology and platform perform as advertised, and that goes into the feature releases, it goes into the release process, it goes into the fact that you were broadly within the open JDK environment for developing and executing the roadmap. From a CIO standpoint, it's important to know that the technology used to develop your applications has talent around. And your, if you're going to develop something like Java, you'll find the right Java engineers to do the job. That is not a question, right? And so that's part of predictability. And finally, again with the change in the six months release cadence that came about three years ago, with the release of Java 10, we've really made sure that it's not, no, a bunch of things come about. You don't know when they're going to be released, but you know, like clockwork, you'll have a new Java list every six months. And that's been the case every March and September, since Java 10, you've had a new release of Java with certain features that come up and we just launched Java 15. So trust innovation predictability, have really been the three pillars on which we've executed the strategy for Java. >> Excellent, thank you for that intro, and we're going to get into it now. I'm glad you mentioned the sun acquisition. I said at the time that Java was the linchpin of that acquisition, many people, of course, we looked at the integration piece with the hardware, but it was really Java and the capabilities that it brings. And of course, a lot of Oracle software written in Java and not the least of which is a fusion. But now let's get into the components of this. And I want to talk a little bit about the methodology of this and going to call on you David Floyer. But essentially my understanding is that Wikibon went through and David, you led this, you did a technical deep dive, which you always do, did a number of in depth interviews with Java customers. And then of course you also did a web survey and then you built from that data and economic model. So you can try to understand the sort of dimensions of the financials if you will. So what were your key findings there? >> So the key findings were that Java was in a good state that people were happy with the Java. The second key finding is that the business case itself for using the Oracle services, the subscription services was good. It didn't mean to say that that wasn't for every company, the right way to do it, but there was a very good return on that. And the third area was that there was a degree of confidence that the new way of doing things, the six-month cycle, as opposed to the three-year cycle was overall a benefit to the rate of change, the ability for them to introduce new features quickly. >> Okay, well, I mean, you know, and I read that research. And to me my takeaways where I saw the continued relevance of Java, which is kind of goes without saying, but a lot of times it gets lost in the headlines. That subscription piece is key. We're going to get into some of the economics as to how that affects customers and it saves you money. And the other piece was the roadmap becoming more transparent. And I don't want to dig into that a little bit, but before we do, let's get into that innovation component Manish, mentioned that several times, but Don, I want to go to you guys. We have a slide on the various components of the innovation. If you would bring this up and Don I wonder if you could talk to this and give us some examples if you would. >> Yeah, sure. So we were the number one development platform for the last 25 years. We want to be the number one development platform for the next 25 years. And in order to do that, we have to be constantly innovating and constantly innovating not only the business side in terms of the subscription and the support offerings and commercial features like Manish was talking about, but also the platform in general. And so the way we like to talk about innovation as we break it down by these pillars that you can see on the slide. And so the first pillar is continuous improvements to the language. So this is watching developers trying to write the same piece of code over and over again, and us asking, can we make you more efficient? Can we give you more language features that reduce the amount of boilerplate that you have to write? The second pillar is a project that we just announced a few months ago called Leyden. And the idea with Leyden is addressing the longterm pinpoints of Java slow startup time and time to peak performance. So if you go back 10 years ago, everybody knows about Java as an enterprise platform, Java EE application servers. They all had the notion of being very long lived. And so Java at that time would be optimized towards long lived applications, startup, and performance. Where if it took a little while to get there, it didn't matter as long as when it got there, it was super fast. And so we're trying to get that peak performance faster in the world of microservices. In a similar vein with project loom, we're looking at making concurrency simple again, looking at how developers are doing more reactive style programming and realizing that the threading model needs to be rethought from the ground up, that project is looking really, really good. Then we have project Panama. Project Panama is all about making it easier to connect Java with native libraries. Valhalla is all about improving, there's a couple of benefits, but it's all about improving memory density and being able to access and iterate and operate over primitive data types at super fast speeds by better optimizing how that information is stored in memory. And then the other pillar of the final pillar that we have been working on from an innovation perspective is ZGC. We introduced a new garbage collector technology a few years ago, G1GCE a generational garbage collector with the eye towards making garbage collection in Java pause lists. So if you, again, if you go back in time and look at the history of Java, memory management is awesome, but there's always that cost and risk of a garbage collection cycle, taking a bit of time away from a critical application. And ZGC is all about getting rid of that. So lots of innovation, lots of different pillars going on right now. >> Awesome, I'm impressed. There's something after Valhalla. I thought that was Nirvana. (laughing) But now, and these are all open source projects, right? And you guys obviously provide committers, there are other people in the open source world who provide that, is that correct Don? >> Yeah, that's correct. We have about 80% of the contributions in open JDK. We are the stewards of open JDK and lead the project. Most of the pillars I talked about here are you know Oracle folks working on that. >> Awesome. Okay, let's get into some of the data. David, I want to come back to you and talk about some of the survey results guys, if you bring up that next slide. Why David, why do people upgrade? What are the drivers? It's really talks to the large companies and what's different from the small company or mid-size companies? What are the takeaways here? >> David: Well, so this is interesting, and as you might expect, large enterprises, have very concerned about application stability. Whereas midsize or enterprises are much more concerned about the performance, making sure that the performance is good. They are both concerned about reliable performance and security, but it's interesting that from a regulation point of view, mid-size companies really want to make sure that they are obeying the regulations, that they are meeting those. Whereas larger organizations usually have their own security and regulation functions looking very hard at these things. So that looking less to the platform to provide those than their own people. >> Yeah, I think you're right. I think the midsize organizations don't have as many people running around taking care of security and it's harder for them to keep up with the edicts of the organization. So they want to stay more current. Don, I wonder if you can add anything to this data from an innovation standpoint. >> Yeah, well, and from a product management standpoint, and what we see here is when you look at just going from fortune 500 to global 2000, you see things that are important to one or less so than the other. You can extrapolate that all the way down to a small company or a startup. And that's why providing the most flexibility in terms of an offering to allow people to decide what, when, where, and how they would be going to upgrade their software so they can do it when they want, and on their own terms. You can see that that becomes really important. And also making sure that we're providing innovation in a broad way so that it'll appeal both to the enterprise and again extrapolating that forward down to even very small startups. >> You know, David, the other thing that struck me in the data, if we bring up that other piece is the upgrade strategy, and there was a stark difference between large enterprises and midsize organizations. Talk to this data, if you would. >> Yes, this is again, a pretty stark difference between them. When you're looking at large enterprises, they really wants stability and they don't want to upgrade so often. Whereas mid-size enterprises, are much more willing to both upgrade on a regular cadence and really have a much more up-to-date, or have always have the latest software. They're driving smaller applications, but they're much more agile about their approach to it. Again, emphasizing what Don was saying about the smaller enterprises wanting a different strategy and a different way of doing things than large enterprises. >> So Manish this says to me that you got it right from a strategy standpoint. I mean, any color you can add here. >> Yeah, it's very intuitive that whether you're a large organization, a mid-sized enterprise or a small business, right? You face competitive pressures, your dynamics are unique. What you're able to do with the resources, what you desire to do at the pace that is appropriate for your environment, are really unique to you, and to try to force one model across any one size or across any set of dynamics is just not appropriate. So we've always felt that giving the enterprises and the organization, the ability to move at the pace of their business is the right approach. And so when we designed the Oracle Java SE subscription, we truly have that front and center in our thought process. And that structure seems to be working well. >> David, what I like about the way you do research is you actually build an economic model. A lot of these business value projects. I know this well, having been in the business a long time, they'll go out to ask the customer what they got, and then the customer said, "Well, I got a 111% ROI, and boom, that's what it is. You actually construct an economic model, you bring in rules of thumb, it allows you to do what ifs you can test that model and calibrate it against the real world. So I commend you on that. You've done a lot of hard work there, but bottom line at forests, I mean, let's bring up the economics. I mean, that's what people ultimately want to know. Does this save me money? What's the bottom line here? >> Yeah. Yes, that's a very important question. And the way we go about it is to ask the questions so that we can extract from those questions, how much effort it took, for example, to upgrade things, how much effort it took for important applications and not so important applications. So we have a very detailed model driven by the survey itself and in the back of the research, I'm a great believer that you should be able to follow exactly what the research said, what the survey said and how it was applied to the model. So, and what were you focused on was, what was the return of using the Java subscription service or taking an upgrade every six months? Those were the two ways that we looked at it. And for large enterprises, the four-year costs for the enterprise was $11 million, but for taking the additional subscription service, and this was well well covered, the payback is within a year, well covered by the lower costs of managing in a lot of systems and environment. And we found a very similar result on those midsize services. There, it was 3 million, and again, they got that back the year in terms of payback. So, but that's one alternative. There is another alternative that may be worthwhile the extra money if you really want to be up-to-date and or if you want to drive a much more aggressive strategy for your organization. >> So these are huge numbers. I mean, he's talking about 30% savings on average for large and mid-sized enterprises in the percentage terms, but the absolute dollars are actually enormous. So, you know, large companies here, we're talking about $20 billion enterprises with 500 or more Java applications. And mid-size is, you're talking about a couple, two, $3 billion companies. Manish, what are you saying in the customer base in terms of the economics? >> Yeah, you know anytime an organization is looking at an offering and a solution, they want to make sure just giving them the value. And we all know that the priorities of businesses have, they want to focus on that. Managing the Java estate is important, but is it the thing where they want to invest the dollars? And if they are investing the dollars, are they getting the return? We find that if you can give the enterprises an ability where they can see the return, the cost is right for them. And if you can mirror that and you can map it also with reduce risk, then you put the right formula. And with the subscription, they're able to not only see the cost savings that the model indicates clearly, but they're also able to reduce the risk in terms of security protection and other things. So it's a really, really good combination for the enterprises. >> Well, thank you, I wonder Manish, if you could bring us home here and just kind of summarize from your thoughts, everything you've heard today, what are the key takeaways? >> You know Java has been around for 25 years, and we certainly believe it's really positioned well for what's required today. And perhaps more importantly, what is needed for the next decade and for the next 25 years. Having now served thousands of customers with the Java subscription, it's clear that it is meeting the needs of fortune 10 organizations all the way down to a 5% development house, for example. What we're hearing from across the board is really Java has been the go to platform and it continues to be the go to platform for mission critical development and deployment. However, the complexity as the Java estate becomes large when you've got tens to hundreds, in some cases over a thousand applications running across the enterprise, that complexity can be daunting. And the Java subscription is really serving the needs in three ways. One, it's getting them the best of class support from Oracle, which is a steward of Java, the company that is generating over 80% of innovation with every single release. The second thing they're getting the business flexibility. So they can move at the pace that works for them. And therapies is as a business model as indicated that they're getting it at a lower cost while having your list. So the combination of these things is the reason why we're seeing very high renewal rates, why we're seeing thousands of organization take it over. And I want to wrap it up by saying one final thing, that you can count on Oracle to be the transparent, to be the right steward or both technology innovation, as well as to ensuring the support for the vast ecosystem whether it's libraries, frameworks, user groups, educational services and so on. So Java is here, has been here for the enterprise, large and small, and it's ready for the next generation as well. >> Great, thank you for that. Well, one more question. What's the call to action? If I'm a mid-sized company or a large company, I've made investments in Java, what, what should I do next? >> I would say, take a look at the Oracle subscription. It will reduce your rates. It'll save you a cost and it'll give you a lower risk parameter for your organization. >> Great, nice and crisp, I like it. If you like, if you guys don't object, I'm going to give you my summary. I've been taking notes this whole time and so, we've explored two options. Customers can do it yourself or go with the subscription on a regular cadence. It's very clear to me that that Java remains relevant as we set up top. It's the world's most popular programming language we know about all that. The ecosystem is really moving fast. Of course, with the stewardship of Oracle cloud microservices, the development of, of modern applications. I think that the directional changes that Manish you guys and, and Don and Oracle have made were really the right call. The research that David you did, shows that it's serving customers better. It lowers costs, it's cutting down risk particularly for the mid-sized companies that maybe are, or don't have the security infrastructure and the talent to go chase those problems. And I love the roadmap piece. The more transparent roadmap really is going to give the industry and the community much more confidence to invest and move forward. So guys, thanks very much for coming on this CUBE Java power panel. It was great to have you. >> Thank you. >> Thank you. >> Thank you. >> All right, I thank you for watching everybody. This is Dave Vellante, for theCUBE, and we'll see you next time. (soft music)

(upbeat music) >> Facilitator: From theCUBE studios in Palo Alto in Boston, connecting with other leaders all around the world. This is a CUBE conversation. >> Java is the world's most popular programming language. And it remains the leading application development platform. But what's the status of Java? What a customers doing? And very importantly, what is Oracle's and the community strategy with respect to Java? Welcome everybody to this Java power panel on theCUBE. I'm your host, Dave Vellante. Manish Gupta here, he's the Vice President of Global Marketing at Java for Oracle, Donald Smith is also on the panel, and he's the Senior Director of Product Management at Oracle and we're joined by David Floyd who is a CTO of Wikibon Research and has done a number of research activities on this very topic. Gentlemen, welcome to theCUBE, great to see you. >> Thank you. >> Thank you. >> Manish, I want to start with you. Can you help us understand really what dig into Oracle strategy with respect to Java. The technology, the licensing, the support. How has that evolved over time? Take us through that. >> Dave, with 51 billion JVMs deployed worldwide, Java has truly cemented its position as the language of innovation and the technology world. There's no question about that. In fact, I like to say it's really the language of empowerment. Given the the impact it has had numerous applications ranging from the Mars Rover to genomics and everything in between. As Oracle acquired sign over 10 years ago, it's really kept it front of mind, two aspects of what we want to do with the technology and the platform. The first one was to ensure there was broad accessibility to the technology and the platform for anybody that wanted to benefit from it. And the second one was to ensure that the ecosystem remained vibrant and thriving throughout. I managed to do both. And underpinning these two objectives were really three pillars of our strategy. The first one was around trust, ensuring that openness and transparency of the technology was as was before continued to be the case going forward. The second element of that within the trust pillar was to ensure that as enterprises invested in the technology that investment was protected, it was not, you invest and you lose over a period of time in a backward compatibility, interoperability, certifications, were all foundational to the platform itself to the features, to the innovation moving forward. And more recently as we have rethought to the support, the licensing and the overall structure of the pricing that we have ensured that ultimately the trust comes along in those dimensions as well. So the launch of the Java subscription came along with, pay as you go model, it's a transparent pricing structure and discuss structure published on the website. So you can go and see what it would cost for the desktop on servers or cloud deployment. So those were the things that made kind of the first pillar happen. The second one was Dunno innovation. Over the last 25 years, Java has stood the test of time. It has delivered the needs of today while preparing for the future. And that remains the case. It is not something that has sort of focused on the fat of the day and the hot thing for the day, but really more important that it is prepared to deal with the mission critical, massive scale deployments that can run for years, for decades, in some cases. And keeping that in mind, Oracle has continued to put more and more technology into the open source world with every release that comes out, you can see 80 plus percent of the contributions come from Oracle. So that's the second pillar around innovation. And the third piece of the strategy has been around predictability. Ensuring that Java, the technology and platform perform as advertised, and that goes into the feature releases, it goes into the release process, it goes into the fact that you were broadly within the open JDK environment for developing and executing the roadmap. From a CIO standpoint, it's important to know that the technology used to develop your applications has talent around. And your, if you're going to develop something like Java, you'll find the right Java engineers to do the job. That is not a question, right? And so that's part of predictability. And finally, again with the change in the six months release cadence that came about three years ago, with the release of Java 10, we've really made sure that it's not, no, a bunch of things come about. You don't know when they're going to be released, but you know, like clockwork, you'll have a new Java list every six months. And that's been the case every March and September, since Java 10, you've had a new release of Java with certain features that come up and we just launched Java 15. So trust innovation predictability, have really been the three pillars on which we've executed the strategy for Java. >> Excellent, thank you for that intro, and we're going to get into it now. I'm glad you mentioned the sun acquisition. I said at the time that Java was the linchpin of that acquisition, many people, of course, we looked at the integration piece with the hardware, but it was really Java and the capabilities that it brings. And of course, a lot of Oracle software written in Java and not the least of which is a fusion. But now let's get into the components of this. And I want to talk a little bit about the methodology of this and going to call on you David Floria. But essentially my understanding is that Wikibon went through and David, you led this, you did a technical deep dive, which you always do, did a number of in depth interviews with Java customers. And then of course you also did a web survey and then you built from that data and economic model. So you can try to understand the sort of dimensions of the financials if you will. So what were your key findings there? >> So the key findings were that Java was in a good state that people were happy with the Java. The second key finding is that the business case itself for using the Oracle services, the subscription services was good. It didn't mean to say that that wasn't for every company, the right way to do it, but there was a very good return on that. And the third area was that there was a degree of confidence that the new way of doing things, the six-month cycle, as opposed to the three-year cycle was overall a benefit to the rate of change, the ability for them to introduce new features quickly. >> Okay, well, I mean, you know, and I read that research. And to me my takeaways where I saw the continued relevance of Java, which is kind of goes without saying, but a lot of times it gets lost in the headlines. That subscription piece is key. We're going to get into some of the economics as to how that affects customers and it saves you money. And the other piece was the roadmap becoming more transparent. And I don't want to dig into that a little bit, but before we do, let's get into that innovation component Manish, mentioned that several times, but Don, I want to go to you guys. We have a slide on the various components of the innovation. If you would bring this up and Don I wonder if you could talk to this and give us some examples if you would. >> Yeah, sure. So we were the number one development platform for the last 25 years. We want to be the number one development platform for the next 25 years. And in order to do that, we have to be constantly innovating and constantly innovating not only the business side in terms of the subscription and the support offerings and commercial features like Manish was talking about, but also the platform in general. And so the way we like to talk about innovation as we break it down by these pillars that you can see on the slide. And so the first pillar is continuous improvements to the language. So this is watching developers trying to write the same piece of code over and over again, and us asking, can we make you more efficient? Can we give you more language features that reduce the amount of boilerplate that you have to write? The second pillar is a project that we just announced a few months ago called Leyden. And the idea with Leyden is addressing the longterm pinpoints of Java slow startup time and time to peak performance. So if you go back 10 years ago, everybody knows about Java as an enterprise platform, Java EE application servers. They all had the notion of being very long lived. And so Java at that time would be optimized towards long lived applications, startup, and performance. Where if it took a little while to get there, it didn't matter as long as when it got there, it was super fast. And so we're trying to get that peak performance faster in the world of microservices. In a similar vein with project loom, we're looking at making concurrency simple again, looking at how developers are doing more reactive style programming and realizing that the threading model needs to be rethought from the ground up, that project is looking really, really good. Then we have project Panama. Project Panama is all about making it easier to connect Java with native libraries. Valhalla is all about improving, there's a couple of benefits, but it's all about improving memory density and being able to access and iterate and operate over primitive data types at super fast speeds by better optimizing how that information is stored in memory. And then the other pillar of the final pillar that we have been working on from an innovation perspective is ZGC. We introduced a new garbage collector technology a few years ago, G1GCE a generational garbage collector with the eye towards making garbage collection in Java pause lists. So if you, again, if you go back in time and look at the history of Java, memory management is awesome, but there's always that cost and risk of a garbage collection cycle, taking a bit of time away from a critical application. And ZGC is all about getting rid of that. So lots of innovation, lots of different pillars going on right now. >> Awesome, I'm impressed. There's something after Valhalla. I thought that was Nirvana. (laughing) But now, and these are all open source projects, right? And you guys obviously provide committers, there are other people in the open source world who provide that, is that correct Don? >> Yeah, that's correct. We have about 80% of the contributions in open JDK. We are the stewards of open JDK and lead the project. Most of the pillars I talked about here are you know Oracle folks working on that. >> Awesome. Okay, let's get into some of the data. David, I want to come back to you and talk about some of the survey results guys, if you bring up that next slide. Why David, why do people upgrade? What are the drivers? It's really talks to the large companies and what's different from the small company or mid-size companies? What are the takeaways here? >> David: Well, so this is interesting, and as you might expect, large enterprises, have very concerned about application stability. Whereas midsize or enterprises are much more concerned about the performance, making sure that the performance is good. They are both concerned about reliable performance and security, but it's interesting that from a regulation point of view, mid-size companies really want to make sure that they are obeying the regulations, that they are meeting those. Whereas larger organizations usually have their own security and regulation functions looking very hard at these things. So that looking less to the platform to provide those than their own people. >> Yeah, I think you're right. I think the midsize organizations don't have as many people running around taking care of security and it's harder for them to keep up with the edicts of the organization. So they want to stay more current. Don, I wonder if you can add anything to this data from an innovation standpoint. >> Yeah, well, and from a product management standpoint, and what we see here is when you look at just going from fortune 500 to global 2000, you see things that are important to one or less so than the other. You can extrapolate that all the way down to a small company or a startup. And that's why providing the most flexibility in terms of an offering to allow people to decide what, when, where, and how they would be going to upgrade their software so they can do it when they want, and on their own terms. You can see that that becomes really important. And also making sure that we're providing innovation in a broad way so that it'll appeal both to the enterprise and again extrapolating that forward down to even very small startups. >> You know, David, the other thing that struck me in the data, if we bring up that other piece is the upgrade strategy, and there was a stark difference between large enterprises and midsize organizations. Talk to this data, if you would. >> Yes, this is again, a pretty stark difference between them. When you're looking at large enterprises, they really wants stability and they don't want to upgrade so often. Whereas mid-size enterprises, are much more willing to both upgrade on a regular cadence and really have a much more up-to-date, or have always have the latest software. They're driving smaller applications, but they're much more agile about their approach to it. Again, emphasizing what Don was saying about the smaller enterprises wanting a different strategy and a different way of doing things than large enterprises. >> So Manish this says to me that you got it right from a strategy standpoint. I mean, any color you can add here. >> Yeah, it's very intuitive that whether you're a large organization, a mid-sized enterprise or a small business, right? You face competitive pressures, your dynamics are unique. What you're able to do with the resources, what you desire to do at the pace that is appropriate for your environment, are really unique to you, and to try to force one model across any one size or across any set of dynamics is just not appropriate. So we've always felt that giving the enterprises and the organization, the ability to move at the pace of their business is the right approach. And so when we designed the Oracle Java SE subscription, we truly have that front and center in our thought process. And that structure seems to be working well. >> David, what I like about the way you do research is you actually build an economic model. A lot of these business value projects. I know this well, having been in the business a long time, they'll go out to ask the customer what they got, and then the customer said, "Well, I got a 111% ROI, and boom, that's what it is. You actually construct an economic model, you bring in rules of thumb, it allows you to do what ifs you can test that model and calibrate it against the real world. So I commend you on that. You've done a lot of hard work there, but bottom line at forests, I mean, let's bring up the economics. I mean, that's what people ultimately want to know. Does this save me money? What's the bottom line here? >> Yeah. Yes, that's a very important question. And the way we go about it is to ask the questions so that we can extract from those questions, how much effort it took, for example, to upgrade things, how much effort it took for important applications and not so important applications. So we have a very detailed model driven by the survey itself and in the back of the research, I'm a great believer that you should be able to follow exactly what the research said, what the survey said and how it was applied to the model. So, and what were you focused on was, what was the return of using the Java subscription service or taking an upgrade every six months? Those were the two ways that we looked at it. And for large enterprises, the four-year costs for the enterprise was $11 million, but for taking the additional subscription service, and this was well well covered, the payback is within a year, well covered by the lower costs of managing in a lot of systems and environment. And we found a very similar result on those midsize services. There, it was 3 million, and again, they got that back the year in terms of payback. So, but that's one alternative. There is another alternative that may be worthwhile the extra money if you really want to be up-to-date and or if you want to drive a much more aggressive strategy for your organization. >> So these are huge numbers. I mean, he's talking about 30% savings on average for large and mid-sized enterprises in the percentage terms, but the absolute dollars are actually enormous. So, you know, large companies here, we're talking about $20 billion enterprises with 500 or more Java applications. And mid-size is, you're talking about a couple, two, $3 billion companies. Manish, what are you saying in the customer base in terms of the economics? >> Yeah, you know anytime an organization is looking at an offering and a solution, they want to make sure just giving them the value. And we all know that the priorities of businesses have, they want to focus on that. Managing the Java estate is important, but is it the thing where they want to invest the dollars? And if they are investing the dollars, are they getting the return? We find that if you can give the enterprises an ability where they can see the return, the cost is right for them. And if you can mirror that and you can map it also with reduce risk, then you put the right formula. And with the subscription, they're able to not only see the cost savings that the model indicates clearly, but they're also able to reduce the risk in terms of security protection and other things. So it's a really, really good combination for the enterprises. >> Well, thank you, I wonder Manish, if you could bring us home here and just kind of summarize from your thoughts, everything you've heard today, what are the key takeaways? >> You know Java has been around for 25 years, and we certainly believe it's really positioned well for what's required today. And perhaps more importantly, what is needed for the next decade and for the next 25 years. Having now served thousands of customers with the Java subscription, it's clear that it is meeting the needs of fortune 10 organizations all the way down to a 5% development house, for example. What we're hearing from across the board is really Java has been the go to platform and it continues to be the go to platform for mission critical development and deployment. However, the complexity as the Java estate becomes large when you've got tens to hundreds, in some cases over a thousand applications running across the enterprise, that complexity can be daunting. And the Java subscription is really serving the needs in three ways. One, it's getting them the best of class support from Oracle, which is a steward of Java, the company that is generating over 80% of innovation with every single release. The second thing they're getting the business flexibility. So they can move at the pace that works for them. And therapies is as a business model as indicated that they're getting it at a lower cost while having your list. So the combination of these things is the reason why we're seeing very high renewal rates, why we're seeing thousands of organization take it over. And I want to wrap it up by saying one final thing, that you can count on Oracle to be the transparent, to be the right steward or both technology innovation, as well as to ensuring the support for the vast ecosystem whether it's libraries, frameworks, user groups, educational services and so on. So Java is here, has been here for the enterprise, large and small, and it's ready for the next generation as well. >> Great, thank you for that. Well, one more question. What's the call to action? If I'm a mid-sized company or a large company, I've made investments in Java, what, what should I do next? >> I would say, take a look at the Oracle subscription. It will reduce your rates. It'll save you a cost and it'll give you a lower risk parameter for your organization. >> Great, nice and crisp, I like it. If you like, if you guys don't object, I'm going to give you my summary. I've been taking notes this whole time and so, we've explored two options. Customers can do it yourself or go with the subscription on a regular cadence. It's very clear to me that that Java remains relevant as we set up top. It's the world's most popular programming language we know about all that. The ecosystem is really moving fast. Of course, with the stewardship of Oracle cloud microservices, the development of, of modern applications. I think that the directional changes that Manish you guys and, and Don and Oracle have made were really the right call. The research that David you did, shows that it's serving customers better. It lowers costs, it's cutting down risk particularly for the mid-sized companies that maybe are, or don't have the security infrastructure and the talent to go chase those problems. And I love the roadmap piece. The more transparent roadmap really is going to give the industry and the community much more confidence to invest and move forward. So guys, thanks very much for coming on this CUBE Java power panel. It was great to have you. >> Thank you. >> Thank you. >> Thank you. >> All right, I thank you for watching everybody. This is Dave Vellante, for theCUBE, and we'll see you next time. (soft music)

[Music] [Music] [Music] [Laughter] [Laughter] [Laughter] [Laughter] [Music] [Music] [Music] [Music] you you [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Applause] [Music] wake up feeling blessed peace you warned that Russia ain't afraid to show it I'll expose it if I dressed up riding in that Chester roasted nigga catch you slippin on myself rocks on I messed up like yes sir [Music] [Music] [Music] [Music] our program [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] you are not welcome to Red Hat summit 2018 2018 [Music] [Music] [Music] [Laughter] [Music] Wow that is truly the coolest introduction I've ever had thank you Wow I don't think I feel cool enough to follow an interaction like that Wow well welcome to the Red Hat summit this is our 14th annual event and I have to say looking out over this audience Wow it's great to see so many people here joining us this is by far our largest summit to date not only did we blow through the numbers we've had in the past we blew through our own expectations this year so I know we have a pretty packed house and I know people are still coming in so it's great to see so many people here it's great to see so many familiar faces when I had a chance to walk around earlier it's great to see so many new people here joining us for the first time I think the record attendance is an indication that more and more enterprises around the world are seeing the power of open source to help them with their challenges that they're facing due to the digital transformation that all of enterprises around the world are going through the theme for the summit this year is ideas worth exploring and we intentionally chose that because as much as we are all going through this digital disruption and the challenges associated with it one thing I think is becoming clear no one person and certainly no one company has the answers to these challenges right this isn't a problem where you can go buy a solution this is a set of capabilities that we all need to build it's a set of cultural changes that we all need to go through and that's going to require the best ideas coming from so many different places so we're not here saying we have the answers we're trying to convene the conversation right we want to serve as a catalyst bringing great minds together to share ideas so we all walk out of here at the end of the week a little wiser than when we first came here we do have an amazing agenda for you we have over 7,000 attendees we may be pushing 8,000 by the time we got through this morning we have 36 keynote speakers and we have a hundred and twenty-five breakout sessions and have to throw in one plug scheduling 325 breakout sessions is actually pretty difficult and so we used the Red Hat business optimizer which is an AI constraint solver that's new in the Red Hat decision manager to help us plan the summit because we have individuals who have a clustered set of interests and we want to make sure that when we schedule two breakout sessions we do it in a way that we don't have overlapping sessions that are really important to the same individual so we tried to use this tool and what we understand about people's interest in history of what they wanted to do to try to make sure that we spaced out different times for things of similar interests for similar people as well as for people who stood in the back of breakouts before and I know I've done that too we've also used it to try to optimize room size so hopefully we will do our best to make sure that we've appropriately sized the spaces for those as well so it's really a phenomenal tool and I know it's helped us a lot this year in addition to the 325 breakouts we have a lot of our customers on stage during the main sessions and so you'll see demos you'll hear from partners you'll hear stories from so many of our customers not on our point of view of how to use these technologies but their point of views of how they actually are using these technologies to solve their problems and you'll hear over and over again from those keynotes that it's not just about the technology it's about how people are changing how people are working to innovate to solve those problems and while we're on the subject of people I'd like to take a moment to recognize the Red Hat certified professional of the year this is known award we do every year I love this award because it truly recognizes an individual for outstanding innovation for outstanding ideas for truly standing out in how they're able to help their organization with Red Hat technologies Red Hat certifications help system administrators application developers IT architects to further their careers and help their organizations by being able to advance their skills and knowledge of Red Hat products and this year's winner really truly is a great example about how their curiosity is helped push the limits of what's possible with technology let's hear a little more about this year's winner when I was studying at the University I had computer science as one of my subjects and that's what created the passion from the very beginning they were quite a few institutions around my University who were offering Red Hat Enterprise Linux as a course and a certification paths through to become an administrator Red Hat Learning subscription has offered me a lot more than any other trainings that have done so far that gave me exposure to so many products under red hair technologies that I wasn't even aware of I started to think about the better ways of how these learnings can be put into the real life use cases and we started off with a discussion with my manager saying I have to try this product and I really want to see how it really fits in our environment and that product was Red Hat virtualization we went from deploying rave and then OpenStack and then the open shift environment we wanted to overcome some of the things that we saw as challenges to the speed and rapidity of release and code etc so it made perfect sense and we were able to do it in a really short space of time so you know we truly did use it as an Innovation Lab I think idea is everything ideas can change the way you see things an Innovation Lab was such an idea that popped into my mind one fine day and it has transformed the way we think as a team and it's given that playpen to pretty much everyone to go and test their things investigate evaluate do whatever they like in a non-critical non production environment I recruited Neha almost 10 years ago now I could see there was a spark a potential with it and you know she had a real Drive a real passion and you know here we are nearly ten years later I'm Neha Sandow I am a Red Hat certified engineer all right well everyone please walk into the states to the stage Neha [Music] [Applause] congratulations thank you [Applause] I think that - well welcome to the red has some of this is your first summit yes it is thanks so much well fantastic sure well it's great to have you here I hope you have a chance to engage and share some of your ideas and enjoy the week thank you thank you congratulations [Applause] neha mentioned that she first got interest in open source at university and it made me think red hats recently started our Red Hat Academy program that looks to programmatically infuse Red Hat technologies in universities around the world it's exploded in a way we had no idea it's grown just incredibly rapidly which i think shows the interest that there really is an open source and working in an open way at university so it's really a phenomenal program I'm also excited to announce that we're launching our newest open source story this year at Summit it's called the science of collective discovery and it looks at what happens when communities use open hardware to monitor the environment around them and really how they can make impactful change based on that technologies the rural premier that will be at 5:15 on Wednesday at McMaster Oni West and so please join us for a drink and we'll also have a number of the experts featured in that and you can have a conversation with them as well so with that let's officially start the show please welcome red hat president of products and technology Paul Cormier [Music] Wow morning you know I say it every year I'm gonna say it again I know I repeat myself it's just amazing we are so proud here to be here today too while you all week on how far we've come with opens with open source and with the products that we that we provide at Red Hat so so welcome and I hope the pride shows through so you know I told you Seven Summits ago on this stage that the future would be open and here we are just seven years later this is the 14th summit but just seven years later after that and much has happened and I think you'll see today and this week that that prediction that the world would be open was a pretty safe predict prediction but I want to take you just back a little bit to see how we started here and it's not just how Red Hat started here this is an open source in Linux based computing is now in an industry norm and I think that's what you'll you'll see in here this week you know we talked back then seven years ago when we put on our prediction about the UNIX error and how Hardware innovation with x86 was it was really the first step in a new era of open innovation you know companies like Sun Deck IBM and HP they really changed the world the computing industry with their UNIX models it was that was really the rise of computing but I think what we we really saw then was that single company innovation could only scale so far could really get so far with that these companies were very very innovative but they coupled hardware innovation with software innovation and as one company they could only solve so many problems and even which comp which even complicated things more they could only hire so many people in each of their companies Intel came on the scene back then as the new independent hardware player and you know that was really the beginning of the drive for horizontal computing power and computing this opened up a brand new vehicle for hardware innovation a new hardware ecosystem was built around this around this common hardware base shortly after that Stallman and leanness they had a vision of his of an open model that was created and they created Linux but it was built around Intel this was really the beginning of having a software based platform that could also drive innovation this kind of was the beginning of the changing of the world here that system-level innovation now having a hardware platform that was ubiquitous and a software platform that was open and ubiquitous it really changed this system level innovation and that continues to thrive today it was only possible because it was open this could not have happened in a closed environment it allowed the best ideas from anywhere from all over to come in in win only because it was the best idea that's what drove the rate of innovation at the pace you're seeing today and it which has never been seen before we at Red Hat we saw the need to bring this innovation to solve real-world problems in the enterprise and I think that's going to be the theme of the show today you're going to see us with our customers and partners talking about and showing you some of those real-world problems that we are sought solving with this open innovation we created rel back then for this for the enterprise it started it's it it wasn't successful because it's scaled it was secure and it was enterprise ready it once again changed the industry but this time through open innovation this gave the hardware ecosystem a software platform this open software platform gave the hardware ecosystem a software platform to build around it Unleashed them the hardware side to compete and thrive it enabled innovation from the OEMs new players building cheaper faster servers even new architectures from armed to power sprung up with this change we have seen an incredible amount of hardware innovation over the last 15 years that same innovation happened on the software side we saw powerful implementations of bare metal Linux distributions out in the market in fact at one point there were 300 there are over 300 distributions out in the market on the foundation of Linux powerful open-source equivalents were even developed in every area of Technology databases middleware messaging containers anything you could imagine innovation just exploded around the Linux platform in innovation it's at the core also drove virtualization both Linux and virtualization led to another area of innovation which you're hearing a lot about now public cloud innovation this innovation started to proceed at a rate that we had never seen before we had never experienced this in the past in this unprecedented speed of innovation and software was now possible because you didn't need a chip foundry in order to innovate you just needed great ideas in the open platform that was out there customers seeing this innovation in the public cloud sparked it sparked their desire to build their own linux based cloud platforms and customers are now are now bringing that cloud efficiency on-premise in their own data centers public clouds demonstrated so much efficiency the data centers and architects wanted to take advantage of it off premise on premise I'm sorry within their own we don't within their own controlled environments this really allowed companies to make the most of existing investments from data centers to hardware they also gained many new advantages from data sovereignty to new flexible agile approaches I want to bring Burr and his team up here to take a look at what building out an on-premise cloud can look like today Bure take it away I am super excited to be with all of you here at Red Hat summit I know we have some amazing things to show you throughout the week but before we dive into this demonstration I want you to take just a few seconds just a quick moment to think about that really important event your life that moment you turned on your first computer maybe it was a trs-80 listen Claire and Atari I even had an 83 b2 at one point but in my specific case I was sitting in a classroom in Hawaii and I could see all the way from Diamond Head to Pearl Harbor so just keep that in mind and I turn on an IBM PC with dual floppies I don't remember issuing my first commands writing my first level of code and I was totally hooked it was like a magical moment and I've been hooked on computers for the last 30 years so I want you to hold that image in your mind for just a moment just a second while we show you the computers we have here on stage let me turn this over to Jay fair and Dini here's our worldwide DevOps manager and he was going to show us his hardware what do you got Jay thank you BER good morning everyone and welcome to Red Hat summit we have so many cool things to show you this week I am so happy to be here and you know my favorite thing about red hat summit is our allowed to kind of share all of our stories much like bird just did we also love to you know talk about the hardware and the technology that we brought with us in fact it's become a bit of a competition so this year we said you know let's win this thing and we actually I think we might have won we brought a cloud with us so right now this is a private cloud for throughout the course of the week we're going to turn this into a very very interesting open hybrid cloud right before your eyes so everything you see here will be real and happening right on this thing right behind me here so thanks for our four incredible partners IBM Dell HP and super micro we've built a very vendor heterogeneous cloud here extra special thanks to IBM because they loaned us a power nine machine so now we actually have multiple architectures in this cloud so as you know one of the greatest benefits to running Red Hat technology is that we run on just about everything and you know I can't stress enough how powerful that is how cost-effective that is and it just makes my life easier to be honest so if you're interested the people that built this actual rack right here gonna be hanging out in the customer success zone this whole week it's on the second floor the lobby there and they'd be glad to show you exactly how they built this thing so let me show you what we actually have in this rack so contained in this rack we have 1056 physical chorus right here we have five and a half terabytes of RAM and just in case we threw 50 terabytes of storage in this thing so burr that's about two million times more powerful than that first machine you boot it up thanks to a PC we're actually capable of putting all the power needs and cooling right in this rack so there's your data center right there you know it occurred to me last night that I can actually pull the power cord on this thing and kick it up a notch we could have the world's first mobile portable hybrid cloud so I'm gonna go ahead and unplug no no no no no seriously it's not unplug the thing we got it working now well Berg gets a little nervous but next year we're rolling this thing around okay okay so to recap multiple vendors check multiple architectures check multiple public clouds plug right into this thing check and everything everywhere is running the same software from Red Hat so that is a giant check so burn Angus why don't we get the demos rolling awesome so we have totally we have some amazing hardware amazing computers on this stage but now we need to light it up and we have Angus Thomas who represents our OpenStack engineering team and he's going to show us what we can do with this awesome hardware Angus thank you Beth so this was an impressive rack of hardware to Joe has bought a pocket stage what I want to talk about today is putting it to work with OpenStack platform director we're going to turn it from a lot of potential into a flexible scalable private cloud we've been using director for a while now to take care of managing hardware and orchestrating the deployment of OpenStack what's new is that we're bringing the same capabilities for on-premise manager the deployment of OpenShift director deploying OpenShift in this way is the best of both worlds it's bare-metal performance but with an underlying infrastructure as a service that can take care of deploying in new instances and scaling out and a lot of the things that we expect from a cloud provider director is running on a virtual machine on Red Hat virtualization at the top of the rack and it's going to bring everything else under control what you can see on the screen right now is the director UI and as you see some of the hardware in the rack is already being managed at the top level we have information about the number of cores in the amount of RAM and the disks that each machine have if we dig in a bit there's information about MAC addresses and IPs and the management interface the BIOS kernel version dig a little deeper and there is information about the hard disks all of this is important because we want to be able to make sure that we put in workloads exactly where we want them Jay could you please power on the two new machines at the top of the rack sure all right thank you so when those two machines come up on the network director is going to see them see that they're new and not already under management and is it immediately going to go into the hardware inspection that populates this database and gets them ready for use so we also have profiles as you can see here profiles are the way that we match the hardware in a machine to the kind of workload that it's suited to this is how we make sure that machines that have all the discs run Seth and machines that have all the RAM when our application workouts for example there's two ways these can be set when you're dealing with a rack like this you could go in an individually tag each machine but director scales up to data centers so we have a rules matching engine which will automatically take the hardware profile of a new machine and make sure it gets tagged in exactly the right way so we can automatically discover new machines on the network and we can automatically match them to a profile that's how we streamline and scale up operations now I want to talk about deploying the software we have a set of validations we've learned over time about the Miss configurations in the underlying infrastructure which can cause the deployment of a multi node distributed application like OpenStack or OpenShift to fail if you have the wrong VLAN tags on a switch port or DHCP isn't running where it should be for example you can get into a situation which is really hard to debug a lot of our validations actually run before the deployment they look at what you're intending to deploy and they check in the environment is the way that it should be and they'll preempts problems and obviously preemption is a lot better than debugging something new that you probably have not seen before is director managing multiple deployments of different things side by side before we came out on stage we also deployed OpenStack on this rack just to keep me honest let me jump over to OpenStack very quickly a lot of our opens that customers will be familiar with this UI and the bare metal deployment of OpenStack on our rack is actually running a set of virtual machines which is running Gluster you're going to see that put to work later on during the summit Jay's gone to an awful lot effort to get this Hardware up on the stage so we're going to use it as many different ways as we can okay let's deploy OpenShift if I switch over to the deployed a deployment plan view there's a few steps first thing you need to do is make sure we have the hardware I already talked about how director manages hardware it's smart enough to make sure that it's not going to attempt to deploy into machines they're already in use it's only going to deploy on machines that have the right profile but I think with the rack that we have here we've got enough next thing is the deployment configuration this is where you get to customize exactly what's going to be deployed to make sure that it really matches your environment if they're external IPs for additional services you can set them here whatever it takes to make sure that the deployment is going to work for you as you can see on the screen we have a set of options around enable TLS for encryption network traffic if I dig a little deeper there are options around enabling ipv6 and network isolation so that different classes of traffic there are over different physical NICs okay then then we have roles now roles this is essentially about the software that's going to be put on each machine director comes with a set of roles for a lot of the software that RedHat supports and you can just use those or you can modify them a little bit if you need to add a monitoring agent or whatever it might be or you can create your own custom roles director has quite a rich syntax for custom role definition and custom Network topologies whatever it is you need in order to make it work in your environment so the rawls that we have right now are going to give us a working instance of openshift if I go ahead and click through the validations are all looking green so right now I can click the button start to the deploy and you will see things lighting up on the rack directors going to use IPMI to reboot the machines provisioned and with a trail image was the containers on them and start up the application stack okay so one last thing once the deployment is done you're going to want to keep director around director has a lot of capabilities around what we call de to operational management bringing in new Hardware scaling out deployments dealing with updates and critically doing upgrades as well so having said all of that it is time for me to switch over to an instance of openshift deployed by a director running on bare metal on our rack and I need to hand this over to our developer team so they can show what they can do it thank you that is so awesome Angus so what you've seen now is going from bare metal to the ultimate private cloud with OpenStack director make an open shift ready for our developers to build their next generation applications thank you so much guys that was totally awesome I love what you guys showed there now I have the honor now I have the honor of introducing a very special guest one of our earliest OpenShift customers who understands the necessity of the private cloud inside their organization and more importantly they're fundamentally redefining their industry please extend a warm welcome to deep mar Foster from Amadeus well good morning everyone a big thank you for having armadillos here and myself so as it was just set I'm at Mario's well first of all we are a large IT provider in the travel industry so serving essentially Airlines hotel chains this distributors like Expedia and others we indeed we started very early what was OpenShift like a bit more than three years ago and we jumped on it when when Retta teamed with Google to bring in kubernetes into this so let me quickly share a few figures about our Mario's to give you like a sense of what we are doing and the scale of our operations so some of our key KPIs one of our key metrics is what what we call passenger borders so that's the number of customers that physically board a plane over the year so through our systems it's roughly 1.6 billion people checking in taking the aircrafts on under the Amarillo systems close to 600 million travel agency bookings virtually all airlines are on the system and one figure I want to stress out a little bit is this one trillion availability requests per day that's when I read this figure my mind boggles a little bit so this means in continuous throughput more than 10 million hits per second so of course these are not traditional database transactions it's it's it's highly cached in memory and these applications are running over like more than 100,000 course so it's it's it's really big stuff so today I want to give some concrete feedback what we are doing so I have chosen two applications products of our Mario's that are currently running on production in different in different hosting environments as the theme here is of this talk hybrid cloud and so I want to give some some concrete feedback of how we architect the applications and of course it stays relatively high level so here I have taken one of our applications that is used in the hospitality environment so it's we have built this for a very large US hotel chain and it's currently in in full swing brought into production so like 30 percent of the globe or 5,000 plus hotels are on this platform not so here you can see that we use as the path of course on openshift on that's that's the most central piece of our hybrid cloud strategy on the database side we use Oracle and Couchbase Couchbase is used for the heavy duty fast access more key value store but also to replicate data across two data centers in this case it's running over to US based data centers east and west coast topology that are fit so run by Mario's that are fit with VMware on for the virtualization OpenStack on top of it and then open shift to host and welcome the applications on the right hand side you you see the kind of tools if you want to call them tools that we use these are the principal ones of course the real picture is much more complex but in essence we use terraform to map to the api's of the underlying infrastructure so they are obviously there are differences when you run on OpenStack or the Google compute engine or AWS Azure so some some tweaking is needed we use right at ansible a lot we also use puppet so you can see these are really the big the big pieces of of this sense installation and if we look to the to the topology again very high high level so these two locations basically map the data centers of our customers so they are in close proximity because the response time and the SLA is of this application is are very tight so that's an example of an application that is architectures mostly was high ability and high availability in minds not necessarily full global worldwide scaling but of course it could be scaled but here the idea is that we can swing from one data center to the unit to the other in matters of of minutes both take traffic data is fully synchronized across those data centers and while the switch back and forth is very fast the second example I have taken is what we call the shopping box this is when people go to kayak or Expedia and they're getting inspired where they want to travel to this is really the piece that shoots most of transit of the transactions into our Mario's so we architect here more for high scalability of course availability is also a key but here scaling and geographical spread is very important so in short it runs partially on-premise in our Amarillo Stata Center again on OpenStack and we we deploy it mostly in the first step on the Google compute engine and currently as we speak on Amazon on AWS and we work also together with Retta to qualify the whole show on Microsoft Azure here in this application it's it's the same building blocks there is a large swimming aspect to it so we bring Kafka into this working with records and another partner to bring Kafka on their open shift because at the end we want to use open shift to administrate the whole show so over time also databases and the topology here when you look to the physical deployment topology while it's very classical we use the the regions and the availability zone concept so this application is spread over three principal continental regions and so it's again it's a high-level view with different availability zones and in each of those availability zones we take a hit of several 10,000 transactions so that was it really in very short just to give you a glimpse on how we implement hybrid clouds I think that's the way forward it gives us a lot of freedom and it allows us to to discuss in a much more educated way with our customers that sometimes have already deals in place with one cloud provider or another so for us it's a lot of value to set two to leave them the choice basically what up that was a very quick overview of what we are doing we were together with records are based on open shift essentially here and more and more OpenStack coming into the picture hope you found this interesting thanks a lot and have a nice summer [Applause] thank you so much deeper great great solution we've worked with deep Marv and his team for a long for a long time great solution so I want to take us back a little bit I want to circle back I sort of ended talking a little bit about the public cloud so let's circle back there you know even so even though some applications need to run in various footprints on premise there's still great gains to be had that for running certain applications in the public cloud a public cloud will be as impactful to to the industry as as UNIX era was of computing was but by itself it'll have some of the same limitations and challenges that that model had today there's tremendous cloud innovation happening in the public cloud it's being driven by a handful of massive companies and much like the innovation that sundeck HP and others drove in a you in the UNIX era of community of computing many customers want to take advantage of the best innovation no matter where it comes from buddy but as they even eventually saw in the UNIX era they can't afford the best innovation at the cost of a siloed operating environment with the open community we are building a hybrid application platform that can give you access to the best innovation no matter which vendor or which cloud that it comes from letting public cloud providers innovate and services beyond what customers or anyone can one provider can do on their own such as large scale learning machine learning or artificial intelligence built on the data that's unique probably to that to that one cloud but consumed in a common way for the end customer across all applications in any environment on any footprint in in their overall IT infrastructure this is exactly what rel brought brought to our customers in the UNIX era of computing that consistency across any of those footprints obviously enterprises will have applications for all different uses some will live on premise some in the cloud hybrid cloud is the only practical way forward I think you've been hearing that from us for a long time it is the only practical way forward and it'll be as impactful as anything we've ever seen before I want to bring Byrne his team back to see a hybrid cloud deployment in action burr [Music] all right earlier you saw what we did with taking bare metal and lighting it up with OpenStack director and making it openshift ready for developers to build their next generation applications now we want to show you when those next turn and generation applications and what we've done is we take an open shift and spread it out and installed it across Asia and Amazon a true hybrid cloud so with me on stage today as Ted who's gonna walk us through an application and Brent Midwood who's our DevOps engineer who's gonna be making sure he's monitoring on the backside that we do make sure we do a good job so at this point Ted what have you got for us Thank You BER and good morning everybody this morning we are running on the stage in our private cloud an application that's providing its providing fraud detection detect serves for financial transactions and our customer base is rather large and we occasionally take extended bursts of traffic of heavy traffic load so in order to keep our latency down and keep our customers happy we've deployed extra service capacity in the public cloud so we have capacity with Microsoft Azure in Texas and with Amazon Web Services in Ohio so we use open chip container platform on all three locations because openshift makes it easy for us to deploy our containerized services wherever we want to put them but the question still remains how do we establish seamless communication across our entire enterprise and more importantly how do we balance the workload across these three locations in such a way that we efficiently use our resources and that we give our customers the best possible experience so this is where Red Hat amq interconnect comes in as you can see we've deployed a MQ interconnect alongside our fraud detection applications in all three locations and if I switch to the MQ console we'll see the topology of the app of the network that we've created here so the router inside the on stage here has made connections outbound to the public routers and AWS and Azure these connections are secured using mutual TLS authentication and encrypt and once these connections are established amq figures out the best way auda matically to route traffic to where it needs to get to so what we have right now is a distributed reliable broker list message bus that expands our entire enterprise now if you want to learn more about this make sure that you catch the a MQ breakout tomorrow at 11:45 with Jack Britton and David Ingham let's have a look at the message flow and we'll dive in and isolate the fraud detection API that we're interested in and what we see is that all the traffic is being handled in the private cloud that's what we expect because our latencies are low and they're acceptable but now if we take a little bit of a burst of increased traffic we're gonna see that an EQ is going to push a little a bi traffic out onto the out to the public cloud so as you're picking up some of the load now to keep the Layton sees down now when that subsides as your finishes up what it's doing and goes back offline now if we take a much bigger load increase you'll see two things first of all asher is going to take a bigger proportion than it did before and Amazon Web Services is going to get thrown into the fray as well now AWS is actually doing less work than I expected it to do I expected a little bit of bigger a slice there but this is a interesting illustration of what's going on for load balancing mq load balancing is sending requests to the services that have the lowest backlog and in order to keep the Layton sees as steady as possible so AWS is probably running slowly for some reason and that's causing a and Q to push less traffic its way now the other thing you're going to notice if you look carefully this graph fluctuate slightly and those fluctuations are caused by all the variances in the network we have the cloud on stage and we have clouds in in the various places across the country there's a lot of equipment locked layers of virtualization and networking in between and we're reacting in real-time to the reality on the digital street so BER what's the story with a to be less I noticed there's a problem right here right now we seem to have a little bit performance issue so guys I noticed that as well and a little bit ago I actually got an alert from red ahead of insights letting us know that there might be some potential optimizations we could make to our environment so let's take a look at insights so here's the Red Hat insights interface you can see our three OpenShift deployments so we have the set up here on stage in San Francisco we have our Azure deployment in Texas and we also have our AWS deployment in Ohio and insights is highlighting that that deployment in Ohio may have some issues that need some attention so Red Hat insights collects anonymized data from manage systems across our customer environment and that gives us visibility into things like vulnerabilities compliance configuration assessment and of course Red Hat subscription consumption all of this is presented in a SAS offering so it's really really easy to use it requires minimal infrastructure upfront and it provides an immediate return on investment what insights is showing us here is that we have some potential issues on the configuration side that may need some attention from this view I actually get a look at all the systems in our inventory including instances and containers and you can see here on the left that insights is highlighting one of those instances as needing some potential attention it might be a candidate for optimization this might be related to the issues that you were seeing just a minute ago insights uses machine learning and AI techniques to analyze all collected data so we combine collected data from not only the system's configuration but also with other systems from across the Red Hat customer base this allows us to compare ourselves to how we're doing across the entire set of industries including our own vertical in this case the financial services industry and we can compare ourselves to other customers we also get access to tailored recommendations that let us know what we can do to optimize our systems so in this particular case we're actually detecting an issue here where we are an outlier so our configuration has been compared to other configurations across the customer base and in this particular instance in this security group were misconfigured and so insights actually gives us the steps that we need to use to remediate the situation and the really neat thing here is that we actually get access to a custom ansible playbook so if we want to automate that type of a remediation we can use this inside of Red Hat ansible tower Red Hat satellite Red Hat cloud forms it's really really powerful the other thing here is that we can actually apply these recommendations right from within the Red Hat insights interface so with just a few clicks I can select all the recommendations that insights is making and using that built-in ansible automation I can apply those recommendations really really quickly across a variety of systems this type of intelligent automation is really cool it's really fast and powerful so really quickly here we're going to see the impact of those changes and so we can tell that we're doing a little better than we were a few minutes ago when compared across the customer base as well as within the financial industry and if we go back and look at the map we should see that our AWS employment in Ohio is in a much better state than it was just a few minutes ago so I'm wondering Ted if this had any effect and might be helping with some of the issues that you were seeing let's take a look looks like went green now let's see what it looks like over here yeah doesn't look like the configuration is taking effect quite yet maybe there's some delay awesome fantastic the man yeah so now we're load balancing across the three clouds very much fantastic well I have two minute Ted I truly love how we can route requests and dynamically load transactions across these three clouds a truly hybrid cloud native application you guys saw here on on stage for the first time and it's a fully portable application if you build your applications with openshift you can mover from cloud to cloud to cloud on stage private all the way out to the public said it's totally awesome we also have the application being fully managed by Red Hat insights I love having that intelligence watching over us and ensuring that we're doing everything correctly that is fundamentally awesome thank you so much for that well we actually have more to show you but you're going to wait a few minutes longer right now we'd like to welcome Paul back to the stage and we have a very special early Red Hat customer an Innovation Award winner from 2010 who's been going boldly forward with their open hybrid cloud strategy please give a warm welcome to Monty Finkelstein from Citigroup [Music] [Music] hi Marty hey Paul nice to see you thank you very much for coming so thank you for having me Oh our pleasure if you if you wanted to we sort of wanted to pick your brain a little bit about your experiences and sort of leading leading the charge in computing here so we're all talking about hybrid cloud how has the hybrid cloud strategy influenced where you are today in your computing environment so you know when we see the variable the various types of workload that we had an hour on from cloud we see the peaks we see the valleys we see the demand on the environment that we have we really determined that we have to have a much more elastic more scalable capability so we can burst and stretch our environments to multiple cloud providers these capabilities have now been proven at City and of course we consider what the data risk is as well as any regulatory requirement so how do you how do you tackle the complexity of multiple cloud environments so every cloud provider has its own unique set of capabilities they have they're own api's distributions value-added services we wanted to make sure that we could arbitrate between the different cloud providers maintain all source code and orchestration capabilities on Prem to drive those capabilities from within our platforms this requires controlling the entitlements in a cohesive fashion across our on Prem and Wolfram both for security services automation telemetry as one seamless unit can you talk a bit about how you decide when you to use your own on-premise infrastructure versus cloud resources sure so there are multiple dimensions that we take into account right so the first dimension we talk about the risk so low risk - high risk and and really that's about the data classification of the environment we're talking about so whether it's public or internal which would be considered low - ooh confidential PII restricted sensitive and so on and above which is really what would be considered a high-risk the second dimension would be would focus on demand volatility and responsiveness sensitivity so this would range from low response sensitivity and low variability of the type of workload that we have to the high response sensitivity and high variability of the workload the first combination that we focused on is the low risk and high variability and high sensitivity for response type workload of course any of the workloads we ensure that we're regulatory compliant as well as we achieve customer benefits with within this environment so how can we give developers greater control of their their infrastructure environments and still help operations maintain that consistency in compliance so the main driver is really to use the public cloud is scale speed and increased developer efficiencies as well as reducing cost as well as risk this would mean providing develop workspaces and multiple environments for our developers to quickly create products for our customers all this is done of course in a DevOps model while maintaining the source and artifacts registry on-prem this would allow our developers to test and select various middleware products another product but also ensure all the compliance activities in a centrally controlled repository so we really really appreciate you coming by and sharing that with us today Monte thank you so much for coming to the red echo thanks a lot thanks again tamati I mean you know there's these real world insight into how our products and technologies are really running the businesses today that's that's just the most exciting part so thank thanks thanks again mati no even it with as much progress as you've seen demonstrated here and you're going to continue to see all week long we're far from done so I want to just take us a little bit into the path forward and where we we go today we've talked about this a lot innovation today is driven by open source development I don't think there's any question about that certainly not in this room and even across the industry as a whole that's a long way that we've come from when we started our first summit 14 years ago with over a million open source projects out there this unit this innovation aggregates into various community platforms and it finally culminates in commercial open source based open source developed products these products run many of the mission-critical applications in business today you've heard just a couple of those today here on stage but it's everywhere it's running the world today but to make customers successful with that interact innovation to run their real-world business applications these open source products have to be able to leverage increase increasingly complex infrastructure footprints we must also ensure a common base for the developer and ultimately the application no matter which footprint they choose as you heard mati say the developers want choice here no matter which no matter which footprint they are ultimately going to run their those applications on they want that flexibility from the data center to possibly any public cloud out there in regardless of whether that application was built yesterday or has been running the business for the last 10 years and was built on 10-year old technology this is the flexibility that developers require today but what does different infrastructure we may require different pieces of the technical stack in that deployment one example of this that Effects of many things as KVM which provides the foundation for many of those use cases that require virtualization KVM offers a level of consistency from a technical perspective but rel extends that consistency to add a level of commercial and ecosystem consistency for the application across all those footprints this is very important in the enterprise but while rel and KVM formed the foundation other technologies are needed to really satisfy the functions on these different footprints traditional virtualization has requirements that are satisfied by projects like overt and products like Rev traditional traditional private cloud implementations has requirements that are satisfied on projects like OpenStack and products like Red Hat OpenStack platform and as applications begin to become more container based we are seeing many requirements driven driven natively into containers the same Linux in different forms provides this common base across these four footprints this level of compatible compatibility is critical to operators who must best utilize the infinite must better utilize secure and deploy the infrastructure that they have and they're responsible for developers on the other hand they care most about having a platform that can creates that consistency for their applications they care about their services and the services that they need to consume within those applications and they don't want limitations on where they run they want service but they want it anywhere not necessarily just from Amazon they want integration between applications no matter where they run they still want to run their Java EE now named Jakarta EE apps and bring those applications forward into containers and micro services they need able to orchestrate these frameworks and many more across all these different footprints in a consistent secure fashion this creates natural tension between development and operations frankly customers amplify this tension with organizational boundaries that are holdover from the UNIX era of computing it's really the job of our platforms to seamlessly remove these boundaries and it's the it's the goal of RedHat to seamlessly get you from the old world to the new world we're gonna show you a really cool demo demonstration now we're gonna show you how you can automate this transition first we're gonna take a Windows virtual machine from a traditional VMware deployment we're gonna convert it into a KVM based virtual machine running in a container all under the kubernetes umbrella this makes virtual machines more access more accessible to the developer this will accelerate the transformation of those virtual machines into cloud native container based form well we will work this prot we will worked as capability over the product line in the coming releases so we can strike the balance of enabling our developers to move in this direction we want to be able to do this while enabling mission-critical operations to still do their job so let's bring Byrne his team back up to show you this in action for one more thanks all right what Red Hat we recognized that large organizations large enterprises have a substantial investment and legacy virtualization technology and this is holding you back you have thousands of virtual machines that need to be modernized so what you're about to see next okay it's something very special with me here on stage we have James Lebowski he's gonna be walking us through he's represents our operations folks and he's gonna be walking us through a mass migration but also is Itamar Hine who's our lead developer of a very special application and he's gonna be modernizing container izing and optimizing our application all right so let's get started James thanks burr yeah so as you can see I have a typical VMware environment here I'm in the vSphere client I've got a number of virtual machines a handful of them that make up my one of my applications for my development environment in this case and what I want to do is migrate those over to a KVM based right at virtualization environment so what I'm gonna do is I'm gonna go to cloud forms our cloud management platform that's our first step and you know cloud forms actually already has discovered both my rev environment and my vSphere environment and understands the compute network and storage there so you'll notice one of the capabilities we built is this new capability called migrations and underneath here I could begin to there's two steps and the first thing I need to do is start to create my infrastructure mappings what this will allow me to do is map my compute networking storage between vSphere and Rev so cloud forms understands how those relate let's go ahead and create an infrastructure mapping I'll call that summit infrastructure mapping and then I'm gonna begin to map my two environments first the compute so the clusters here next the data stores so those virtual machines happen to live on datastore - in vSphere and I'll target them a datastore data to inside of my revenue Arman and finally my networks those live on network 100 so I'll map those from vSphere to rover so once my infrastructure is map the next step I need to do is actually begin to create a plan to migrate those virtual machines so I'll continue to the plan wizard here I'll select the infrastructure mapping I just created and I'll select migrate my development environment from those virtual machines to Rev and then I need to import a CSV file the CSV file is going to contain a list of all the virtual machines that I want to migrate that were there and that's it once I hit create what's going to happen cloud forms is going to begin in an automated fashion shutting down those virtual machines begin converting them taking care of all the minutia that you'd have to do manually it's gonna do that all automatically for me so I don't have to worry about all those manual interactions and no longer do I have to go manually shut them down but it's going to take care of that all for me you can see the migrations kicked off here this is the I've got the my VMs are migrating here and if I go back to the screen here you can see that we're gonna start seeing those shutdown okay awesome but as people want to know more information about this how would they dive deeper into this technology later this week yeah it's a great question so we have a workload portability session in the hybrid cloud on Wednesday if you want to see a presentation that deep dives into this topic and how some of the methodologies to migrate and then on Thursday we actually have a hands-on lab it's the IT optimization VM migration lab that you can check out and as you can see those are shutting down here yeah we see a powering off right now that's fantastic absolutely so if I go back now that's gonna take a while you got to convert all the disks and move them over but we'll notice is previously I had already run one migration of a single application that was a Windows virtual machine running and if I browse over to Red Hat virtualization I can see on the dashboard here I could browse to virtual machines I have migrated that Windows virtual machine and if I open up a tab I can now browse to my Windows virtual machine which is running our wingtip toy store application our sample application here and now my VM has been moved over from Rev to Vita from VMware to Rev and is available for Itamar all right great available to our developers all right Itamar what are you gonna do for us here well James it's great that you can save cost by moving from VMware to reddit virtualization but I want to containerize our application and with container native virtualization I can run my virtual machine on OpenShift like any other container using Huebert a kubernetes operator to run and manage virtual machines let's look at the open ship service catalog you can see we have a new virtualization section here we can import KVM or VMware virtual machines or if there are already loaded we can create new instances of them for the developer to work with just need to give named CPU memory we can do other virtualization parameters and create our virtual machines now let's see how this looks like in the openshift console the cool thing about KVM is virtual machines are just Linux processes so they can act and behave like other open shipped applications we build in more than a decade of virtualization experience with KVM reddit virtualization and OpenStack and can now benefit from kubernetes and open shift to manage and orchestrate our virtual machines since we know this virtual machine this container is actually a virtual machine we can do virtual machine stuff with it like shutdown reboot or open a remote desktop session to it but we can also see this is just a container like any other container in openshift and even though the web application is running inside a Windows virtual machine the developer can still use open shift mechanisms like services and routes let's browse our web application using the OpenShift service it's the same wingtip toys application but this time the virtual machine is running on open shift but we're not done we want to containerize our application since it's a Windows virtual machine we can open a remote desktop session to it we see we have here Visual Studio and an asp.net application let's start container izing by moving the Microsoft sequel server database from running inside the Windows virtual machine to running on Red Hat Enterprise Linux as an open shipped container we'll go back to the open shipped Service Catalog this time we'll go to the database section and just as easily we'll create a sequel server container just need to accept the EULA provide password and choose the Edition we want and create a database and again we can see the sequel server is just another container running on OpenShift now let's take let's find the connection details for our database to keep this simple we'll take the IP address of our database service go back to the web application to visual studio update the IP address in the connection string publish our application and go back to browse it through OpenShift fortunately for us the user experience team heard we're modernizing our application so they pitched in and pushed new icons to use with our containerized database to also modernize the look and feel it's still the same wingtip toys application it's running in a virtual machine on openshift but it's now using a containerized database to recap we saw that we can run virtual machines natively on openshift like any other container based application modernize and mesh them together we containerize the database but we can use the same approach to containerize any part of our application so some items here to deserve repeating one thing you saw is Red Hat Enterprise Linux burning sequel server in a container on open shift and you also saw Windows VM where the dotnet native application also running inside of open ships so tell us what's special about that that seems pretty crazy what you did there exactly burr if we take a look under the hood we can use the kubernetes commands to see the list of our containers in this case the sequel server and the virtual machine containers but since Q Bert is a kubernetes operator we can actually use kubernetes commands like cube Cpl to list our virtual machines and manage our virtual machines like any other entity in kubernetes I love that so there's your crew meta gem oh we can see the kind says virtual machine that is totally awesome now people here are gonna be very excited about what they just saw we're gonna get more information and when will this be coming well you know what can they do to dive in this will be available as part of reddit Cloud suite in tech preview later this year but we are looking for early adopters now so give us a call also come check our deep dive session introducing container native virtualization Thursday 2:00 p.m. awesome that is so incredible so we went from the old to the new from the close to the open the Red Hat way you're gonna be seeing more from our demonstration team that's coming Thursday at 8 a.m. do not be late if you like what you saw this today you're gonna see a lot more of that going forward so we got some really special things in store for you so at this point thank you so much in tomorrow thank you so much you guys are awesome yeah now we have one more special guest a very early adopter of Red Hat Enterprise Linux we've had over a 12-year partnership and relationship with this organization they've been a steadfast Linux and middleware customer for many many years now please extend a warm welcome to Raj China from the Royal Bank of Canada thank you thank you it's great to be here RBC is a large global full-service is back we have the largest bank in Canada top 10 global operate in 30 countries and run five key business segments personal commercial banking investor in Treasury services capital markets wealth management and insurance but honestly unless you're in the banking segment those five business segments that I just mentioned may not mean a lot to you but what you might appreciate is the fact that we've been around in business for over 150 years we started our digital transformation journey about four years ago and we are focused on new and innovative technologies that will help deliver the capabilities and lifestyle our clients are looking for we have a very simple vision and we often refer to it as the digitally enabled bank of the future but as you can appreciate transforming a hundred fifty year old Bank is not easy it certainly does not happen overnight to that end we had a clear unwavering vision a very strong innovation agenda and most importantly a focus towards a flawless execution today in banking business strategy and IT strategy are one in the same they are not two separate things we believe that in order to be the number one bank we have to have the number one tactic there is no question that most of today's innovations happens in the open source community RBC relies on RedHat as a key partner to help us consume these open source innovations in a manner that it meets our enterprise needs RBC was an early adopter of Linux we operate one of the largest footprints of rel in Canada same with tables we had tremendous success in driving cost out of infrastructure by partnering with rahat while at the same time delivering a world-class hosting service to your business over our 12 year partnership Red Hat has proven that they have mastered the art of working closely with the upstream open source community understanding the needs of an enterprise like us in delivering these open source innovations in a manner that we can consume and build upon we are working with red hat to help increase our agility and better leverage public and private cloud offerings we adopted virtualization ansible and containers and are excited about continuing our partnership with Red Hat in this journey throughout this journey we simply cannot replace everything we've had from the past we have to bring forward these investments of the past and improve upon them with new and emerging technologies it is about utilizing emerging technologies but at the same time focusing on the business outcome the business outcome for us is serving our clients and delivering the information that they are looking for whenever they need it and in whatever form factor they're looking for but technology improvements alone are simply not sufficient to do a digital transformation creating the right culture of change and adopting new methodologies is key we introduced agile and DevOps which has boosted the number of adult projects at RBC and increase the frequency at which we do new releases to our mobile app as a matter of fact these methodologies have enabled us to deliver apps over 20x faster than before the other point about around culture that I wanted to mention was we wanted to build an engineering culture an engineering culture is one which rewards curiosity trying new things investing in new technologies and being a leader not necessarily a follower Red Hat has been a critical partner in our journey to date as we adopt elements of open source culture in engineering culture what you seen today about red hearts focus on new technology innovations while never losing sight of helping you bring forward the investments you've already made in the past is something that makes Red Hat unique we are excited to see red arts investment in leadership in open source technologies to help bring the potential of these amazing things together thank you that's great the thing you know seeing going from the old world to the new with automation so you know the things you've seen demonstrated today they're they're they're more sophisticated than any one company could ever have done on their own certainly not by using a proprietary development model because of this it's really easy to see why open source has become the center of gravity for enterprise computing today with all the progress open-source has made we're constantly looking for new ways of accelerating that into our products so we can take that into the enterprise with customers like these that you've met what you've met today now we recently made in addition to the Red Hat family we brought in core OS to the Red Hat family and you know adding core OS has really been our latest move to accelerate that innovation into our products this will help the adoption of open shift container platform even deeper into the enterprise and as we did with the Linux core platform in 2002 this is just exactly what we did with with Linux back then today we're announcing some exciting new technology directions first we'll integrate the benefits of automated operations so for example you'll see dramatic improvements in the automated intelligence about the state of your clusters in OpenShift with the core OS additions also as part of open shift will include a new variant of rel called Red Hat core OS maintaining the consistency of rel farhat for the operation side of the house while allowing for a consumption of over-the-air updates from the kernel to kubernetes later today you'll hear how we are extending automated operations beyond customers and even out to partners all of this starting with the next release of open shift in July now all of this of course will continue in an upstream open source innovation model that includes continuing container linux for the community users today while also evolving the commercial products to bring that innovation out to the enterprise this this combination is really defining the platform of the future everything we've done for the last 16 years since we first brought rel to the commercial market because get has been to get us just to this point hybrid cloud computing is now being deployed multiple times in enterprises every single day all powered by the open source model and powered by the open source model we will continue to redefine the software industry forever no in 2002 with all of you we made Linux the choice for enterprise computing this changed the innovation model forever and I started the session today talking about our prediction of seven years ago on the future being open we've all seen so much happen in those in those seven years we at Red Hat have celebrated our 25th anniversary including 16 years of rel and the enterprise it's now 2018 open hybrid cloud is not only a reality but it is the driving model in enterprise computing today and this hybrid cloud world would not even be possible without Linux as a platform in the open source development model a build around it and while we have think we may have accomplished a lot in that time and we may think we have changed the world a lot we have but I'm telling you the best is yet to come now that Linux and open source software is firmly driving that innovation in the enterprise what we've accomplished today and up till now has just set the stage for us together to change the world once again and just as we did with rel more than 15 years ago with our partners we will make hybrid cloud the default in the enterprise and I will take that bet every single day have a great show and have fun watching the future of computing unfold right in front of your eyes see you later [Applause] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] anytime [Music]

>> Announcer: Live, from Las Vegas, it's the Cube. Covering I.B.M. Think 2018. Brought to you by I.B.M. >> Welcome back to the Cube. We are live at I.B.M. Think 2018, our inaugural event. I'm Lisa Martin with Dave Vellante. We're joined by another Vegas veteran, as we all are. First time guest to the Cube, Bret Greenstein, the V.P. of Watson I.o.T. Offerings. Bret, welcome to the Cube. >> Thank you very much, exciting to be here. >> This is the inaugural Think 2018 event. >> Yes. >> 40,000 plus attendees, expected over 10 keynotes, lots of cool stuff. Speaking of cool stuff, I.o.T. What is happening in I.o.T. this year? >> Yeah, so we've been here in Vegas several times over the last several years talking about the Internet of Things, but what's really pivoted, what's really changed, is people talking about applied I.o.T. How are they using it to get business outcomes. Something different happening. And I think when we all started with the Internet of Things we talked a lot about, connecting stuff and devices. But really, it was always about the data and the effect that data had on changing business, changing user engagement, changing outcomes. And so here, on stage, you're going to see people talking about how their businesses have been changed, how their customers are changing as a result of I.o.T. >> Yeah so, I've always felt like I.o.T. is the intersection of devices, data, and machine intelligence. >> Bret: Yeah. >> How are those sort of three things coming together and what's the data model look like? >> Data model is every type of data. I think what people really didn't expect was it wasn't just machine data coming off sensors, temperatures, vibrations. It's all this unstructured data coming in from connected things that are everywhere in our lives. So sensors with cameras for example, being able to see. It's not just recorded images, but it's information. Tons of information that you need A.I. systems and other systems to interpret. So we're able to take all that data, structured data, numeric stuff coming off of devices and sensors, but images and sound and vibration. Even emotional content in people's dialogue. All of that is relevant to the Internet of Things. >> What's the conversation like with customers? For example, when we say, what physical assets do we have that we can instrument. >> Bret: Right. >> Parking meters or whatever, okay. >> Bret: Right. >> What physical assets don't we have that we should have? How can we leverage our existing data? What's the conversation like in terms of transformations that are going on? >> I think the conversations have shifted a lot. Over the couple years people were talking about we want to connect our thing, whatever the thing is, whether it's an elevator or car or whatever. We want to connect it, what does that mean? And that's shifted very quickly to customers who are coming in talking about information data and insights and they want to know, what should I do to get more of those insights? So I'm seeing customers now with Chief Data Officers or heads of digital transformation. Totally new roles that didn't exist before. And they're coming in with a data centric view. They're saying, we're going to be a digital business. We need to understand all of these live data about our customers and our things and our business process. Help us do that. And so that's much more than just instrumenting the individual devices now. And I find that conversation is really, really focused on the value of the data. >> What about the industry impact in this context? Do you see, does I.B.M.'s perspective, is I.o.T., it's certainly transformative. >> Bret: Right. >> But is it disruptive or it is sort of the guys with infrastructure are going to evolve to it? Is it more evolutionary, is it more disruptive? How do you see it? >> I think there's room for both. Obviously traditional players are going to instrument their business process. They're bringing in connected cars and all that. But you could also look at those same industries and say there's new players emerging who are coming in with software defined products that are digital by design. And they can come in and suddenly become leaders in their field. I don't think people would've expected companies like Tesla to be so disruptive in automotive, but coming in as electric changes the game without having to build on a hundred years of mechanical design. You're building on some new principles. And now we see some new players coming in to automotive who've never built cars at all before. Like Dyson for example, that recently announced they were working on electric cars. So I think a digital platform, a digital way of thinking, also creates opportunities for new entrance in every market. >> I think automobiles is a great example because it's an industry that hasn't been largely disrupted. But then you use an example of Tesla which is extremely innovative, you could actually pretend disruptions coming out. And you see whole ecosystems form around that. >> Right, right. And I think what was so powerful about the effect they had was it's a software defined product. The software in it is upgraded constantly. Sometimes you buy the car, the next day you get a new feature you didn't even expect. And this is the way we've come to appreciate, experience through mobile and everything else. Software that continues to improve products that get more valuable over time. Not less valuable over time. >> So let's talk about Watson and I.o.T. I'd also love to maybe take a slice on how I.B.M. is helping customers that maybe have been around maybe the flip side of a Tesla. They've been around a long time. How are they leveraging Watson and I.o.T. to transform their businesses? So kind of start with, what's new with Watson and I.o.T. >> Sure, so I mentioned before that there's a whole part of many data types now that previously were very hard to interpret through traditional analytics. But A.I. and machine learning give you the ability to absorb and consume some of that data. Unstructured sound, images, video, vibration, all of that stuff is now able to become part of a business process. So even traditional companies that have been around a long time can start to look at the data coming off of cameras, visual inspection in manufacturing, sound and voice for example. We work with Jefferson Hospital where they brought Watson into patients rooms so you could ask questions like visiting hours, or set the temperature. Put the patients in control of their experience in a hospital. That takes a traditional experience, like a hospital recovery room, and turns it into something A.I. driven, I.o.T. powered and puts the patient at the center. So very big changes can occur when you do that. >> How far do you see us being able to take A.I. in this whole world of I.o.T.? How far should we take it? >> I think we have to start become more appreciative of the power of machine learning to drive outcomes that are not as easily prescribed with code. So all of us, all of our business processes, all of our businesses will be enhanced with A.I. And we shouldn't look at that in any other way as a better tool to understand data in a way that's different than the way you interpret data. And so it wasn't long ago when big data just meant writing an algorithm across large volumes of data. And now we literally have algorithms whose job is to find patterns. Whose job is to understand data from training. And deliver an outcome that you couldn't have prescribed before. And so those type of problems, it just opens up a class of problems we can all solve now that we couldn't before. >> You're seeing a whole set of digital services emerge. The lingua franca is changing. It's sense, hear, see, respond. >> Bret: Right. >> Optimize. >> Right. >> Fix. (chuckles) >> And all that comes from comprehending. So having a system that can look. For example, I have a camera outside the window of my house and every once in a while I feed the images into Watson to see what it sees. When I first did it, it would say truck. But later, as we make Watson better, now it says FedEx truck or U.P.S. truck. It can read the writing, it can see the patterns. Every camera should know what it sees. Whether it's in a car or a home or somewhere else. Because it's much more valuable than just taking a picture and letting a human being interpret it later. So cameras should know what they see. Machines should know what they hear. Machines should tell us when they're about to break based on vibration or sound. And so this is possible with machine learning. >> So you're saying machines actually take on a whole new set of human-like activities. Digital twins is an example. >> Bret: Okay. >> What's your perspective on, let's start there, digital twins? >> Digital twins, for me, represents sort of the evolution of I.o.T. and that it's digitalizing things. And so, a thing that has no connectivity and very few sensors, is just a thing, it's just a box, it's a block. But as you start to put sensors on it and start to understand it's behavior, it's motion, it's vibration, it's location. Any of the mechanisms, the angels, all this stuff. Then you add a virtual representation of that thing. And if you can do that with all the things in your business, you can start to look for patterns. You can start to assess what's working and what's not working. So I think it just represents a true digitization of a business, of a class of objects in your business. >> Does I.o.T. make security a do-over in your opinion? >> No, but it certainly raises the bar. And so, when we all started connecting our computers to the internet, I remember everyone being panicked. It you put a disc in your machine, you might get a virus. Then we connected them to the internet, we all panicked, but the tools evolved and we start to get things that can help detect zero day problems. In the case of I.o.T. we've got these software defined products that are connected. That are inherently vulnerable cause they're in the real world. They can be touched by other things. So it raises the bar in the expectation of monitoring normal behavior for things. Monitoring all kinds of different threats and stuff, So companies like I.B.M. they focus so much on security and security services, we build that right into our platform so we can keep an eye on that. And also, when things occur, be able to push out new software that is protected. So for more updates, keeping the products live and current is a huge security protection. >> Bret, how would you describe the ecosystem. I.B.M.'s point of view on the ecosystem that you've got to form and catalog in order to succeed in I.o.T.? What does that look like? >> Yeah so, there are so many things for people to do in the world of I.o.T. That I.B.M. doesn't prescribe to do all of them, at all. There's certain things that we're really, really good at. We're certainly good at our cloud infrastructure and analytics and the platforms that enable this and deep industry knowledge. But the ability to apply that in businesses, to take on machine learning algorithms and make it work on the thousands of classes of machines in manufacturing, requires a huge partner ecosystem. So we work very openly on contributions to standards and open source. We certainly work with partners to build a lot of value around our stuff. So for example, on stage this week, we have several partners who are going to be up there. One of them is Harmen, who builds all kinds of things that's including info-tainment units in cars and the professional equipment that goes into hotels and buildings. So we work with them to build great innovative value together and they do things that they're experts in and we do what we're experts in. >> So, from an I.o.T. perspective, what are some of the cool things that are here at I.B.M. Think 2018, that those that are attending are going to get to see and feel and touch and smell? >> Well there are some things I can talk about, things that I can't. Tomorrow we have some very exciting announcements coming up. Going to talk a lot more about Watson and I.o.T. coming together, that's all I can say about that. You'll also see physical representations of things. There's a Jaguar Land Rover out here on the floor. To look at where we have contributed significantly to the engineering and the software development inside these kinds of products like J.L.R. So they're going to be up on stage talking about some of the things we're doing together. You'll hear A.B.B. here talking about some of the work we're doing around manufacturing techniques and helping manage wind turbines. So all kinds of really cool, industrial use cases. It's really exciting and I think working in I.o.T. is great because not only do you get to talk about the technology and the analytics and the data, but you actually get to see things. So it makes all of this feel very real when you walk up to and see a thing that's infused with I.o.T. and made better because of I.B.M. >> What inning are we in? >> What's that? >> What inning are we in? >> Oh it's still early, still early. Third inning still, mostly because so much of the market is still working to figure out how to take advantage of the data and the insights about this to transform their business. I think if you thought of the dot com era and how long it took for companies to emerge to be truly digital e-businesses, on demand businesses. The I.o.T. businesses, the A.I. driven businesses of the future, still very early. Some of them, you probably don't even know their names yet. But they're going to be the leaders that's coming. >> Do you think it'll happen faster because there is an internet? Or not so much because of the physical infrastructure that has to get built out? >> The infrastructure is actually not the gate at all. >> Dave: Okay. >> The real gate is the cultural difference of having people who are data driven, data thinkers. Having a leadership role in our clients. If you can think about it, mechanical things have dominated for a hundred years. Software engineers are still not even the most senior people in most of the companies that build physical things. But to have the data scientists, have the data leaders have a strong enough role to define business process. It's really the readiness and maturity of those data leaders. >> Yeah so the culture of a mechanical engineering culture that says "don't touch my things," >> Right. >> I'm not going to let a software engineer come in and mess with it because it works, it's secure, I trust it. >> Right. >> So that's the cultural one of the cultural dimensions. >> It's to look at what the data might mean. Just understand how your users use your things or if you want to understand what they're doing with those things somewhere else. Or even with the value of your insights of your users are and building entirely new ecosystems of the data of I.o.T. >> Alright, so we're in the third inning. We'll say the top of the third. >> Okay. >> But one of the things that you shared with us is that you're excited about is this is about applied I.o.T. To get business outcomes. >> Yes. >> Shared some examples that attendees of the event are going to hear from A.B.B., you mentioned, you mentioned the >> Bret: J.L.R. >> Land Rover that's here. Harman as well. And maybe some best practices for how to advise companies to get through some of those cultural hurdles, we'll say, to start embracing the opportunities that are within the I.o.T. space. >> I think the best thing people could do is to start to really, I'm going to say it again, put value on data science. It doesn't mean everyone has to be a data geek. But it does mean you have to have a certain value on the skills and the insights that come from a data driven business. What does it mean to make decisions in real time based on your customers? For a hundred years when companies shipped a washing machine it went into someone's house and sat for 10 years and they never heard from the person ever again until they bought another one 10 years later. But now when you ship a washing machine, you want people to connect it to the wi-fi. You want to know the features that are used. Suddenly as a manufacturer of things, you have to respect the data coming off those things because they inform you on how to design better. How to deliver better service and value. Which means those engineers who were the experts in washing machines, now have to be the experts in the data of washing machines and the data of their users. So, I would say, focus on the education, the recruitment, the enablement, the empowerment of people who are data centric by nature and who are looking for the transformation of a digital business from a physical business. >> Awesome, Bret thank you so much for stopping by the Cube and sharing your insights. >> You're very welcome. >> Good luck tomorrow with your presentations and we are going to be waiting on the edge of our seats for those lots of I.o.T. announcements. >> Very exciting. >> Very exciting. >> Okay. >> Alright you heard it here. >> Thank you so much. >> You can watch all of our good stuff on thecube.net live, of course, as we are now as well as the interviews that we've already done and those that we'll be doing for the next two days as our coverage continues of I.B.M. Think 2018. Also check out siliconangle.com our media site for all of your real time coverage of this event and others. For Dave Vellante and Bret, two Vegas Veterans, I'm Lisa Martin. Stick around, Dave and I are going to be right back after a short break. (upbeat music)

(techno music) >> Announcer: Live, from Silicon Valley, it's "the Cube," covering Mobile World Congress 2017. Brought to you by Mintel. >> Okay, welcome back everyone. We're here live in Palo Alto, California, covering Mobile World Congress, which is later in Spain right now, in Barcelona, it's gettin' close to bedtime, or, if you're a night owl, you're out hittin' the town, because Barcelona stays out very late, or just finishing your dinner. Of course, we'll bring in all theCube coverage here. News analysis, commentary, and of course, reaction to all the big mega-trends. And our next two guests is Guy Churchward who is the President and CEO of Data Torrent, formerly of EMC. You probably recognize him from theCube, from the EMC world, the many times he's been on. Cube alumni. And Phu Hoang, who's the co-founder and Chief Strategy Officer of Data Torrent. Co-founder, one of the founders. Also one of the early, early Yahoo engineers. I think he was the fourth engineer at Yahoo. Going way back on the 90s. Built that to a large scale. And Yahoo is credited for the invention of Hadoop, and many other great big data things. And we all know Yahoo was data-full. Guys, welcome to theCube's special coverage. Great to see you. >> Thank you so much. So I'm psyched that you guys came in, because, two things. I want to talk about the new opportunity at Data Torrent, and get some stories around the large scales experience that you guys have dealing with data. 'Cause you're in the middle of where this is intersecting with Mobile World Congress. Right now, Mobile World Congress is on the collision course between cloud-ready, classic enterprise network architectures with consumer, all happening at the same time. And data, with internet of things, is that going to be at the center of all the action? So, (laughing) these are not devices. So, that's the core theme. So, Guy, I want to get your take on, what attracted you to Data Torrent? What was the appeal for the opportunity? >> You mean, why am I here, why have I just arrived? >> I've always data-obsessed. You know this. From the days of running the storage business on their data protection, before that I was doing data analytics and security forensics. And if you look at, as you said, whether it's big data, or cloud, and the immersion of IOT, one thing's for sure, for me. It was never about big data, as in a big blob of stuff. It was all about small data sprawl. And the world's just getting more diverse by the second, and you can see that by Mobile World, right? The challenge then you have is, companies, they need to analyze their business. In other words, data analytics. About 30 years ago, when I was working for BA Systems, I remember meeting a general of the army. And he said the next war will be one in the data center, not on the battlegrounds. And so you really understand-- >> He's right about that. >> Yeah. And you have to be very, very close. So in other words, companies have started to obsess about what I call the do loop. And that really means, when data is created, and then ingesting the data, and getting insight from the data, and then actioning on that. And it's that do loop. And what you want to do, is you want to squeeze that down into a sub-second. And if you can run your analytics at the pace of your business, then you're in good shape. If you can't, you lose. And that means from a security perspective, or you're not going to win the bids. In any shape or form. That's not a business-- >> John: So speed is critical. >> Yeah, and people say, speed and accuracy. Because what you don't want to do is to run really really fast and fall off a cliff. So you really need to make sure that speed is there and accuracy is there. In the good old days, when I was running security forensics, you could either do complex end processing, which was a very small amount of information coming in and then querying it like crazy, or things like log management, where you would store data at rest, and then look at it afterwards. But now with the paradigm of all the technology catching up, so whether that's the disk space that you get, and the storage and the processing, and things like Hadoop with the clustering, you now break that paradigm. Where you can collect all the information from a business and process it before you land the data, and then get the insight out of it, and then action. So that was my thing, of looking and saying, look, this whole thing's going to happen. In last year -- >> And at large scale, too. I mean, what you're talking about in the theoretical side makes a lot of sense, but also putting that into large scale, is even more challenging. >> Yeah, we had, when I was going through the processes, dating, you know, to see whether was a company that made sense, I chatted one of our investors. And they're also a customer. And I said, why did you choose Data Torrent? And they said, "We tested everything in production, we tested all the competitive products out there, and we broke everything except Data Torrent. And actually, we tested you in production up to a billion events per second, and you didn't break. And we believe that that quantity is something that you need as a stepping stone to move forward." >> And what use cases does that fit for? Just give me some anecdotal (snaps fingers) billion transactions. At that speed, what's some use cases that really take advantage of that? >> They were mastering in, what I would call, industrialization of IT. So in other words, once you get into things like turbines, wind generation, train parts. We're going to be very very soon, looking out of a window and seeing -- >> John: So is it flow data? Is it the speed of the flow? Is it the feed of all the calculations, or both? >> It's a bit of both. And what I'll do, is I'll give Phu a chance, otherwise, we'll end up chatting about it. >> John: Phu, come on, you're the star. (laughing) When you founded this company, you had a background at Yahoo, which you built from scratch, but that was a first-mover opportunity, Web 1.0, as they say. That evolved up and then, everyone used Yahoo Finance. Everyone used Yahoo Search as a directory early on. And then everything just got bigger and bigger and bigger, and then you had to build your own stuff with Hadoop. >> Yeah. >> So you lived it. The telcos don't have the same problem. They actually got backed into the data, from being in the voice business, and then the data business. The data came after the voice. So what's the motivation behind Data Torrent? Tell us a little bit more. >> It's exactly what you say, actually. Going through the 12 years at Yahoo, and really, we learned big data the hard way. Making mistakes month after month, about how to do this thing right. We didn't have the money, and then we found out that, actually, proprietary systems of the shelf system that we thought were available, really couldn't do their jobs. So we had to invent our own technology, to deal with the kind of data processing that we had. At some point, Yahoo had a billion users using Yahoo at any given point in time, right? And the amount of impressions, the amount of clicks, the amount of activity, that a billion users have, onto the system. And all of the log files that you have to process to understand what's going on. On the other side of that, we need to be able to understand all of those activities in order to sell to our advertisers. Slice and dice behaviors and users, and so on. We didn't have the technology to do that. The only thing we knew how to do was, to have these cheap racks of cheap servers, that we were using to serve webpages. And we turned to that to say, this is what we're going to need to do, to solve these big data problems. And so, the idea of, okay we need to take this big problem and divide it into smaller pieces, so that we can run on these cheap servers, sort of became the core tenant of how we do distributor processing that became Hadoop, at the end of the day, right? >> You had big data come in because you were, big data-full, as we say. You weren't building software to solve someone else's problem. You had your own problem, you had a lot of data. You were full with data. >> Exactly. >> Had to go on a data diet, to your point. (crosstalk) >> And no one to turn to. >> And no one to turn to. >> All right. So let's spin this around or Mobile World Congress. 'Cause the big theme is, obviously, we all know what device is. In fact, we just released here on theCube early this morning Peter Burris pre-announced our new research initiative called IOTP. Which stands for Internet Of Things And People. And so now you add the complexity of people devices, whether that's going to be some sort of watch, phones, anything around them. That adds to the industrial aspect of turbines and what not. Internet of Things is a new edge architecture. So the data tsunami coming, besides the challenges of telcos to provision these devices, are going to be very challenging. So the question I want to ask you guys is, how do you see this evolving, because you have certainly connectivity. Yeah, you know, low latency, small little data coming from the windmills or whatever. Versus big high-dense bandwidth, mobility. And then you got network core issues, right. So how does this going to look like? Where does the data piece fit in? Because all aspects of this have data. What's your thoughts on this, and architecture. Tell us about your impressions, and the conversations you've had. >> First of all, I think data will exist everywhere. On the fringe, in the middle, at the center. And there's going to be data analytics and processing in every path of that. The challenge will be to kind of figure out what part of processing do you put on the fringe, what part do you put at the center. And I think that's a fluid thing that is going to be constantly changing. Going back to the telcos. We've had numbers of conversationw with telcos. And, yes we're helping them right now with their current set of issues around capacity management and billing, all those things. But they are also looking to the next step in their business. They're making all this money from provisioning, but they know they sit on top of this massive amount of really valuable data, from their customers. Every cellphone is sending them all of this data. And so there's a huge opportunity for them to monetize, or really produce value, back to their customers. And that could come in form of offers, to customers. But now you're talking about massive analytics targeting. That is also real-time, because if you're sending an offer to someone at a particular location, if you do that slowly, or in batch, and you give them an offer 10 minutes later, they're no longer where they are. They're 10 minutes away, right? >> Well, first two questions to follow up on that. One, do they know they have a data advantage opportunity here? Do they know that data is potentially a competitive advantage? >> From our conversation, they absolutely do. They're just trying to figure out, so what do we do here? It's new to them. >> I want to get both your perspectives. Guy, I want you to weigh in on this one, 'cause this is another theme that's coming out of the reporting and analysis from Mobile World Congress. This has come also from the cloud side as well. Integration now, is more important than ever, because, for instance, they might have an Oracle there, there might be Oracle databases outside their network. That they might want to tap into. So tapping other people's data. Not just what they can get, the telcos. It's going to be important. So how do you guys see the integration aspect, how we, top of the first inning, national anthem going on. I mean, where are we in this integration? There's a pregame, or, what inning are we in on this? >> Yeah, we're definitely not on the home run on it. I think our friend, and your friend Steve Manly, I sat down with him, and I gave him a brief, you know, what we were doing, and he was blown away by the technology and the opportunity, but he was certainly saying, but the challenge is the diversity of the data types. And then where they're going to be. Autonomic cars. You know each manufacturer will tell the car behind it, what it just experienced, but the question is, when will a Tesla tell a Range Rover, or tell a BMW? So you have actually -- >> They're different platforms, just different stats, it's a nightmare. >> Right. So in other words, >> And trackability. And whether it's going to be open APIs, whether it's technologies like Kafka. But the integration of that, and making sure that you can do transformation and then normalize it and drive it forward. It's kind of interesting, you know. You mentioned the telco space, and do they understand it. In some respects, what Phu went through with Yahoo, in other words, you go to a webpage, you pull it up, it knows you because of a cookie and it figures out, and then sells advertising to you on that page. Now think about you as a location, and you're walking past a Starbucks, and they want to sell you a coffee for ten cents less than they would normally do. They need to know you're there then. And this is the thing, and this is why real-time is going to be so critical. And similarly, like you said, you look out the window and you see DHL, or UPS, or FedEx drones out the window. You not only have an insight issue. You also have a security issue, you have a compliance issue, you have a locational issue. >> I think you're onto something. And I think I actually had this talk today with Steve Manly EMC World last year, around time series data. So this is interesting. Everyone wants to store everything, but it actually might not be worth anything anymore. If the drone is delivering your package, or whatever realtime data is in realtime, it's really important right there in realtime, or near realtime. It might not be worth anything after. But yet a purchase at a store, at a time, might be worth knowing that as a record to pull in. You get what I'm saying? So there's a notion of data that's interesting. >> And I think, and again, Phu's the expert. I'm still running up onto it. It's just a pet hobby, an obsession of mine. But the market has this term ETL. In other words, Extract, Transform, Land. Or load. But in essence, it's always talked about in that (mumbles) batch. In other words, I get the data, transform it, drop it, and then I have a look at it. We're going upside-down. So the idea now is to actually extract, transform, insight, action, then landing. So in other words, get the value at the fresh data, before it's the data late. Because if you set the data late, by default, it's actually stale. And actually, then there's the fascination of saying, if you're delivering realtime data to a person, you can't think fast enough to actually make a live decision. So therefore, you've almost got any information that comes to you, has to tier out. So it comes to a process. You get that fresh use of it, and then it drops into a data lake. And so I think there's using both, but I think what will you see in the market, and, again, you've experienced the disk flash momentum that happened last year. You're going to see that from a data source from at-rest, advanced, to real-time data streams on our applications next year. So I think the issue is, the formative year, and back to your, you know, get it right, get the integration, but make sure your APIs are there, talking to the right technologies. I think everything's going to be exciting this year and new and fresh and people really want to do it. Next year is going to be the year where you're going to see an absolute changing of the guards. >> And then also the SLA requirements, they'll start to get into this when you start looking at integration. >> You're absolutely right. Actually, the SLA part is actually very very important here. Because, as you move analytics from this back world, where it has, you do it once a day, and if it dies, it's okay, you just do it again. To where it is now continuous, 24 by 7, giving you insight continuously about your business, your people, your services, and so on. Then all of a sudden, it has to have the same characteristics as your business. Which is, it's 24 by 7, it can never go down, it can never lose data. So, all of a sudden you're putting tremendous requirements on an analytics system, which has, all the way from the beginning of history 'til now, been a very relaxed batch thing, to all of a sudden being something that is enterprise-grade, 24 by 7. And I think that that's actually where it's going to be the toughest nut to crack. >> So tell about some of the things that you've learned. And pretend for a second, let's pretend that you, as a co-founder at Data Torrent, and Guy, and you are teamed up. You guys run this telco. Let's just make one up, Verizon. Or AT&T, or pick one. And you sit there saying, okay, you've got the keys to the kingdom. And you can do whatever you want (laughing). You can be Donald Trump, or you can be whoever you want. You can fire everybody, or you can pick it over and run it. What would you do? You know you've got IOT. So this is business model innovation opportunities. I want you to put the technical hat on, plus knowing what you know around the business model opportunities. What do you do? You know IOT's an opportunity. Amazon is going after that heavily. Do you bolt a cloud together? Do you go after Amazon? Do you co-op with Amazon? Do you co-integrate? Do you grab the IOT? Do you use the data? I mean, given where we are today, what's the best move if we were consulting with this. >> You know, I will be the last person to be talking about giving advice to a telco. But since we are, we own our own telco here, and then we're pretending, I would say the following. IOT is going to happen, right? Earlier, when I say a billion people, that's just human beings. Once you now talk about censoring, you can program how many times they can send you data per second, then the growth in volume is immense, right? I think there's a huge opportunity, as a telco, in terms of the data that they have available and the insight that they could have about what's going on. That is not easy. I don't think that, as a telco, in the current DNA of a telco, I can go ahead and do all that analytics and really open up my business to the data insight layer. I would partner, and find a way-- >> Well, we're consulting, we're going to sit around and say hey, what do we have? We have relationship with the consumer, big marketing budgets. We can talk to them directly, we have access to their device. >> But you'll bifurcate the business. We're in the boardroom here, this is nothing more than that. But I would look at it and say look, you've got a consumer business, the same as in IOT. There's really, for me, there's three parts of IOT. There is the bit that I love which, you can geek out, which is basically the consumer market, which, there's no money in for a large-scale tenant, right, enterprise. And then you have the industrialization of IOT, which is I've got a leaky pipe, and I want a hardened device, ruggedized, which is wifi, so, now as a telco, I could create a IOT cloud, that allows me to put these devices out there, and in fact, I use Arlo, the little cameras. And they've got one now, where I can basically float it with its own cellular signal. So it's its own cellphone. That's a great use of IOT for that. And then you step to the consumer side of, I've got a cellphone, and then what I'll do is literally, in essence, riff off what Yahoo did in the early days and say, I'm now the new browser. The person's the browser. So in other words, follow the location, follow where he is, and then basically do locational-based advertising. >> By the way, you have to license the patent from our earlier guest, he'll say will he leak, 'cause he's got th6e patent on personal firewall for personal server. He's built a mobile personal server. >> Yeah. >> But this is the opportunity around wireless. Why I love the confusion, but the opportunity around wireless right now is, you can get bandwidth at high capacity. You have millimeter wave four, that doesn't go through walls, but you have other diverse frequencies and spectrum for instance, you can blend it all together to have that little drip signal, if you will, going into the cloud from the leaky pipe. Or if you need turbine, full-fat pipe, you maybe go somewhere. So, I think this is an interesting opportunity. >> And they're going to end up watching the data centers as well. There's still the gamut of saying our customer is going to continue to support their own data centers, or are there going to be one to a hundred data centers out there? And then how does selling a manufacturer or a telco play into that, and do they want to be that guy or not? >> Guy, Phu, thanks for coming in. I want to give you guys a chance to put a plug in for Data Torrent. Thanks for sharing some great commentary on the industry. So, what's up with you guys? Give us the update. Are you hiring? You growing? What are you guys doing? Customers? What's the update? Technology, innovations? >> So we've got a release coming out tomorrow which is a momentum release. I can't talk too much about the numbers, but in essence, from a fact base, we have a thing called a patchy apex. So it's open sourced, so you can use our product for free. But that's growing like gangbusters. From a top-level project, that's actually the fastest-growing one, and it's only been out for seven months. We just broke through 50,000 users on it. From our product, we're doing very well on the back of it. So we actually have subscription for the production side. >> So revenue is a subscription model. >> Yeah, and we meet both sides. So in other words, for the engineer who writes it, you've got the open source. And then when you put it into production, from the operations side, you can then license our products to enable you to manage an easy-- >> So when it gets commercialized, you pay as you go, when you use it. >> And you don't have to, if you don't want to. You've got all the tools to do it. But, we focus for our products group of, time to value, total cost of ownership. We're trying to bring Hadoop and real scale, realtime streaming to the masses. So what's the technology innovation? What's the disruptive enabler for you guys? >> I think we talked about it, right? You've got two really competing trends going on here. On one side, data is getting more and more and more massive. So it's going to take longer and longer to process it. Yet at the other side, business wants to be able to get data, have insight, and take action sub-second. So how do you get both at the same time? That's really the magic of the technology. >> Thanks for coming in. Great to meet you, Phu. I'd love to talk about the old Yahoo days, a total throwback, Web 1.0, a great time in history, pre-bubble bursting. Greatness happening in the valley and all around the world, and I remember those days clearly. Guy, great to see you. Congratulations on your new CEO committee. And great to have you on theCube. This is theCube bringing the coverage, and commentary, and reaction of Mobile World Congress here, in California. As everyone goes to bed in Barcelona, we're just gettin' down to the end of our day here in the afternoon in California. Be right back with more after this short break. (techno music)