(upbeat music) (logo crystals tingle) >> Hi, everybody, welcome back to FalCon22, I'm Dave Vellante and you're watching theCube's continuous coverage, this is day two. We live in an API economy, but APIs, you know, they're sometimes vulnerable, Michael Nicosia is here, he's the Chief Operating Officer and co-founder of Salt Security, API Security Specialist, Michael, welcome to theCUBE, thanks for coming on. >> Thank you so much, Dave, glad to be here. >> You're very welcome. Why did you and your co-founder, is it Roy? >> Yeah. >> Why did you guys start Salt Security? >> So really easy, I mean, as you mentioned, the proliferation of APIs constantly is growing on a year to year basis. So in 2015, when he and I met, we had this idea that it was going to continue to grow and APIs were going to be critical to every organization from an innovation perspective, from a safety perspective and we thought that current tools out there couldn't protect against the new threat vector that we thought was going to happen. And, you know, you fast forward to 2022 and here we are, it's the largest growing threat vector from an API perspective because APIs are just growing like crazy. >> Right. Well, let's talk about the news, CrowdStrike made an investment in your company. >> Michael: Yes. >> Congratulations. >> Michael: Thank you. >> Tell us about that, why it's important, and to have a strategic partner like that. >> Yeah, so first of all, we're super thrilled about the partnership, I mean, it's amazing. And not only the partnership, the strategic investment for us just signifies the importance of our two companies in terms of what we want to do in the field together or in the market together. So the strategic investment is amazing, the partnership is even more amazing just because it's kind of like, you know, the first in its class from an API security perspective, we've got partners from the cloud providers and then the only other partnerships really have is with API Management vendors. So this is unique in that it goes outside the security ecosystem to provide this partnership and the nice thing about it is it's exclusive, excuse me, and it just continues to validate the leadership where we have an API security, as well as obviously a leadership that CrowdStrike has. >> Exclusive in the sense that CrowdStrike's not going to invest in another API competitor and you're not going to take investment from an endpoint- >> Michael: Exactly. >> Or something like that. >> Endpoint or, you know, really cloud workload situation. >> Anything within that vastly expanding portfolio. >> Michael: Exactly. >> So pretty much anybody. >> Michael: Exactly. >> Except network security, from what I saw in the keynote yesterday, that's sort of on the table, for now. So, okay, so why should customers care about this? What's the benefit to them? >> Yeah, so if you think about, the security profile of organizations and where they seem to have potential risk, threat vectors, you know, endpoint, you know, Cloud obviously API becomes a bigger, threat vector as well. So I think the partnership just solidifies the fact that we want to create a better security profile for organizations and we want to make it safe for them to innovate and continue to do what they do. So I think that's the importance and when you put the two together it just creates a larger value proposition, more stickiness from end point to cloud, to APIs. >> So we have a partner, theCUBE, and in New York city and it's called ETR and they do quarterly surveys of CISOs, CIOs, IT buyers, about 12 to 1500 a quarter. And so I was chatting with those guys last week, they knew we were going to be at CrowdStrike and so they ran some data for all the API security vendors and you guys were, you know they had like the Gartner Magic Quadrant but it's not, you know, vision and execution, it's spending momentum and like presence in their survey, it's like market share, mind share. >> Sure. >> You guys were up and to the right, like, way, way, way ahead, I presume that's why you got the attention of CrowdStrike. I found their data set to be incredibly good, that's how we found CrowdStrike years ago, like, "Wow, who's this company?" >> Yeah. >> You know, companies like CrowdStrike, Okta, Zscaler, Snowflake Off The Charts, but you guys were really noticeable. Talk about the spending momentum you're seeing with customers, where's that coming from? >> Yeah, I mean look, for us it's a continuing growing market, it's accelerating and we're still in the, you know, early stages of the market, which is amazing. But if you think about what organizations do, they innovate, right, they innovate through, you know, software, through applications or APIs. So if you think about, you know, how do they continue to innovate safely? They need a solution, like Salt Security to protect from any bad actors that could potentially create any breaches, vulnerabilities. So I think that that's why CISOs in particular are super excited about talking to us, making sure that they have all of their bases covered especially when it comes to applications that they have within their organization, which continues to grow. >> And not to not to be a methodology geek, but the methodology they use is to essentially say, is a customer spending more or less, they subtract the lesses from the mores and that's what you're left with. And one of the lesses is churn, and if you have high churn, you're spending momentum, >> you know- >> Micheal: Yeah. >> In their methodology goes into the tank. So you have obviously admitted you have very low churn is that what you're saying in the field? >> Micheal: Absolutely. >> Why is that? >> Yeah, I mean, again, I think it's, it goes back to the value that we bring to customers. I think, you know, our solution works, we're the only AI/ML-based solution with deep context so we can really take a closer granular look at the APIs, model those APIs, create a baseline and really protect against them. So I mean, our solution works and it works really well and I think we provide value in that, you know, CISOs don't have to worry about any bad actors trying to infiltrate their applications 'cause they know that Salt Security is there protecting them. >> I know you're not the tech guy but you're the founder, co-founder of a technology company so you got to be conversant in the tech, 'cause this is the way it is in our business, so tell us about the tech, what's so cool about it? What's the differentiation? >> Yeah, I guess, and I mentioned that it's really AI/ML based, you know, we leverage big data and it's really the context associated to that, which means that, you know, we can get into granular details of really baselining the API itself. And what we do really well is, because these are unique attacks and these attacks could be days, weeks, months and we're the only vendor that, that can really correlate across that timeline because of the context-based big data that we leverage to be able to, you know, spot these potential bad actors that we look for. >> And all this happens in the cloud or? >> Absolutely, it's all... >> You have a server in your office? >> No, no, it's all it's a hundred percent SaaS-based, Cloud-based solution, I think that's one of the reasons why the partnership with CrowdStrike is so amazing as well. >> Talk a little bit more about the synergies between CrowdStrike and Salt Security. >> Tons of synergies, I mean, if you think about from, you know, from the part of being a little fluffy culture, the two companies have similar cultures, we go after similar you know, first Cloud, innovative companies. If you think about kind of the technology that CrowdStrike has put forth, revolutionized the endpoint security, and now moving into the Cloud, you know, leveraging AI and ML, we're doing the exact same thing so I think there's a lot of synergies associated with that. And again, the final point that I'll make is that you know, we think together the, you know, better together story is, resonates just because if you think about all of the areas that you know have potential breaches, these threats, we kind of cover 'em all with the partnership. >> When I talk to a founding, you know, co-founder, who's a go to market pro, I like to ask them how did you know when to scale? I mean, you got to have product market fit, I see so many companies failing because they try to go to market before they have, they try to scale go to market before they have product market, but how did you do it? How did you know when to scale? >> You know, it's tricky, and you got to look at a couple of, you know, factors, you got to look at the market, you got to look at, you know, how much potential opportunity exists and you really need to look at, the momentum that is being established. You know, when you talk to CISOs, kind of, you know, talking to them about projects and how, how they prioritize projects and where API security fits, you know, once it begins to be the top three and you start that momentum and obviously you bringing in the revenue. I think that those are signs that we see, that we say, "Okay, we need to double down on making sure we've got coverage across the world in order for us to support demand." >> And you were the first sales rep, right? >> Michael: Yeah. >> Okay. >> Roy and I, I was the first AE, here was the first SE. >> Okay, but your early go-to market pros are probably different than what you're bringing in today, you didn't have, you know, a lot of BDRs at the time, but you guys were hands on consultants- >> Absolutely. >> Like sort of process consultants, sales folks, right? And then you codify that when you're ready to scale and now you're, is that kind of a, what you're doing? >> Absolutely, I mean, you nailed it, I mean, it's in the early stages, it's validating that there's a problem that exists in the market and how important is that problem, you know, to CISOs. So when we first started we met probably about 50 CISOs where we just had that conversation, not about sales, it was more about, "Hey we just want to talk to you about a problem we think exists in the market, love to get your reaction on that problem and then obviously how you're solving that problem and how much of a priority is that problem," How important is it to you? And then once you have those discussions then you can really find those individuals, early adopters if you will, that are ready to buy and then it kind of proliferates from there. >> And then you have a CRO , I presume, right? So what was that like finding him or her, is a really important first sales hire. >> Super important, yeah. >> How did you go about that? How long did it take? >> Yeah so it took about six to eight months and you know it's really tough because, you know, we look at cultural fit, above everything else. So it's not, that, "Can they do the job?" it's culturally, do they fit in? And you know, how much can that individual scale the organization? So there's a lot of factors associated, there's a lot of individuals associated to, you know with the interview process. So that's how we looked at it and obviously we wanted somebody that had experience in a company our size, was able to scale it and so on. The one tricky thing is, and I'll tell you this, is, you know, for Roy and I, you kind of have to let go a little bit, that was really tough, so knowing that you need to do that is something that- >> A little bit of founderitis? >> Micheal: Yeah. >> Dave: It's hard, right? >> Micheal: It's hard. >> Dave: Yeah, it's your baby. >> It's like, whaat? >> I get it, Michael, thanks so much for coming to theCUBE, congratulations on the news- >> Thank you Dave. >> The investment and good luck. >> Awesome, thank you so much, appreciate it. >> You're really welcome. All right, keep it right there, we'll be back right after this short break. Dave Vellante for theCUBE at FalCon22, CrowdStrike's big user event, we'll be right back. (cheerful bouncy music)

(upbeat music) >> Hey welcome back everybody. Jeff Frick here with theCUBE. We're at San Francisco International at Gate 54B if you want to stop by and say hello. We're here for Alaska's Elevated Flying Experience launch. It's really an interesting opportunity. Alaska took advantage of the purchase of Virgin to kind of rethink the brand, rethink the branding of the planes, and add a bunch of new amenities. This is the one that you're going to care about more than any of the others, and we're really excited to have the founder and CEO of Salt & Straw the ice cream, Kim Malek. >> Hi! >> Great to meet you! >> Thank you! >> I am a huge fan! >> Aw! I appreciate that. >> I don't know how many hours I've stood in line and burned, waiting to get into your restaurant in Portland. >> Aw, thank you so much! >> So for folks that haven't stood in line for their Salt & Straw, give us a quick update on Salt & Straw, who you guys are, what you're all about. >> Yeah, so we started actually in 2011 as a little push cart which is a big deal in Portland, and we've grown now to 19 shops up and down the West Coast. We make all of our ice cream in 5 gallon batches, so we savor the smallest and we're the largest small batch ice cream company in the world and we're excited to have this new partnership with Alaska. >> Right, so I don't know kind of what the official industry categories are, but you would certainly be like in the super rich premium category. (laughter) Right. Really, really rich ingredients, fresh ingredients >> Yeah >> crazy flavors. >> So, each city that we operate in we make a different menu, so it reflects that city's local flavors, what's going on with the food scene and we make everything in house, so whether it's a brownie or rendering bone marrow, or making gummy bears ourselves, it's all made in house with great great care and love. >> I'm just curious if you have a feel for, you know, what is the formula for your success? Right, it's ice cream. There's a lot of ice cream choices, of course Farrell's was one of my favorite back at Portland >> Aw, I love Farrell's. Yeah. >> and they don't have that anymore at the zoo. But, what are some of the secrets to have, you know, "a commodity product" if you will, it's ice cream, but to build such a passionate following and really have people that are so connected to the product and the brand? >> Yeah, well we feel so fortunate to have this loyal following and I think it's really, you know we invest a lot in earning people's business and earning that attention, and so like I said, we have a different menu in every city that we operate in, we change our menu every 4 weeks, so it's reflective of what's happening locally and seasonally, and then when you come into our store, we try to offer a pretty special experience, so from the store design to the way we take care of people, they can sample through the whole menu. I was just at one of our stores and a customer said this is like a wine tasting, I mean I'm tasting all of these flavors, hearing the stories behind how they were made, and the collaborations that went into it, so we pack a lot into the experience. >> Right and so it's interesting that we are here at Alaska because Ben and the opening talked about really the culture and about people because the seat, it's kind of the same thing, a seat mile is a seat mile, so how do you differentiate your product and your offering, and he talked about values and wanting to work with companies that reflect the similar values. You're here, so tell the people why are you here at the Alaska event? >> I love that he talked about values. I noticed that as well and you know I think that's definitely one thing that we share, is a care for the people first and foremost. I mean, we scoop ice cream, but you know we offer people I think four days of training before they show up to actually start scooping ice cream, and that's all about you know, how to create connections with people, how to have a really special experience when someone is standing in front of you and how to connect. So, you know, we invest a lot in our team and I think that really shines through in the way that they take care of customers and I definitely see that when I fly with Alaska Airlines and it was one of the reasons I was so excited to be able to partner with them. >> Right, so we got to tell the people, so you can now get Salt & Straw on Alaska Airlines. >> Yeah, that's right, so just for a couple of months now we've been offering a little single serve container that we actually developed in conjunction with Alaska Airlines, so they helped us design the packaging, so that it would really fit with the experience that they were offering and then we launched it in the air and we don't really sell ice cream outside of our stores very much, so it was really a big deal to work with them on this project. >> Yeah and I would imagine in terms of the packaging and the experience, you're so dialed into that, that is such a part of your brand that you probably have a lot of, I would imagine initial concerns about making sure that was consistent with the brand that you guys represent. >> Yeah, definitely, I mean we had a lot of conversations about how they were going to handle the product, how they were going to educate their team about the ice cream so they can be communicating it with the people who were flying and they were of course there in spades and it was a really easy conversation to have. >> Alright, well Kim, thanks for, thanks for the ice cream earlier. >> Aw, thank you. >> And thanks for taking a few minutes. Congratulations and safe flying back to Portland. >> Awesome! I appreciate being here. Thank you! >> You're welcome! She's Kim, I'm Jeff, you're watching theCUBE. We're at San Francisco Gate 54B at the Alaska Airlines Better Experience. Thanks for watching. (upbeat music)

>> Announcer: Live from Nassau. (electronic music) Live from Nassau in The Bahamas, it's The Cube, covering Polygon '18, brought to you by Polymath. >> Welcome back, everyone. It's The Cube's exclusive coverage live in The Bahamas for Polycon '18. This is where all the action is, cryptocurrency, Bitcoin, blockchain, you name it, token economics, a paradigm shift of epic proportions. This is a decentralized internet. It's impacting the world. Missions, technology, applications, and all sectors. Our next guest, Shawn Owen, CEO of SALT Lending, serial entrepreneur, killer idea, so simple, so stupid simple. No one's doing it, he's doing it, lending cash for Bitcoin and currency. Welcome to The Cube. >> Thank you, it's good to be here. >> You know, there's two things that I love, the crazy ideas that everyone says is the dumbest idea on the planet that becomes billion-dollar opportunities, then something that's so simple and obvious that no one does because either a bag at your dogma or other interests. You're in kind of both. You got the simple idea, lending. Take a minute to talk about SALT Lending and your innovation that you guys do on the business side. >> Yeah, you got it. Everybody here at these conferences, or hopefully, people that are watching, have some interest in cryptocurrencies or blockchain, and probably accumulate some value in that currency, or the asset class. Once you do, then you have options, that you can either continue to hold that, or you can sell it. We're opening up a new market for the ability to see that as property and borrow against it. In fact, the technology makes a perfect form of collateral. We have all this ability to program in smart contracts. You can write in the rules. You can make it highly secure, yet nobody is doing it, so it's one of these simple things that, as this market emerges, became kind of obvious as a pain point, which is, I go to the bank, and I show them my personal financial statement, and they look at Bitcoin, and scratch their head. Somebody's got to bridge that gap, so we're building technology that ultimately should be used by banks or financial institutions to bring this together to where you have that ability like you would with any other type of property. If you look at any other type of property, you can lend against it, somebody's figured out how to, whether it's minerals, whether it's land, whether it's cars. Really now, we're doing that for cryptocurrency. SALT Lending stands for secured automated lending technology, so it's very much a technology-driven company, yet it's foundational in lending. It's just very simple to understand because it's the oldest business known to man. >> We covered cloud computing from day one. It's interesting, automation wins the day. We're seeing a lot of things where automating M&A process, we talked to those guys at LEXIT. You're doing something here with lending. You're just so simple. Here's the question, if I have Bitcoin, and there's a lot of whales walking around here, people, billionaires, millionaires, a lot of people have made money over the past couple of years. Certainly, if you were in it 2011 after, you're a whale. They got value. I put it up, and I get cash? Is that how it works? >> That's right. Everybody has assets that they want to hold onto, that are precious to them, whether it be gold, heirlooms, art, Bitcoin. Then they have currencies that are things that they want to spend quickly and/or just don't even think twice about it, I'll pay for a cup of coffee, a bottle of water, whatever. As the world moves into the blockchain era, as all value can be recorded on distributed ledgers in blockchains, you have this new way of thinking about everything. You can imagine a wallet where you have all the things you really care about, and you can dynamically decide what your currency is based off where you're traveling, where you want to spend, what you think is happening with inflation, depending on what your interest is. Maybe it's video game points you want to spend in the future. However, having that scale, and saying, at any point in time, I want to hold onto this, and I want to spend more of that, there's a partnership, right? A really easy way to think about that is, how can I leverage what I have, which is portfolio lending, or any type of lending, into more of the currencies I need, whether it's, I need to go buy a house, I need to buy a car, I want to buy more investments? We see it as a very powerful tool, and almost a necessity, but then, on top of that, just extremely cool in how you could imagine the future of finance in this world. >> Yeah, it's a total game-changer. I love what you're doing. I think, getting the fiat conversion really gets immediate liquidity in a currency that people can spend. If someone says, "Hey, I don't want Bitcoin," great, I want to buy a boat, or start a business, I need to get some fiat, I pledge up my coin. >> That's right. >> Now, you go valuation issues, so I'm assuming you have math behind this that says, "Hmm, but if Bitcoin drops..." >> Yep, that's the thing. We really solve a couple fundamental pieces of the blockchain that, at its core, are difficult for people to do well. One is security, and the other is user interface. When you wrap that into a product, and you build out the user interface and the security, suddenly, it becomes a lot easier. When it comes to the risk mitigation, it's simply over-collatoralized. We're going to pitch you as a borrower, and say, "You're already probably storing all this "somewhere anyway, in a wallet. "Why not put it in a secure wallet, "drive the loan to value ratio way down "so you're only borrowing what you need "when you need it, you don't bring out "these giant loans for no good reason, "you just borrow what you need, "the interest rate becomes a lot lower, "and then you have extra collateral for the volatility?" Ideally, that's the scenario. If, in a world where it's very volatile, and you're at a higher loan value rate, then that's where we give you options. We say, "Hey, would you like to sell some of this, "or would you like to add more? "Would you like to prepay your loan if not?" There's always the option for somebody to correct the loan instrument, but that's the other really cool part about a smart contract, or a smart written language around the instrument itself, is that you can get a little more creative. Instead of just having legal paperwork, you can say, "Let's put this into the code." It becomes very dynamic in the ability for it to cure, the instrument itself, to stay course. >> Software money, I love this. Let's go down, talk about the token that you have, SALT Token, and that's for the borrower, or the lender? >> It's, right now, the borrower, although it will expand into all uses. It's effectively, as people say, it's powering the network, or it's the gasoline behind it. It's our internal currency. It acts as a store value in the regards of how you would think about a serial number. If I have Microsoft Office, and you buy a serial number, that's the key that lets you in, and it tells you how much of the product you have. If you have 20 or 30 of them, you can give them to your employees, or you could redeem it for some other value. We just think that tokens actually do a better job of that recording 'cause it's now put on a permanent ledger. You have the permanent auditability of it, than just a serial number in a private database. >> I think you got a great solution because the alternative to not having it is essentially, get a liquid on an exchange, which some people might not want to do. Then also, where do you do it, right? There's all kinds of dynamics on the exchange side. Here, I'm saying, I'm long on Bitcoin, but I need to get some working capital for whatever the project is, so you're there. Is there any competition? Is anyone else doing this? >> There's no competition yet. There's definitely some people that are out there saying that they are, and I would be careful. Some of them may be legitimate. We've seen a few that are scams, so always be protected, and be wary. >> John: Give an example of what a scam would look like for the people. >> A scam would be somebody who says, "Hey, we're doing an ICO," and you start looking at it, and it looks exactly like what we've built, except for they're, maybe, in Russia, and you can't actually contact the people, and they don't have any banks behind them, or any kind of regulatory framework. >> They're spoofing your brand. >> Yeah, we've seen a lot of that. We've had a lot of phishing attempts, and people trying to spoof the idea or the site, and that's a little worrisome, but there probably will be competitors. It's a big market. >> Yeah, that's going to happen more and more, more of those spear phishing attacks too. Great, and outlook for you guys. Where are you guys at with the company? Talk about what your needs are. You hiring? What's going on with the operation? >> Yeah, we're constantly hiring, looking for anybody who's got great financial background and wants to be in the blockchain space, and/or developers, constantly looking for blockchain-focused developers, people that either want to learn the space, or already know the space, either way is fine. We'd love to talk to you. We've issued $30 million in loans in the states we're approved. We're rapidly expanding that genre of where we can lend. We're working to partner with banks, so if you're a bank, or you're a financial institution, there's a lot of capital money at this conference, we'd love to talk to all you guys because there's an opportunity for us to give you an indirect exposure into the market. >> It's good for the big whales who have a lot of currency, a lot of value, to pay it forward in the mission, in the community. They could be lenders too, right? >> Very much so, yes. >> Wow, so what states aren't you in? 30 million, that's a good number. What's your top list? >> The next on the list that we're working towards, we're really close to Texas, we're really close to California, really close to New York, really close to Utah. Those are some big ones. Lots of interest in Puerto Rico, so we're heavily focused on getting there, and it's just a road map, a heat map. There's a lot of interest in Europe, so we're going over into Europe, lots in Canada. >> Shawn, thanks for coming on, sharing the project, your success. Love your idea, again. Disruption continues. The stampede is coming behind us at Polycon. That's their logo. Polymath is the company behind this event. Of course, we're The Cube, we're independent, we're bringing you all the action here at Polycon '18. More live coverage after this short break. (electronic music)

>>The Cube presents UI Path Forward five. Brought to you by UI Path. >>Hi everybody. We're back at UI path forward to five. This is Dave Ante with Dave Nicholson. Derek Mu is here. He's automation product line lead for Merck. Thank you, by the way, for, you know, all you guys do, and thank you Dave for having in the, in the, in the vaccine area, saving our butts. And Bill Engel is back on the cube. He's the director at cgi. Guys, good to see you again. >>Good to see you. Thank >>You. So Merrick, Wow, it's been quite a few years for you guys. Take us through Derek, what's happening in sort of your world that's informing your automation strategy? >>Well, Dave, I mean as you know, we just came out of the pandemic. We actually have quite a few products like Gabriel Antiviral Pill. Obviously we worked, you know, continue to drive our products through a difficult time. But, you know, is during these can last few years that, you know, we've accelerated our journey in automation. We're about four years plus in our journey, you know, so just like the theme of this conference we're we're trying to move towards, you know, bigger automations, transformational change, continue to drive digital transformation in our company. >>Now Bill, you've been on before, but CGI tell people about the firm. It's not computer graphics imaging. >>Sure. No, it's, it's definitely not. So cgi, we're a global consultancy about 90,000 folks across the world. We're a, we're both a product company and a services company. So we have a lot of different, you know, software products that we deliver to our clients, such as CGI Advantage, which is a state local government EER P platform. And so outside of that, we, my team does automation and so we wrap automation around R IP and deliver that to our clients. >>So you guys are automation pros, implementation partners, right? So, so let's go back. Yep. Derek said four years I think. Yep. Right, You're in. So take us through what was the catalyst, how did you get started? Obviously it was pre pandemic, so it's interesting, a lot of companies pre pandemic gave lip service to digital transformation. Sounds like you guys already started your journey, but I'll come back to that. But take us back to the Catalyst four years ago. Why automation? We'll get into why UI path, >>Right. So I, I would say it started pretty niche in our company. Started first in our finance area. Of course, you know, we were looking in technology evaluating different companies, Blue Prism, ui P. Ultimately we chose UI p did it on-prem to start to use automation in sort of our invoice processing, sort of our financial processes, right? And then from there, after it was really when the pandemic hit, that's when sort of we all went to remote work. That's when the team, the COE continued to scale up, especially during pandemic. We were trying to automate more and more processes given the fact that more and more of our workers are remote, they reprocesses. How, how do you do events? You know, part of our livelihood is, is meeting with engaging with customers. Customers in this case is, are doctors and physicians, right? How do you engage with them digitally? How do you, you know, you know, a lot of the face to face contact now have to kind of shift to more digital, digital way. And so automation was a way to kind of help accelerate that, help facilitate that. >>You, you, I think you mentioned COE as in center of excellence. Yep. So, so describe your approach to implementing automation. It's, that sounds like when you say center, it sounds like something is centralized as, as opposed to a bunch of what we've been hearing a lot about citizen developers. What does that interaction >>Look like? We do have both. I would say in the beginning was more decentralized, but over time we, over the few years as, as we built more and more bots, we're now at maybe somewhere between four to 500 bots. We now have sort of internal to the company functional verticals, right? So there's an animal health, we have an animal health function. So there's, there's a team building engaging with the animal health business to build animal health box. There's human health, which is what I work on as well as hr, finance, manufacturing, research. And so internally there's engagement leads, one of the engagement leads that interact with the business. Then when there's an engineering squads that help build and design, develop and support and maintain those as well as sort of a DevOps team that supports the platform and maintains all the bot infrastructure. >>So you started in finance common story, right? I'm sure you hear this a lot Belt, How did you decide what to target? Was it, was it process driven decision? Was it, was it data oriented? Like some kind of combination? How did you decide, Do you remember? Or do you, could you take >>Us back to Oh yeah. So for, for cgi how we started to engage with MER is, you know, we, we do a lot of other business with Merck. We work on all their different business lines and we, we understand the business process. So we, we knew where there was potential for automation. So we brought those ideas to Merck and, and really kind of landed there and helped them realize the value from automation from that standpoint. And then from there the journey just continued to expand, you know, looking for those use cases that, that, you know, fit the mold for, for, for RPA to start. And now the evolution is to go to broader hyper automation. >>And, and was it CFO led into the finance department and then, or was it sort of more bottoms >>Up? Yeah, so, so I think it started in, in finance and, and, but we actually really started out in the business line. So out in regulatory clinical, that's, that's where we, we have the life science expertise that are embedded. And so I partnered with them to come up with, hey, here's a real solution we could do to help streamline, say submission archiving. So when, when submissions come back from the fda, they need to be archived into, you know, the, their system of record. So that's, those are the types of use cases that, that we helped automate. >>Okay. Cause you're saying a human had to sort physically archive that and you were able to sort of replicate that. Okay. And you started with software robots, obviously rpa and now you're expanding into, we we're hearing from UI this the platform message. How does that coincide Derek, with what you guys are doing? Are you sort of adding platform? What aspects of the platform are, are you adding? >>Yeah, no, I mean we are, we are on-premise, right? So we have the platform, but some of the cool things we just had, another colleague of mine presented earlier today. Some of the cool things we're, we're doing ephemeral infrastructure. So infrastructure as code, which essentially means instead of having all these dedicated bot machines, that that, you know, cuz these bots only in some cases run 10 minutes and they're done. So we're, we're soon of doing all on demand, you know, start up a server, run the bot when it's finished, you know, kill the server. So we only pay for the servers that we use, which allows us to save a whole >>Lot of money. Serverless bots. So you, but you're doing that OnPrem, so you >>No, >>No, but >>That's >>Cloud. We, >>We, we we're doing it OnPrem, but our, our bot machines that actually run the, let's say SAP process, right? We spin that machine up, it's on the cloud, it runs it finish, Let's say it's processed in one hour and then when it's done, we kill that machine. So we only play for that one hour usage of that bot machine. >>Okay. So you mentioned SAP earlier you mentioned Blue Prism when you probably looked at other competitors too. You pull the Gartner Magic quadrant, blah, blah, you know, with the way people, you know, evaluate technology, but SAP's got a product. Why UI path mean? Is it that a company like SAP two narrow for their only sap you wanted to apply it other ways? Maybe they weren't even in the business that back then four years ago they probably weren't. Right? But I'm curious as to how the decision was made for UiPath. >>Well, I think you hit it right on the nail. You know, SAP sort of came on a little later and they're specific to sort of their function, right? So UiPath for us is the most flexible tool can interact by UI to our sales and marketing systems, to, to workday, to service Now. It's, it cuts across every function that we have in the company as well as you're the most mature. I mean, you're the market leader, right? So Right. Definitely you, you continue to build upon those capabilities and we are exploring the new capabilities, especially being announced today. >>And what do you see Bill in the marketplace? Are you, are you kind of automation tool agnostic? Are you more sort of all in on? I >>Would say we are, we are agnostic as a company, but obviously as part of a, as an automation practice lead, you know, I want to deliver solutions to my clients that are gonna benefit them as a whole. So looking at UI path, you know, that this platform is, it covers the end to end spectrum of, of automation. So I can go really into any use case and be able to provide a solution that, that delivers value. And so that's, that's where I see the value in UI path and that's why CGI is, is a customer as well. We automate our internal processes. We actually have, we just launched probably SALT in the, in the market last week, expanded partnership with UiPath. We launched CGI, Excel 360. That's our fully managed service around automation. We host our clients whole UI path infrastructure and bots. It's completely hands off to them and they just get the value outta >>Automation. Nice, nice. Love >>It. Derek, you mentioned, you mentioned this ephemeral infrastructure. Yeah. Sounds like it's also ethereal possibility possibly you're saying, you, you're saying you have processes that are running on premises, right? But then you reach out to have an automation process run that's happening off pre and you're, and you're sort of, >>It's on the cloud, so, so yeah, so we have a in-house orchestrator, so we don't, we're not using your sort of on the cloud orchestrator. So, so we brought it in-house for security reasons. Okay. But we use, you know, so inside the vpn, you know, we have these cloud machines that run these automations. So, so that's, that's the ephemeral side of the, of the >>Infrastructure. But is there a financial angle to that in terms of when you're spinning these things up, are you, is it a, is it a pay by the drink or by the, by the CPU >>Hours, if you can imagine like we, you know, like I mentioned where somewhere between four to 500 bots and every bot has a time slot to run and takes a certain amount of time. And so that's hundreds and hundreds of bot machines that we in the old days have to have to buy and procure and, you know, staff and support and maintain. So in this new model, and we're just beginning to kind of move from pilot into implementation, we're moving all, all of bots this in ephemeral infrastructure, right? So these, okay, these machines, these bot machines are, you know, spun up. They run the, they, they run their automation and then they spin >>Down. But just to be clear, they're being spun up on physical infrastructure that is in your >>Purview and they spun up on aws. Yeah. Okay. And then they spin down. Okay, got >>It. Got it. Interesting. Four >>To 500 bots. You know, Daniel one point play out this vision of a bot chicken in every pot, I called it a bot for every employee. Is that where you're headed or is that kind of in this new ephemeral world, not necessary, it's like maybe every employee has access to an ephemeral bot. How, how are you thinking about that? >>That's a good question. So obviously the, the four to 500 is a mix of unattended bonds versus attended bonds, right? That, that we also have a citizen developer, sort of a group team. We support that as well from a coe. So, you know, we see the future as a mix. There's, there's a spectrum of, we are the professional development team. There's also, we support and nurture the personal automation and we provide the resources to help them build smaller scale automations that help, you know, reduce the, you know, the mundaneness and the hours of their own tasks. But you know, for us, we want to focus more and more on building bigger and bigger transfer transformational automations that really drive process efficiencies and, and savings. >>And what's the, what's the business impact been? You mentioned savings and maybe there's other sort of productivity. How do you measure the benefit, the ROI and, and >>Quantify that we, you know, I, I don't, I don't profess I don't think we have all the right answers, but yeah, simple metrics like number of hours saved or other sort of excitement sort of in like an nps, internal NPS between the different groups that we engage. But we definitely see automation demand coming from our, our functional teams going up, driving up. So it's, it's continued to be a hot area and hopefully we, we can, you know, like, like what the key message and theme of this, of this conference. Essentially we want to take and build upon the, the good work that we've done in terms of rpa and we want to drive it more towards digital transformation. >>So Bill, what are you seeing across the, your customer base in terms of, of, of roi? I'm not looking for percentages there. I'm sure they're off the charts, but in terms of, you know, you can optimize for fast payback, you know, maybe lower the denominator, you know, or you can optimize for, you know, net benefit over time, right? You know, what are you seeing? What are customers after they want fast payback and little quick hits? Or are they looking for sort of a bigger enterprise wide impact? >>Yeah, I think it's, it's the latter. It's that larger impact, right? Obviously they, you know, they want an roi and just depending upon the use case, that's gonna vary in terms of the, the benefits delivered. And a lot of our clients, depending on the industry, so in in life sciences it may be around, you know, compliance like GXP compliance is huge. And so that may may not be much of a time saver, but it ensures that they're, they're running their processes and they're being compliant with, you know, federal standards. So that's, that's one aspect to it. But you know, to, you know, a bank, they're looking to reduce their overall costs and and so on. But yeah, I think, I think the other, the other part of it is, you know, impacting broader business processes. So taking that top down approach versus kind of bottom up, you know, doing ta you know, the ones you choose the tasks is not as impactful as looking at broader across the entire business process and seeing how we can impact >>It. Now, Derek, when you guys support a citizen developer, how does that work? So, hey, I got this task I want to automate, I'm gonna go write a, you know, software robot. I'm gonna go do an automation. Do I just do it and then throw her to the defense? You guys, you guys send me a video on how to do it. Hold my hand. How's that work? >>Yeah, I mean, good question. So, so we obviously direct them to the UI path Academy, get some training. We also have some internal training materials to how to build a bot sort of internal inside Merck. We, we go through, we have writeups and SOPs on using the right framework for automations, using the right documentation, PDD kind of materials, and then ultimately how do we deploy bot inside the MER ecosystem. But I, I, maybe I'll just add, I think you asked the point about ROI before. Yeah. I'll also say because we're, we're a pharmaceutical company. I think one of the other key metrics is actually time saved, right? So if, if, if we have a bot that helps us get through the clinical process or even the getting a, a label approved faster, even if it's eight days saved, that's eight days of a product that can get out to the market faster to, to our patients and, and healthcare professionals. And that's, that, that's immeasurable benefit. >>Yeah, I bet if you compress that ELAP time of, of getting approval and so forth. All right guys, we've gotta go. Thanks so much. Congratulations on all the success and appreciate you sharing your story. Thank >>You so much. Appreciate it. You're welcome. >>Appreciate it. All right. Thank you for watching this Dave Ante for Dave Nicholson, The cubes coverage, two day coverage. We're here in day one, UI path forward, five. We'll be right back right after the short break. Awesome. >>Great.

>> From The Cube Studios in Palo Alto and Boston, bringing you data driven insights from The Cube at ETR. This is "Breaking Analysis" with Dave Vellante. >> The reverse momentum in tech stocks caused by rising interest rates, less attractive discounted cash flow models, and more tepid forward guidance, can be easily measured by public market valuations. And while there's lots of discussion about the impact on private companies and cash runway and 409A valuations, measuring the performance of non-public companies isn't as easy. IPOs have dried up and public statements by private companies, of course, they accentuate the good and they kind of hide the bad. Real data, unless you're an insider, is hard to find. Hello and welcome to this week's "Wikibon Cube Insights" powered by ETR. In this "Breaking Analysis", we unlock some of the secrets that non-public, emerging tech companies may or may not be sharing. And we do this by introducing you to a capability from ETR that we've not exposed you to over the past couple of years, it's called the Emerging Technologies Survey, and it is packed with sentiment data and performance data based on surveys of more than a thousand CIOs and IT buyers covering more than 400 companies. And we've invited back our colleague, Erik Bradley of ETR to help explain the survey and the data that we're going to cover today. Erik, this survey is something that I've not personally spent much time on, but I'm blown away at the data. It's really unique and detailed. First of all, welcome. Good to see you again. >> Great to see you too, Dave, and I'm really happy to be talking about the ETS or the Emerging Technology Survey. Even our own clients of constituents probably don't spend as much time in here as they should. >> Yeah, because there's so much in the mainstream, but let's pull up a slide to bring out the survey composition. Tell us about the study. How often do you run it? What's the background and the methodology? >> Yeah, you were just spot on the way you were talking about the private tech companies out there. So what we did is we decided to take all the vendors that we track that are not yet public and move 'em over to the ETS. And there isn't a lot of information out there. If you're not in Silicon (indistinct), you're not going to get this stuff. So PitchBook and Tech Crunch are two out there that gives some data on these guys. But what we really wanted to do was go out to our community. We have 6,000, ITDMs in our community. We wanted to ask them, "Are you aware of these companies? And if so, are you allocating any resources to them? Are you planning to evaluate them," and really just kind of figure out what we can do. So this particular survey, as you can see, 1000 plus responses, over 450 vendors that we track. And essentially what we're trying to do here is talk about your evaluation and awareness of these companies and also your utilization. And also if you're not utilizing 'em, then we can also figure out your sales conversion or churn. So this is interesting, not only for the ITDMs themselves to figure out what their peers are evaluating and what they should put in POCs against the big guys when contracts come up. But it's also really interesting for the tech vendors themselves to see how they're performing. >> And you can see 2/3 of the respondents are director level of above. You got 28% is C-suite. There is of course a North America bias, 70, 75% is North America. But these smaller companies, you know, that's when they start doing business. So, okay. We're going to do a couple of things here today. First, we're going to give you the big picture across the sectors that ETR covers within the ETS survey. And then we're going to look at the high and low sentiment for the larger private companies. And then we're going to do the same for the smaller private companies, the ones that don't have as much mindshare. And then I'm going to put those two groups together and we're going to look at two dimensions, actually three dimensions, which companies are being evaluated the most. Second, companies are getting the most usage and adoption of their offerings. And then third, which companies are seeing the highest churn rates, which of course is a silent killer of companies. And then finally, we're going to look at the sentiment and mindshare for two key areas that we like to cover often here on "Breaking Analysis", security and data. And data comprises database, including data warehousing, and then big data analytics is the second part of data. And then machine learning and AI is the third section within data that we're going to look at. Now, one other thing before we get into it, ETR very often will include open source offerings in the mix, even though they're not companies like TensorFlow or Kubernetes, for example. And we'll call that out during this discussion. The reason this is done is for context, because everyone is using open source. It is the heart of innovation and many business models are super glued to an open source offering, like take MariaDB, for example. There's the foundation and then there's with the open source code and then there, of course, the company that sells services around the offering. Okay, so let's first look at the highest and lowest sentiment among these private firms, the ones that have the highest mindshare. So they're naturally going to be somewhat larger. And we do this on two dimensions, sentiment on the vertical axis and mindshare on the horizontal axis and note the open source tool, see Kubernetes, Postgres, Kafka, TensorFlow, Jenkins, Grafana, et cetera. So Erik, please explain what we're looking at here, how it's derived and what the data tells us. >> Certainly, so there is a lot here, so we're going to break it down first of all by explaining just what mindshare and net sentiment is. You explain the axis. We have so many evaluation metrics, but we need to aggregate them into one so that way we can rank against each other. Net sentiment is really the aggregation of all the positive and subtracting out the negative. So the net sentiment is a very quick way of looking at where these companies stand versus their peers in their sectors and sub sectors. Mindshare is basically the awareness of them, which is good for very early stage companies. And you'll see some names on here that are obviously been around for a very long time. And they're clearly be the bigger on the axis on the outside. Kubernetes, for instance, as you mentioned, is open source. This de facto standard for all container orchestration, and it should be that far up into the right, because that's what everyone's using. In fact, the open source leaders are so prevalent in the emerging technology survey that we break them out later in our analysis, 'cause it's really not fair to include them and compare them to the actual companies that are providing the support and the security around that open source technology. But no survey, no analysis, no research would be complete without including these open source tech. So what we're looking at here, if I can just get away from the open source names, we see other things like Databricks and OneTrust . They're repeating as top net sentiment performers here. And then also the design vendors. People don't spend a lot of time on 'em, but Miro and Figma. This is their third survey in a row where they're just dominating that sentiment overall. And Adobe should probably take note of that because they're really coming after them. But Databricks, we all know probably would've been a public company by now if the market hadn't turned, but you can see just how dominant they are in a survey of nothing but private companies. And we'll see that again when we talk about the database later. >> And I'll just add, so you see automation anywhere on there, the big UiPath competitor company that was not able to get to the public markets. They've been trying. Snyk, Peter McKay's company, they've raised a bunch of money, big security player. They're doing some really interesting things in developer security, helping developers secure the data flow, H2O.ai, Dataiku AI company. We saw them at the Snowflake Summit. Redis Labs, Netskope and security. So a lot of names that we know that ultimately we think are probably going to be hitting the public market. Okay, here's the same view for private companies with less mindshare, Erik. Take us through this one. >> On the previous slide too real quickly, I wanted to pull that security scorecard and we'll get back into it. But this is a newcomer, that I couldn't believe how strong their data was, but we'll bring that up in a second. Now, when we go to the ones of lower mindshare, it's interesting to talk about open source, right? Kubernetes was all the way on the top right. Everyone uses containers. Here we see Istio up there. Not everyone is using service mesh as much. And that's why Istio is in the smaller breakout. But still when you talk about net sentiment, it's about the leader, it's the highest one there is. So really interesting to point out. Then we see other names like Collibra in the data side really performing well. And again, as always security, very well represented here. We have Aqua, Wiz, Armis, which is a standout in this survey this time around. They do IoT security. I hadn't even heard of them until I started digging into the data here. And I couldn't believe how well they were doing. And then of course you have AnyScale, which is doing a second best in this and the best name in the survey Hugging Face, which is a machine learning AI tool. Also doing really well on a net sentiment, but they're not as far along on that access of mindshare just yet. So these are again, emerging companies that might not be as well represented in the enterprise as they will be in a couple of years. >> Hugging Face sounds like something you do with your two year old. Like you said, you see high performers, AnyScale do machine learning and you mentioned them. They came out of Berkeley. Collibra Governance, InfluxData is on there. InfluxDB's a time series database. And yeah, of course, Alex, if you bring that back up, you get a big group of red dots, right? That's the bad zone, I guess, which Sisense does vis, Yellowbrick Data is a NPP database. How should we interpret the red dots, Erik? I mean, is it necessarily a bad thing? Could it be misinterpreted? What's your take on that? >> Sure, well, let me just explain the definition of it first from a data science perspective, right? We're a data company first. So the gray dots that you're seeing that aren't named, that's the mean that's the average. So in order for you to be on this chart, you have to be at least one standard deviation above or below that average. So that gray is where we're saying, "Hey, this is where the lump of average comes in. This is where everyone normally stands." So you either have to be an outperformer or an underperformer to even show up in this analysis. So by definition, yes, the red dots are bad. You're at least one standard deviation below the average of your peers. It's not where you want to be. And if you're on the lower left, not only are you not performing well from a utilization or an actual usage rate, but people don't even know who you are. So that's a problem, obviously. And the VCs and the PEs out there that are backing these companies, they're the ones who mostly are interested in this data. >> Yeah. Oh, that's great explanation. Thank you for that. No, nice benchmarking there and yeah, you don't want to be in the red. All right, let's get into the next segment here. Here going to look at evaluation rates, adoption and the all important churn. First new evaluations. Let's bring up that slide. And Erik, take us through this. >> So essentially I just want to explain what evaluation means is that people will cite that they either plan to evaluate the company or they're currently evaluating. So that means we're aware of 'em and we are choosing to do a POC of them. And then we'll see later how that turns into utilization, which is what a company wants to see, awareness, evaluation, and then actually utilizing them. That's sort of the life cycle for these emerging companies. So what we're seeing here, again, with very high evaluation rates. H2O, we mentioned. SecurityScorecard jumped up again. Chargebee, Snyk, Salt Security, Armis. A lot of security names are up here, Aqua, Netskope, which God has been around forever. I still can't believe it's in an Emerging Technology Survey But so many of these names fall in data and security again, which is why we decided to pick those out Dave. And on the lower side, Vena, Acton, those unfortunately took the dubious award of the lowest evaluations in our survey, but I prefer to focus on the positive. So SecurityScorecard, again, real standout in this one, they're in a security assessment space, basically. They'll come in and assess for you how your security hygiene is. And it's an area of a real interest right now amongst our ITDM community. >> Yeah, I mean, I think those, and then Arctic Wolf is up there too. They're doing managed services. You had mentioned Netskope. Yeah, okay. All right, let's look at now adoption. These are the companies whose offerings are being used the most and are above that standard deviation in the green. Take us through this, Erik. >> Sure, yet again, what we're looking at is, okay, we went from awareness, we went to evaluation. Now it's about utilization, which means a survey respondent's going to state "Yes, we evaluated and we plan to utilize it" or "It's already in our enterprise and we're actually allocating further resources to it." Not surprising, again, a lot of open source, the reason why, it's free. So it's really easy to grow your utilization on something that's free. But as you and I both know, as Red Hat proved, there's a lot of money to be made once the open source is adopted, right? You need the governance, you need the security, you need the support wrapped around it. So here we're seeing Kubernetes, Postgres, Apache Kafka, Jenkins, Grafana. These are all open source based names. But if we're looking at names that are non open source, we're going to see Databricks, Automation Anywhere, Rubrik all have the highest mindshare. So these are the names, not surprisingly, all names that probably should have been public by now. Everyone's expecting an IPO imminently. These are the names that have the highest mindshare. If we talk about the highest utilization rates, again, Miro and Figma pop up, and I know they're not household names, but they are just dominant in this survey. These are applications that are meant for design software and, again, they're going after an Autodesk or a CAD or Adobe type of thing. It is just dominant how high the utilization rates are here, which again is something Adobe should be paying attention to. And then you'll see a little bit lower, but also interesting, we see Collibra again, we see Hugging Face again. And these are names that are obviously in the data governance, ML, AI side. So we're seeing a ton of data, a ton of security and Rubrik was interesting in this one, too, high utilization and high mindshare. We know how pervasive they are in the enterprise already. >> Erik, Alex, keep that up for a second, if you would. So yeah, you mentioned Rubrik. Cohesity's not on there. They're sort of the big one. We're going to talk about them in a moment. Puppet is interesting to me because you remember the early days of that sort of space, you had Puppet and Chef and then you had Ansible. Red Hat bought Ansible and then Ansible really took off. So it's interesting to see Puppet on there as well. Okay. So now let's look at the churn because this one is where you don't want to be. It's, of course, all red 'cause churn is bad. Take us through this, Erik. >> Yeah, definitely don't want to be here and I don't love to dwell on the negative. So we won't spend as much time. But to your point, there's one thing I want to point out that think it's important. So you see Rubrik in the same spot, but Rubrik has so many citations in our survey that it actually would make sense that they're both being high utilization and churn just because they're so well represented. They have such a high overall representation in our survey. And the reason I call that out is Cohesity. Cohesity has an extremely high churn rate here about 17% and unlike Rubrik, they were not on the utilization side. So Rubrik is seeing both, Cohesity is not. It's not being utilized, but it's seeing a high churn. So that's the way you can look at this data and say, "Hm." Same thing with Puppet. You noticed that it was on the other slide. It's also on this one. So basically what it means is a lot of people are giving Puppet a shot, but it's starting to churn, which means it's not as sticky as we would like. One that was surprising on here for me was Tanium. It's kind of jumbled in there. It's hard to see in the middle, but Tanium, I was very surprised to see as high of a churn because what I do hear from our end user community is that people that use it, like it. It really kind of spreads into not only vulnerability management, but also that endpoint detection and response side. So I was surprised by that one, mostly to see Tanium in here. Mural, again, was another one of those application design softwares that's seeing a very high churn as well. >> So you're saying if you're in both... Alex, bring that back up if you would. So if you're in both like MariaDB is for example, I think, yeah, they're in both. They're both green in the previous one and red here, that's not as bad. You mentioned Rubrik is going to be in both. Cohesity is a bit of a concern. Cohesity just brought on Sanjay Poonen. So this could be a go to market issue, right? I mean, 'cause Cohesity has got a great product and they got really happy customers. So they're just maybe having to figure out, okay, what's the right ideal customer profile and Sanjay Poonen, I guarantee, is going to have that company cranking. I mean they had been doing very well on the surveys and had fallen off of a bit. The other interesting things wondering the previous survey I saw Cvent, which is an event platform. My only reason I pay attention to that is 'cause we actually have an event platform. We don't sell it separately. We bundle it as part of our offerings. And you see Hopin on here. Hopin raised a billion dollars during the pandemic. And we were like, "Wow, that's going to blow up." And so you see Hopin on the churn and you didn't see 'em in the previous chart, but that's sort of interesting. Like you said, let's not kind of dwell on the negative, but you really don't. You know, churn is a real big concern. Okay, now we're going to drill down into two sectors, security and data. Where data comprises three areas, database and data warehousing, machine learning and AI and big data analytics. So first let's take a look at the security sector. Now this is interesting because not only is it a sector drill down, but also gives an indicator of how much money the firm has raised, which is the size of that bubble. And to tell us if a company is punching above its weight and efficiently using its venture capital. Erik, take us through this slide. Explain the dots, the size of the dots. Set this up please. >> Yeah. So again, the axis is still the same, net sentiment and mindshare, but what we've done this time is we've taken publicly available information on how much capital company is raised and that'll be the size of the circle you see around the name. And then whether it's green or red is basically saying relative to the amount of money they've raised, how are they doing in our data? So when you see a Netskope, which has been around forever, raised a lot of money, that's why you're going to see them more leading towards red, 'cause it's just been around forever and kind of would expect it. Versus a name like SecurityScorecard, which is only raised a little bit of money and it's actually performing just as well, if not better than a name, like a Netskope. OneTrust doing absolutely incredible right now. BeyondTrust. We've seen the issues with Okta, right. So those are two names that play in that space that obviously are probably getting some looks about what's going on right now. Wiz, we've all heard about right? So raised a ton of money. It's doing well on net sentiment, but the mindshare isn't as well as you'd want, which is why you're going to see a little bit of that red versus a name like Aqua, which is doing container and application security. And hasn't raised as much money, but is really neck and neck with a name like Wiz. So that is why on a relative basis, you'll see that more green. As we all know, information security is never going away. But as we'll get to later in the program, Dave, I'm not sure in this current market environment, if people are as willing to do POCs and switch away from their security provider, right. There's a little bit of tepidness out there, a little trepidation. So right now we're seeing overall a slight pause, a slight cooling in overall evaluations on the security side versus historical levels a year ago. >> Now let's stay on here for a second. So a couple things I want to point out. So it's interesting. Now Snyk has raised over, I think $800 million but you can see them, they're high on the vertical and the horizontal, but now compare that to Lacework. It's hard to see, but they're kind of buried in the middle there. That's the biggest dot in this whole thing. I think I'm interpreting this correctly. They've raised over a billion dollars. It's a Mike Speiser company. He was the founding investor in Snowflake. So people watch that very closely, but that's an example of where they're not punching above their weight. They recently had a layoff and they got to fine tune things, but I'm still confident they they're going to do well. 'Cause they're approaching security as a data problem, which is probably people having trouble getting their arms around that. And then again, I see Arctic Wolf. They're not red, they're not green, but they've raised fair amount of money, but it's showing up to the right and decent level there. And a couple of the other ones that you mentioned, Netskope. Yeah, they've raised a lot of money, but they're actually performing where you want. What you don't want is where Lacework is, right. They've got some work to do to really take advantage of the money that they raised last November and prior to that. >> Yeah, if you're seeing that more neutral color, like you're calling out with an Arctic Wolf, like that means relative to their peers, this is where they should be. It's when you're seeing that red on a Lacework where we all know, wow, you raised a ton of money and your mindshare isn't where it should be. Your net sentiment is not where it should be comparatively. And then you see these great standouts, like Salt Security and SecurityScorecard and Abnormal. You know they haven't raised that much money yet, but their net sentiment's higher and their mindshare's doing well. So those basically in a nutshell, if you're a PE or a VC and you see a small green circle, then you're doing well, then it means you made a good investment. >> Some of these guys, I don't know, but you see these small green circles. Those are the ones you want to start digging into and maybe help them catch a wave. Okay, let's get into the data discussion. And again, three areas, database slash data warehousing, big data analytics and ML AI. First, we're going to look at the database sector. So Alex, thank you for bringing that up. Alright, take us through this, Erik. Actually, let me just say Postgres SQL. I got to ask you about this. It shows some funding, but that actually could be a mix of EDB, the company that commercializes Postgres and Postgres the open source database, which is a transaction system and kind of an open source Oracle. You see MariaDB is a database, but open source database. But the companies they've raised over $200 million and they filed an S-4. So Erik looks like this might be a little bit of mashup of companies and open source products. Help us understand this. >> Yeah, it's tough when you start dealing with the open source side and I'll be honest with you, there is a little bit of a mashup here. There are certain names here that are a hundred percent for profit companies. And then there are others that are obviously open source based like Redis is open source, but Redis Labs is the one trying to monetize the support around it. So you're a hundred percent accurate on this slide. I think one of the things here that's important to note though, is just how important open source is to data. If you're going to be going to any of these areas, it's going to be open source based to begin with. And Neo4j is one I want to call out here. It's not one everyone's familiar with, but it's basically geographical charting database, which is a name that we're seeing on a net sentiment side actually really, really high. When you think about it's the third overall net sentiment for a niche database play. It's not as big on the mindshare 'cause it's use cases aren't as often, but third biggest play on net sentiment. I found really interesting on this slide. >> And again, so MariaDB, as I said, they filed an S-4 I think $50 million in revenue, that might even be ARR. So they're not huge, but they're getting there. And by the way, MariaDB, if you don't know, was the company that was formed the day that Oracle bought Sun in which they got MySQL and MariaDB has done a really good job of replacing a lot of MySQL instances. Oracle has responded with MySQL HeatWave, which was kind of the Oracle version of MySQL. So there's some interesting battles going on there. If you think about the LAMP stack, the M in the LAMP stack was MySQL. And so now it's all MariaDB replacing that MySQL for a large part. And then you see again, the red, you know, you got to have some concerns about there. Aerospike's been around for a long time. SingleStore changed their name a couple years ago, last year. Yellowbrick Data, Fire Bolt was kind of going after Snowflake for a while, but yeah, you want to get out of that red zone. So they got some work to do. >> And Dave, real quick for the people that aren't aware, I just want to let them know that we can cut this data with the public company data as well. So we can cross over this with that because some of these names are competing with the larger public company names as well. So we can go ahead and cross reference like a MariaDB with a Mongo, for instance, or of something of that nature. So it's not in this slide, but at another point we can certainly explain on a relative basis how these private names are doing compared to the other ones as well. >> All right, let's take a quick look at analytics. Alex, bring that up if you would. Go ahead, Erik. >> Yeah, I mean, essentially here, I can't see it on my screen, my apologies. I just kind of went to blank on that. So gimme one second to catch up. >> So I could set it up while you're doing that. You got Grafana up and to the right. I mean, this is huge right. >> Got it thank you. I lost my screen there for a second. Yep. Again, open source name Grafana, absolutely up and to the right. But as we know, Grafana Labs is actually picking up a lot of speed based on Grafana, of course. And I think we might actually hear some noise from them coming this year. The names that are actually a little bit more disappointing than I want to call out are names like ThoughtSpot. It's been around forever. Their mindshare of course is second best here but based on the amount of time they've been around and the amount of money they've raised, it's not actually outperforming the way it should be. We're seeing Moogsoft obviously make some waves. That's very high net sentiment for that company. It's, you know, what, third, fourth position overall in this entire area, Another name like Fivetran, Matillion is doing well. Fivetran, even though it's got a high net sentiment, again, it's raised so much money that we would've expected a little bit more at this point. I know you know this space extremely well, but basically what we're looking at here and to the bottom left, you're going to see some names with a lot of red, large circles that really just aren't performing that well. InfluxData, however, second highest net sentiment. And it's really pretty early on in this stage and the feedback we're getting on this name is the use cases are great, the efficacy's great. And I think it's one to watch out for. >> InfluxData, time series database. The other interesting things I just noticed here, you got Tamer on here, which is that little small green. Those are the ones we were saying before, look for those guys. They might be some of the interesting companies out there and then observe Jeremy Burton's company. They do observability on top of Snowflake, not green, but kind of in that gray. So that's kind of cool. Monte Carlo is another one, they're sort of slightly green. They are doing some really interesting things in data and data mesh. So yeah, okay. So I can spend all day on this stuff, Erik, phenomenal data. I got to get back and really dig in. Let's end with machine learning and AI. Now this chart it's similar in its dimensions, of course, except for the money raised. We're not showing that size of the bubble, but AI is so hot. We wanted to cover that here, Erik, explain this please. Why TensorFlow is highlighted and walk us through this chart. >> Yeah, it's funny yet again, right? Another open source name, TensorFlow being up there. And I just want to explain, we do break out machine learning, AI is its own sector. A lot of this of course really is intertwined with the data side, but it is on its own area. And one of the things I think that's most important here to break out is Databricks. We started to cover Databricks in machine learning, AI. That company has grown into much, much more than that. So I do want to state to you Dave, and also the audience out there that moving forward, we're going to be moving Databricks out of only the MA/AI into other sectors. So we can kind of value them against their peers a little bit better. But in this instance, you could just see how dominant they are in this area. And one thing that's not here, but I do want to point out is that we have the ability to break this down by industry vertical, organization size. And when I break this down into Fortune 500 and Fortune 1000, both Databricks and Tensorflow are even better than you see here. So it's quite interesting to see that the names that are succeeding are also succeeding with the largest organizations in the world. And as we know, large organizations means large budgets. So this is one area that I just thought was really interesting to point out that as we break it down, the data by vertical, these two names still are the outstanding players. >> I just also want to call it H2O.ai. They're getting a lot of buzz in the marketplace and I'm seeing them a lot more. Anaconda, another one. Dataiku consistently popping up. DataRobot is also interesting because all the kerfuffle that's going on there. The Cube guy, Cube alum, Chris Lynch stepped down as executive chairman. All this stuff came out about how the executives were taking money off the table and didn't allow the employees to participate in that money raising deal. So that's pissed a lot of people off. And so they're now going through some kind of uncomfortable things, which is unfortunate because DataRobot, I noticed, we haven't covered them that much in "Breaking Analysis", but I've noticed them oftentimes, Erik, in the surveys doing really well. So you would think that company has a lot of potential. But yeah, it's an important space that we're going to continue to watch. Let me ask you Erik, can you contextualize this from a time series standpoint? I mean, how is this changed over time? >> Yeah, again, not show here, but in the data. I'm sorry, go ahead. >> No, I'm sorry. What I meant, I should have interjected. In other words, you would think in a downturn that these emerging companies would be less interesting to buyers 'cause they're more risky. What have you seen? >> Yeah, and it was interesting before we went live, you and I were having this conversation about "Is the downturn stopping people from evaluating these private companies or not," right. In a larger sense, that's really what we're doing here. How are these private companies doing when it comes down to the actual practitioners? The people with the budget, the people with the decision making. And so what I did is, we have historical data as you know, I went back to the Emerging Technology Survey we did in November of 21, right at the crest right before the market started to really fall and everything kind of started to fall apart there. And what I noticed is on the security side, very much so, we're seeing less evaluations than we were in November 21. So I broke it down. On cloud security, net sentiment went from 21% to 16% from November '21. That's a pretty big drop. And again, that sentiment is our one aggregate metric for overall positivity, meaning utilization and actual evaluation of the name. Again in database, we saw it drop a little bit from 19% to 13%. However, in analytics we actually saw it stay steady. So it's pretty interesting that yes, cloud security and security in general is always going to be important. But right now we're seeing less overall net sentiment in that space. But within analytics, we're seeing steady with growing mindshare. And also to your point earlier in machine learning, AI, we're seeing steady net sentiment and mindshare has grown a whopping 25% to 30%. So despite the downturn, we're seeing more awareness of these companies in analytics and machine learning and a steady, actual utilization of them. I can't say the same in security and database. They're actually shrinking a little bit since the end of last year. >> You know it's interesting, we were on a round table, Erik does these round tables with CISOs and CIOs, and I remember one time you had asked the question, "How do you think about some of these emerging tech companies?" And one of the executives said, "I always include somebody in the bottom left of the Gartner Magic Quadrant in my RFPs. I think he said, "That's how I found," I don't know, it was Zscaler or something like that years before anybody ever knew of them "Because they're going to help me get to the next level." So it's interesting to see Erik in these sectors, how they're holding up in many cases. >> Yeah. It's a very important part for the actual IT practitioners themselves. There's always contracts coming up and you always have to worry about your next round of negotiations. And that's one of the roles these guys play. You have to do a POC when contracts come up, but it's also their job to stay on top of the new technology. You can't fall behind. Like everyone's a software company. Now everyone's a tech company, no matter what you're doing. So these guys have to stay in on top of it. And that's what this ETS can do. You can go in here and look and say, "All right, I'm going to evaluate their technology," and it could be twofold. It might be that you're ready to upgrade your technology and they're actually pushing the envelope or it simply might be I'm using them as a negotiation ploy. So when I go back to the big guy who I have full intentions of writing that contract to, at least I have some negotiation leverage. >> Erik, we got to leave it there. I could spend all day. I'm going to definitely dig into this on my own time. Thank you for introducing this, really appreciate your time today. >> I always enjoy it, Dave and I hope everyone out there has a great holiday weekend. Enjoy the rest of the summer. And, you know, I love to talk data. So anytime you want, just point the camera on me and I'll start talking data. >> You got it. I also want to thank the team at ETR, not only Erik, but Darren Bramen who's a data scientist, really helped prepare this data, the entire team over at ETR. I cannot tell you how much additional data there is. We are just scratching the surface in this "Breaking Analysis". So great job guys. I want to thank Alex Myerson. Who's on production and he manages the podcast. Ken Shifman as well, who's just coming back from VMware Explore. Kristen Martin and Cheryl Knight help get the word out on social media and in our newsletters. And Rob Hof is our editor in chief over at SiliconANGLE. Does some great editing for us. Thank you. All of you guys. Remember these episodes, they're all available as podcast, wherever you listen. All you got to do is just search "Breaking Analysis" podcast. I publish each week on wikibon.com and siliconangle.com. Or you can email me to get in touch david.vellante@siliconangle.com. You can DM me at dvellante or comment on my LinkedIn posts and please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for Erik Bradley and The Cube Insights powered by ETR. Thanks for watching. Be well. And we'll see you next time on "Breaking Analysis". (upbeat music)

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

>> Narrator: From around the globe, it's theCUBE with digital coverage of AnsibleFest 2020, brought to you by Red Hat. >> The ascendancy of massive clouds underscored the limits of human labor. People, they simply don't scale at the pace of today's technology. And this trend created an automation mandate for IT which has been further accentuated by the pandemic. The world is witnessing the build-out of a massively distributed system that comprises on-prem apps, public clouds and edge computing. The challenge we face is how to go from managing things you can see and touch to cost effectively managing, securing and scaling these vast systems. It requires an automation first mindset. Hello, everyone. This is Dave Vellante and welcome back to AnsibleFest 2020. We have a great panel to wrap up this show. With me are our three excellent guests and CUBE alums. Ashesh Badani is the Senior Vice President of Cloud Platforms at Red Hat. Ashesh, good to see you again. Thanks for coming on. >> Yeah, likewise. Thanks for having me on again, Dave. >> Stefanie Chiras is Vice President and General Manager of the RHEL Business Unit and my sports buddy. Stefanie, glad to see you back in the New England area. I knew you'd be back. >> Yeah, good to see you, Dave. Thanks for having us today. >> You're very welcome. And then finally, Joe Fitzgerald, longtime CUBE alum, Vice President and General Manager of the Management Business Unit at Red Hat. Joe, good to see you. >> Hey, Dave, good to be here with you. >> Ashesh, I'm going to start with you. Lay out the big picture for us. So how do you see this evolution to what we sometimes talk about as hybrid cloud, but really truly a hybrid cloud environment across these three platforms that I just talked about? >> Yeah, let me start off by echoing something that most of your viewers have probably heard in the past. There's always this notion about developers, developers, developers. And you know, that still holds true. We aren't going away from that anymore. Developers are the new kingmakers. But increasingly, as the scope and complexity of applications and services that are deployed in this heterogeneous environment increases, it's more and more about automation, automation, automation. In the times we live in today, even, you know, before dealing with the crises that, you know, we have, just the sheer magnitude of requirements that are being placed on enterprises and expectations from customers require us to be more and more focused on automating tasks which humans just can't keep up with. So you know, as we look forward, this conversation here today, you know, what Ansible's doing, you know, is squarely aimed at dealing with this complexity that we all face. >> So Stefanie, I wonder if you could talk about what it's going to take to implement what I call this true hybrid cloud, this connection and management of this environment. RHEL is obviously a key piece of that. That's going to be your business unit, but take us through your thoughts there. >> Yeah, so I'm kind of building on what Ashesh said. When we look at this hybrid cloud world, right, which now hybrid is much more than it was considered five years ago. It used to be hybrid was on-prem versus off-prem. Now, hybrid translates to many layers in the stack. It can be VMs hybrid with containers. It can be on-prem with off-prem and clearly with edge involved, as well. Whenever you start to require the ability to bridge across these, that's where we focus on having a platform that allows you to access sort of all of those and be able to deploy your applications in a simple way. When I look at what customers require, it's all about speed of deploying applications, right, build, deploy and run your applications. It's about stability, which is clearly where we're focused on RHEL being able to provide that stability across multiple types of hybrid deployment models. And third is all about scale. It is absolutely all about scale and that's across multiple ranges in hybrid, be it on-prem, off-prem, edge and that's where all of this automation comes in, so to me, it's really about where do you make those strategic decisions that allow you to choose, right, for the flexibility that you need and still be able to deploy applications with speed, have that stability, resiliency, and be able to scale. >> So Joe, let's talk about your swim lane and it's weird to even use that term, right? 'Cause as Stefanie just said, we're kind of breaking down all these silos that we talk in terms of platform, but how do you see this evolving, and specifically, what's the contribution from a management perspective? >> Right, so Stefanie and Ashesh talked about sort of speed, scale and complexity. Right, people are trying to deploy things faster or larger scale, and oh, by the way, keep everything highly available and secure. That's a challenge, right? And so, you know, interestingly enough, Red Hat, about five years ago, we recognized that automation was going to be a problem as people were moving into open hybrid clouds, which we've been working with our customers for years on. And so we acquired this small company called Ansible, which had some really early emerging technology, all open source, right, to do automation. And what we've done over the past five years is we've really amplified that automation and amplified the innovation in that community to be able to provide automation across a wide array of domains that you need to automate, right, and to be able to plug that in to all the different processes that people need in order to be able to go faster, but to track, manage, secure and govern these kind of environments. So we made this bet years ago and it's paying off for Red Hat in very big ways. >> I mean, no doubt about it. I mean, when you guys bought Ansible, so it wasn't clear that it was going to be the clear leader. It is now. I mean, it's pulled ahead of Chef, Puppet. You saw, you know, VMware bought Salt, but I mean, Ansible very clearly has, based on our surveys, the greatest market momentum. We're going to talk about that. I know some of the other analysts have chimed in on this, but let me come back to this notion of on-prem and cloud and edge and this is complicated. I mean, the edge, it's kind of its own island, isn't it? I mean, you got the IT and the OT schism, so maybe you could talk a little bit about how you see those worlds coming together, the cloud, the on-prem, the edge. Maybe Stefanie, you can start. >> Yeah, I think the magic, Dave, is going to happen when it's not its own island, right, as we start to see this world driven by data cause the spread of a data center to be really dis-aggregated and allow that compute to move out closer to the data, the magic happens when it doesn't feel like an island, right, that's the beauty and the promise of hybrid. So when you start to look at what can you provide that is consistent that serves as a single language that you can talk to from on-prem, off-prem and edge, you know, it all comes down to, for us, having a platform that you can build once and deploy across all of those, but the real delicacy with edge is there are some different deployment models. I think that comes into deployment space and we're clearly getting feedback from customers. We're working on some capabilities where edge requires some different deployment models in the ways you update, et cetera, and thanks to all of you out there who are working with us upstream in order to deliver that. And I think the second place where it's unique is in this ability to manage and automate out at the edge, but our goal is certainly at our platform levels, whether it be on RHEL, whether it be on OpenShift to provide that consistent platform that allows you that ease of deployment, then you got to manage and automate it and that's where the whole Ansible and the ecosystem really plays in. You need that ecosystem and that's always what I love about AnsibleFest is this community comes together and it's a vibrant community, for sure. >> Well, I mean, Ashesh, you guys are betting big on this and I often think of the cloud is just this one big cloud. You got the on-prem cloud, you got the public clouds. Edge becomes just an extension of that cloud. Is that how you think about it and what is it actually going to take to make that edge not an island? >> Yeah, great point, Dave, and that's exactly how we think about it. We've always thought about our vision of the cloud as being a platform and abstraction that spans all the underlying infrastructure that the user can take advantage of, so if it happens to reside in a data center, some in a private cloud running off a data center, more increasingly in the public cloud setting, and as Stefanie called out, we're also starting to see edge deployments come in. We're seeing, you know, big build-outs in the work we're doing with telecom providers from a 5G perspective that's helping drive that. We're seeing, if you will, IOT-like opportunities with, let's say, the automotive sector or some in the retail sector, as well. And so this fabric, if you will, needs to span this entire set of deployment that a customer will take advantage of. And Joe started touching on this a little bit, right, with this notion of the speed, scale and complexity, so we see this platform needing to expand to all these footprints that customers are using. At the same time, the requirements that they have, even when they're going out the edge, is the same with regard to what they see in the data center and the public cloud, so putting all that together really is our sweet spot. That's our focus. And to the point you're making, Dave, that's where we're making a huge bet across all of Red Hat. >> So I mentioned, you know, some of our research and I do these breaking analysis segments every week and recently I was digging into cloud and specifically was interested in hybrid and multi. And you know, hybrid been I think pretty well understood for awhile. Multi I think was a lot of, you know, a lot of talk, but it's becoming real and the data really shows that. It shows OpenShift and Ansible have momentum. I mentioned that before. Yeah, you know, obviously VMware is there, but clearly Red Hat is well positioned specifically in multicloud and hybrid. And I know some of the other analyst firms have picked up on this. What are you guys seeing in the market? Maybe Joe, you can chime in and Ashesh, you can maybe add some color. >> Yeah, so you know, there's a lot of fashion, right, around hybrid and multicloud today, so every vendor is jumping on with multicloud storing. And you know, a lot of the vendors' strategies are, pick my solution and vertically use my stuff in the public cloud on-premise, maybe even at the edge, right, and you'll be fine. And you know, obviously customers don't like lock-in. They like to be able to take advantage of the best services, availability, security, different things that are available in each of these different clouds, right? So there is a strong preference for hybrid and multicloud. Red Hat is sort of the Switzerland of hybrid and multicloud because we enable you to run your workloads across all these different substrates, whether it's in public clouds, multiple, right, into the data center and physical, virtual, bare metal, out to the edge and edge is not a single homogeneous, you know, set of hardware or even implementation. It varies a lot by vertical, so you have a lot of diversity, right? And so Red Hat is really good at helping provide the platforms like OpenShift and RHEL that are going to provide that consistency across those different environments or also in the case of Ansible to provide automation that's going to match the physics of management and automation that are required across each of those different environments. Trust me, managing or automating something at the edge and with very small footprint of some device across the constraint network is very, very different than managing things in a public cloud or in a data center and that's where I think Red Hat is really focused and that's our sweet spot, helping people manage those environments. >> And Ashesh, you guys have obviously put a lot of effort there. If you could maybe comment. >> Yeah, I was just going to say, Dave, I'll add just really quickly to what Joe said. He said it well. But the thing I will add is the way for us to succeed here is to follow the user, follow the customer. Right, instead of us just coming out with regard to what we believe the path to be, you know, we're really kind of working closely with the actual customers that we have. So for example, recently been working with a large water utility in Italy, but they're thinking about, you know, the world that they live in and how can they go off and, you know, have kiosks that are spread throughout Italy, able to provide reports with regard to the quality of the water that's available, as well as other services to all their citizens. But it's really interesting use case for us to go off and pursue because in some sense, you can ask yourself, well, is that public cloud? Are they going to take advantage of those services? Is that, you know, private cloud? Is that data center, is that IOT, is that edge? At a certain point in time, what you've got to think about is, well, we've got to provide integrated end-to-end solution that spans all of these different worlds, and so as long as I think we keep that focus, as long as we make sure our North Star is really what the user's trying to do, what problem they're trying to solve, I think we'll come out just fine on the other side of this. >> So I'd love to get all your thoughts, all three of you, on just what's going on in containers, generally, Kubernetes, specifically. I mean, everybody knows it's a hot space and the data shows that it is maturing, but it's amazing to me how much momentum it still has. I mean, it's like the new shiny toy, but it's everywhere and so it's able to sort of maintain that velocity and it's really becoming the go-to cloud native development platform, so the question is how is Red Hat, you know, helping your customers connect OpenShift to the rest of their IT infrastructure, platforms, their processes, the tools. I mean, who wants to start? I'd love to hear from all three of you. Ashesh, why don't you kick it off and then we'll just go left to right. >> So Dave, we've spoken to you and to folks the CUBE, as well, other for many years on this. We've made a huge investment in the Kubernetes market and been one of the earliest to do that and we continue to believe in the promise that it delivers to users, this notion of being able to have an environment that customers can use regardless of the underlying choices that they make. Here's an extremely powerful one, it's truly an open source, right? This is key to, you know, what we do. Increasingly, what we're working on is to ensure that one, if you make a commitment to Kubernetes and increasingly we see lots of customers around the world doing that, that we ensure that we're working closely, that our entire portfolio helps support that. So if you're going to make a choice with regard to Kubernetes base deployment, we help support you running it yourself wherever it is that you choose to run it, we help support you whether you choose to have us manage on your behalf and then also make sure we're providing an entire portfolio of services, both within Red Hat as well as from third parties so that you have the most productive, integrated experience possible. >> Okay, and Stefanie, loved your point of view on this, and Joe, I'd love to understand how you're bridging kind of the Ansible and Kubernetes communities, but Stefanie, why don't you chime in first? >> Yeah, I'll quickly add to what Ashesh said and talked about well on really the promise and the value of containers, but particularly from a RHEL perspective, we have taken all our capabilities and knowledge in the Linux space and we have taken that to apply it to OpenShift, right, because Kubernetes and containers is just another way to deploy Linux, so making sure that that underpinning is stable, secure and resilient and tied to an ecosystem, right? An ecosystem of various architectures, an ecosystem of ISVs and tooling, right? We've pulled that together and everything we've done in Linux for, you know, over decades now at Red Hat and we've put that into that customer experience around OpenShift to deploy containers, so we've really built, it has been a portfolio-wide effort, as Ashesh alluded to, and of course, it passes over to Ansible as well with Joe's portfolio. >> Yeah, we talked about this upfront, Joe. The communities are so crucial, so how are you bridging those Ansible and Kubernetes communities? What's your thought on that? >> Well, a quick note about those communities. So you know, OpenShift is built on Kubernetes and a number of other projects. Kubernetes is number seven in the top 10 open source projects based on the number of contributors. Turns out Ansible is number nine, right? So if you think about it, these are two incredibly robust communities, right? On the one hand, building the container platform in Kubernetes and in the other around Ansible and automation. It turns out that as the need for this digital acceleration and building these container-based applications comes along, there's a lot of other things that have to be done when you deploy container-based applications, whether it's infrastructure automation, right, to expand and manage and automate the infrastructure that you're running your container-based applications on, creating more clusters, you know, configuring storage, network, you know, counts, things like that, but also connecting to other systems in the environment that need to be integrated with around, you know, ITSM or systems of record, change management, inventory, cost, things like that, so what we've done is we've integrated Ansible, right, in a very powerful way with OpenShift through our advanced cluster management capability, which allows us to provide an easy way to instrument Ansible during critical points, whether it's you're deploying new clusters out there or you're deploying a new version of an application or a new application for the first time, whether you're checking policy, right, to ensure that, you know, the thing is secure and that, you know, you can govern these environments, right, that you're relying on. So we've really now tied together two sort of de facto standards, OpenShift built on Kubernetes and a number of other projects and then Ansible, or Red Hat, has taken this innovation in the community and created these certified content collections, platforms and capabilities that people can actually build and rely on and know that it's going to work. >> Ashesh, I mean, Red Hat has earned the right, really, to play in both the cloud native world and of course the traditional infrastructure world, but I'm interested in what you're seeing there, how you're bringing those two worlds together. Are they still, you know, largely separate? Are you seeing traditional IT? I mean, you're certainly seeing them lean in to more and more cloud native, but what are you guys doing specifically to kind of bring those worlds together? >> Yeah, increasingly it's really hard to be able to separate out those worlds, right? So in the past, we used to call it shadow IT. There really is no shadow IT anymore, right? This is IT. So we've embraced that completely. You know, our take on that is to say there are certain applications that are going to be appropriate for being run in a data center a certain way. There are certain other workloads that'll find their way appropriate for the public cloud. We want to make sure we're meeting them across, but what we want to do is constantly introduce technologies to help support the choices customers make. What do I mean by that? Let me give a couple examples. One is, you know, we can say customers have VMs that are based out in specific environments and they can only run as VMs. That code can't be containerized for a variety of reasons, right? You know, hard to re-architect that, don't have the funds, you know, have certain security compliance reasons. Well, what if we could take those VMs and then have them be run in containers in a native fashion? Wouldn't that be extremely powerful value proposition to run containers and then VMs as containers sort of side by side with Kubernetes orchestrating them all. So that's a capability we call open source virtualization. We've introduced that and made that generally available within our platform. Another one, which I think Joe starting to touch on a little bit here, is both around this notion of Ansible, as well as advanced cluster management. And say, once technologies like Ansible are familiar to our customers, how about if we find ways to introduce things like the operator framework to help support people's use of Ansible and introduce technologies like advanced cluster management, which allows for us to say, well, regardless of where you run your clusters, whether you run your Kubernetes clusters on premise, you run them in the cloud, right, we can imagine a consistent fashion and manage, you know, health and policy and compliance of applications across that entire state. So David, question's extremely good one, right, but what we are trying to do is try to be able to say, you know, we are going to just span those two worlds and provide as many tools as possible to ensure that customers feel like, you know, the shift, if you will, or the move between traditional enterprise software application development and the more modern cloud native can be bridged as seamlessly as possible. >> Yeah, Joe, we heard a lot of this at AnsibleFest, so the ACM as a key component of your innovation, and frankly, your competitive posture. Anything you would add to what Ashesh just shared? >> Well, I think that one of the things that Red Hat is really good at is we take management and automation as sort of an intrinsic part of what needs to go on. It's not an afterthought. You just don't go build something, go, "Oh I need management," go out and, you know, go get something, right, so we've been working on, sort of automation and management for many, many years, right, so we build it in concert with these platforms, right, and we understand the physics of these different environments, so we're very focused on that from inception, as opposed to an afterthought when people sort of paint themselves into a corner or have management challenges they can't deal with. >> There's a lot of analogs in our business, isn't there? Management is a bolt-on and security is a bolt-on. It just doesn't work that well and certainly doesn't scale. Stefanie, I want to come back to you and I want to come back to the edge. We hear a lot of people talking about extending their deployments to the edge in the future. I mean, you look at what IBM's doing. They're essentially betting its business on RHEL and OpenShift and betting that its customers are going to do the same as well are you. Maybe talk about, you know, what you're doing to specifically extend RHEL to the edge. >> Yeah, Dave, so we've been looking at this space consistent with our strategy, as Ashesh talked about, right? Our goal is to make sure that it all looks and feels the same and provides one single Linux experience. We've been building on a number of those aspects for quite some time, things like being able to deal with heterogeneous architectures, as an example, being able to deal with, you know, having Arm components and x86 components and power components and being able to leverage all of that from multiple vendors and being able to deploy. Those are things we've been focused on for a long time and now when you move into the space of the edge, certainly we're seeing, you know, essentially data center level hardware move out to be dis-aggregated and dispersed as they move it closer to the data and where that's coming in and where the analysis needs to be done, but some of those foundational things that we've been working on for years starts to pay off because the edge tends to be more heterogeneous all the way from an architecture level to an application level, so now we're seeing some asks. We've been working upstream in order to pull in some features that drive capabilities around specifically updating, deploying those updates, doing rollbacks and things like that, so we're focused on that. But really, it's about pulling together the capabilities of having multiple architectures, dealing with heterogeneous infrastructure out there at the edge, being able to reliably deploy it even when, for example, we have customers who they deploy their hardware and they can't touch it for years. How do they make sure that that's out there in a stable environment that they can count on? And then, you know, adding in things like containerization. We talked about the magic of that, being able to deploy an application consistently and being able to deploy a single container out there to the edge. We're thinking about it all the way from the architecture up to how the application gets deployed and it's going to take the whole portfolio to do that as you need to manage it, as you need to deploy containers, so it's a focus across the company for how we deal with that. >> And as we were talking about before, you know, it takes a village. You know that bromide, but it does, requires an ecosystem of jobs. I mean, there's some real technical challenges in R&D that has to happen. I mean, you've got to be, you know, you're talking about cloud native in all three different clouds, and you know, and not just the big three, but other clouds and then bringing that to the edge, so there's some clear technical challenges, but there's also some business challenges out there. So you know, what are you seeing in that regard? You know, what are some of those things that you hope to solve by bridging that gap? >> Well, I think one of the things we're trying to do and I'm focused on the management and automation side is to provide a common set of management tooling of automation, right, and I think Ansible fits that quite well. So for the past five years since Ansible's been part of Red Hat, we've expanded from, you know, they started off initially doing configuration management, right? We've expanded to include, you know, network and storage and security, now edge. At AnsibleFest, we demonstrated things like serverless event-driven automation, right, building an OpenShift serverless in Knative. We're trying to expand the use cases for Ansible so that there's a simplicity, there's a tool reduction, right, across all these environments and you don't have to go deal with nine vendors, and you know, 17 different tools to try to manage each element here to be able to provide a common set. It reduces complexity, cost and allows skills to be able to be reused across these different areas. It's going to all be about digital acceleration, right, and reducing that complexity. And one last comment. One of the reasons we bought Ansible years ago is the architecture, it's agent-less. Many of our competitors that you hear, the first thing they want to do is go deploy an agent somewhere and that creates its own ongoing burden of, do I have the latest version of the agent? Is it secure? Does it fit on the device? As Stefanie mentioned, is there a version that fits on the architecture the device is running on? It starts getting really, really complicated. So Ansible is just simple, elegant, agent-less. We've expanded the domains we can automate with it and we've expanded sort of the modality. How can I call it? User, driven by an event, as part of some life cycle management, app deployment, Ansible plugs right in. >> Well, Joe, you can tell you're a management guy, right? Agents, another thing that has to be managed. You just laundry list of stuff. (laughs) I want to come back to this notion Joe just touched on, this digital transformation. They say, "If it ain't broke, don't fix it." Well, COVID broke everything. And I got to say, I mean, all the talk about digital transformation over the last, you know, several years, yes, it was certainly happening, but there was also a lot of lip service going on and now if you're not digital, you're out of business. And so, you know, given everything that we've seen in the last, you know, whatever, 150, 200 days or so, what's the impact that you're seeing on customers' digital transformation initiatives, and you know, what is Red Hat doing to respond? Maybe Ashesh, you could start and we can get feedback from the others. >> Yeah, David, it's an unfortunate thing to say, right, but there's that meme going around with regard to who's responsible for digital transformation and it's a little bit of I guess gallows humor to call it COVID, but we're increasingly seeing that customers and the journey that they're on is one that they haven't really gotten off, even with this, if you will, change of environment that's come about. So projects that we've seen in play, you know, are still underway. We've seen acceleration, actually, in some places with regard to making services more easily accessible. Anyone who's invested in hybrid cloud or public cloud is seeing huge value with regard to being able to consume services remotely, being able to do this on demand and that's a big part of the value proposition, you know, that comes forward. And increasingly what we're trying to do is try to say, how can we engage and assist you in these times, right? So our services team, for example, has transformed to be able to help customers remotely. Our support team has gone off and work more and more with customers. For a company like Red Hat, that hasn't been completely, if you will, difficult thing to do mostly because we've been so used to working in a distributed fashion, working remotely with our customers, so that's not a challenge in itself, but making sure customers understand that this is really a critical journey for them to go on and how we can kind of help them, you know, walk through that has been good and we're finding that that message really resonates. Right, so both Stefanie and Joe talked a little bit about, you know, how essentially our entire portfolio is now built around, you know, ensuring that if you'd like to consume on demand, we can help support you, if you'd like to consume in a traditional fashion, we can help you. That amount of flexibility that we provide to customers is really coming to bear at this point in time. >> So maybe we could wrap with, we haven't really dropped any customer names. Stefanie and Joe and Ashesh, I wonder if you have any stories you can share or, you know, customer examples that we could close on that are exciting to you this year. >> So I can start, if that's okay. >> Please. >> So an area that I find super interesting from a customer perspective that we're increasingly seeing more and more customers go down is sheer interest in, if you will, kind of diversity of use cases that we're seeing, right? So we see this, for example, in automotive, right? So whether it's a BMW or a Volkswagen, we see this now in health care with the ACA, in we'll say a little bit more traditional industries like energy with Exxon or Schlumberger around increasingly embrace of AIML, right? So artificial machine learning, if you will, advanced analytics being much more proactive with regard to how they can take data that's coming in, adjust it, be able to make sense of the patterns and then be able to, you know, have some action that has real business impact. So this whole trend towards, you know, AIML workloads that they can run is extremely powerful. We work very closely with Nvidia, as well, and we're seeing a lot of interest, for example, in being able to run a Kubernetes-based platform, support Nvidia GPUs for specific class workloads. There's a whole bunch of customers, people in financial services that, you know, this is a rich area of interest. You know, we've seen great use cases for example around grid with Deutsche Bank. And so, to me, I'm personally really excited to see kind of that embrace the PC from our customers regard to saying there's a whole lot of data that's out there. You know, how can we essentially use all of these tools that we have in place? You know, we talk about containers, microservices, DevOps, you know, all of this and then put it to bear to really put to work and get business value. >> Great, thank you for that, Ashesh. Stefanie, Joe, Stefanie, anything you want to add or final thoughts? >> Yeah, just one thing to add and I think Ashesh talked to a whole number across industry verticals and customers. But I think the one thing that I've seen through COVID is that if nothing else, it's taught us that change is the only constant and I think, you know, our whole vision of open hybrid cloud is how to enable customers to be flexible and do what they need to do when they need to do it, wherever they want to deploy, however they want to build. We provide them some consistency, right, across that as they make those changes and I think as I've worked with customers here through since the beginning of COVID, it's been amazing to me the diversity of how they've had to respond. Some have doubled down in the data center, some have doubled down on going public cloud and to me, this is the proof of the strategy that we're on, right, that open hybrid cloud is about delivering flexibility, and boy, nothing's taught us the need for flexibility like COVID has recently, so I think there's a lot more to do. I think pulling together the platforms and the automation is what is going to enable the ability to do that in a simple fashion. >> So Joe, you get the final word. I mean, AnsibleFest 2020, I mean, it's weird, right? But that's the way these events are, all virtual. Hopefully, next year we got a shot at being face to face, but bring us home, please. >> Yeah, I got to tell ya, having, you know, 20,000 or so of your closest friends get together to talk about automation for a couple of days is just amazing. That just shows you sort of the power of it. You know, we have a lot of customers this week at AnsibleFest telling you their story, you know, CarMax and ExxonMobil, you know, BlueCross BlueShield. I mean, there's a number across all different verticals, globally, Cepsa from Europe. I mean, just an incredibly, you know, diverse array of customers and use cases. I would encourage people to look at some of the customer presentations that were on at AnsibleFest, listen to the customer telling you what they're doing with Ansible, deploying their networks, deploying their apps, managing their infrastructure, container apps, traditional apps, connecting it, moving faster. They have amazing stories. I encourage people to go look. >> Well, guys, thanks so much for helping us wrap up AnsibleFest 2020. It was really a great discussion. You guys have always been awesome CUBE guests. Really appreciate the partnership and so thank you. >> Thanks a lot, Dave. Appreciate it. >> Yeah, thanks, Dave. >> Thanks for having us. >> All right, and thank you for watching, everybody. This is Dave Vellante for theCUBE and we'll see you next time. (calm music)

>> Announcer: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is a CUBE conversation. >> As you may recall, coming into the second part of 2019 we reported, based on ETR Survey data, that there was a narrowing of spending on emerging tech and an unplugging of a lot of legacy systems. This was really because people were going from experimentation into operationalizing their digital initiatives. When COVID hit, conventional wisdom suggested that there would be a flight to safety. Now, interestingly, we reported with Eric Bradley, based on one of the Venns, that a lot of CIOs were still experimenting with emerging vendors. But this was very anecdotal. Today, we have more data, fresh data, from the ETR Emerging Technology Study on private companies, which really does suggest that there's a notable decline in experimentation, and that's affecting emerging technology vendors. Hi, everybody, this is Dave Vellante, and welcome to this week's Wikibon Cube Insights, powered by ETR. Once again, Sagar Kadakia is joining us. Sagar is the Director of Research at ETR. Sagar, good to see you. Thanks for coming on. >> Good to see you again. Thanks for having me, Dave. >> So, it's really important to point out, this Emerging Tech Study that you guys do, it's different from your quarterly Technology Spending Intention Survey. Take us through the methodology. Guys, maybe you could bring up the first chart. And, Sagar, walk us through how you guys approach this. >> No problem. So, a lot of the viewers are used to seeing a lot of the results from the Technology Spending Intention Survey, or the TSIS, as we call it. That study, as the title says, it really tracks spending intentions on more pervasive vendors, right, Microsoft, AWS, as an example. What we're going to look at today is our Emerging Technology Study, which we conduct biannually, in May and November. This study is a little bit different. We ask CIOs around evaluations, awareness, planned evaluations, so think of this as pre-spend, right. So that's a major differentiator from the TSIS. That, and this study, really focuses on private emerging providers. We're really only focused on those really emerging private companies, say, like your Series B to Series G or H, whatever it may be, so, two big differences within those studies. And then today what we're really going to look at is the results from the Emerging Technology Study. Just a couple of quick things here. We had 811 CIOs participate, which represents about 380 billion in annual IT spend, so the results from this study matter. We had almost 75 Fortune 100s take it. So, again, we're really measuring how private emerging providers are doing in the largest organizations. And so today we're going to be reviewing notable sectors, but largely this survey tracks roughly 356 private technologies and frameworks. >> All right, guys, bring up the pie chart, the next slide. Now, Sagar, this is sort of a snapshot here, and it basically says that 44% of CIOs agree that COVID has decreased the organization's evaluation and utilization of emerging tech, despite what I mentioned, Eric Bradley's Venn, which suggested one CIO in particular said, "Hey, I always pick somebody in the lower left "of the magic quadrant." But, again, this is a static view. I know we have some other data, but take us through this, and how this compares to other surveys that you've done. >> No problem. So let's start with the high level takeaways. And I'll actually kind of get into to the point that Eric was debating, 'cause that point is true. It's just really how you kind of slice and dice the data to get to that. So, what you're looking at here, and what the overall takeaway from the Emerging Technology Study was, is, you know, you are going to see notable declines in POCs, of proof-of-concepts, any valuations because of COVID-19. Even though we had been communicating for quite some time, you know, the last few months, that there's increasing pressure for companies to further digitize with COVID-19, there are IT budget constraints. There is a huge pivot in IT resources towards supporting remote employees, a decrease in risk tolerance, and so that's why what you're seeing here is a rather notable number of CIOs, 44%, that said that they are decreasing their organization's evaluation and utilization of private emerging providers. So that is notable. >> Now, as you pointed out, you guys run this survey a couple of times a year. So now let's look at the time series. Guys, if you bring up the next chart. We can see how the sentiment has changed since last year. And, of course, we're isolating here on some of larger companies. So, take us through what this data means. >> No problem. So, how do we quantify what we just saw in the prior slide? We saw 44% of CIOs indicating that they are going to be decreasing their evaluations. But what exactly does that mean? We can pretty much determine that by looking at a lot of the data that we captured through our Emerging Technology Study. There's a lot going on in this slide, but I'll walk you through it. What you're looking at here is Fortune 1000 organizations, so we've really isolated the data to those organizations that matter. So, let's start with the teal, kind of green line first, because I think it's a little bit easier to understand. What you're looking at, Fortune 1000 evaluations, both planned and current, okay? And you're looking at a time series, one year ago and six months ago. So, two of the answer options that we provide CIOs in this survey, right, think about the survey as a grid, where you have seven answer options going horizontally, and then 300-plus vendors and technologies going vertically. For any given vendor, they can essentially indicate one of these options, two of them being on currently evaluating them or I plan to evaluate them in six months. So what you're looking at here is effectively the aggregate number, or the average number of Fortune 1000 evaluations. So if you look into May 2019, all the way on the left of that chart, that 24% roughly means that a quarter of selections made by Fortune 1000 of the survey, they selected plan to evaluate or currently evaluating. If you fast-forward six months, to the middle of the chart, November '19, it's roughly the same, one in four technologies that are Fortune 1000 selected, they indicated that I plan or am currently evaluating them. But now look at that big drop off going into May 2020, the 17%, right? So now one out of every six technologies, or one out of every selections that they made was an evaluation. So a very notable drop. And then if you look at the blue line, this is another answer option that we provided CIOs: I'm aware of the technology but I have no plans to evaluate. So this answer option essentially tracks awareness levels. If you look at the last six months, look at that big uptick from 44% to over 50%, right? So now, essentially one out of every two technologies, or private technologies that a CIO is aware of, they have no plans to evaluate. So this is going to have an impact on the general landscape, when we think about those private emerging providers. But there is one caveat, and, Dave, this is what you mentioned earlier, this is what Eric was talking about. The providers that are doing well are the ones that are work-from-home aligned. And so, just like a few years ago, we were really analyzing results based on are you cloud-native or are you Cloud-aligned, because those technologies are going to do the best, what we're seeing in the emerging space is now the same thing. Those emerging providers that enable organizations to maintain productivity for their employees, essentially allowing their employees to work remotely, those emerging providers are still doing well. And that is probably the second biggest takeaway from this study. >> So now what we're seeing here is this flight to perceive safety, which, to your point, Sagar, doesn't necessarily mean good news for all enterprise tech vendors, but certainly for those that are positioned for the work-from-home pivot. So now let's take a look at a couple of sectors. We'll start with information security. We've reported for years about how the perimeter's been broken down, and that more spend was going to shift from inside the moat to a distributed network, and that's clearly what's happened as a result of COVID. Guys, if you bring up the next chart. Sagar, you take us through this. >> No problem. And as you imagine, I think that the big theme here is zero trust. So, a couple of things here. And let me just explain this chart a little bit, because we're going to be going through a couple of these. What you're seeing on the X-axis here, is this is effectively what we're classifying as near term growth opportunity from all customers. The way we measure that effectively is we look at all the evaluations, current evaluations, planned evaluations, we look at people who are evaluated and plan to utilize these vendors. The more indications you get on that the more to the top right you're going to be. The more indications you get around I'm aware of but I don't plan to evaluate, or I'm replacing this early-stage vendor, the further down and on the left you're going to be. So, on the X-axis you have near term growth opportunity from all customers, and on the Y-axis you have near term growth opportunity from, really, the biggest shops in the world, your Global 2000, your Forbes Private 225, like Cargill, as an example, and then, of course, your federal agencies. So you really want to be positioned up and to the right here. So, the big takeaway here is zero trust. So, just a couple of things on this slide when we think about zero trust. As organizations accelerate their Cloud and Saas spend because of COVID-19, and, you know, what we were talking about earlier, Dave, remote work becomes the new normal, that perimeter security approach is losing appeal, because the perimeter's less defined, right? Apps and data are increasingly being stored in the Cloud. That, and employees are working remotely from everywhere, and they're accessing all of these items. And so what we're seeing now is a big move into zero trust. So, if we look at that chart again, what you're going to see in that upper right quadrant are a lot of identity and access management players. And look at the bifurcation in general. This is what we were talking about earlier in terms of the landscape not doing well. Most security vendors are in that red area, you know, in the middle to the bottom. But if you look at the top right, what are you seeing here? Unify ID, Auth0, WSO2, right, all identity and access management players. These are critical in your zero trust approach, and this is one of the few area where we are seeing upticks. You also see here BitSight, Lucideus. So that's going to be security assessment. You're seeing VECTRA and Netskope and Darktrace, and a few others here. And Cloud Security and IDPS, Intrusion Detection and Prevention System. So, very few sectors are seeing an uptick, very few security sectors actually look pretty good, based on opportunities that are coming. But, essentially, all of them are in that work-from-home aligned security stack, so to speak. >> Right, and of course, as we know, as we've been reporting, buyers have options, from both established companies and these emerging companies that are public, Okta, CrowdStrike, Zscaler. We've seen the work-from-home pivot benefit those guys, but even Palo Alto Networks, even CISCO, I asked (other speaker drowns out speech) last week, I said, "Hey, what about this pivot to work from home? "What about this zero trust?" And he said, "Look, the reality is, yes, "a big part of our portfolio is exposed "to that traditional infrastructure, "but we have options for zero trust as well." So, from a buyer's standpoint, that perceived flight to safety, you have a lot of established vendors, and that clearly is showing up in your data. Now, the other sector that we want to talk about is database. We've been reporting a lot on database, data warehouse. So, why don't you take us through the next graphic here, if you would. >> Sagar: No problem. So, our theme here is that Snowflake is really separating itself from the pack, and, again, you can see that here. Private database and data warehousing vendors really continue to impact a lot of their public peers, and Snowflake is leading the way. We expect Snowflake to gain momentum in the next few years. And, look, there's some rumors that IPOing soon. And so when we think about that set-up, we like it, because as organizations transition away from hybrid Cloud architectures to 100% or near-100% public Cloud, Snowflake is really going to benefit. So they look good, their data stacks look pretty good, right, that's resiliency, redundancy across data centers. So we kind of like them as well. Redis Labs bring a DB and they look pretty good here on the opportunity side, but we are seeing a little bit of churn, so I think probably Snowflake and DataStax are probably our two favorites here. And again, when you think about Snowflake, we continue to think more pervasive vendors, like Paradata and Cloudera, and some of the other larger database firms, they're going to continue seeing wallet and market share losses due to some of these emerging providers. >> Yeah. If you could just keep that slide up for a second, I would point out, in many ways Snowflake is kind of a safer bet, you know, we talk about flight to safety, because they're well-funded, they're established. You can go from zero to Snowflake very quickly, that's sort of their mantra, if you will. But I want to point out and recognize that it is somewhat oranges and tangerines here, Snowflake being an analytical database. You take MariaDB, for instance, I look at that, anyway, as relational and operational. And then you mentioned DataStax. I would say Couchbase, Redis Labs, Aerospike. Cockroach is really a... EValue Store. You've got some non-relational databases in there. But we're looking at the entire sector of databases, which has become a really interesting market. But again, some of those established players are going to do very well, and I would put Snowflake on that cusp. As you pointed out, Bloomberg broke the story, I think last week, that they were contemplating an IPO, which we've known for a while. >> Yeah. And just one last thing on that. We do like some of the more pervasive players, right. Obviously, AWS, all their products, Redshift and DynamoDB. Microsoft looks really good. It's just really some of the other legacy ones, like the Teradatas, the Oracles, the Hadoops, right, that we are going to be impacted. And so the claw providers look really good. >> So, the last decade has really brought forth this whole notion of DevOps, infrastructure as code, the whole API economy. And that's the piece we want to jump into now. And there are some real stand-outs here, you know, despite the early data that we showed you, where CIOs are less prone to look at emerging vendors. There are some, for instance, if you bring up the next chart, guys, like Hashi, that really are standing out, aren't they? >> That's right, Dave. So, again, what you're seeing here is you're seeing that bifurcation that we were talking about earlier. There are a lot of infrastructure software vendors that are not positioned well, but if you look at the ones at the top right that are positioned well... We have two kind of things on here, starting with infrastructure automation. We think a winner here is emerging with Terraform. Look all the way up to the right, how well-positioned they are, how many opportunities they're getting. And for the second straight survey now, Terraform is leading along their peers, Chef, Puppet, SaltStack. And they're leading their peers in so many different categories, notably on allocating more spend, which is obviously very important. For Chef, Puppet and SaltStack, which you can see a little bit below, probably a little bit higher than the middle, we are seeing some elevator churn levels. And so, really, Terraform looks like they're kind of separating themselves. And we've got this great quote from the CIO just a few months ago, on why Terraform is likely pulling away, and I'll read it out here quickly. "The Terraform tool creates "an entire infrastructure in a box. "Unlike vendors that use procedural languages, "like Ants, Bull and Chef, "it will show you the infrastructure "in the way you want it to be. "You don't have to worry about "the things that happen underneath." I know some companies where you can put your entire Amazon infrastructure through Terraform. If Amazon disappears, if your availability drops, load balancers, RDS, everything, you just run Terraform and everything will be created in 10 to 15 minutes. So that shows you the power of Terraform and why we think it's ranked better than some of the other vendors. >> Yeah, I think that really does sum it up. And, actually, guys, if you don't mind bringing that chart back up again. So, a point out, so, Mitchell Hashimoto, Hashi, really, I believe I'm correct, talking to Stu about this a little bit, he sort of led the Terraform project, which is an Open Source project, and, to your point, very easy to deploy. Chef, Puppet, Salt, they were largely disrupted by Cloud, because they're designed to automate deployment largely on-prem and DevOps, and now Terraform sort of packages everything up into a platform. So, Hashi actually makes money, and you'll see it on this slide, and things, Vault, which is kind of their security play. You see GitLab on here. That's really application tooling to deploy code. You see Docker containers, you know, Docker, really all about open source, and they've had great adoption, Docker's challenge has always been monetization. You see Turbonomic on here, which is application resource management. You can't go too deep on these things, but it's pretty deep within this sector. But we are comparing different types of companies, but just to give you a sense as to where the momentum is. All right, let's wrap here. So maybe some final thoughts, Sagar, on the Emerging Technology Study, and then what we can expect in the coming month here, on the update in the Technology Spending Intention Study, please. >> Yeah, no problem. One last thing on the zero trust side that has been a big issue that we didn't get to cover, is VPN spend. Our data is pointing that, yes, even though VPN spend did increase the last few months because of remote work, we actually think that people are going to move away from that as they move onto zero trust. So just one last point on that, just in terms of overall thoughts, you know, again, as we cover it, you can see how bifurcated all these spaces are. Really, if we were to go sector by sector by sector, right, storage and block chain and MLAI and all that stuff, you would see there's a few or maybe one or two vendors doing well, and the majority of vendors are not seeing as many opportunities. And so, again, are you work-from-home aligned? Are you the best vendor of all the other emerging providers? And if you fit those two criteria then you will continue seeing POCs and evaluations. And if you don't fit that criteria, unfortunately, you're going to see less opportunities. So think that's really the big takeaway on that. And then, just in terms of next steps, we're already transitioning now to our next Technology Spending Intention Survey. That launched last week. And so, again, we're going to start getting a feel for how CIOs are spending in 2H-20, right, so, for the back half of the year. And our question changes a little bit. We ask them, "How do you plan on spending in the back half year "versus how you actually spent "in the first half of the year, or 1H-20?" So, we're kind of, tighten the screw, so to speak, and really getting an idea of what's spend going to look like in the back half, and we're also going to get some updates as it relates to budget impacts from COVID-19, as well as how vendor-relationships have changed, as well as business impacts, like layoffs and furloughs, and all that stuff. So we have a tremendous amount of data that's going to be coming in the next few weeks, and it should really prepare us for what to see over the summer and into the fall. >> Yeah, very excited, Sagar, to see that. I just wanted to double down on what you said about changes in networking. We've reported with you guys on NPLS networks, shifting to SD-WAN. But even VPN and SD-WAN are being called into question as the internet becomes the new private network. And so lots of changes there. And again, very excited to see updated data, return of post-COVID, as we exit this isolation economy. Really want to point out to folks that this is not a snapshot survey, right? This is an ongoing exercise that ETR runs, and grateful for our partnership with you guys. Check out ETR.plus, that's the ETR website. I publish weekly on Wikibon.com and SiliconANGLE.com. Sagar, thanks so much for coming on. Once again, great to have you. >> Thank you so much, for having me, Dave. I really appreciate it, as always. >> And thank you for watching this episode of theCube Insights, powered by ETR. This Dave Vellante. We'll see you next time. (gentle music)

>> From around the globe, it's "theCUBE" with coverage of SUSECON Digital. Brought to you by SUSE. >> Welcome back, I'm Stu Miniman and this is CUBE's coverage of SUSECON Digital '20. Happy to welcome back to the program one of our CUBE alumni, Alan Clark, he is in the CTO office of SUSE. He works on emerging technologies and open source. Sits on many of the boards for many of those open source organizations. Alan, nice to chat with you. Thanks so much for joining us. >> Thanks for the invitation. I appreciate the opportunity. It's always fun to chat with you, Stu. >> All right, so Alan, you know, open source of course, you know, had a broad impact on the industry. Lots of talk. You know, we talk about soft breeding the world, the impact of open source. Haas on software. Give us, you know, start us a little bit kind of the state of the state as to what you're seeing broadly when it comes to. >> You know, I'm just, I keep, I enjoy this industry, 'cause it's just booming. I got into open source a long time ago, before my hair was gray, and I just can't, it just continues to surprise me and amaze me at how much it's grown. And even from, not just as projects, right? Those continue to exponentially grow, but think about the adoption, right? And from SUSE's perspective, we've got critical mission infrastructure running on open source and that is just totally amazing, right? And they've got aerospace manufacturing firms, Fortune 100s, Fortune 500s, Fortune 50s, the world's largest banks, four or five of the world's largest banks are running on SUSE Linux, right? Automotive vendors, 12 of the 15 largest automotive vendors are running on open source, running on SUSE Linux, and 10 of the largest telecommunications firms are running on SUSE, and it just goes to show that open source is really growing and is being adopted and used by critical infrastructure for the world. Particularly in these troubling days, right? >> Yeah, I mean, Alan, I've always loved diggin' into the data, you know? I haven't followed it for quite as long as you, but I've been involved for comin' up on 20 years now, and you think back 15 or 20 years it was somebody in the back room contributing some code in their spare time when they have it. When I look at the state of open source today, you mentioned lots of enterprises are using it, but lots of enterprises are contributing to it, and it's not necessarily somebody in their spare time doing it, but more and more it part of my job is leveraging and contributing back, upsource to what's happening there, so how are you seeing that? How does that impact the overall governance of open source? >> So, that's a very good question, 'cause the amount of change is huge, right? So these open source foundations have grown very large and the number of people that are contributing to them, not just in code, but in ideas, in best practices and so forth has exponentially grown, and it's amazing to see that. Plus, I guess the other part of it that I really enjoy is it's gone global, right? It used to be these projects were kind of regional, and perhaps North America to Europe, but it's, they've gone global, so these larger projects'll have 170, 180 countries that are involved. That's truly amazing. And the thing that I find very interesting, particularly given the pandemic era, we're all sitting at our homes right now. As open source developers, we're very used to this environment. We're working from home. We're scattered around the globe. We're used to working in different time zones, different geographies, and we know how to communicate and work together, so having this distance and lack of an office is actually not that much of an impediment for open source. So it's actually kind of to their advantage. >> Yeah, no, you're absolutely right. I'd done lots of interviews with developer communities and remote work is just the way they do things. Contributing code is very much an asynchronous nature of what they were doing. Alan, I love you talked about the global nature. One of the things, I was looking forward to being at this event in person was we were going to go to Dublin, you know, great city. (Alan laughs) Love to travel. When we cover a European show, it's always, "Okay, what is different "about different geographies "compared to North America?" You know, you talk about cloud adoption in general tends to be a little bit higher in North America. Any data or anecdotes that you have globally as to how open source is maybe a little bit different and culturally thought of from organizations that might be based in Europe, Asia, Latin America, or the like? >> Yeah, that's to me one of the strengths of these communities now is the difference in perspectives that you get from the different geographies, right? From Europe to Asia and so forth, and it sometimes surprises you, right? You get so used to a few vendors maybe dominating a certain area, and what you find out is they may be strong in a certain geography, but they're not globally. And as other developers and community members and users come in and start talking about their needs and their use cases, you find that their perspective is different than yours and it's kind of that "Ah ha" moment of "Oh, we need to make sure "the software works for everybody "and fits their need." And I guess the second part of that would be, you know, with this pandemic, it's causing the whole industry dynamics to change, and businesses are finding that they've got to rapidly adapt and change, and open source is one of the ways they're able to do that, right? Our customer sentiments are changing. Their purchasing habits are obviously changed. The way we shop, the way we do business, the way we're meeting people, right? We're all doing it digitally now. That's changing the services that companies need to deliver. And one of the powers of open source is being able to provide that to them and deliver those services very rapidly to them. And another dynamic here that I'm finding is interesting is customers, or consumers of open source, the businesses that are consuming open source are realizing that with these times, you know, you've got to have multiple sources for your supply chain. We have a lot more discussion about being nationalized instead of globalized, you know, when borders shut down and you can't get your supplies from another country, where are you going to get them, right? So those kinds of discussions change your source of supplies and so forth, so you have to diversify a little bit, and that's causing new types of services that are going to be created, needed. The beauty of open source, though, is it's global, and so I can get access to it whether I'm here in Salt Lake City or I'm sitting up in Dublin, wherever I'm at. And it's awesome. It's just amazing. >> Excellent, Alan. So, you know, you talked about some of the impact of what the global pandemic happening. They can leverage remote work. Open source is something that they can get ready access to. I'm curious if there's any other things in the community, you know, rallying points that you're seeing, any good stories or anecdotes that you might be able to share. >> So, I guess the other aspect of this I find extremely encouraging is, open source is amazing for individuals, not just businesses, right, to consume it, but me as an individual to learn new ideas, new technologies, try things out. And it's a great opportunity right now, particularly for home bound to go out and learn new ideas, learn about new concepts, new technologies, learn about Kubernetes, learn about containers, learn about rapid software development, right? And SUSE's actually caught onto this. This is one of the things I find really cool is they've got a couple things that are going on. First, they've created a sandbox out there where I, as an individual, for free can go out there and give rapid application development a try. It's being at home, often I don't have the full equipment that I would have at the office, right? So getting an environment set up, having the equipment and access that I need to get an environment set up to try something out, you know, like Kubernetes or application development. I may not have that at my home. So SUSE's set up some sandboxes out there where, as a developer, I can go out and give SUSE's application platform development a try. It's easy, it's all set up for me. I can go out there and I can play. Try out new concepts, see what Kubernetes is about, see what rapid development is about. And it minimizes my, you know, the task and the equipment that I need to be able to do that. The second part of that is they've opened up a lot of their online training courses for free for developers as well and operators. So it's a great time for, we're stuck at home, it's a great time to take advantage of these resources and learn more about open source. >> Great, yeah, absolutely. Alan, I spoke to your CEO, Melissa, and we talked about the importance of the developer communities. You mentioned the sandbox there. I'm curious, anything else you've seen, kind of the changing dynamic about how developers integrate with the business. One of the constant themes we talk about is IT isn't just something that's on the side, but is a clear partner with the business and often is a driver for the business, so the developers often need some education, they need communication. What do you see and how are the development communities changing? >> Oh, so I think a great part of this, this year is all the events that are going virtual. So we've got tons of resources available within these communities and through companies like SUSE, as we just talked about, and we also have these events that are going virtual, so all this content is now becoming readily accessible. I hear often from developers saying, "Well, my company doesn't give us much "for money for traveling to these events "and conferences and so forth." Now that they're all going virtual it's given 'em great access to amazing materials, and the beauty of these events is that a lot of the material is framed around helping you understand how to develop open source, how to become a part of the community, and then also about what this technology is about, where it's heading. So you, particularly as an IT organization, I get a great insight as to where the technology's going. What's the future look like? What are the ideas that are being formed by all these individuals from around the world? What's their perspectives? And then I can turn, and tying that to the business, is I can take that and take that to my business and say, "Look, here's where the technology is heading. "Here's how we can use it to enhance our business "and deliver better services to our customer." So it's a great opportunity this year. >> Yeah, you're right, Alan. There's often that gap between the people that can attend and what content is available to everyone else, and, you know, seems to be opening up. Everything from, you know, it funny, Disney is giving away the recipes for some of the things that they're doing through the conferences, typically free to attend and on demand soon after doing. All right, Alan, you're in the emerging technologies group. So, last thing I want to ask is give us a little bit look forward. What is your group looking at or the communities that you're involved in? What are some of the things that are exciting you and your peers? >> So, SUSE expanding from the edge to the cloud, to the core, right? And so we're covering things all the way from the gamut. Lot of new exciting stuff happening out on the edge with IoT and with edge services. Pretty excited about that area. SUSE's had a lot of experience in that space, particularly if you look at manufacturing providing, helping them, those businesses, the manufacturing firms meet their SLAs. Had a lot of experience in the retail space, around point of service. That, of course, is pivoting to self-service, to frictionless shopping, that types of stuff, so it's pretty exciting in those areas. So there's a lot going on in the edge. Healthcare, SUSE's been very involved, embedded in a lot of healthcare devices. That business will continue to grow, so we're seeing a lot about, on the edge. We talked a bit about rapid development. So back at the core and the cloud we're trying to make that a seamless experience so you can push those workloads, build those workloads in a containerized, micro-service manner, and distribute those pieces where it makes sense, right? So we talk about artificial intelligence gathering the data out on the edge, doing a bit of filtering and processing, moving that up to the core and the cloud, being able to mine that data, learn intelligently, then orchestrate your services, orchestrate your core appropriately, right? To meet those demands that your customers are putting on you. There's just a lot going on. We got containers. We've got hybrid cloud. We've got multicloud. We got intelligent orchestration. Then we could go on and talk a ton, we could talk for 30 minutes just about what's happening in the data space. So there's a lot to look forward to when it comes to open source and the innovation that's happening out there. >> All right, well, Alan Clark. Great to catch up with you. Thank you so much for giving us a little bit of vision. >> Thank you, Stu. >> Where we've been, and where we're going. >> Thank you very much. >> All right, I'm Stu Miniman and stay tuned for more coverage from SUSECON Digital '20. Thank you for watching "theCUBE." (calm electronic music)

>> From the SiliconANGLE Media Office in Boston, Massachusetts, it's theCUBE. Now, here's your host, Dave Vellante. >> Hello everyone and welcome to this week's episode of theCUBE Insights, powered by ETR. In this Breaking Analysis I want to lay out my 2020 predictions using insights gleaned from theCUBE blended with ETR spending data. You know, 2019 marked our 10th year of doing theCUBE. Over that time we've had the pleasure of covering nearly 1000 events and milestones, including the exit from the great softness of 2008 and 2009. You know theCUBE has extensively tracked a 10 year bull market. We've covered the era of data. We saw the rise and profitless prosperity of the big data and opensource Hadoop movement, where we predicted the practitioners, not vendors, would benefit the most from big data. We've covered many dozens of acquisitions including the 60 billion dollar chess move made by Michael Dell acquiring EMC, and a launch of hundreds of startups in flash, hyper-converged, big data, AI, blockchain, crypto, security and SaaS. There'll be other days to talk about theCUBE and review that, today's all about predicting the future, using spending data and insights from the thousands of interviews we've done on theCUBE. So let's get right into the ETR data and start with the high-level spending. Remember in October, ETR released its survey results and stated that we're coming out of a multiyear investment cycle in digital transformation. Enterprise IT buyers have learned what works, and on which technologies they're going to double down. They're now narrowing their investments on emerging technologies, picking those winners for the next gen tech, and at the same time, they're cutting redundancies from legacy players that they were keeping on as a hedge. Buyers are picking bundled suites from a handful of mega vendors, and solidifying their investments. We're seeing a multi-generational dynamic repeat itself, where buyers are creating a balance between the convenience of packaged offerings, i.e. bundles, and leveraging best of breed technologies to drive innovation. So on balance, the ETR data shows that a contraction in spending and tepid CIO sentiment is impacting both emerging vendors as well as traditional players, and these trends are most pronounced in the very largest organizations, which have always been the best bellwether in ETR's data sets. Let me share with you what one IT executive said recently that I think really sums up the situation quite well. He said, "ETR's findings mirror what we're doing today, "in that we spend most of 2018 bringing in "a lot of the new, core technology. "I believe what you're seeing now is not a lull in spend, "but an operationalization of what we've already purchased. "We're not spending on what's next yet, "because we're still rolling out what we just bought." This is from a VP of global IT at a large public manufacturing company, I said he, it could be a she as well. I think that she's summing it up correctly, and it reflects many of what customers on theCUBE tell us. Now, let's take a look at the macroeconomy. GDP growth is going to come in at about 2.3% this year, give or take. It's not going to hit the Trump administration's goal of 3% plus, but consumers are clearly powering steady growth. At least for now. IT spending should grow at about a point or two above GDP, so let's put that at, say, 4%. We're right in the middle of a Santa Claus rally, and the S&P is above 3200 today. Tech has been a powerful tailwind for stocks, and I think stocks, tech stock's going to take a breath in early 2020, but I expect continued strong growth in the economy and tech spending after a Q1 pause. I could see the S&P flirting with 3700 or even higher in 2020, and I think the tech sector will be a benefactor of that momentum, providing an impetus for continued growth. Here's my thinking on that. So much of 2020 is going to be about the election, and to me the election is going to be really about the economy. And I predict the economy is going to remain steady. And as the IT leader I quoted earlier said, customers will be operationalizing what's been previously purchased. Here's what's different in 2020. Tech projects have historically been very risky investments, and have required higher internal rates of return, IRRs, to get approved by CFOs. But the cloud has altered two factors. One, is that it's allowed more experimentation for way less money. The second is cloud, by shifting CAPEX to OPEX, allows for much more incremental, lower risk investments. So I think you'll see continued steady growth, powered by the cloud, which allows experimentation, and importantly higher hit rates of success. These successful projects will throw off cash for companies, and CFOs are getting on board because they realize it's driving innovation. They also realize that IT does matter, maybe not in the form that Nick Carr envisioned, but a new generation of IT that creates competitive advantage. This brings me to my first main prediction, which is the growth of cloud computing is going to moderate, but the cloud will continue to steal significant share from on-prem spending. Now the narrative that the pendulum is swinging back in my view, is a false narrative. Rather, the pendulum has swung, and the cloud is the underpinning of innovation. Now having said that, I do think we're seeing a bit of an equilibrium in spending, where buyers have identified those workloads that are going to remain on-prem, which is why you see, for example, AWS, Azure, and Google making moves in hybrid. Hybrid slash on-prem offerings. What this chart here shows from ETR, so from 2010 through October '19 survey on cloud spending, I had to block out the 2020 survey as it's currently in the field, I'm not allowed to show that data. The yellow line is market share, which in ETR parlance, as you remember, is pervasiveness, or mentions in their survey. The blue line is spending momentum, measured as net score, which essentially subtracts the percent of customers spending less from those spending more. The long, steady march of cloud, as you can see, continues, and there's no indication that it's going to abate. That said, the penetration of cloud has become much more meaningful, so share gains will be more hard-fought for the cloud guys. Now, you may see this as a non-prediction, or a hedge. It's not, let me be clear. Cloud will continue to steal share from on-prem, but share gains for the cloud vendors will be more difficult. Which brings me to part B of this prediction. What I'm showing in this chart is market share from ETR's January 2016 survey through October '19. And I'm showing spending for three on-prem vendors within AWS, Azure, and Google Cloud accounts. And I'm picking on Oracle, IBM, and Dell EMC as three prominent on-prem proxies, and you can see the steady decline in market share for these companies. And even though there's a bit of an uptick in October, I don't see this as a reversal. What's going to happen is that traditional on-prem vendors are going to step up their cloud strategies. Specifically with multicloud management. This is going to be the case with Dell, who's going to leverage VMware, and in the case of IBM, they'll try to take advantage of Red Hat in that multicloud game. Now both IBM and Oracle, who each have public clouds are going to dig their heels in, they're going to get customers in a headlock, and provide big financial incentives for them to use their captive clouds. All right, so with the high-level spending comments that I made earlier, and that cloud discussion that we just had as a backdrop, the question is, which companies will do well in the coming year? I'm going to call out five companies, that I want to highlight where the ETR data intersects what we're seeing on theCUBE. The prediction is these five players will do well in 2020, they're going to power through any downturn in spending, and they're going to thrive in the face of the cloud share shift. So the chart here shows data from the ETR October 2019 survey, and it lays out net score or spending momentum for these companies, that I am predicting will be winners in 2020 and beyond. And the five companies are UIPath, Snowflake, Databricks, HashiCorp, and Rubrik. Let me start with UIPath. They are the leader in robotic process automation. I think RPA is going to do well even in a downturn, because more companies will be looking to automate and save money, even in a softer climate. Automation Anywhere is another player in this space, they're doing pretty well, and I predict that UIPath will come out on top of this space, but both UIPath and Automation Anywhere can thrive. Next company is Snowflake, they are changing the analytic database market, and I've covered them before in previous Breaking Analysis segments. They are going to continue to grow nicely in my view. They are 100% cloud-based, and they participate in all popular cloud platforms. Now ironically, they compete with AWS RedShift, who continues to copy some of the innovations that Snowflake has popularized. But AWS and Snowflake are strong partners, so there's room for both companies to thrive. Snowflake especially, as they play in clouds other than just AWS. Which brings me to Databricks. We're seeing a new type of workload emerge in the cloud for modern analytic databases, where organizations are taking all this data that they have, lots of it in the cloud, and they're structuring it within a Snowflake database, or RedShift, and they're bringing Databricks tooling to the equation to be able to query and visualize the data in near real time. Now of course, as I say, AWS plays here with RedShift, and they're selling a lot of EC2, so they love Snowflake. All major cloud players are seeing this type of workload enter the mix, and it's going to be a strong area of growth in 2020 and beyond. Next thing I want to talk about is HashiCorp. HashiCorp is capitalizing on this trend toward cloud-native computing. The company provides opensource tooling for developers, and is all about simplifying application deployment independent of the underlying platform, whether it's virtual, container, or cloud. Five years ago, the players in the space that got all the attention on theCUBE were Chef, Puppet, Ansible and Salt, and today, especially again on theCUBE, you hear the most about Hashi and Ansible, and in fact we were at AnsibleFest with theCUBE, and we heard lots about HashiCorp, so they both complement and compete with the older players. To me, this reminds me of Spark within the Hadoop ecosystem. Hashi has raised about 174 million in VC, and as you can see they have very strong spending momentum in the ETR dataset, with a net score, as shown, of 63%. Now finally, I want to talk about Rubrik, which has been a consistent performer in the ETR dataset. They're trying to transform backup into data management as a discipline. They compete with established players in the data protection space, guys like Veritas, Dell EMC, IBM and CommVault. Now Rubrik is not the only new or newish player here, that's doing very well, Cohesity, who's relatively new, Veeam, which has been around for a decade, both doing very well and showing up strong in ETR surveys, especially Veeam, but Rubrik has been a consistently strong performer and has been outpacing the others, so I want to call them out. Look for these five to do very well in 2020, and into the next decade. So that brings me to my next prediction, I want to talk about Kubernetes. This prediction is twofold. Kubernetes is going to continue its strong showing as this data from ETR shows. This is Kubernetes' market share in the October 2019 survey, so Kubernetes spend had a 76% net score. So very very strong. But the other part of the prediction is that Kubernetes will become embedded into virtually every platform, and people will stop thinking about it as a separate market. Already today, there's little discussion of the idea of a Kubernetes distro, I mean Anthos is an example of a Kubernetes stack, but it can be run in the cloud, it can be run on-prem, anywhere. VMware Tanzu, Microsoft Azure Arc are other examples, they're really not stacks, but they're management platforms that can manage anyone's Kubernetes instances. I like to think of this as kind of like flash. You remember when everyone looked at flash storage as a separate market, well today it's just embedded everywhere. And that's kind of what's happening with Kubernetes. So spending momentum is going to continue to be strong, but by 2023, Kubernetes will be ubiquitous, and not really thought of as a separate entity. All right, for my next prediction, I want to talk about cybersecurity. I did a Breaking Analysis earlier this year on security, and I showed this slide. And as you can see, I've added a little something in the red stars for my prediction. So what this chart shows is two views of net score, the left-hand side shows the ranking by net score, and you can see CrowdStrike, Okta, Shape Security, which was just, by the way, bought by F5, that was an announcement. Twistlock, which is now Palo Alto Networks, and you can see the others down that list. On the right-hand side is net score, but it's ranked by shared N, which is a measure of pervasiveness in the ETR dataset. What I've added is the four star companies, that is those companies that have both spending momentum and are pervasive in the ETR survey. So the prediction is 2020 we'll see the four star companies maintain their position and gain strength in 2020. These include established players with portfolios where they can bundle like Microsoft, Cisco, Palo Alto Networks, Splunk, Proofpoint, Fortinet, and CyberArk Software. And then the newer companies like Okta and CrowdStrike are going to continue to gain share faster than the larger players. Now you also may see companies like SailPoint, Illumio, and SentinelOne emerge as four star companies over the next 24 months. Now the one company that's not on this list that is a major player in security is AWS. AWS is the cloud security leader, and is in a category all by itself in many ways. As I said in my security segment earlier this year, the market is incredibly fragmented, and it's going to stay that way. Each year we look back and say "Did we spend more on security?" and "Are we more safe?" And every year the answer is yes, and no. And 2020 will be no different. Now if you look at the various data sources, we spend approximately 120 billion dollars annually on cybersecurity. The worldwide economy is about 85 trillion in dollar terms, so on balance, we spend about .14% on securing our economy, so we're barely scratching the surface. The market is going to remain highly fragmented, the rich will get richer if they have four stars, new players will continue to enter the space, and M&A will continue to be robust. Now if you exclude my long shot that the S&P will break through 3700 next year, that makes nine predictions. For my 10th and final prediction, I don't have hard data from ETR, but I have a strong opinion on this, and that is that the edge will be won by developers, you've heard me talk about this before. Specifically, platforms like Outposts, which are essentially programmable infrastructure which bring a cloud development platform to the edge, is how that space will evolve. It won't be won by shoving traditional servers and storage boxes out to the edge. Rather, it will grow by coders being able to build new applications and workloads on top of infrastructure as code. Okay, that wraps up my 2020 predictions. I'd very much like to hear your opinion, so you can leave your thoughts or your own predictions in the comments sections of this video, or go to my LinkedIn posts. You can reach me @DVellante on Twitter, love to hear your thoughts. And don't forget, this series is available on iTunes, Spotify, and other podcast platforms for your listening pleasure. I'd like to wish everyone a safe and restful holiday season and a prosperous, healthy 2020. Enjoy your families, enjoy this time, this is Dave Vellante, signing out from the latest episode of theCUBE Insights powered by ETR, thanks for watching, everybody. We'll see you next time. (techno music)

(upbeat techno music) >> Announcer: From New York City, it's theCUBE, covering New Relic FutureStack 2019, brought to you by the New Relic. >> Hi, I'm Stu Miniman and this is theCUBE's exclusive coverage of New Relic's Futurestack 2019 here in New York City, seventh year of the show. Our first year here, about 600 or so in attendance, and real excited, because we've had some of the users here to help kick off our coverage. And joining us, first time guest on the program, Josh Biggely is a senior engineer of Enterprise Monitoring, with Cardinal Health coming to us from a little bit further north and east than I do, Prince Edward Island, thank you so much for coming here to New York City and joining me on the program. >> Yeah, thanks for having me Stu, I'm excited to be here. I haven't been in New York, it's probably been more two decades. So it's nice to be back in a big city, I live in a very small place. >> Yeah, so if you go to Times Square, it's now Disneyland, is what we call it. It's not the 42nd street that it might've been a couple of decades ago. I grew up about 45 minutes from here, so it's gone through a lot, love the city, especially gorgeous weather we're having here in the fall. >> I'm excited for it. >> All right, so Josh, Cardinal Health, health is in the name so we think we understand a little bit about it, but tell us a little bit about the organization itself and how it's going through changes these days. >> Sure, so Cardinal Health is a global healthcare solutions provider. We are essential to care, which means we deliver the products and solutions that your healthcare providers need to literally cure disease, keep people healthy. So we're in 85% of the hospitals in the United States, 26,000 pharmacies, about 3,000,000 different home healthcare users receive products from us. Again we're global, so we're based in Dublin, Ohio, just outside of Columbus. But obviously, I live in Canada so I work for the Cardinal Health Canada Division. We've got acquisitions around the world. So yeah, it's an exciting company. We've recently gone through a transformation not only as a company, but from a technology side where we've shifted one of our data centers entirely into the cloud. >> All right, and Josh, your role inside the company, tell us a little bit about, you said it's global, what's under your purview? >> So my team is responsible for Enterprise Monitoring, and that means that we develop, deploy, support and integrate solutions for monitoring both infrastructure applications and digital experience for our customers. We have a number of tools, including New Relic, that we use. But it's a broad scope for a small team. >> Stu: Okay, and you've talked about that transformation. Walk us through a little bit about that, what led to, as you said, some big moves into public cloud? >> Yeah, our team is part of an overall effort to allow Cardinal Health to be more adaptive, to be more agile. The move to cloud allows teams that are developing applications and platforms to make a decision how to respond to the needs of their customers more rapidly. Gone are the days of, "I need a new server, "I need to predict six months from now "that I'm going to need a new server, "put the order in, get it delivered, "get it racked, get it wired." We watch a lot of people, the provision on demand. I mean, our senior vice president, or my senior vice president, likes to say, "I want you to fail fast, fail cheap." He does not say fail often. Although sometimes I do that, but that's okay. As long as you recognize that you're failing and can roll that back, redeploy, It's been really transformative for my team in particular, who was very infrastructure focused when I started with the company five years ago. >> Stu: All right, and can you bring us inside from your application portfolio, was it a set of applications, was it an entire data center? What moved over, how long did it take, and can you share what cloud you're using? >> Sure, so it's been about a two year journey. We're actually a multicloud company. We've got a small footprint in Azure, small footprint in AWS, but we're primarily in Google Cloud. We are shutting down one data center, we are minimizing another data center, and we've moved everything. We've moved everything from small bespoke applications that are targeted on team to entire ecommerce platforms and we've done everything from lift and shift, which I know you don't like to hear. But we've done lift and shift, we've done rehosting, we've done refactoring and we have re-architected entire platforms. >> Yeah, so if you could expand a little bit when we say lift and shift, I'm fine with lift and shift as long as there's another word or plan after that which I'm expecting you do have. >> Josh: Yeah, absolutely. So the lift and shift was, "Hey, let's move from our data centers into GCP. "Let's give teams the visibility, the observability "that they need so that they can make the decisions on "what they need to do best." In a lot of cases, or in fact, in 15% of the 6,500 severs that we touch, we actually full out decommed the instance. Teams had them, they were running at our data centers but they weren't actually providing any value to the company. >> So you said your team before was mostly concerned about infrastructure and a lot of what you did is now on GCP so you fired the entire team and you hired a bunch of PhDs to be able to manage Google environments? >> Absolutely not. (laughter) The principals of enterprise monitoring as a practice still apply in a cloud. We are, at heart, data geeks. And I would fair say that we're actually data story tellers. Our job is to give tools and methodologies to application teams who know what the data means in context, but we give the tools to provide that data to them. >> Stu: All right, love that. I believe I've actually seen data geek shirts at the the New Relic shows itself. But data story tellers, that was kind of thing that you heard, "I have a data scientist "that's going to help us to do this." Is that data scientist in New York or are you actually enabling who is able to tell those data stories today? >> So that is the unique part. Data story telling is not a data science. I wish that I could be a data scientist, I like math, but I'm not nearly that good at it. A data story teller takes the data and the narrative of the business, and weaves them together. When you tell someone, "Here's some data." They will look at it and they will develop their own narrative around it. But as a story teller you help craft that narrative for them. They're going to look at that data and they're going to feel it, They're going to understand it and it's going to motivate them to act in a way that is aligned with what the business objectives are. So data story tellers come in all forms. They come as monitoring engineers, they're app engineers, but they're also people who are facing the customer, they're business leaders, they're people in our distribution centers who are trying to understand the impacts of orders in their order flow, in their personnel that they have. It is a discipline that anyone can engage in if we're willing to give them the right tools. >> All right, so Josh, you got rid of a data center, you're minimizing a data center, you're shifting to cloud, you're making a lot of changes and now being able to tell data stories. Can you tell us organizationally everything goes smoothly or are their anythings that you learned along the way that maybe you could share with your peers to help them along that journey? And any rough spots, with hindsight being what it is, that you might be able to learn from? >> Yeah, so hindsight definitely 20/20. The one thing that I would say to folks is get your data right. Metadata, trusting your data is key, it's absolutely vital. We talk a lot about automation and automation is one of those things that the cloud enables very nicely. If you automate on garbage data, you are going to automate garbage generation. That was one of our struggles but I think that every organization struggles with data fidelity. But teams need to spend more time in making sure that their data, specifically their metadata, around, "Hey is this prod, is it non-prod, "what stack is this running, who built it?" Those things definitely need to be sorted out. >> Okay, talk about the observability and the monitoring that you do, how long have you been using New Relic and what products? And tell us a little about that journey. >> Sure, so we've been using New Relic for about two years. It was a bit of a slow run up to its adoption. We are a multi-tool company so we have a number of tools. Some of them are focused primarily on our network infrastructure, our on-prem storage. Although Cardinal had moved predominantly to the cloud, we have distribution centers, nuclear pharmacies all around the world. And those facilities have not gone into the cloud. So you've got network connectivity. New Relic for us has filled our cloud niche and observability, as Lou announced, is going to give us context to things that we're after. You hear the term dark data, we call them obs logs. It's data that we want to have, we only need it for a very short period of time to help us do post-op or RCAs as well as to look at, overall in our organization, the performance of the applications. For us, New Relic is going to give us an option to put data for observability. Observability is really about high fidelity data. In its world of cloud, everyone wants everything right now. And they also want it down to the millisecond. A platform that can pull that off, that's a remarkable thing. >> Yeah, Veruca Salt had it right, "I want it now." So are you using New Relic One yet? >> We have been using New Relic One for at least a couple of months going back into March this year. It's exciting, we're one of those companies that Lou talked about in his key note, we have hundreds of sub accounts. And we did so very intentfully, but it was a bit of a nightmare before we got to New Relic One. That ability for a platform team to see across multiple sub accounts, really powerful. >> Okay, so you saw a lot of announcements this morning. Anything particular that jumped out, you were excited? Because Lou kept saying over and over, and if you're using New Relic One, "This is free, this is free, this is free." That platform where it's all available for you now. >> I think the programmability is one of the things that really got me excited. One of the engineers on my team had a chance to go and sit with Lou and team, two weeks ago, and was part of that initial Hackathon. Made some really interesting things. That's exciting so shout out to Zack and the work he did. Logging, for me, is something that is huge. I know we've got data that we should have in context. So that Lou announced five terabytes of ingestion for free, all I could do was tap my fingers together and think, "Oh, okay. You're asking for it, Lou. Challenge accepted." (laughter) >> Stu: That's exciting, right. So you feel that you're going to be building apps, it sounds like already, at the FutureHack. That you're starting to move down that path. >> Definitely, and I'm really excited. Not to necessarily give it to my team. We build the patterns for teams that needs patterns, but there are so many talented individuals at Cardinal Health who, if we give them the patterns to follow, they're just going to go execute. Open sourcing that is a brilliant idea and really crowd sourcing development is the way to go. >> Yeah, I think you bring up a really interesting point. So even though your team might be the one that provides the platform, you're giving that programmability, sensibility to a broader audience inside the team and democratizing the data that you have in there. >> Yes, you keyed in on one of the things I love to talk about which is democratized access to data. Over and over again you'll hear me preach that, "I know what I know but I also know what I don't know "and more particular I don't know what I don't know. "I need other people to help me recognize that." >> We've really talked about that buzzword out there about digital transformation. When it is actually being happened, it goes from, "Oh, somebody had an opinion," to, "Wait, I actually now can actually get to the data, "and show you the data and leverage the data "to be able to take good actions on that." >> That's right, data driven decision making is not just just an idiom. It's not something that is a buzzword, it is a practice that we all need to follow. >> Stu: All right, so Josh, you're speaking here at the show. Give our audience just a quick taste, if you will, about what you're going to be sharing with your peers here at the show. >> We've actually talked about a lot of it already so I hope that people are not going to watch this session before my session later. But it really is around the power of additional transformation, the power of observability, what happens when you do things right, and the way the cloud makes teams more nimble. I won't give you it all because then people won't watch my session on Replay but, yeah, it'll be good. >> Well, definitely they should check that out. I'm hoping New Relic has that available on Replay. Give the final word here, what you're really hoping to come out of this week. Sounds like your team's deeply engaged, you've done the Hackathon, you're working with the executive teams. So FutureStack 2019, what are you hoping to walk away with? >> For me, it's about developing patterns. My team, in addition to our enterprise architecture team, is responsible for mapping out what we're going to do and how we're going to do it. Teams want to go fast and if we're not going to lay down the foundation for them to move quickly, especially in the realm of enterprise monitoring, they're going to try do it themselves. Which may or may not work. We don't want to turn teams away from using specific tools if it fits, but if there's a platform that will allow them to execute and to keep all that data centralized, that is really the key to observability. Having that high fidelity data, but then being able to ask questions, not just of the data you put in, but the data that put in maybe by a platform team or by a team that supported Kubernetes or PCF. >> All right, well, Josh Biggely, thank you so much for sharing all that you've been going through in Cardinal Health's transformation. Great to talk to you. >> Thanks so much, Stu. >> All right, lots more here at New Relic's FutureStack 2019. I'm Stu Miniman and as always, thank you for watching theCUBE. (light techno music)

>> Narrator: From Seattle, Washington it's the CUBE covering AWS Imagine non-profit. Brought to you by Amazon web services. >> Hey welcome back everybody, Jeff Frick here with the CUBE. We're on the waterfront in Seattle, it's an absolutely gorgeous couple of days here at the AWS Imagine Nonprofit Conference. We went to the AWS Imagine Education Conference, this is really all about nonprofits and we're hearing all kinds of interesting stories about how these people are using AWS to help conquer really big problems. We're going to shift gears a little bit from the two footed problems to the four footed problems and that's animals and everybody likes animals but nobody likes animal shelters and nobody likes the ultimate solution that many animal shelters used to use to take care of problems. But thank you to our next guest, that is not quite the case so much anymore. So we're really happy to have Angie Embree on. She is the CIO of Best Friends Animal Society, Angie great to see you. >> It's great to see you as well and thank you for having me. >> Oh absolutely! So before we got on I just heard this crazy, crazy statistic that when your organization started in 1984 approximately 17 million animals were killed in US shelters per year. That number is now down to 700 thousand, that is a giant, giant reduction. And yet you, with big audacious goals really are looking to get that to zero. So, that's a giant goal, give us a little bit of background on the organization and how you decided to go after a goal like that and some of the ways you are actually going to achieve it. >> Well, the organization started in 1984 and it started with a group of friends in Southern Utah who decided that, you know the killing in America's shelters just had to go. So really the Best Friends founders started the no-kill movement along with a gentleman in San Francisco by the name of Rich Avanzino. And as you said, they took you know the killing down from 17 million in 1984 to approximately 733 thousand now. The organization started as just the sanctuary, we have the largest no-kill companion animal sanctuary in the country where we hold about 17 hundred animals every day. And we also have, you know, knowing that we needed to help out the rest of the country we have built life saving centers in Houston, Texas. Or we're working on Houston, Texas but Los Angels, California, New York City, Salt Lake City, Atlanta, Georgia, it seems like I've left somebody out but, >> Probably, but that's okay. >> We have life saving centers all over the country. So it was really, you know, when they realized what was going on in America's shelters it was really the idea that we should not be killing animals for space. So, just recently in fact, I will say recently but in the last few years, Julie Castle our CEO put kind of, did our moon shot, put that stake in the ground and said we're going to take this country no-kill by the year 2025. >> Right. >> So it's super exciting. >> So it's really interesting because you guys are trying to execute your vision, and it's easy to execute your own vision, but it's a whole different thing when you're trying to execute your vision through this huge infrastructure of shelters that have been around forever. So, I wonder if you can explain kind of what's your relationship with shelters that you don't own. I guess, I think you said before we turned on the cameras there are affiliates, so how does that relationship work? How do you help them achieve your goal which is no-kill. >> Yeah, so we have over 27 hundred network partners around the country. And what we do is we help to educate them on, you know we understand their problems, we have creative programs to solve those problems. So we help to educate them on, you know, how they can implement these programs within their shelters. We provide them grant funding, we have an annual conference every year where they can come and learn. But they're really our partners and you know we know we can't do it alone. It's going to take us, it's going to take them and it's going to take everybody in every community to really step up and help solve the problem. >> Right, and what was the biggest thing that changed in terms of kind of attitude in terms of the way they operate the shelter because I think you said before that a lot of the killing was done to make room. >> Right, killing is done usually for space. >> So what do they do know? Clearly the space demands probably haven't changed so what are they doing alternatively where before they would put the animal down? >> Well alternatively we're doing transport programs. So there are areas in the country that actually have a demand for animals. So instead of killing the animals, we put them on some sort of transport vehicle and we take them to the areas that are in demand. We also do what's called a trap-neuter-return program. So one of the biggest problems across the country are community cats so those, a lot of people call them feral cats but they're community cats and usually have a caretaker. But what we do is we trap those cats, we take them into the shelter, we neuter them and vaccinate them and then return them to their home. That keeps them from making a lot of other little cats. >> Making babies (laughs) >> So yeah, cat's are one of the biggest problems in shelters today because of the community cats, they're feral cats and they're not adoptable. So if we can, we don't have to kill them. We can, you know, we can keep them from reproducing as I said and then we can put them back in their habitat where they live a long healthy life, happy life. >> Right, so you said you've joined the organization 5 years ago, 5 and 1/2 years ago and you're the CIO, first ever CIO. >> I am (laughs) >> What brought you here and then now that you're here with kind of a CIO hat, what are some of the new perspective that you can bring to the organization that didn't necessarily, that they had had before from kind of a technical perspective? >> Well, what brought me here was, I never expected to be here, if you would have told me I would be the CIO at Best Friends Animal Society you know 10 years ago I would have said you're kidding because I didn't really realize that there were professional positions in organizations like Best Friends. But I, you know, my journey begins the same as, began the same as a lot of peoples did. I was that little kid always bringing home animals and you know my mother hated it. You know it was always something showing up at our doorstep with me, you know. And I just loved animals all my life and as I went through college and got my degree and started my professional career, then I thought well I'm going to of course have animals because I can have as many as I want now, right! (laughs) So I started adopting, and I didn't even realize until I was in my 30s that they were killing in shelters and I learned that in Houston, Texas when I lived there. I was working for IBM at the time, and one day a lady came on the television and she said they were doing a new segment and she said we're a no-kill shelter and I thought oh my god if there are no-kill shelters then there are kill shelters, right? >> There must be the other. >> Yeah so, to make a long story short then I started not working in animal welfare but doing more to support the movement and donating. Adopting from shelters and fostering animals and then one day I had been to Best Friends as a visitor vacationing in this beautiful part of Utah. But I saw the CIO ... >> Position. >> position open and I said I'm going for it. >> Good for you. >> Yeah. >> Good for you, so now you're there so what are some of the things you've implemented from kind of a techy, you know kind of data perspective that they didn't have before? >> Well, they didn't have a lot. >> They probably didn't have a lot, besides email and the obvious things. >> Being the first CIO I don't know that I knew what I was walking into at the time because I got to Kanab, and Kanab Utah where the sanctuary is, is the headquarters. And Kanab is very infrastructure challenged. >> (laughs) Infrastructure challenged, I like that. >> There is one ISP in Kanab and there is no redundancy in networks so we really don't have, you know, you come from the city and you think, you take these things for granted and you find out oh my god, what am I going to do? And Kanab is you know the hub of our network, so if Kanab goes down, you know the whole organization is down so one of the first decisions I made was that we were going to the cloud. >> Right, right. >> Because we had to get Kanab out of that position and that was one of our, one of the first major decisions I made and we chose AWS as our partner to do that so that was very very exciting. We knew that they had infrastructure we couldn't dream of providing. >> Right, right. >> And, you know we could really make our whole network more robust, our applications would be available and we could really do some great things. >> You're not worried about the one ISP provider in Kanab because of an accident that knocks a phone pole down. >> Yeah, yeah. >> All right but then you're talking about some new things that you're working on and a new thing you talked about before we turned the cameras on community lifesaving dashboards, what is that all about? >> Okay, so a couple of years ago the community lifesaving dashboard is the culmination of two years of work. From all across the Best Friends organization not just the IT department, in fact it was the brainchild of our Chief Mission Officer Holly Sizemore. But it's really, in animal welfare there's never been a national picture of what the problem really is regarding killing animals in shelters. So we did this big. >> Because they're all regional right? They're all regional shelters, very local. >> They're all local community shelters, yes. And transparency isn't forced, so you know some states force transparency, they reinforce in the report numbers but a lot of states don't. >> At the state level. >> Yeah, a lot of states don't, so. You know when you're killing animals in shelters you really don't want people to know that. >> Yeah, yeah it's not something you want to advertise. >> Because the American public doesn't believe in it. So anyway we worked really hard to collect all this data from across the country and we put it all into this dashboard and it is now a tool where anybody in the public, it's on our website, can look at it and they can see that where we're at from a national level. They can see where they're at from a state level, they can drill down into their community and they can drill down to an individual shelter. >> Wow. >> And the idea behind the dashboard is to really, is to get communities behind helping their shelters. Because as I said earlier, it's going to take us all. >> Right. >> And not only Best Friends and our partners but the public plays a big part of this. >> Right, and so when did that roll out? Do you have any kind of feedback, how's it working? >> It's working wonderfully, we rolled it out at our conference in July. >> So recently, so it's a pretty new initiative. >> Yeah it's just a few weeks old. >> Okay. >> We rolled it out at our national conference and we were all a bit nervous about it, you know especially from a technology perspective. >> Right, right. >> We knew that being the first of it's kind ever in animal welfare that you know it was going to get a lot of publicity both inside and outside the movement. >> (laughs) How you want to say both pro and con. >> Yeah, and it's sitting on our website, well really pro and con. >> Right, right. >> But it's sitting on our website and we're like okay, we don't know what kind of traffic we're going to get, you know what are we going to do about this? So we spent a lot of time with Amazon prior to the launch, you know having them look at our environment and getting advice, discussing it with them. >> Not going to bring down that ISP in Utah. >> No, thank god! (laughs) >> (laughs) >> No it wasn't, thank god we were in the cloud. So Amazon really helped us prepare and then the day of the launch, we knew the time of the launch. So we actually had a war room set up, a virtual war room and we had Amazon employees participating in our war room. We watched the traffic and we did get huge spikes in traffic at all times through the day when certain things were happening. And I'm happy to say from a technology perspective it was a non-event because we did not crash we stayed up, we handled all the traffic, we scaled when we needed to, and we did it you know, virtually at the press of a button. >> Awesome. >> Or the flick of a switch, whatever you want to say. >> That's what you want right? >> Yeah, exactly. >> You just don't want anyone to know, I was like give a good ref, nobody's talking about you you probably did a good job. >> Yeah, exactly yeah. >> Good, so before I let you go so what are some of your initiatives now looking forward. You've got this great partner in AWS, you have basically as much horsepower as you need to get done what you need to get done. What are some of the things that you see, you know kind of next for your roadmap? >> Well, we have a lot. >> Don't give me the whole list (laughs) >> No I'm just going to hit on a few key points. I think, you know we used Amazon initially as our cloud infrastructure but I think the biggest thing we're looking at is platform as a service. There is so much capability out there with predictive analytics, machine learning, artificial intelligence, ARVR, you name it facial recognitions, so we're really investigating those technologies because we think they have you know they could have a huge impact on our movement and really help us achieve life saving. >> Right, right. >> And, I think that, you know we're starting we have our fledgling data science program. We're using the Amazon data lake technology, Athena, Glue, they were just telling me about data lake formation which I just a few minutes ago emailed my data guy and said start looking at data lake formation. >> Right, right. >> So, I mean we're really investing in the platform as a service. The other thing I see is that we're, animal welfare is sort of broken from a technology perspective and a data perspective. In that we have no interoperability and you know we don't have the data available. So lets say you want to adopt a 5-year old animal. Well, you go to a shelter you can't get 5 years of history on a 5 year old animal. So it's really starting to fix the foundation for the movement as a whole, not just Best Friends. So, making sure that you know the veterinary data is there, all the data from the pet ecosystem is there. So we're investigating with AWS they're actually coming to our sanctuary in a couple of months, we're going to do a workshop to figure out how we do this, how we really fix it so that we have interoperability between every shelter when an animal moves from shelter to rescue or whatever so that their data follows them wherever they go. So adopters are fully informed when adopting an animal. >> Because you're in a pretty interesting position, because you're not with any one particular shelter you kind of cross many many boundaries. So you're in a good position to be that aggregator of that data. >> Yeah, I don't know that we want to be the aggregator but we want to lead the movement towards doing that. Just getting the technology players, the shelter management systems, the other people who play a role in technology for animal welfare, getting them in a room and talking and figuring out this problem is huge. >> Right. >> And with a partner like Amazon we feel it can be solved. >> Right. Well Angie thank you for taking a few minutes and sharing your story, really really enjoyed hearing it. >> All right thank you so much. >> All right, she's Angie, I'm Jeff you're watching the CUBE we're at AWS Imagine in Seattle, thanks for watching we'll see you next time. (upbeat music)

>> live from Boston, Massachusetts. It's the Cube covering A W s reinforce 2019. Brought to you by Amazon Web service is and its ecosystem partners. >> Hey, welcome back and run cubes. Live coverage of A W S Amazon Webster's reinforced their inaugural conference around security here in Boston. Messages. I'm John for a day. Volante Day we've been talking about Blockchain has been part of security, but no mention of it here. Amazon announced a Blockchain intention, but was more of a service model. Less of a pure play infrastructure or kind of a new game changes. So we thought we would get our friends to come on, the Cuban tell. Tell us about it. Val Birch, Avicii CEO and founder. A pencil day that Cube alumni formerly of NetApp, among other great companies, and Ed You, founder and CEO of Strong Salt. Welcome to the Q. Tell us why aren't we taught him a Blockchain at a security conference on cloud computing, where they always resource is different. Paradigm is decentralized. What's your take? >> So maybe having been in this world for about 18 24 months now, Enterprise lodging reinvents about six months ago and jazz he mentioned that he finally understood US enterprise an opportunity, and it was the integrity value, finest complex, even announced a specific product announced database available, >> maybe bythe on cryptographic verifiability of transactions minus the complexity of smart contract wallets. Wait, you party with Amazon way too. Versions right? One for distributed use cases. When I call, everyone rises. Never like you need to know what >> the Amazon wants to be that hard on top like complexity. But the reality is, they're they're They're world is targeting a new generation star 14 show is the new generation of developing >> a >> new generation of David. They were. Some of those are in trouble, and I'm hard core on this because it's just so obvious. >> I just can't get him behind myself if you don't >> see this out quicker. The new developers are younger and older systems people. There's a range of ages doing it. They're they're seeing the agility, and it's a cultural shift, not just the age thing. Head this. They're not here right now. This is the missing picture of this show, and my criticism of reinforces big, gaping hole around crypto and blocks, >> and I actually know that people I don't see anything here because it is difficult to currency. >> Blocking is very important that people understand way. Launch strong allows you to see the launching. I don't think that works. Basically, Just like Well, well said everything you do, you always have a single source. I think that's something that people doing this thing here. You want to get your thoughts on this because you made a comment >> about security native being the team here and security native implying that Dev ops what they did for configuration hardening the infrastructures code. You have to consider this token economic business model side of it with the apple cases, a decision application is still an application. Okay. Blockchain is still in infrastructure dynamic their software involved. I mean, we're talking about the same thing is they're lost in translation. In your opinion? >> Well, yeah, I think that you know, to your point, Val, if you can abstract that complexity away, But the fundamentals of of cryptography and software engineering and game theory coming together is what always has fascinated me about this space. And so you're right. I think certainly enterprise customers don't wanna you know, they hear crypto, though no, although it's interesting it was just a conference IBM yesterday. They talk a lot about Blockchain. Don't talk about crypto to me. They go together. Of course, IBM. They don't like to talk a lot about job loss and automation, but But the reality is it's there and it's it's it's has a lot of momentum, which is why you started the company. >> Yeah, we're actually seeing it all over right now. And again, our thing is around reducing, If not eliminating the friction towards adopting Blockchain so less is more. In our case, we're explicitly choosing not to do crypto wallets or currency transactions. It's that Andy Jassy observation the integrity value, the core integrity, value for financial reconciliation, for detecting supply chain counterfeiting for tracking assets and inventory across to your distribution. Unifying multiple source systems of record into a shared state. Those are the kinds of applications received >> culture, and there's so many different use cases, obviously, so >> an Amazon likes to use that word. Words raised the bar, which is more functionality, but on the other, phrases undifferentiated, heavy lifting. There's a lot of details involved in some of those complexity exactly what you're talking about that can be automated away. That's goodness. But you still have a security problem of mutability, which is a beautiful thing with Blockchain. >> Actually, a lot of times people actually forgot to mention one thing that blotchy and all you do that's actually different before was Actually privacy is actually not just security is also privacy, which actually is getting bigger and bigger. As we know, it's something that people feel very strongly about because it's something they feel personal about. And that's something that, in fact, took economics encourages a lot of things that enables privacy that was not able to do before. >> Well, look at Facebook. What do you think about >> face? I'm wonder that you know, I'm a public face book critic. I think they've been atrocious job on the privacy front so far in protecting our data. On the other hand, if you know it's kind of like the mullahs report, if you actually read Facebook's white paper, it's a it's not a launch. It's an announcement. That's a technical announcement. It's so well written, designed so far, and it's Facebook doesn't completely control it. They do have a vision for program ability. They're evolving it from being a permissions toe, ultimately a permission less system. So on paper, I like what I read. And I think it will start to, you know, popularizing democratize the notion of crypto amongst the broader population. I'm going to take a much more weight see approach. Just you know, >> I always love Facebook. I think the den atrocious job. But I'm addicted. I have all my stuff on there, um, centralized. They're bringing up, they bring in an education. Bitcoin is up for a reason. They're bringing the masses. They're showing that this is real market. This is kind of like when the web was still viewed as Kitty Playground for technologists say, Oh, well, it's so slow. And that was for dummies. And you had the Web World Wide Web. So when that hit, that same arguments went down right this minute, crypto things for years. But with Facebook coming, it really legitimizes that well, you bring 2,000,000,000 people to the party. Exactly a lot of good. Now the critics of Facebook is copied pass craft kind of model and there's no way they're gonna get it through because the world's not gonna let Facebook running run commerce and currents. It's like it's like and they don't do it well anyway. So I think it's gonna be a game changing market making move. I think they'll have a play in there, but I don't think that's not gonna have a global force. Says a >> lot that you get 100 companies to put up 10 >> 1,000,000 Starship is already the first accomplice. >> They don't need any more money. We have my dear to us, but >> still the power but the power of that ecosystem to me. I was a big fan of this because I think it gives credibility. So many companies get get interested in it, and I'm not sure exactly what's gonna come out of it. It's interesting that, you know, Bitcoins up. They said, Oh, cell, you're becoming like No, no, no, this is This is a very mature >> Well, I I think open is gonna always win. If you look at you know, the Web's kind of one example of kind of maturity argument. I think the rial analog for me, at least my generation value probably relate to this. David, you as well, you know, I've been born yet you are But, you know, T c p I p came after S n a which IBM on the deck net was the largest network at that time to >> not serious. Says >> mammal. Novell was land all three proprietary network operating systems. So proprietary Narcisse decimated by T c p i p. So to me, I think even their Facebook does go in there. They will recognize that unless they stay open, I think open will always win. I think I think this is the beginning of the death of the closed platform. >> Yeah, they're forced her. I think they have to open it up because if you didn't open up, people won't trust them, and people will use them. And if a Blockchain if you don't have a community behind it, there will be nothing. >> Well, so the thing about the crypto spraying everywhere with crypto winter, But but to your point d c p i p h t t p d >> N s SMTP >> Those were government funded or academic funded protocols. People stop spending money on him, and then the big Internet companies just co opted. No, no, that's what G mails built on. >> Well, I've always said >> so But when you finish the thought, is all this crypto money that came in drove innovation? Yeah, So you're seeing, you know, this new Internet emerge, and I think it's it's really think people, you know, sort of overlooked a lot of the innovation that's >> coming. I have always said, Dave, that Facebook is what the Web would look like if Tim Berners Lee took venture financing. Okay, because what they had at the time was a browser and the way that stand up websites for self service information. They kept it open and it drives. Facebook became basically the Web's version of a, well, lengthen does the same Twitter has opened. They have no developer community. So yeah, I think it is the only company in my opinion, actually does a good job opening up their data. Now they charge you for that. It brings up way still haven't encrypt those. The only community that's entire ethos is based on openness and community you mentioned. And that is a key word >> in traditional media. Of course, focus on the bad stuff that happens, but you know those of us in the business who will pay attention to it, see There's a lot of goodness to is a lot of mission driven, a lot of openness, and it's a model for innovation. What do you guys think about the narrative now to break up big tech? You know you're hearing Facebook, Amazon, Google coming under fire. What are your thoughts on that? >> So I wrote a block, maybe was ahead of its time about 18 months ago. Is coincided with Ginny Rometty, a Davos and 2018 2019 talking about data responsibility. Reason we're having this conversation is at the tech industry. By and large and especially the fang stocks or whatever we're calling them now have been irresponsible with our data. The backlash is palpable in Europe. It's law in Europe. Backlash we knew was going to start at the state level here. There's already ahead of my personal schedule. Federal discussions, FTC DOJ is in a couple weeks ago, so it's inevitable that this sort of tech reckoning is coming in. Maur responsibility is gonna have to be demonstrated by all the custodians of our data, and that's why we're positioning. Check it as a chain of custody is a service to demonstrate to the regulators your customers, your partners, suppliers, you know, transparency, irrefutable transparency, using Blockchain for how you're handling data. You know, if you don't have that, transparency can prove it. Or back to the same old discussions were back Thio Uninformed old legislators making you know Internet, his tubes type regulations. So here, here >> and DOJ, you could argue that they may be too slow to respond to Microsoft back in the nineties. I'm not sure breaking up big tech is the right thing, because I think it's almost like a t. The little Tex will become big checks again, but they should not be breaking the law. >> I think there's a reason why is there's actually a limitation off. What is possible in technology because they understand and also Facebook understands well, is that it's actually very, very hard to have data that's owned by your customers. But you are the one who's keeping track over everything, and you are the one using the data right. It's like a no win, because if you think about encryption cryptography, yes, you can make the data encrypted. That way, the customer has the key. They control it, but then Facebook can offer the service is. So now you have a Congress thinking, Well, if there's no technological way of doing this, what can you do in a legal perspective on a, you know, on the law perspective, toddy make it so that the customer actually owned the data. We actually think that is a perfect reason why you have to actually fix the book. Actually, technical should be built on our platform because we actually allow them to have a day that's encrypted and stupid able to operations holiday tha if the customer give them the permission to do so. And I think that's the perfect word way to go forward. And I think Blockchain is the fundamental thing that brings everybody together, you know, way that actually benefits everyone knows >> and take him into explain strong salt your project. What's it about? What's the mission? Where you >> so so we see strong saw as actually privacy. First, we literally are beauty, a platform where developers including Facebook linked and salesforce can't you build on top of platform, right? So what happens when you do this is that they actually give the data governess to the customers, customers Mashona data. But because our cryptography they actually can offer service is to the customers. When a customer allowed them to do so, for example, we have something. All search of encryption allows you to encrypt the data and still give the search. Aubrey on the data without decrypting the data. First, by giving the power to developers and also the community there, you can have our abstract you currently use. But they're not hard to use that frictionless and still offer the same service that Frank Facebook or sell stolen offer the favor. >> You could do some discovery on it. >> You can't do things >> some program ability around >> exactly, even though the data is encrypted. But custom owns the day. So the customer has to give them permission to do so Right this way. Actually, in fact, launched the first app that I told you it's called strong vote. You can Donald ios or Andrew it And you can't you see the Blockchain play little You can see the rocking your fingerprint. I think a fingertip to see what happens to a data. You see everything that happens when Sheriff I or you open a fire or something, I guess. >> Congratulations, Val. Give a quick plug for your project chain kid into the new branding. They're like it. Pencil data. Where are you on your project? >> So after nine months of hard selling, we're finding out what customers actually paying for right now. In our case, it's hardening their APS, their data and their logs and wrapping the chain of custody around those things. And the use case of the security conference like this is actually quite existential When you think about it, One of the things that the industry doesn't talk enough about is that every attack we read about in the headlines was three privilege escalation. So the attackers somehow hacked. Your Web server managed to get administrative credentials and network or domain administrative credentials. And here's what professional attackers do once they have godlike authority on your network. They identify all the installed security solutions, and they make themselves invisible because they can. After that, they operate with impunity. Our technology, the security use case that we're seeing a lot of traction is, is we can detect that we're applying Blockchain. We're agnostic, so bring your own Blockchain in our case. But we're able >> chain kit a product. Is it a development environment >> globally. Available service Jose on AWS rest ful AP eyes and fundamentally were enabling developers to harden their app stuff to wrap a chain of custody around key data or logs in their laps so that when the attacker's attempt a leverage at administrative authority and tamper with locks tamper >> with service, not a software, >> it's a apply. It's a developer oriented service, but >> this is one of the biggest problems and challenges security today. You see the stat after you get infiltrated. It takes 250 or 300 days to even detect, and I have not heard that number shrink. I've heard people aspire number streaking this. >> We can get it down to realize a crime tip of the spear. That's what we're excited to be here. We're excited to talk about One of the dirty secrets of the security industry is that it shouldn't take a year to detect in advance attack. >> Guys, Thanks for coming on. Cuban sharing your insight. Concussions in your head. Well, great to see you. >> Likewise. And thank you, j for having us on here, and we're looking forward to coming back and weigh. Appreciate. Absolutely >> thankful. Spj Thanks for you. >> It was always paying it forward. Of course, really the most important conversation, that security is gonna be a Blockchain type of implementation. This is a reality that's coming very soon, but we're here. They do is reinforce. I'm talking about the first conference with Amazon Web sources dedicated to sightsee. So's Cee Io's around security jumper. Develop the stables for more coverage. After this short break, >> my name is David.

>> Announcer: Live, from Washington DC, it's theCube. Covering .conf2017 Brought to you by splunk. >> Welcome back inside the Walter Washington Convention Center. We're at .conf2017 in Washington DC, the nations capital, it is alive and well and thriving. A little warm out there, almost 90 degrees. But hot topic inside here, Dave. >> There's a lot of heat in this city. (laughter) >> A lot of hot air. >> Yeah, absolutely. >> We'll just leave it at that. Politics aside, of course. Joining us is Ben Miller, who is Director of High Thoughput Screening at Recursion Pharmaceuticals. Ben, thanks for being with us here on theCube. We appreciate the time. First off, I have many questions. First off let's talk about the company, what you do, and then what high throughput screening means, and how that operation comes into play when you have this great nexus of biology and engineering that you've brought together. >> Recursion Pharmaceuticals is treating drug discovery as a facial recognition problem. We're applying machine-learning concepts to biological images to help detect what types of drugs can rescue what types of diseases. We're one of the few companies that is both generating and analyzing our own data. As the director of the high throughput screening group, what I do is generate images for our data science teams to analyze, and that means growing human cells up in massive quantities, perturbing them with different types of disease reagents that cause their morphology to change, and then photographing them in the presence of compounds and in the absence of compounds. So we can see which compounds cause these disease states to revert more to a normal state for the cell. >> Okay, HTS then ... Walk us through that if you would. >> HTS is a general term that's used in the pharmaceutical industry to denote a assay that is executed in very large scale and in parallel. We tend to work on the order of multiples of 384 experiments per plate. We're looking at hundreds of thousands of images per plate, and we're looking at hundreds of plates per week. So when we say high throughput, we mean 6-10 terabytes of data per day. >> Just extraordinary amounts of data. And the mission, as we understand it, you're looking at very rare genetic diseases, your goal is to find cures for these over the next 15-20 years. Up to 100 of them, so that's why you're going through this multiple examinations of vast amounts of data. Human data. >> Yeah, there's been a trend in the pharmaceutical industry over the last years, where the number of dollars spent per drug developed is increasing. And it now takes over one billion dollars to bring a drug to market. And every year it costs more to bring a drug to market. We believe we can change that by operating at a massively parallel scale and also analyzing image data at a truly deep level. Looking at thousands of different features per image, instead of just a single feature in the image. >> That business is just like this vicious cycle going on, and you guys are trying to break it. >> Yes, exactly. >> So what's the state of facial recognition been? I've had mixed reviews about it. Because I rave about it, I go, "Oh my God, "Facebook tagged me again, it must be really good." And then other's have told me, "Well it's not really "as reliable as you might think." What is your experience been? >> The only experience I've had with facial recognition has been like yours, on Facebook and things like that. What we're doing is looking more at cellular recognition. Being able to see differences in these cellular morphologies. I think there are some unique challenges when you're looking at images of thousands of cells, versus images of a single person's face. >> Okay, so you've taken that concept down to the cell level and it's highly accurate, presumably. >> It's highly reproducible is what I would say, yeah. >> So it takes some work to be accurate, and once you get it there you can reproduce that, is that right? How does the sequence work? >> Yes, so there are two parts to the coin. One is how consistently we can produce these images and then how consistently those images represent the disease state. My focus is on making the images as consistent as they can be, while realizing that the disease states are all unique. So from our perspective, we're looking at thousands of different features in each image, and figuring out how consistent those features are from image to image. >> So paint a picture of your data stack, if you will. Infrastructure on up to the apps, and where splunk fits in. >> Sure. So I guess you could say that our data stack actually begins at hospitals around the world where human cells are collected from various medical waste samples. We culture those up, perturb them with different reagents, add different potential drugs back to them, and then photograph them. So at the beginning of our stack we've got biological agents that are mixed together and then photographs are generated. Those photographs are actually .tif files, and we have thousands and thousands of them. They're all uploaded in to Amazon Web Services, their S3 system. We spin up a near infinite number of virtual computers to process all of that image data within a couple of hours. And then produce a result. This drug makes this disease model look more like healthy and doesn't have other side effects. We're really reducing those thousands of dimensions in our image down to two. How much does it look like a healthy cell, and how much does it just look different then it should. >> And where does splunk fit into that stack? >> All of those instruments that are generating that data are equipped with splunk forwarders. So splunk is pulling all of our operational data from the laboratory together, and marrying it up with the image analysis that comes from our proprietary data analysis system. So by looking at the data that we're generating, how many cells we're counting, how bright the intensity of the image is, comparing that back to which dispenser we used, how long the plates sat at room temperature, et cetera. We can figure out how to optimize our production process so that we get reliable data. >> It's essentially storing machine data in the splunk data store. And then do you have an image database for ...? >> Yeah. And the image database is incredibly large. I wouldn't even guess at the current size. >> Dave: And what is it? Is it something on Amazon, an Amazon service? >> Yeah. So right now all of our image data is stored on AWS. >> This is one of those interviews Dave that the subject matter kind of trumps the technology because I want to know how it works. But you need the technology obviously to drive it. So I'm trying to figure out, "Alright, so you're taking "human cells and you're taking snapshots in time, "and then looking at how they react "to certain perturbed actions." But how does that picture of maybe one person's cell reacting to a reagent to another person's ... How does your data analysis provide you with some insight because Dave's DNA is different from my DNA, different from everybody in this building, so ultimately how are you combing through all of that data to make sense of it. >> That's true. Everybody has a unique genetic fingerprint, but everybody is susceptible to the same sets of major diseases. By looking at these images, and really that's the billion dollar question, is how representative are these individual cellular images, how representative are they of the general human population? And the effects that we see at a cellular level, will they translate in to human populations? We're very close to clinical trials on several compounds, but that's when we will really find out how much proof there is in this concept. >> Okay. You can't really predict ... Do you have a timeframe or is just sort of, "Keep going, keep getting funding until you reach the answer?" Is it like survive until you thrive? >> I personally don't maintain that kind of timeline. My role is within the laboratory producing the data as quickly as we can. We do have a goal of treating 100 different diseases in the next 10 years. And it's really early days, we're about 2 1/2 years in to that goal. It seems like we're on track, but there's still a lot of work to be done between now and then. >> So it's all cloud, right? And then splunk is throughout that stack, as we talked about. How do you envision, or do you envision, using it differently? Are you trying to get more out of the splunk platform? What do you want to see from splunk? >> That's a good question. I think right now we're using really the rudimentary basic features of splunk. Their database-connect app and their Machine Learning Toolkit are both pretty foundational to the work that we do. But right now a lot of our data models are one time use. We do a particular analysis to find the root cause of a particular problem, we learn that, and that's the last time we use that model. Continuous implementation of data models is something that is high on my list to do. As well as just ingesting more and more data. We're still fairly siloed. Our temperature and humidity data is separate from our machine data, and bringing that all into splunk is on the list. >> Why are your models disposable? It sounds like it's not done on purpose, it's more of some kind of infrastructure barrier? >> We're really at the cutting edge of technology right now, and we're learning a lot of things that people haven't learned, that in retrospect are obvious. To figure out the true cause of a particular situation, a data model or a machine-learning model is really valuable, but once you know that key salient fact, you don't need to keep track of it over time. You don't need to know that when your tire pressure is low your car gets less miles to the gallon. >> David: You have the answer. >> Right. But there are a lot of problems like that in our field that have not been discovered yet. >> I inferred from your answer you do see the potential to have some kind of ongoing model evolution. For new use cases? >> In the extreme situation we have a set of hundreds of operational parameters that are going into producing this image of cells. And then we have thousands of cellular features that are extracted from that image. There's a machine-learning problem there. What are the optimal parameters to extract the optimal information? And that whole process could be automated to the point where we're using machine-learning to optimize our assay. To me that's the future of what we want to do. >> Were you with Recursion when they brought in splunk? >> Yeah. >> You were. Did you look at alternatives? Did you look at maybe rolling your own with open source? Is that even feasible? Wonder if you could talk about that. >> I had already been introduced to splunk at my previous job, and at that previous company, before I heard of splunk, I was starting to roll my own. I was writing a ton of Perl scripts, and all of these regular expressions, and searching network drives to pull log files together. And I thought that maybe there would be a good business model behind that. >> You were building splunk. (laughter) >> And then I found splunk, and those guys were so far ahead of things I was trying to do on my own in a lab. So for me it was a no-brainer. But for our software engineering team, they are really dedicated to open source platforms whenever possible. They evaluated the ELK Stack. Some of us had used Sumo Logic and things like that. But for me, splunk had the right license model and I could get off the ground really really rapidly with it. >> What about the license model was attractive to you? >> Unlimited users, and only paying for the data that we ingest. The ability to democratize that data, so that everybody in the lab can go in and view it and I don't have to worry about how many accounts I'm creating. That was really powerful. >> Dave: So you like the pricing model. >> Yeah. >> Some users have chirped about the pricing, I saw some Wall Street concerns about the pricing. The guys that we've talked to on theCube today have said, "They like the pricing model, that there's value there." And you're sort of confirming that. >> Ben: Yeah. >> You're not concerned about the exponential growth of you data causing your license fees to go through the roof >> In the laboratory, the image data that we're generating is exponentially growing, but the operational parameter data is more linearly growing. >> Dave: So it's under control basically. >> Yeah, for our needs it is. >> Dave: You're not paying for the images, you're paying for the meta data around that. >> Yeah. >> Well it's a fascinating proposition, it really is. Very eager to keep up with this, keep track, and see the progress. Good luck with that. Look for having you back on theCube to monitor that progress, alright Ben? >> Great. Very good, thank you so much. Ben Miller joining us from Salt Lake City, good to have you here. Back with more on theCube in just a bit. You're watching our live coverage of .conf2017. (upbeat innovative music)