(upbeat music) >> Welcome back to Supercloud 2, which is an open industry collaboration between technologists, consultants, analysts, and of course, practitioners, to help shape the future of cloud. And at this event, one of the key areas we're exploring is the intersection of cloud and data, and how building value on top of hyperscale clouds and across clouds is evolving, a concept we call supercloud. And we're pleased to welcome Harvir Singh, who's the chief data architect and global head of data at Western Union. Harvir, it's good to see you again. Thanks for coming on the program. >> Thanks, David, it's always a pleasure to talk to you. >> So many things stand out from when we first met, and one of the most gripping for me was when you said to me, "When data moves, money moves." And that's the world we live in today, and really have for a long time. Money has moved as bits, and when it has to move, we want it to move quickly, securely, and in a governed manner. And the pressure to do so is only growing. So tell us how that trend is evolved over the past decade in the context of your industry generally, and Western Union, specifically. Look, I always say to people that we are probably the first ones to introduce digital currency around the world because, hey, somebody around the world needs money, we move data to make that happen. That trend has actually accelerated quite a bit. If you look at the last 10 years, and you look at all these payment companies, digital companies, credit card companies that have evolved, majority of them are working on the same principle. When data moves, money moves. When data is stale, the money goes away, right? I think that trend is continuing, and it's not just the trend is in this space, it's also continuing in other spaces, specifically around, you know, acquisition of customers, communication with customers. It's all becoming digital, and it's, at the end of the day, it's all data being moved from one place or another. At the end of the day, you're not seeing the customer, but you're looking at, you know, the data that he's consuming, and you're making actionable items on it, and be able to respond to what they need. So I think 10 years, it's really, really evolved. >> Hmm, you operate, Western Union operates in more than 200 countries, and you you have what I would call a pseudo federated organization. You're trying to standardize wherever possible on the infrastructure, and you're curating the tooling and doing the heavy lifting in the data stack, which of course lessens the burden on the developers and the line of business consumers, so my question is, in operating in 200 countries, how do you deal with all the diversity of laws and regulations across those regions? I know you're heavily involved in AWS, but AWS isn't everywhere, you still have some on-prem infrastructure. Can you paint a picture of, you know, what that looks like? >> Yeah, a few years ago , we were primarily mostly on-prem, and one of the biggest pain points has been managing that infrastructure around the world in those countries. Yes, we operate in 200 countries, but we don't have infrastructure in 200 countries, but we do have agent locations in 200 countries. United Nations says we only have like 183 are countries, but there are countries which, you know, declare themselves countries, and we are there as well because somebody wants to send money there, right? Somebody has an agent location down there as well. So that infrastructure is obviously very hard to manage and maintain. We have to comply by numerous laws, you know. And the last few years, specifically with GDPR, CCPA, data localization laws in different countries, it's been a challenge, right? And one of the things that we did a few years ago, we decided that we want to be in the business of helping our customers move money faster, security, and with complete trust in us. We don't want to be able to, we don't want to be in the business of managing infrastructure. And that's one of the reasons we started to, you know, migrate and move our journey to the cloud. AWS, obviously chosen first because of its, you know, first in the game, has more locations, and more data centers around the world where we operate. But we still have, you know, existing infrastructure, which is in some countries, which is still localized because AWS hasn't reached there, or we don't have a comparable provider there. We still manage those. And we have to comply by those laws. Our data privacy and our data localization tech stack is pretty good, I would say. We manage our data very well, we manage our customer data very well, but it comes with a lot of complexity. You know, we get a lot of requests from European Union, we get a lot of requests from Asia Pacific every pretty much on a weekly basis to explain, you know, how we are taking controls and putting measures in place to make sure that the data is secured and is in the right place. So it's a complex environment. We do have exposure to other clouds as well, like Google and Azure. And as much as we would love to be completely, you know, very, very hybrid kind of an organization, it's still at a stage where we are still very heavily focused on AWS yet, but at some point, you know, we would love to see a world which is not reliant on a single provider, but it's more a little bit more democratized, you know, as and when what I want to use, I should be able to use, and pay-per-use. And the concept started like that, but it's obviously it's now, again, there are like three big players in the market, and, you know, they're doing their own thing. Would love to see them come collaborate at some point. >> Yeah, wouldn't we all. I want to double-click on the whole multi-cloud strategy, but if I understand it correctly, and in a perfect world, everything on-premises would be in the cloud is, first of all, is that a correct statement? Is that nirvana for you or not necessarily? >> I would say it is nirvana for us, but I would also put a caveat, is it's very tricky because from a regulatory perspective, we are a regulated entity in many countries. The regulators would want to see some control if something happens with a relationship with AWS in one country, or with Google in another country, and it keeps happening, right? For example, Russia was a good example where we had to switch things off. We should be able to do that. But if let's say somewhere in Asia, this country decides that they don't want to partner with AWS, and majority of our stuff is on AWS, where do I go from there? So we have to have some level of confidence in our own infrastructure, so we do maintain some to be able to fail back into and move things it needs to be. So it's a tricky question. Yes, it's nirvana state that I don't have to manage infrastructure, but I think it's far less practical than it said. We will still own something that we call it our own where we have complete control, being a financial entity. >> And so do you try to, I'm sure you do, standardize between all the different on-premise, and in this case, the AWS cloud or maybe even other clouds. How do you do that? Do you work with, you know, different vendors at the various places of the stack to try to do that? Some of the vendors, you know, like a Snowflake is only in the cloud. You know, others, you know, whether it's whatever, analytics, or storage, or database, might be hybrid. What's your strategy with regard to creating as common an experience as possible between your on-prem and your clouds? >> You asked a question which I asked when I joined as well, right? Which question, this is one of the most important questions is how soon when I fail back, if I need to fail back? And how quickly can I, because not everything that is sitting on the cloud is comparable to on-prem or is backward compatible. And the reason I say backward compatible is, you know, there are, our on-prem cloud is obviously behind. We haven't taken enough time to kind of put it to a state where, because we started to migrate and now we have access to infrastructure on the cloud, most of the new things are being built there. But for critical application, I would say we have chronology that could be used to move back if need to be. So, you know, technologies like Couchbase, technologies like PostgreSQL, technologies like Db2, et cetera. We still have and maintain a fairly large portion of it on-prem where critical applications could potentially be serviced. We'll give you one example. We use Neo4j very heavily for our AML use cases. And that's an important one because if Neo4j on the cloud goes down, and it's happened in the past, again, even with three clusters, having all three clusters going down with a DR, we still need some accessibility of that because that's one of the biggest, you know, fraud and risk application it supports. So we do still maintain some comparable technology. Snowflake is an odd one. It's obviously there is none on-prem. But then, you know, Snowflake, I also feel it's more analytical based technology, not a transactional-based technology, at least in our ecosystem. So for me to replicate that, yes, it'll probably take time, but I can live with that. But my business will not stop because our transactional applications can potentially move over if need to. >> Yeah, and of course, you know, all these big market cap companies, so the Snowflake or Databricks, which is not public yet, but they've got big aspirations. And so, you know, we've seen things like Snowflake do a deal with Dell for on-prem object store. I think they do the same thing with Pure. And so over time, you see, Mongo, you know, extending its estate. And so over time all these things are coming together. I want to step out of this conversation for a second. I just ask you, given the current macroeconomic climate, what are the priorities? You know, obviously, people are, CIOs are tapping the breaks on spending, we've reported on that, but what is it? Is it security? Is it analytics? Is it modernization of the on-prem stack, which you were saying a little bit behind. Where are the priorities today given the economic headwinds? >> So the most important priority right now is growing the business, I would say. It's a different, I know this is more, this is not a very techy or a tech answer that, you know, you would expect, but it's growing the business. We want to acquire more customers and be able to service them as best needed. So the majority of our investment is going in the space where tech can support that initiative. During our earnings call, we released the new pillars of our organization where we will focus on, you know, omnichannel digital experience, and then one experience for customer, whether it's retail, whether it's digital. We want to open up our own experience stores, et cetera. So we are investing in technology where it's going to support those pillars. But the spend is in a way that we are obviously taking away from the things that do not support those. So it's, I would say it's flat for us. We are not like in heavily investing or aggressively increasing our tech budget, but it's more like, hey, switch this off because it doesn't make us money, but now switch this on because this is going to support what we can do with money, right? So that's kind of where we are heading towards. So it's not not driven by technology, but it's driven by business and how it supports our customers and our ability to compete in the market. >> You know, I think Harvir, that's consistent with what we heard in some other work that we've done, our ETR partner who does these types of surveys. We're hearing the same thing, is that, you know, we might not be spending on modernizing our on-prem stack. Yeah, we want to get to the cloud at some point and modernize that. But if it supports revenue, you know, we'll invest in that, and get the, you know, instant ROI. I want to ask you about, you know, this concept of supercloud, this abstracted layer of value on top of hyperscale infrastructure, and maybe on-prem. But we were talking about the integration, for instance, between Snowflake and Salesforce, where you got different data sources and you were explaining that you had great interest in being able to, you know, have a kind of, I'll say seamless, sorry, I know it's an overused word, but integration between the data sources and those two different platforms. Can you explain that and why that's attractive to you? >> Yeah, I'm a big supporter of action where the data is, right? Because the minute you start to move, things are already lost in translation. The time is lost, you can't get to it fast enough. So if, for example, for us, Snowflake, Salesforce, is our actionable platform where we action, we send marketing campaigns, we send customer communication via SMS, in app, as well as via email. Now, we would like to be able to interact with our customers pretty much on a, I would say near real time, but the concept of real time doesn't work well with me because I always feel that if you're observing something, it's not real time, it's already happened. But how soon can I react? That's the question. And given that I have to move that data all the way from our, let's say, engagement platforms like Adobe, and particles of the world into Snowflake first, and then do my modeling in some way, and be able to then put it back into Salesforce, it takes time. Yes, you know, I can do it in a few hours, but that few hours makes a lot of difference. Somebody sitting on my website, you know, couldn't find something, walked away, how soon do you think he will lose interest? Three hours, four hours, he'll probably gone, he will never come back. I think if I can react to that as fast as possible without too much data movement, I think that's a lot of good benefit that this kind of integration will bring. Yes, I can potentially take data directly into Salesforce, but I then now have two copies of data, which is, again, something that I'm not a big (indistinct) of. Let's keep the source of the data simple, clean, and a single source. I think this kind of integration will help a lot if the actions can be brought very close to where the data resides. >> Thank you for that. And so, you know, it's funny, we sometimes try to define real time as before you lose the customer, so that's kind of real time. But I want to come back to this idea of governed data sharing. You mentioned some other clouds, a little bit of Azure, a little bit of Google. In a world where, let's say you go more aggressively, and we know that for instance, if you want to use Google's AI tools, you got to use BigQuery. You know, today, anyway, they're not sort of so friendly with Snowflake, maybe different for the AWS, maybe Microsoft's going to be different as well. But in an ideal world, what I'm hearing is you want to keep the data in place. You don't want to move the data. Moving data is expensive, making copies is badness. It's expensive, and it's also, you know, changes the state, right? So you got governance issues. So this idea of supercloud is that you can leave the data in place and actually have a common experience across clouds. Let's just say, let's assume for a minute Google kind of wakes up, my words, not yours, and says, "Hey, maybe, you know what, partnering with a Snowflake or a Databricks is better for our business. It's better for the customers," how would that affect your business and the value that you can bring to your customers? >> Again, I would say that would be the nirvana state that, you know, we want to get to. Because I would say not everyone's perfect. They have great engineers and great products that they're developing, but that's where they compete as well, right? I would like to use the best of breed as much as possible. And I've been a person who has done this in the past as well. I've used, you know, tools to integrate. And the reason why this integration has worked is primarily because sometimes you do pick the best thing for that job. And Google's AI products are definitely doing really well, but, you know, that accessibility, if it's a problem, then I really can't depend on them, right? I would love to move some of that down there, but they have to make it possible for us. Azure is doing really, really good at investing, so I think they're a little bit more and more closer to getting to that state, and I know seeking our attention than Google at this point of time. But I think there will be a revelation moment because more and more people that I talk to like myself, they're also talking about the same thing. I'd like to be able to use Google's AdSense, I would like to be able to use Google's advertising platform, but you know what? I already have all this data, why do I need to move it? Can't they just go and access it? That question will keep haunting them (indistinct). >> You know, I think, obviously, Microsoft has always known, you know, understood ecosystems. I mean, AWS is nailing it, when you go to re:Invent, it's all about the ecosystem. And they think they realized they can make a lot more money, you know, together, than trying to have, and Google's got to figure that out. I think Google thinks, "All right, hey, we got to have the best tech." And that tech, they do have the great tech, and that's our competitive advantage. They got to wake up to the ecosystem and what's happening in the field and the go-to-market. I want to ask you about how you see data and cloud evolving in the future. You mentioned that things that are driving revenue are the priorities, and maybe you're already doing this today, but my question is, do you see a day when companies like yours are increasingly offering data and software services? You've been around for a long time as a company, you've got, you know, first party data, you've got proprietary knowledge, and maybe tooling that you've developed, and you're becoming more, you're already a technology company. Do you see someday pointing that at customers, or again, maybe you're doing it already, or is that not practical in your view? >> So data monetization has always been on the charts. The reason why it hasn't seen the light is regulatory pressure at this point of time. We are partnering up with certain agencies, again, you know, some pilots are happening to see the value of that and be able to offer that. But I think, you know, eventually, we'll get to a state where our, because we are trying to build accessible financial services, we will be in a state that we will be offering those to partners, which could then extended to their customers as well. So we are definitely exploring that. We are definitely exploring how to enrich our data with other data, and be able to complete a super set of data that can be used. Because frankly speaking, the data that we have is very interesting. We have trends of people migrating, we have trends of people migrating within the US, right? So if a new, let's say there's a new, like, I'll give you an example. Let's say New York City, I can tell you, at any given point of time, with my data, what is, you know, a dominant population in that area from migrant perspective. And if I see a change in that data, I can tell you where that is moving towards. I think it's going to be very interesting. We're a little bit, obviously, sometimes, you know, you're scared of sharing too much detail because there's too much data. So, but at the end of the day, I think at some point, we'll get to a state where we are confident that the data can be used for good. One simple example is, you know, pharmacies. They would love to get, you know, we've been talking to CVS and we are talking to Walgreens, and trying to figure out, if they would get access to this kind of data demographic information, what could they do be better? Because, you know, from a gene pool perspective, there are diseases and stuff that are very prevalent in one community versus the other. We could probably equip them with this information to be able to better, you know, let's say, staff their pharmacies or keep better inventory of products that could be used for the population in that area. Similarly, the likes of Walmarts and Krogers, they would like to have more, let's say, ethnic products in their aisles, right? How do you enable that? That data is primarily, I think we are the biggest source of that data. So we do take pride in it, but you know, with caution, we are obviously exploring that as well. >> My last question for you, Harvir, is I'm going to ask you to do a thought exercise. So in that vein, that whole monetization piece, imagine that now, Harvir, you are running a P&L that is going to monetize that data. And my question to you is a there's a business vector and a technology vector. So from a business standpoint, the more distribution channels you have, the better. So running on AWS cloud, partnering with Microsoft, partnering with Google, going to market with them, going to give you more revenue. Okay, so there's a motivation for multi-cloud or supercloud. That's indisputable. But from a technical standpoint, is there an advantage to running on multiple clouds or is that a disadvantage for you? >> It's, I would say it's a disadvantage because if my data is distributed, I have to combine it at some place. So the very first step that we had taken was obviously we brought in Snowflake. The reason, we wanted our analytical data and we want our historical data in the same place. So we are already there and ready to share. And we are actually participating in the data share, but in a private setting at the moment. So we are technically enabled to share, unless there is a significant, I would say, upside to moving that data to another cloud. I don't see any reason because I can enable anyone to come and get it from Snowflake. It's already enabled for us. >> Yeah, or if somehow, magically, several years down the road, some standard developed so you don't have to move the data. Maybe there's a new, Mogli is talking about a new data architecture, and, you know, that's probably years away, but, Harvir, you're an awesome guest. I love having you on, and really appreciate you participating in the program. >> I appreciate it. Thank you, and good luck (indistinct) >> Ah, thank you very much. This is Dave Vellante for John Furrier and the entire Cube community. Keep it right there for more great coverage from Supercloud 2. (uplifting music)

>>Hello everyone. Welcome back to the Cube Live, AWS Reinvent 2022. This is our first day of three and a half days of wall to wall coverage on the cube. Lisa Martin here with Dave Valante. Dave, it's getting louder and louder behind us. People are back. They're excited. >>You know what somebody told me today? Hm? They said that less than 15% of the audience is developers. I'm like, no way. I don't believe it. But now maybe there's a redefinition of developers because it's all about the data and it's all about the developers in my mind. And that'll never change. >>It is. And one of the things we're gonna be talking about is app modernization. As customers really navigate the journey to do that so that they can be competitive and, and meet the demands of customers. We've got an alumni back with us to talk about that. AJ Patel joins us, the SVP and GM Modern Apps and Management business group at VMware. Aj, welcome back. Thank >>You. It's always great to be here, so thank you David. Good to see >>You. Isn't great. It's great to be back in person. So the VMware Tansu team here back at Reinvent on the Flow Shore Flow show floor. There we go. Talk about some of the things that you guys are doing together, innovating with aws. >>Yeah, so it's, it's great to be back after in person after multiple years and the energy level continues to amaze me. The partnership with AWS started on the infrastructure side with VMware cloud on aws. And when with tanza, we're extending it to the application space. And the work here is really about how do you make developers productive To your earlier point, it's all about developers. It's all about getting applications in production securely, safely, continuously. And tanza is all about making that bridge between great applications being built, getting them deployed and running, running and operating at scale. And EKS is a dominant Kubernetes platform. And so the better together story of tanu and EKS is a great one for us, and we're excited to announce some sort of innovations in that area. >>Well, Tanu was so front and center at VMware Explorer. I wasn't at in, in VMware Explorer, Europe. Right. But I'm sure it was a similar kind of focus. When are customers choosing Tanu? Why are they choosing Tanu? What's, what's, what's the update since last August when >>We, you know, the market settled into three main use cases. One is all about developer productivity. You know, consistently we're all dealing with skill set gap issues. How do we make every developer productive, modern developer? And so 10 is all about enabling that develop productivity. And we can talk quite a bit about it. Second one is security's front and center and security's being shifted left right into how you build great software. How do you secure that through the entire supply chain process? And how do you run and operationalize secure at runtime? So we're hearing consistently about making secure software supply chain heart of what our solution is. And third one is, how do I run and operate the modern application at scale across any Kubernetes, across any cloud? These are the three teams that are continuing to get resonance and empowering. All of this is exciting. David is this formation of platform teams. I just finished a study with Bain Consulting doing some research for me. 40% of our organization now have some form of a central team that's responsive for, for we call platform engineering and building platforms to make developers productive. That is a big change since about two years ago even. So this is becoming mainstream and customers are really focusing on delivering in value to making developers productive. >>Now. And, and, and the other nuance that I see, and you kinda see it here in the ecosystem, but when you talk about your customers with platform engineering, they're actually building their, they're pointing their business. They gonna page outta aws, pointing their businesses to their customers, right? Becoming software companies, becoming cloud companies and really generating new forms of revenue. >>You know, the interesting thing is, some of my customers I would never have thought as leading edge are retailers. Yeah. And not your typical Starbucks that you get a great example. I have an auto parts company that's completely modernizing how they deliver point of sale all the way to the supply chain. All built on ES at scale. You're typically think of that a financial services or a telco leading the pack. But I'm seeing innovation in India. I'm seeing the innovation in AMEA coming out of there, across the board. Every industry is becoming a product company. A digital twin as we would call it. Yeah. And means they become software houses. Yeah. They behave more like you and I in this event versus a, a traditional enterprise. >>And they're building their own ecosystems and that ecosystem's generating data that's generating more value. And it's just this cycle. It's, >>It's a amazing, it's a flywheel. So innovation continues to grow. Talk about really unlocking the developer experience and delivering to them what they need to modernize apps to move as fast and quickly as they want to. >>So, you know, I think AWS coin this word undifferentiated heavy lifting. If you think of a typical developer today, how much effort does he have to put in before he can get a single line of code out in production? If you can take away all the complexity, typically security compliance is a big headache for them, right? Developer doesn't wanna worry about that. Infrastructure provisioning, getting all the configurations right, is a headache for them. Being able to understand what size of infrastructure or resource to use cost effectively. How do you run it operationally? Cuz the application team is responsible for the operational cost of the product or service. So these are the un you know, heavy lifting that developers want to get away from. So they wanna write great code, build great experiences. And we've always talked about frameworks a way to abstract with the complexity. And so for us, there's a massive opportunity to say, how do I simplify and take away all the heavy lifting to get an idea into production seamlessly, continuously, securely. >>Is that part of your partnership? Because you think about a aws, they're really not about frameworks, they're about primitives. I mean, Warner Vos even talks about that in his, in his speech, you know, but, but that makes it more challenging for developers. >>No, actually, if you look at some of their initial investments around proton and et cetera work, they're starting to do, they're recognized, you know, PS is a bad, bad word, but the outcomes a platform as a service offers is what everybody wants. Just talking to the AWS leaders, responsible area, he actually has a separate build team. He didn't know what to call the third team. He has a Kubernetes team, he has a serverless team and has a build team. And that build team is everything above Kubernetes to make the developer productive. Right. And the ecosystem to bring together to make that happen. So I think AWS is recognizing that primitives are great for the elite developers, but if they want to get the mass scale and adoption in the business, it, if you will, they're gonna have to provide richer set of building blocks and reduce the complex and partnership like ours. Make that a reality. And what I'm excited about is there's a clear gap here, and t's the best platform to kind of fill that gap. Well, >>And I, I think that, you know, they're gonna double down triple, I just wrote about this double down, triple down on the primitives. Yes. They have to have the best, you know, servers and storage and database. And I think the way they, they, I call it taping the seams is with the ecosystem. Correct. You know, and they, nobody has a, a better ecosystem. I mean, you guys are, you know, the, the postage child for the ecosystem and now this even exceeds that. But partnering up, that's how they >>Continue to, and they're looking for someone who's open, right? Yeah. Yeah. And so one of the first question is, you know, are you proprie or open? Because one of the things they're fighting against is the lock in. So they can find a friendly partner who is open source, led, you know, upstream committing to the code, delivering that innovation, and bring the ecosystem into orchestrated choreography. It's like singing a music, right? They're running a, running an application delivery team is like running a, a musical orchestra. There's so many moving parts here, right? How do you make them sing together? And so if Tan Zoo and our platform can help them sing and drive more of their services, it's only more valuable for them. And >>I think the partners would generally say, you know, AWS always talking about customer obsession. It's like becomes this bromine, you go, yeah, yeah. But I actually think in the field, the the sellers would say, yeah, we're gonna do what the customer, if that means we're gonna partner up. Yeah. And I think AWS's comp structure makes it sort >>Of, I learned today how, how incentives with marketplaces work. Yeah. And it is powerful. It's very powerful. Yeah. Right. So you line up the sales incentive, you line up the customer and the benefits, you line up bringing the ecosystem to drive business results and everybody, and so everybody wins. And which is what you're seeing here, the excitement and the crowd is really the whole, all boats are rising. Yeah. Yeah. Right, right. And it's driven by the fact that customers are getting true value out of it. >>Oh, absolutely. Tremendous value. Speaking of customers, give us an example of a customer story that you think really articulates the value of what Tanzi was delivering, especially making that developer experience far simpler. What are some of those big business outcomes that that delivers? >>You know, at Explorer we had the CIO of cvs and with their acquisition of Aetna and CVS Health, they're transforming the, the health industry. And they talked about the whole covid and then how they had to deliver the number of, you know, vaccines to u i and how quickly they had to deliver on that. It talked about Tanu and how they leverage, leverage a Tanza platform to get those new applications out and start to build that. And Ro was basically talking about his number one prior is how does he get his developers more productive? Number to priority? How does he make sure the apps are secure? Number three, priority, how does he do it cost effectively in the world? Particularly where we're heading towards where, you know, the budgets are gonna get tighter. So how do I move more dollars to innovation while I continue to drive more efficiency in my platform? And so cloud is the future. How does he make the best use of the cloud both for his developers and his operations team? Right? >>What's happening in serverless, I, in 2017, Andy Chassy was in the cube. He said if AWS or if Amazon had to build all over again, they would build in, in was using serverless. And that was a big quote. We've mined that for years. And as you were talking about developer productivity, I started writing down all the things developers have to do. Yep. With it, they gotta, they gotta build a container image. They said they gotta deploy an EC two instance. They gotta allocate memory, they gotta fence off the apps in a virtual machine. They gotta run the, you know, compute against the app goes, they gotta pay for all that. So, okay, what's your story on, what's the market asking for in terms of serverless? Because there's still some people who want control over the run time. Help us sift through that. >>And it really comes back to the application pattern or the type you're running. If it's a stateless application that you need to spin up and spin down. Serverless is awesome. Why would I wanna worry about scaling it up in, I wanna set up some SLAs, SLIs service level objectives or, or, or indicators and then let the systems bring the resources I need as I need them. That's a perfect example for serverless, right? On the other hand, if you have a, a more of a workflow type application, there's a sequence, there's state, try building an application using serverless where you had to maintain state between two, two steps in the process. Not so much fun, right? So I don't think serverless is the answer for everything, but many use cases, the scale to zero is a tremendous benefit. Events happen. You wanna process something, work is done, you quietly go away. I don't wanna shut down the server started up, I want that to happen magically. So I think there's a role of serverless. So I believe Kubernetes and servers are the new runtime platform. It's not one or the other. It's about marrying that around the application patterns. I DevOps shouldn't care about it. That's an infrastructure concern. Let me just run application, let the infrastructure manage the operations of it, whether it's serverless, whether it's Kubernetes clusters, whether it's orchestration, that's details right. I I I shouldn't worry about it. Right. >>So we shouldn't think of those as separate architectures. We should think of it as an architecture, >>The continuum in some ways Yeah. Of different application workload types. And, and that's a toolkit that the operator has at his disposal to configure and saying, where does, should that application run? Should I want control? You can run it on a, a conveyance cluster. Can I just run it on a serverless infrastructure and and leave it to the cloud provider? Do it all for me. Sure. What, what was PAs? PAs was exactly that. Yeah. Yeah. Write the code once you do the rest. Yeah. Okay. Those are just elements of that. >>And then K native is kinda in the middle, >>Right? K native is just a technology that's starting to build that capability out in a standards way to make serverless available consistently across all clouds. So I'm not building to a, a lambda or a particular, you know, technology type. I'm building it in a standard way, in a standard programming model. And infrastructure just >>Works for me on any cloud. >>The whole idea portability. Consistency. >>Right. Powerful. Yep. >>What are some of the things that, that folks can expect to learn from VMware Tan to AWS this week at the >>Show? Yeah, so there's some really great announcements. First of all, we're excited to extend our, our partnership with AWS in the area of eks. What I mean by that is we traditionally, we would manage an EKS cluster, you visibility of what's running in there, but we weren't able to manage the lifecycle With this announcement. We can give you a full management of lifecycle of S workloads. Our customers have 400 plus EKS clusters, multiple teams sharing those in a multi-tenanted way with common policy. And they wanna manage a full life cycle, including all the upstream open source component that make up Kubernetes people. That ES is the one thing, it's a collection of a lot of open, open source packages. We're making it simple to manage it consistently from a single place on the security front. We're now making tons of service mesh available in the marketplace. >>And if you look at what service MeSHs, it's an overlay. It's an abstraction. I can create an idea of a global name space that cuts across multiple VPCs. I'm, I'm hearing at Amazon's gonna make some announcements around VPC and how they stitch VPCs together. It's all moving towards this idea of abstractions. I can set policy at logical level. I don't have to worry about data security and the communication between services. These are the things we're now enabling, which are really an, and to make EKS even more productive, making enterprise grade enterprise ready. And so a lot of excitement from the EKS development teams as well to partner closely with us to make this an end to end solution for our >>Customers. Yeah. So I mean it's under chasy, it was really driving those primitives and helping developers under continuing that path, but also recognizing the need for solutions. And that's where the ecosystem comes in, >>Right? And the question is, what is that box? As you said last time, right? For the super cloud, there is a cloud infrastructure, which is becoming the new palette, but how do you make sense of the 300 plus primitives? How do you bring them together? What are the best practices, patterns? How do I manage that when something goes wrong? These are real problems that we're looking to solve. >>And if you're gonna have deeper business integration with the cloud and technology in general, you have to have that >>Abstraction. You know, one of the simple question I ask is, how do you know you're getting value from your cloud investment? That's a very hard question. What's your trade off between performance and cost? Do you know where your security, when a lock 4G happens, do you know all the open source packages you need to patch? These are very simple questions, but imagine today having to do that when everybody's doing in a bespoke manner using the set of primitives. You need a platform. The industry is shown at scale. You have to start standardizing and building a consistent way of delivering and abstracting stuff. And that's where the next stage of the cloud journey >>And, and with the economic environment, I think people are also saying, okay, how do we get more? Exactly. We're in the cloud now. How do we get more? How do we >>Value out of the cloud? >>Exactly. Totally. >>How do we transform the business? Last question, AJ for you, is, if you had a bumper sticker and you're gonna put it on your fancy car, what would it say about VMware tan zone aws? >>I would say tan accelerates apps. >>Love >>It. Thank you so much. >>Thank you. Thank you so much for joining us. >>Appreciate it. Always great to be here. >>Pleasure. Likewise. For our guest, I'm Dave Ante. I'm Lisa Martin. You're watching The Cube, the leader in emerging and enterprise tech coverage.

(soft music) >> Welcome back, everyone. theCube's live coverage. Day two here at VMware Explore. Our 12th year covering VMware's annual conference formally called Vmworld, now it's VMware Explore. Exploring new frontiers multi-cloud and also bearing some of the fruit from all the investments in cloud native Tanzu and others. I'm John Furrier with Dave Vellante. We have the man who's in charge of a lot of that business and a lot of stuff coming out of the oven and hitting the market. Ajay Patel, senior vice president and general manager of the modern applications and management group at VMware, basically the modern apps. >> Absolutely. >> That's Tanzu. All the good stuff. >> And Aria now. >> And Aria, the management platform, which got social graph and all kinds of graph databases. Welcome back. >> Oh, thank you so much. Thanks for having me. >> Great to see you in person, been since 2019 when you were on. So, a lot's happened since 2019 in your area. Again, things get, the way VMware does it as we all know, they announce something and then you build it and then you ship it and then you announce it. >> I don't think that's true, but okay. (laughs) >> You guys had announced a lot of cool stuff. You bought Heptio, we saw that Kubernetes investment and all the cloud native goodness around it. Bearing fruit now, what's the status? Give us the update on the modern applications of the management, obviously the areas, the big announcement here on the management side, but in general holistically, what's the update? >> I think the first update is just the speed and momentum that containers and Kubernetes are getting in the marketplace. So if you take the market context, over 70% of organizations now have Kubernetes in production, not one or two clusters, but hundreds of clusters, sometimes tens of clusters. So, to me, that is a market opportunity that's coming to fruition. Sometimes people will come and say, Ajay, aren't you late to the market? I say, no, I'm just perfectly timing it. 'Cause where does our value come in? It's enterprise readiness. We're the company that people look to when you have complexity, you have scale, you need performance, you need security, you need the robustness. And so, Tanzu is really about making modern applications real, helping you design, develop, build and run these applications. And with Aria, we're fundamentally changing the game around multicloud management. So the one-two punch of Tanzu and Aria is I'm most excited about. >> Isn't it true that most of the Kubernetes, you know, today is people pulling down open source and banging away. And now, they're looking for, you know, like you say, more of a robust management capability. >> You know, last two years when I would go to many of the largest customers, like, you know, we're doing good. We've got a DIY platform, we're building this. And then you go to the customer a year later, he's got knocked 30, 40 teams and he has Log4j happen. And all of a sudden he is like, oh, I don't want to be in the business of patching this thing or updating it. And, you know, when's the next shoe going to fall? So, that maturity curve is what I was talking about. >> Yeah. Free like a puppy. >> Ajay, you know, mentioned readiness, enterprise readiness and the timing's perfect. You kind of included, not your exact words, but I'm paraphrasing. That's a lot to do with what's going on. I mean, I'll say Cloud Native, IWS, think of the hyper scale partner, big partner and Google and even Google said it today. You know, the market world's spinning in their direction. Especially with respect to VMware. You get the relationship with the hyperscalers. Cloud's been on everyone's agenda for a long time. So, it's always been ready. But enterprise, you are customer base at VMware, very cloud savvy in the sense they know it's there, there's some dabbling, there's some endeavors in the cloud, no problem. But from a business perspective and truly transforming the VMware value proposition, is already, they're ready and it's already time now for them, like, you can see the movement. And so, can you explain the timing of that? I mean, I get enterprise readiness, so we're ready to scale all that good stuff. But the timing of product market fit is important here. >> I think when Raghu talks about that cloud first to cloud chaos, to cloud smart, that's the transition we're seeing. And what I mean by that is, they're hitting that inflection point where it's not just about a single team. One of the guys, basically I talked to the CIO, he was like, look, let's assume hypothetically I have thousand developers. Hundred can talk about microservices, maybe 50 has built a microservice and three are really good at it. So how do I get my thousand developers productive? Right? And the other CIO says, this team comes to me and says, I should be able develop directly to the public cloud. And he goes, absolutely you can do that. You don't have to come through IT. But here's the book of security and compliance that you need to enforce to get that thing in production. >> Go for it. >> Go for it. >> Good luck with that. >> So that reality of how do I scale my dev developers is turning into a developer experience problem. We now have titles which says, head of developer experience. Imagine that two years ago. We didn't talk about it. People start, hey, containers Kubernetes. I'm good to go. I can go get all the open source technology you talked about. And now they're saying no. >> And also software supply chains, another board that you're think. This is a symptom of the growth. I mean, open source is the software industry. That is, I don't think debatable. >> Right. >> Okay. That's cool. But now integration becomes vetting, trust, trusting codes. It's very interesting software time right now. >> That's right. >> And how is that impacting the cloud native momentum in your mind? Accelerating it? What inning are we in? How would you peg the progress? >> You know, on that scale of 1 to 10, I think we're halfway marked now. And that moved pretty quickly. >> It really did. >> And if you sit back today, the kinds of applications we're involved in, I have a Chicago wealth management company. We're building the next generation wealth management application. It's a fundamental refactoring of the legacy application. If you go to a prescription company, they're building a brand new prescription platform. These are not just trivial. What they're learning is the lift and shift. Doesn't work for these major applications. They're having to refactor them which is the modernization. >> So how specifically, are they putting some kind of abstraction layer on that? Are they actually gutting it and rewriting it? >> There's always going to be brownfield. Remember the old days of SOA? >> Yeah, yeah. >> They are putting APIs in front of their main systems. They're not rewriting the core banking or the core platform, but the user experience, the business logic, the AIML capability to bring intelligence in the platform. It's surrounding the capability to make it much more intuitive, much more usable, much more declarative. That's where things are going. And so I'm seeing this mix of integration all over again. Showing my age now. But, you know, the new EAI so is now microservices and messaging and events with the same patterns. But again, being much more accelerated with cloud native services. >> And it is to the point, it's accelerated today. They're not having to freeze the code for six months or nine months and that which would kill the whole recipe for failure. So they're able to now to fast track their modernization. They have to prioritize 'cause they got limited resources. But how are you guys coming up to that? >> But the practice is changing as well, right? Well, the old days, it was 12, 18 months cycle or anything software. If you heard the CVS CIO, Rohan. >> Yeah. >> Three months where they started to engage with us in getting an app in production, right? If you look at the COVID, 10 days to get kind of a new application for getting small loans going with Pfizer, right? These are dramatically short term, but it's not rewriting the entire app. It's just putting these newer experiences, newer capability in front with newer modern developer practices. And they're saying, I need to do it not just once, but for 100, 200, 5,000 members. JPMC has 50,000 developers. Fifty thousand. They're not a bank anymore. >> We just have thousands of apps. >> Exactly. >> Ajay, I want to get your thoughts on something that we've been talking about on our super cloud event. I know we had an event a couple weeks ago, you guys were one of our sponsors, VMware was. It was called super cloud where we're defining that this next gen environment's a super cloud and every company will have a super cloud capability. And underneath that is cross cloud capabilities. So, super cloud is like a super set on top of a multi-cloud. And little word play or play on words is, ecosystem partners versus partners in the ecosystem. Because if you're coming down to the integration side of things, it's about knowing what goes what, it's almost like building an OS if you're a coder or an operating systems person. You got to put the pieces together right, not just go to the directory and say, okay, who's got the cheapest price in DR or air gaping or something or some solution. So ecosystem partners are truly partners. Partners in the ecosystem are a bunch of people out on a list. How do you see that? Because the trend we're seeing is, the development process includes partners at day one. >> That's right. Not bolt-on. >> Completely agree. >> Share your thoughts on that. >> So let's look at that. The first thing I'm hearing from my customers is, they're trying to use all the public clouds as a new IS. That's the first API or contract infrastructures code IS. From then on they're saying, I want more and more portable services. And if you see the success of some of the data vendors and the messaging vendors, you're starting to see best of breed becoming part of the platform. So you are to identify which of these are truly, you know, getting market momentum and are becoming kind of defacto leaders. So, Kafka goes hand in hand with streaming. RabbitMQ from my portfolio goes with messaging. Postgres for database. So these are the, in your definition, ecosystem partners, they're foundational. In the security space, you know, Snyk is a common player in terms of scanning or Aqua and Prisma even though we have Carbon Black. Those become partners from a container security perspective. So, what's happening is the industry stabilizing a handful of critical players that are becoming multi-cloud preference of choice in this. And our job is to bring it all together in a all coordinated, orchestrated manner to give them a platform. >> I mean, you guys always had ecosystem, but I think that priority more than ever. It wasn't really your job at VMware, even, Dave, 10 years ago to say, hey, this is the strategic role that you might play one partner. It was pretty much the partners all kind of fed off the momentum of VMware. Virtualization. And there's not a lot of nuance there. There's pretty much they plug in and you got. >> So what we're doing here is, since we're not the center of the universe, unfortunately, for the application world, things like Backstage is a developer portal from Spotify that became open source. That's becoming the place where everyone wants to provide a plugin. And so we took Backstage, we said, let's provide enterprise support for Backstage. If you take a technology like, you know, what we have with Spring. Every job where developer uses Spring, how do we make it modern with Spring cloud. We work with Microsoft to launch a service with Azure Spring Enterprise for Spring. So you're starting to see us taking communities where they have momentum and bringing the ecosystem around those technologies. Cluster API for Kubernetes, for have you managed stuff. >> Yeah. >> So it's about standard. >> Because the developers are voting with their clicks and their code repos. And so you're identifying the patterns that they like. >> That's right. >> And aligning with them and connecting with them rather than trying to sell against it. >> Exactly. It's the end story with everyone. I say stop competing. So people used to think Tanzu is Kubernetes. It's really Tanzu is the modern application platform that runs on any Kubernetes. So I've changed the narrative. When Heptio was here, we were trying to be a Kubernetes player. I'm like, Kubernetes is just another dial tone. You can use mine, you can use OpenShift. So this week we announced support for OpenShift by Tanzu application platform. The values moving up, it's around outcomes. So industry standards, taking lead and solving the problem. >> You know, we had a panel at super cloud. Dave, I know you got a question. I'll get to you in a second. But the panel was the innovator's dilemma. And then during the event, one of the panelists, Chris Hoff knows VMware very well, Beaker on Twitter, said it should be called the integrators dilemma. Because the innovations here, >> How do you put it all together? >> But the integration of the, putting the piece parts together, building the thing is the innovation. >> And we come back and say, it's a secure software supply chain. It starts with great content. Did you know, I published most of the open source content on every hyperscaler through my Bitnami acquisition. So I start with great content that's curated. Then I allow you to create your own golden images. Then I have a build service that secures and so on and so forth and we bring the part. So, that opinionated solution, but batteries included but you can change it is been one of our key differentiator. We recognize the roles is going to be modular, come back and solve for it. >> So I want to understand sort of relationship Tanzu and Aria, John was talking about, you know, super cloud before we had our event. We had an earlier session where we help people understand that Aria was not, you know, vRealize renamed. >> It's rebranded. >> And reason I bring that up is because we had said it around super cloud, that one of the defining characteristics was, sorry, super PaaS, which is a specific purpose built PaaS layer designed to support your objective for multi-cloud. And speaking to a lot of people this week, there's a federated architecture, there's graph relationships, there's real time ability to ingest and analyze. That's unique. And that's IP that is purpose built for what you're doing. >> Absolutely. When I think what came out of all that learning is after 20 years of Pivotal and BA and what we learned that you still need some abstraction layer. Kubernetes is too low level. So what are the developer problems? What are the delivery problems? What are the operations and management problems? Aria solves all the operations and management problem. Tanzu solves a super PaaS problems. >> Yes. Right. >> Of providing a consistent way to build great software and the secure software supply chain to run on any infrastructure. So the combination of Tanzu and Aria complete the value chain. >> And it's different. Again, we get a lot of heat for this, but we're saying, look, we're trying to describe, it's not just IAS, PaaS, and SaaS of last decade. There's something new that's happening. And we chose the name super cloud. >> And what's the difference? It's modular. It's pluggable. It fits into the way you operate. >> Whereas PaaS was very prescriptive. If you couldn't fit, you couldn't jump down to the next level. This is very much, you can stay at the abstraction level or go lower level. >> Oh, we got to add that to the attribute. >> We're recruiting him right now. (laughs) >> We'll give you credit. >> I mean, funny all the web service's background. Look at an app server. You well knew all about app servers. Basically the company is an app. So, if you believe that, say, Capital One is an application as a company and Amazon's providing all the CapEx, >> That's it. >> Okay. And they run all their quote, old IT spend millions, billions of dollars on operating expenses that's going to translate to the top line called the income statement. So, Dave always says, oh, it's on the balance sheet, but now they're going to go to the top line. So we're seeing dynamic. Ajay, I want to get your reaction to this where the business model shift if everything's tech enabled, the company is like an app server. >> Correct. >> So therefore, the revenue that's generated from the technology, making the app work has to get recognized in the income. Okay. But Amazon's doing all, or the cloud hyperscale is doing all the heavy lifting on the CapEx. So technically it's the cloud on top of a cloud. >> Yes and no. The way I look at it, >> I call that a super cloud. >> So I like the idea of super cloud, but I think we're mixing two different constructs. One is, the cloud is a new hardware, right? In terms of dynamic, elastic, always available, et cetera. And I believe when more and more customer I talk about, there's a service catalog of infrastructure services. That's emerging. This super cloud is the next set of PaaS super PaaS services. And the management service is to use the cloud. We spend so much time as VMware building clouds, the problem seems, how do you effectively use the cloud? What problems do we solve around digital where every company is a digital company and the product is this application, as you said. So everything starts with an application. And you look at from the lens of how you run the application, what it costs the application, what impact it's driving. And I think that's the change. So I agree with you in some way. That is a digital strategy. >> And that's the company. >> That's the company. The application is the company. >> That's the t-shirt. >> And API is the currency. >> So, Ajay, first of all, we love having you in theCube 'cause you're like a masterclass in multiple dimensions. So, I want to get your thoughts on the abstraction layer. 'Cause we were also talking earlier in theCube here as well as before. But abstraction layers happen when you have major movements in markets that are game changing or major inflection points because you've reached a complexity point where it's working so great, this new thing, that's too complex to reign it in. And we were quoting Andy Grove by saying, "let chaos reign then reign in the chaos". So, all major industry moments go back 30, 40 years happen with abstractions. So the question is is that, you can't be a vendor, we've observed you can't be a vendor and be the abstraction. Like, if Cisco's running routers, they can't be the abstraction layer. They have to be the benefit of the abstraction layer. And if you're on the other side of the abstraction layer, you can't be running that either. >> I like the way you're thinking about it. Yeah. Do you agree? >> I completely agree. And, you know, I'm an old middleware guy. And when I used to say this to my CEO, he's like, no, it's not middleware, it's just a new middleware. And what's middleware, right? It's a thing between app and infrastructure. You could define it whatever we want, right? And so this is the new distributed middleware. >> It's a metaphor and it's a good one because it does a purpose. >> It's a purpose. >> It creates a separation but then you have, it's like a DMZ zone or whatever you want to call it. It's an area that things happen. >> But the difference before last time was, you could always deploy it to a thing. The thing is now the cloud. The thing is a set of services. So now it's as much of a networking problem at the application layer is as much as security problem. It's how you build software, how we design. So APIs, become part of your development. You can't think of APIs after the fact, right? When you build an API, you got to publish API because the minute you publish it and if you change it, the API's out of. So you can't have it as a documentation process. So, the way you build software, you use software consume is all about it. So to me, digital product with an API as a currency is where we're headed towards. >> Yeah, that's a great observation. Want to make a mental note of that and make that a clip. I want to get your thoughts on software development. You mentioned that, obviously software development life cycles are changing. I'll say open sources now. I mean, it's unlimited codes, supply chain issue. What's in the code, I get that verified codes going to happen. Is software development coding as much or is coding changing the notion of writing code? Or is it more glue layer you're writing. >> I think you're onto something. I call software developments composition now. My son's at Facebook or Google. They have so many libraries. So you don't no longer start with the very similar primitive, you start with building blocks, components, services, libraries, open source technology. What are you really doing? You're composing these things from multiple artifacts. And how do you make sure those artifacts are good artifacts? So someone's not sticking in security in a vulnerability into it. So, the world is moving towards composition and there are few experts who build the core components. Most of the time we're just using those to build solutions. And so, the art here is, how do you provide that set of best practices? We call them patterns or building blocks or services that you can compose to build these next generation (indistinct) >> It's interesting. >> Cooking meals. >> I agree with you a hundred percent what you're thinking. I agree about that worldview. Here's a dilemma that I'm seeing. In the security world, you've got zero trust. You know, Which is, I don't know you, I don't trust you at all. And if you're going to go down this composed, we're going to have an orchestra of players with instruments, say to speak, Dave, metaphor. That's trust involved. >> Yes. >> So you have two spectrums of issues. >> Yes. >> If software's going trust and you're seeing Docker containers getting more verifications, software supply chain, and then you got hardware I call network guys, love zero trust. Where's the balance? How do you reconcile that? Is it just decoupled? Nuance? I mean, what's the point? >> No, no. I think it all comes together. And what I mean by that is, it starts with left shifting it all the way to hands of the developers, right? So, are you starting with good content? You have providence of the stuff you're using. Are you building it correctly? So you're not introducing bad things like solar winds along the process. Are you testing it along the way of the development process? And then once in production, do you know, half the time it's configurations of where you're running the stuff versus the software itself. So you can think of the two coming together. And the network security is protecting people from going laterally once they've got in there. So, a whole security solution requires all of the above, a secure software supply chain, the way to kind of monitor and look at configuration, we call posture management or workload management and the network security of SaaS-e for zero trust. That's a hard thing. And the boundary is the application. >> All right. >> So is it earned trust model sort of over time? >> No, it's designed in, it's been a thing. >> Okay. So it's not a, >> Because it developed. >> You can bolt in afterwards. >> Because the developers are driving it. They got to know what they're doing. >> And it's changing every week. If I'm putting a new code out every week. You can't, it can be changed to something else. >> Well, you guys got guardrails. The guardrails constant is a good example. >> It stops on the configuration side, but I also need the software. So, Tanzu is all about, the secure chain is about the development side of the house. Guardrails are on the operational side of the house. >> To make sure the developers don't stop. >> That's right. >> Things will always get out there. And I find out there's a CV that I use a library, I found after the fact. >> Okay. So again, while I got here again, this is great. I want to get test this thesis. So, we've been saying on theCube, talking about the new ops, the new kind of ops that emerging. DevOps, which we believe is cloud native. So DevOps moving infrastructure's code, that's happened, it's all good. Open source is growing. DevOps is done deal. It's done deal. Developers are doing that. That ops was IT. Then don't need the server, clouds my hardware. Check. That balances. The new ops is data and security which has to match up to the velocity of the developers. Do you believe that? >> Completely. That's why we call it DevSecOps. And the Sec is where all the action is. >> And data. And data too. >> And data is about making the data available where the app meets. So the problem was, you know, we had to move the logic to where the data is or you're going to move the data where the logic is. So data fabrics are going to become more and more interesting. I'll give you a simple example. I publish content today in a service catalog. My customer's saying, but my content catalog needs to be in 300 locations. How do I get the content to each of the repos that are running in 300 location? So I have a content distribution problem. So you call it a data problem. Yes, it's about getting the right data. Whether it's simple as even content, images available for use for deployment. >> So you think when I think about the application development stack and the analytics stack, the data stack, if I can call it that, they're separate, right? Are those worlds, I mean, people say, I want to inject data and AI intelligence into apps. Those worlds have deployment? I think about the insight from the historical being projected in the operational versus they all coming together. I have a Greenplum platform, it's a great analytics platform. I have a transactional platform. Do my customers buy the same? No, they're different buyers, they're different users. But the insight from that is being now plugged in so that at real time I can ask the question. So even this information is being made available on demand. So that's where I see it. And that's most coming together, but the insight is being incorporated in the operational use. So I can say, do I give the risk score? Do I give you credit? It's based on a whole bunch of historical analytics done. And at the real time, processing is happening, but the intelligence is behind it. >> It's a mind shift for sure because the old model was, I have a database, we're good. Now you have time series database, you got graphs. Each one has a role in the overall construct of the new thing. >> But it's about at the end. How do I make use of it? Someone built a smart AI model. I don't know how it was built, but I want to apply it for that particular purpose. >> Okay. So the final question for you, at least from my standpoint is, here at VMware Explore, you have a lot of the customers and so new people coming in that we've heard about, what's their core order of operations right now? Get on the bandwagon for modern apps. How do you see their world unfolding as they go back to the ranch, their places, and go back to their boss? Okay. We got the modern application. We're on the right track boss, full steam ahead. Or what change do they make? >> I think the biggest thing I saw was with some of the branding changes well and some of the new offerings. The same leader had two teams, the VMware team and the public cloud team. And they're saying, hey, maybe VMware's going to be the answer for both. And that's the world model. That's the biggest change I'm seeing. They were only thinking of us on the left column. Now they see us as a unifying player to play across cloud native and VMware, the uniquely set up to bring it all together. That's been really exciting this week. >> All right, Ajay, great to have you on. Great perspective. Worthy of great stuff. Congratulations on the success of all that investment coming to bear. >> Thank you. >> And on the new management platform. >> Yeah. Thank you. And thanks always for giving us all the support we need. It's always great. >> All right Cube coverage here. Getting all the data, getting inside the heads, getting all the specifics and all the new trends and actually connecting the dots here on theCube. I'm John Furrier with Dave Vellante. Stay tuned for more coverage from day two. Two sets, three days, Cube at VMware Explore. We'll be right back. (gentle music)

(upbeat music) >> Welcome back everyone to theCUBE's coverage of VMware Explore '22, formerly VMworld. This is our 12th year covering it. I'm John Furrier with Dave Vellente. Two sets, three days of wall-to-wall coverage. We're starting to get the execs rolling in from VMware. Sumit Dhawan, president of VMware's here. Great to see you. Great keynote, day one. >> Great to be here, John. Great to see you, Dave. Day one, super exciting. We're pumped. >> And you had no problem with the keynotes. We're back in person. Smooth as silk up there. >> We were talking about it. We had to like dust off a cobweb to make some of these inputs. >> It's not like riding a bike. >> No, it's not. We had about 40% of our agencies that we had to change out because they're no longer in business. So, I have to give kudos to the team who pulled it together. They did a fabulous job. >> You do a great check, great presentation. I know you had a lot to crack in there. Raghu set the table. I know this is for him, this was a big moment to lay out the narrative, address the Broadcom thing right out of the gate, wave from Hock Tan in the audience, and then got into the top big news. Still a lot of meat on the bone. You get up there, you got to talk about the use cases, vSphere 8, big release, a lot of stuff. Take us through the keynote. What was the important highlights for you to share, the folks watching that didn't see the keynote or wanted to get your perspective? >> Well, first of all, did any of you notice that Raghu was running on the stage? He did not do that in rehearsal. (John chuckles) I was a little bit worried, but he really did it. >> I said, I betcha that was real. (everyone chuckles) >> Anyways, the jokes aside, he did fabulous. Lays out the strategy. My thinking, as you said, was to first of all speak with their customers and explain how every enterprise is facing with this concept of cloud chaos that Raghu laid out and CVS Health story sort of exemplifies the situation that every customer is facing. They go in, they start with cloud first, which is needed, I think that's the absolutely right approach. Very quickly build out a model of getting a cloud ops team and a platform engineering team which oftentimes be a parallel work stream to a private cloud infrastructure. Great start. But as Roshan, the CIO at CVS Health laid out, there's an inflection point. And that's when you have to converge these because the use cases are where stakeholders, this is the lines of businesses, app developers, finance teams, and security teams, they don't need this stove piped information coming at 'em. And the converge model is how he opted to organize his team. So we called it a multi-cloud team, just like a workspace team. And listen, our commitment and innovations are to solve the problems of those teams so that the stakeholders get what they need. That's the rest of the keynote. >> Yeah, first of all, great point. I want to call out that inflection point comment because we've been reporting coming into VMworld with super cloud and other things across open source and down into the weeds and into the hood. The chaos is real. So, good call. I love how you guys brought that up there. But all industry inflection points, if you go back in history of the tech industry, at every single major inflection point, there was chaos, complexity, or an enemy proprietary. However you want to look at it, there was a situation where you needed to kind of reign in the chaos as Andy Grove would say. So we're at that inflection point, I think that's consistent. And also the ecosystem floor yesterday, the expo floor here in San Francisco with your partners, it was vibrant. They're all on this wave. There is a wave and an inflection point. So, okay. I buy that. So, if you buy the inflection point, what has to happen next? Because this is where we're at. People are feeling it. Some say, I don't have a problem but they're cut chaos such is the problem. So, where do you see that? How does VMware's team organizing in the industry and for customers specifically to solve the chaos, to reign it in and cross over? >> Yeah, you're a 100% right. Every inflection point is associated with some kind of a chaos that had to be reigned in. So we are focused on two major things right now which we have made progress in. And maybe third, we are still work in-progress. Number one is technology. Today's technology announcements are directly to address how that streamlining of chaos can be done through a cloud smart approach that we laid out. Our Aria, a brand new solution for management, significant enhancements to Tanzu, all of these for public cloud based workloads that also extend to private cloud. And then our cloud infrastructure with newer capabilities with AWS, Azure, as well as with new innovations on vSphere 8 and vSAN 8. And then last but not the least, our continuous automation to enable anywhere workspace. All these are simple innovation that have to address because without those innovations, the problem is that the chaos oftentimes is created because lack of technology and as a result structure has to be put in place because tooling and technology is not there. So, number one goal we see is providing that. Second is we have to be independent, provide support for every possible cloud but not without being a partner of theirs. That's not an easy thing to do but we have the DNA as a company, we have done that with data centers in the past, even though being part of Dell we did that in the data center in the past, we have done that in mobility. And so we have taken the challenge of doing that with the cloud. So we are continually building newer innovation and stronger and stronger partnerships with cloud provider which is the basis of our commercial relationships with Microsoft Azure too, where we have brought Azure VMware solution into VMware cloud universal. Again, that strengthens the value of us being neutral because it's very important to have a Switzerland party that can provide these multi-cloud solutions that doesn't have an agenda of a specific cloud, yet an ecosystem, or at least an influence with the ecosystem that can bring going forward. >> Okay, so technology, I get that. Open, not going to be too competitive, but more open. So the question I got to ask you is what is the disruptive enabler to make that happen? 'Cause you got customers, partners and team of VMware, what's the disruptive enabler that's going to get you to that level? >> Over the hump. I mean, listen, our value is this community. All this community has one of two paths to go. Either, they become stove piped into just the public-private cloud infrastructure or they step up as this convergence that's happening around them to say, "You know what? I have the solution to tame this multi-cloud complexity, to reign the chaos," as you mentioned because tooling and technologies are available. And I know they work with the ecosystem. And our objective is to bring this community to that point. And to me, that is the best path to overcome it. >> You are the connective tissue. I was able to sit into the analyst meeting today. You were sort of the proxy for CVS Health where you talked about the private that's where you started, the public cloud ops team, bringing that together. The platform is the glue. That is the connective tissue. That's where Tanzu comes in. That's where Aria comes in. And that is the disruptive technology which it's hard to build that. >> From a technology perspective, it's an enabler of something that has never been done before in that level of comprehensiveness, from a more of a infrastructure side thinking perspective. Yes, infrastructure teams have enabled self-service portals. Yes, infrastructure teams have given APIs to developers, but what we are enabling through Tanzu is completely next level where you have a lot richer experience for developers so that they never ever have to think about the infrastructure at all. Because even when you enable infrastructure as API, that's still an API of the infrastructure. We go straight to the application tier where they're just thinking about authorized set of microservices. Containers can be orchestrated and built automatically, shifting security left where we're truly checking them or enabling them to check the security vulnerabilities as they're developing the application, not going into the production when they have to touch the infrastructure. To me, that's an enabler of a special power that this new multi-cloud team can have across cloud which they haven't had in the past. >> Yeah, it's funny, John, I'd say very challenging technically. The challenge in 2010 was the software mainframe, remember the marketing people killed that term. >> Yeah, exactly. >> But you think about that. We're going to make virtualization and the overhead associated with that irrelevant. We're going to be able to run any workload and VMware achieved that. Now you're saying we run anything anywhere, any Kubernete, any container. >> That's the reality. That's the chaos. >> And the cloud and that's a new, real problem. Real challenging problem that requires serious engineering. >> Well, I mean it's aspirational, right? Let's get the reality, right? So true spanning cloud, not yet there. You guys, I think your vision is definitely right on in the sense that we'd like the chaos and multicloud's a reality. The question is AWS, Azure, Google Cloud, other clouds, they're not going to sit still. No one's going to let VMware just come up and take everything. You got to enable so the market- >> True, true. I don't think this is the case of us versus them because there is so much that they have to express in terms of the value of every cloud. And this happened in the case of, by the way, whether you go into infrastructure or even workspace solutions, as long as the richest of the experience and richest of the controls are provided, for their cloud to the developers that makes the adoption of their cloud simpler. It's a win-win for every party. >> That's the key. I think the simplest. So, I want to ask you, this comes up a lot and I love that you brought that up, simple and self-service has proven developers who are driving the change, cloud DevOps developers. They're driving the change. They're in charge more than ever. They want self-service, easier to deploy. I want a test, if I don't like it, I want to throw it away. But if I like something, I want to stick with it. So it's got to be self-service. Now that's antithetical to the old enterprise model of solve complexity with more complexity. >> Yeah, yeah. >> So the question for you is as the president of VMware, do you feel good that you guys are looking out over the landscape where you're riding into the valley of the future with the demand being automation, completely invisible, abstraction layer, new use case scenarios for IT and whatever IT becomes. Take us through your mindset there, because I think that's what I'm hearing here at this year, VMware Explorer is that you guys have recognized the shift in demographics on the developer side, but ops isn't going away either. They're connecting. >> They're connected. Yeah, so our vision is, if you think about the role of developers, they have a huge influence. And most importantly they're the ones who are driving innovation, just the amount of application development, the number of developers that have emerged, yet remains the scarcest resource for the enterprise are critical. So developers often time have taken control over decision on infrastructure and ops. Why? Because infrastructure and ops haven't shown up. Not because they like it. In fact, they hate it. (John chuckles) Developers like being developers. They like writing code. They don't really want to get into the day to day operations. In fact, here's what we see with almost all our customers. They start taking control of the ops until they go into production. And at that point in time, they start requesting one by one functions of ops, move to ops because they don't like it. So with our approach and this sort of, as we are driving into the beautiful valley of multi-cloud like you laid out, in our approach with the cross cloud services, what we are saying is that why don't we enable this new team which is a reformatted version of the traditional ops, it has the platform engineering in it, the key skill that enables the developer in it, through a platform that becomes an interface to the developers. It creates that secure workflows that developers need. So that developers think and do what they really love. And the infrastructure is seamless and invisible. It's bound to happen, John. Think about it this way. >> Infrastructure is code. >> Infrastructure has code, and even next year, it's invisible because they're just dealing with the services that they need. >> So it's self-service infrastructure. And then you've got to have that capability to simplified, I'll even say automated or computational governance and security. So Chris Wolf is coming on Thursday. >> Yeah. >> Unfortunately I won't be here. And he's going to talk about all the future projects. 'Cause you're not done yet. The project narrows, it's kind of one of these boring, but important. >> Yeah, there's a lot of stuff in the oven coming out. >> There's really critical projects coming down the pipeline that support this multi-cloud vision, is it's early days. >> Well, this is the thing that we were talking about. I want to get your thoughts on. And we were commenting on the keynote review, Hock Tan bought VMware. He's a lot more there than he thought. I mean, I got to imagine him sitting in the front row going there's some stuff coming out of the oven. I didn't even, might not have known. >> He'd be like, "Hmm, this extra value." (everyone chuckles) >> He's got to be pretty stoked, don't you think? >> He is, he is. >> There's a lot of headroom on the margin. >> I mean, independent to that, I think the strategy that he sees is something that's compelling to customers which is what, in my assessment, speaking with him, he bought VMware because it's strategic to customers and the strategic value of VMware becomes even higher as we take our multi-cloud portfolio. So it's all great. >> Well, plus the ecosystem is now re-energize. It's always been energized, but energized cuz it's sort of had to be, cuz it's such a strong- >> And there was the Dell history there too. >> But, yeah it was always EMC, and then Dell, and now it's like, wow, the ecosystem's- >> Really it's released almost. I like this new team, we've been calling this new ops kind of vibe going refactored ops, as you said, that's where the action's happening because the developers want to go faster. >> They want to go faster. >> They want to go fast cuz the velocity's paying off of them. They don't want to have to wait. They don't want security reviews. They want policy. They want some guardrails. Show me the track. >> That's it. >> And let me drive this car. >> That's it because I mean think about it, if you were a developer, listen, I've been a developer. I never really wanted to see how to operate the code in production because it took time away for developing. I like developing and I like to spend my time building the applications and that's the goal of Aria and Tanzu. >> And then I got to mention the props of seeing project Monterey actually come out to fruition is huge because that's the future of computing architecture. >> I mean at this stage, if a customer from here on is modernizing their infrastructure and they're not investing in a holistic new infrastructure from a hardware and software perspective, they're missing out an opportunity on leveraging the numbers that we were showing, 20% increase in calls. Why would you not just make that investment on both the hardware and the software layer now to get the benefits for the next five-six years. >> You would and if I don't have to make any changes and I get 20% automatically. And the other thing, I don't know if people really appreciate the new curve that the Silicon industry is on. It blows away the history of Moore's law which was whatever, 35-40% a year, we're talking about 100% a year price performance or performance improvements. >> I think when you have an inflection point as we said earlier, there's going to be some things that you know is going to happen, but I think there's going to be a lot that's going to surprise people. New brands will emerge, new startups, new talent, new functionality, new use cases. So, we're going to watch that carefully. And for the folks watching that know that theCUBE's been 12 years with covering VMware VMworld, now VMware Explore, we've kind of met everybody over the years, but I want to point out a little nuance, Raghu thing in the keynote. During the end, before the collective responsibility sustainment commitment he had, he made a comment, "As proud as we are," which is a word he used, there's a lot of pride here at VMware. Raghu kind of weaved that in there, I noticed that, I want to call that out there because Raghu's proud. He's a proud product guy. He said, "I'm a product guy." He's delivering keynote. >> Almost 20 years. >> As proud as we are, there's a lot of pride at VMware, Sumit, talk about that dynamic because you mentioned customers, your customer is not a lot of churn. They've been there for a long time. They're embedded in every single company out there, pretty much VMware is in every enterprise, if not all, I mean 99%, whatever percentage it is, it's huge penetration. >> We are proud of three things. It comes down to number one, we are proud of our innovations. You can see it, you can see the tone from Raghu or myself, or other executives changes with excitement when we're talking about our technologies, we're just proud. We're just proud of it. We are a technology and product centric company. The second thing that sort of gets us excited and be proud of is exactly what you mentioned, which is the customers. The customers like us. It's a pleasure when I bring Roshan on stage and he talks about how he's expecting certain relationship and what he's viewing VMware in this new world of multi-cloud, that makes us proud. And then third, we're proud of our talent. I mean, I was jokingly talking to just the events team alone. Of course our engineers do amazing job, our sellers do amazing job, our support teams do amazing job, but we brought this team and we said, "We are going to get you to run an event after three years from not they doing one, we're going to change the name on you, we're going to change the attendees you're going to invite, we're going to change the fact that it's going to be new speakers who have never been on the stage and done that kind of presentation. >> You're also going to serve a virtual audience. >> And we're going to have a virtual audience. And you know what? They embraced it and they surprised us and it looks beautiful. So I'm proud of the talent. >> The VMware team always steps up. You never slight it, you've got great talent over there. The big thing I want to highlight as we end this day, the segment, and I'll get your thoughts and reactions, Sumit, is again, you guys were early on hybrid. We have theCUBE tape to go back into the video data lake and find the word hybrid mentioned 2013, 2014, 2015. Even when nobody was talking about hybrid. >> Yeah, yeah. >> Multicloud, Raghu, I talked to Raghu in 2016 when he did the Pat Gelsinger, I mean Raghu, Pat and Andy Jassy. >> Yeah. >> When that cloud thing got cleared up, he cleared that up. He mentioned multicloud, even then 2016, so this is not new. >> Yeah. >> You had the vision, there's a lot of stuff in the oven. You guys make announcements directionally, and then start chipping away at it. Now you got Broadcom buys VMware, what's in the oven? How much goodness is coming out that's like just hitting the fruits are starting to bear on the tree. There's a lot of good stuff and just put that, contextualize and scale that for us. What's in the oven? >> First of all, I think the vision, you have to be early to be first and we believe in it. Okay, so that's number one. Now having said that what's in the oven, you would see us actually do more controls across cloud. We are not done on networking side. Okay, we announced something as project Northstar with networking portfolio, that's not generally available. That's in the oven. We are going to come up with more capability on supporting any Kubernetes on any cloud. We did some previews of supporting, for example, EKS. You're going to see more of those cluster controls across any Kubernetes. We have more work happening on our telco partners for enablement of O-RAN as well as our edge solutions, along with the ecosystem. So more to come on those fronts. But they're all aligned with enabling customers multi-cloud through these five cross cloud services. They're all really, some of them where we have put a big sort of a version one of solution out there such as Aria continuation, some of them where even the version one's not out and you're going to see that very soon. >> All right. Sumit, what's next for you as the president? You're proud of your team, we got that. Great oven description of what's coming out for the next meal. What's next for you guys, the team? >> I think for us, two things, first of all, this is our momentum season as we call it. So for the first time, after three years, we are now being in, I think we've expanded, explored to five cities. So getting this orchestrated properly, we are expecting nearly 50,000 customers to be engaging in person and maybe a same number virtually. So a significant touchpoint, cuz we have been missing. Our customers have departed their strategy formulation and we have departed our strategy formulation. Getting them connected together is our number one priority. And number two, we are focused on getting better and better at making customers successful. There is work needed for us. We learn, then we code it and then we repeat it. And to me, those are the two key things here in the next six months. >> Sumit, thank you for coming on theCUBE. Thanks for your valuable time, sharing what's going on. Appreciate it. >> Always great to have chatting. >> Here with the president, the CEO's coming up next in theCUBE. Of course, we're John and Dave. More coverage after the short breaks, stay with us. (upbeat music)

>>mhm. >>Good morning. Live from Las Vegas. That snowflake Summit 22. Lisa Martin With Day Volonte David's Great. We have three wall to wall days of coverage at Snowflake Summit 22 this year. >>Yeah, it's all about data and bringing data to applications. And we've got some big announcements coming this week. Super exciting >>collaboration around data. We are excited to welcome our first two guests before the keynote. We have seen Nielsen in S V. P of data and Analytics Service offering head at emphasis. And Chris Dignan alumni is back with us to chief revenue officer at stuff like guys. Great to have you on the programme. Thanks for having us. Thank you very much. So he'll tell us what's going on with emphasis and snowflake and the partnership. Give us all that good stuff. >>Yeah, No, I think with the convergence of, uh, data digital and computing economy, um, you know that convergence is creating so much possibilities for for customers, uh, snowflake and emphases working together to help our customers realise the vision and these possibilities that are getting driven. We share a very strategic partnership where we are thinking ahead for our customers in terms of what, uh, we can do together in order to build solutions in order to bring out the expertise that is needed for such transformations and also influencing the thinking, Um, and the and the point of view in the market together so that, you know there is there is cohesive approach to doing this transformation and getting to those business outcomes. So it's a It's a partnership that's very successful and its strategic for for our customers, and we continue to invest for the market. >>Got some great customer. Some of my favourite CVS, Nike, William Sanoma. Gotta love that one. Chris talked to us about the snowflake data cloud. What makes it so unique and compelling in the market? >>Well, I think our customers, really they are going through digital transformation today, and they're moving from on premise to the cloud and historically speaking, there just hasn't been the right tool set to help them do that. I think snowflake brings to the table an opportunity for them to take all of their data and take it and and allow it to go from one cloud to the other so they can sit on a W s it can sit on Azure can sit on G, C, P and I can move around from cloud to cloud, and they can do analytics on top of that. >>So data has been traditionally really hard. And we saw that in the big data movement. But we learned a lot. Uh, and AI has been, you know, challenging. So what are you seeing with with customers? What are they struggling with? And how are you guys helping them? >>Yeah. So if you look at the customer journey, they have invested in a number of technologies in the past and are now at a juncture where they need to transform that landscape. They have the challenges of legacy debt that they need to, you know, get rid of or transform. They have the challenges of really bringing, you know, a cohesive understanding within the enterprise as to what these possibilities are for their business. Given the strategy that they are pursuing, um, business and I t cycles are not necessarily aligned. Um, you have the challenge of very fragmented data landscape that they have created over a period of time. How do you, you know, put all these together and work with a specific outcome in mind so that you're not doing transformation for the purpose of transformation. But to be able to actually drive new business models, new data driven products and services ability for you to collaborate with your partners and create unique competitive advantage in the market. And how do you bring those purposes together with the transformation that that's really happening? And and that's where you know our our customers, um, you know, grapple with the challenges of bringing it together. So, >>Chris, how do you see? Because it was talking about, uh, legacy that I think technical debt. Um, you kind of started out making the data warehouse easier. Then this data cloud thing comes out. You're like, Oh, that's an interesting vision and all of a sudden it's way more than vision. You get this huge ecosystem you're extending, we're gonna hear the announcements this morning. We won't. We won't spill the beans, but but really expanding the data cloud. So it's hard to keep up with with where you're at. So I think modernisation, right? So how do you think about modernisation? How are your customers thinking about it? And what's the scope of Snowflake. >>Well, you know, I think historically, you asked about AI and Ml and, you know, in the A I world historically, they've lacked data, and I think because we're the data cloud, we're bringing data, you know, and making it available and democratising it for everybody. And then, you know, partners like emphasis are actually helping us bring, you know, applications and new business models to to the table to our customers and their innovating on top of the data that we already have in the Snowflake Data Club. >>Chris, can you talk about some of the verticals where you guys are successful with emphasis that the three that I mentioned are retailers, But I know that finance, healthcare and life sciences are are huge for smooth, like talk to me, give us a perspective of the verticals that are coming to you. Guys saying help us out with transport. >>You know, I'll give you just an example. So So in the in the retail space, for example, Kraft Heinz is a is a joint customer of ours. And, you know, they've been all in on on snowflakes, Data Cloud and one of our big customers as well it is is Albertsons, and Albertans realises, Oh my gosh, I have all this information around the consumer in in the grocery stores and Kraft Heinz. They want access to that, and they actually can make supply chain decisions a lot faster if they have access to it. So with snowflakes data sharing, we can actually allow them to share data. Albertans share data directly with Kraft, Heinz and Kraft. Heinz can actually make supply chain decisions in real time so that these are some of the stuff that emphasis and stuff like help our customers self. >>So traditionally, the data pipeline goes through some very highly specialised individuals, whether the data engineer, the data scientists and data analyst. So that example that you just gave our organisation you mentioned before democratisation. So democratisation needs to be as a businessperson, I actually can get access to the data. So in that example that you gave between Kraft, Heinz and and and Albertson, is it the the highly hyper specialised teams sharing that data? Or is it actually extending into the line of business focus? >>That's so that's the interesting part for us is I think, snowflake, we just recently reorganise my sales team this year into verticals, and the reason we did that is customers no longer want to talk to us about speeds and feeds of how fast my database goes. They want to actually talk about business outcomes. How do I solve for demand forecasting? How do I supply fix my supply chain issues? Those are things. Those are the. That's how we're aligning with emphasis. So well is they've been doing this for a long time, Can only we haven't. And so we need their help on getting us to the next level of of the sales motion and talking to our customers on solving these business challenges in >>terms of that next level. So no question for you. Where are the customer conversations happening? At what level? I mean, we've seen such dramatic changes in the market in the last couple of years. Now we're dealing with inflation rising interest rates. Ukraine. Are you seeing the conversations in terms of building data platforms rising up the C suite? As every company recognises, we're going to be a data company. We're not gonna be a business. >>Absolutely. And I think all the macroeconomic forces that you talked about that's working on the enterprises globally is actually leading them to think about how to future proof their business models. Right? And there are tonnes of learning that they've hired in the last two or three years and digitising in embracing more digital models. The conversation with the customers have really pivoted towards business outcome. It is a C suite conversation. It is no longer just an incremental change for the for the companies they recognise. That data has been touted as a strategic asset for a long time, but I think it's taking a purpose and a meaning as to what it does for for the customers, the conversations are around industry verticals. You know, what are the specific challenges and opportunities that the the enterprises have, uh, and how you realise those and these cuts across multiple different layers. You know, we're talking about how your democratised data, which in our point of view, is absolute, must in terms of putting a foundation that doesn't take super specialised people to be able to run every operation and every bit of data that you process we have invested in building autonomous data and a state that can process data as it comes in without any manual intervention and take it all the way to consumption but also investing in those industry solutions. Along with snowflake, we launched the healthcare and life Sciences solution. We launched the only channel for retail and CPG. And these are great examples of how Snowflake Foundation enables democratisation on one side but also help solve business problems. In fact, with Snowflake, we have a very, uh, special partnership because our point of view on data economy is about how you connect with the network partners externally, and snowflake brings native capabilities. On this, we leverage that to Dr Exchanges for our customers and one of the services company in the recycling business. Uh, we're actually building and in exchange, which will allow the data points from multiple different sources and partners to come together. So they have a better understanding of their customers, their operations, the field operations and things >>like building a data ecosystem. Yes. Alright, They they Is it a two sided market place where you guys are observers and providing the the technology and the process, you know, guidance. What's your role in that? >>Yeah. So, um, we were seeing their revolution coming? Uh, two stages. Maybe even more. Um, customers are comfortable building an ecosystem. That's kind of private for them. Which means that they know who they are sharing data with. They know what the data is getting used for. And how do you really put governance on this? So that on one side you can trust it on the other side. There is a good use of that data, Uh, and not, uh, you know, compromise on their quality or privacy and some of the other regulations. But we do see this opening up to the two sided market places as well. Uh, some of the industry's lend themselves extremely well for that kind of play. We have seen that happening in trading area. We've seen that happen. And, uh, you know, the credit checks and things like that which are usually open for, you know, those kind of ecosystem. But the conversations and the and the programmes are really leading towards towards that in the market. >>You know, Lisa, one of things I wrote about this weekend is I was decided to come to stuff like summit and and see one of the, you know, thesis I have is that we're going to move not just beyond analytics, including analytics, but also building data products that can be monetised and and I'm hoping we're going to see some of that here. Are you seeing that Christian in the customer? It's It's >>a great question, David. So So we have You know, I just thought of it as as he was talking about. We have a customer who's a very large customer of ours who's in the financial services space, and they handle roughly 40% of the credit card transactions that happen in the US and they're coming to us and saying they want to go from zero in data business today to a $2 billion business over the next five years, and they're leaning on us to help them do that. And one of the things that's exciting for me is they're coming to us not saying Hey, how do you do it? You know, they're saying, Hey, we want to build a consumption model on top of snowflake and we want to use you as the delivery mechanism and the billing mechanism to help us actually monetise that data. So yes, the answer is. You know, I I used to sell to, you know, chief Data Officers and and see IOS. Now I'm talking to VPs of sales and I'm talking to chief operating officers and I'm talking to CEOs about how do we actually create a new revenue stream? And that's just I mean, it's exhilarating to have those conversations. That's >>data products. They don't have to worry about the infrastructure that comes from the cloud. They don't have to worry about the governance, as Senior was saying, Just put >>it in stuff like Just >>put stuff like that. So I call it The super cloud is kind of a, you know, a funny little tongue in cheek. But it's happening. It's this layer. It's not just multiple clouds. You see a lot of your critical competitors adjacent competitors saying, Hey, we're now running in in Google or we're running in Azure. We've been running on AWS. This is different. This is different, isn't it? It's a cloud that floats above the The infrastructure of the hyper scale is, and that's that's a new era. I think >>it's a new error. I think they're you know, I think the hyper scholars want to, you know, keep us as a as a data warehouse and and we're not. The customers are not letting them so So I think that's you know where emphasis kind of saw the light early on. And they were our innovation partner of the year, uh, this past year and they're helping us in our customers innovate, >>but you're uniquely qualified to do that where? I don't think it's the hyper scholars agenda. At least I never say never with the hyper scale is, but yeah, they have focused on providing infrastructure. And, yeah, they have databases and other tools. But that that cross cloud that continuum to your point, talking to VPs of sales and how do you generate revenue? That maybe, is a conversation that they have, but not explicitly as to how to actually do it in a data >>cloud. That's right. I mean, those and those are the Those are the fun conversations because you're you're saying, Hey, we can actually create a new revenue stream. And how can we actually help you solve our joint customers problems? So, yes, it is. Well, >>that's competitive differentiation for businesses. I mean, this is, as I mentioned Every company has to be a data company. If they're not, they're probably not going to be around much longer. They've got to be able to to leverage a data platform like snowflake, to find insights, be able to act on them and create value new services, new products to stay competitive, to stay ahead of the competition. That's no longer nice to have >>100%. I mean, I think they're they're all scared. I mean, you know, like if you look in the financial services space, they look at some of the fintech, as you know, the giant £800 gorillas look at the small fintech has huge threats to the business, and they're coming to us and say, How can we innovate our business now? And they're looking at us as the the innovator, and they're looking at emphasis to help them do that. So I think these are These are incredible times. >>So the narrative on Wall Street, of course, this past earnings season was consumption and who has best visibility and and they they were able to snowflake had a couple of large customers dial down consumption, some consumer facing. Here's the thing. If you're selling a data product for more than it costs you to make. If you dial down consumption in the future, you're gonna dial down revenue. So that's it's going to become less and less discretionary over time. And that, to me, is the next error. That's really exciting. >>The key, The key there is understanding the unit of measure. I think that's the number. One question that we get from customers is what is the unit of measure that we care about, that we want to monetise because to your point, it costs you more to make the product. You're not going to sell it right? And so I think that those are the things that the energy that we're spending with customers today is advising them, jointly advising them on how to actually monetise the specific, you know, unit of measure that they care >>about because when they get the Amazon bill or the snowflake bill, the CFO starts knocking the door. The answer has to be well, look at all the revenue that we generated and all the operating profit and the free cash flow that we drove, and then it's like, Oh, I get it. Keep doing it well, if I'm >>if I'm going on sales calls with the VP of sales and his their sales team, fantastic, right generated helping them generate revenue, right? That's a great conversation >>dynamic. And I think the adoption is really driven through the value, uh, that they can drive in their ecosystem. Their products are similar to products and services that these companies sell. And if you're embedding data inside Syria into your products services, that makes you that much more competitive in the market and drive value for your stakeholders. And that's essentially the future business model that we're talking about. On one side, the other one is the agility. Things aren't remaining constant, they are constantly changing, and we talked about some of those forces earlier. All of this is changing. The landscape is changing the the needs in the economy and things like that, and how you adapt to those kind of models in the future and pivoted on data capabilities that lets you identify new opportunities and and create new value. >>Speaking of creating new value last question guys, before we wrap, what's the go to market approach here between the two companies working customers go to get engaged. I imagine both sides. >>Yeah. I mean, the way that partnership looks good to me is is sell with co selling. So So I think, you know, we look at developing joint solutions with emphasis. They've done a wonderful job of leading into our partnership. So, you know, Sue Neill and I have a regular cadence where we talked every quarter, and our sales teams and our partner teams are are all leaning in and co selling. I don't know if you >>have Absolutely, um, you know, we we proactively identify, you know, the opportunities for our customers. And we work together at all levels within, you know, between the two companies to be able to bring a cohesive solution and a proposition for the customers. Really help them understand how to, you know, what is it that they can, um, get to and how you get that journey actually executed. And it's a partnership that works very seamlessly through that entire process, not just upstream when we're selling, but also downstream and we're executing. And we've had tremendous success together and look forward to more. >>Congratulations on that success, guys. Thank you so much for coming on talking about new possibilities with data and AI and sharing some of the impact that the technologies are making. We appreciate your insights. >>Thank you. Thank >>you. Thank you So much >>for our guests and a Volonte. I'm Lisa Martin. You're watching the Cube live in Las Vegas from Snowflake Summit 22 back after the keynote with more breaking news. Mhm, mhm.

>>no real filter and that kind of stuff. But you're also an entrepreneur, right? And you know the business, you've been in software, you detect business. I'm instructing you get a lot of pictures, this entertainment business on our show, we're a bubble. We don't do a lot of tech deals that were talking because it's boring tv tech people love tech consumers love the benefit of text. No consumer opens up their iphone and says, oh my gosh, I love the technology behind my, what's it been like being on the shark tank? You know, filming is fun and hang out just fun and it's fun to be a celebrity at first your head gets really big and you get a really good tables at restaurants and who says texas has got a little possessed more skin in the game today in charge of his destiny. Great robert Herjavec. No, these two stars cube alumni >>welcome back to the cubes coverage of A W. S. Public sector seven. I'm john for your host of the cube got a great segment here on healthcare startup accelerators of course. Sandy carter is co hosting media. This one Vice President Aws. She's awesome on the cuBA and jennifer Blumenthal co founder and C of one record entrepreneur, very successful. Thanks for coming on jennifer. Thank good to see you. Sandy thanks for joining me again. You >>are most welcome, >>jennifer. Before we get into the whole accelerated dynamic, just take a minute to explain what you guys do. One record. >>Sure. So one record is a digital health company that enables users to access aggregate and share their healthcare information. So what that means is we help you as a person get your data and then we also help companies who would like to have workflows were consumers in the loop to get their data. So whether they're sharing it with a provider, researcher payer. >>So, Sandy, we've talked about this amazon web services, healthcare accelerator cohort batches. What do you call cohort batches? Cohorts explain what's going on with the healthcare accelerator? >>Yeah. So, um, we decided that we would launch and partner an accelerator program and accelerator program just provides to a start up a little bit extra technical help. A little bit extra subject matter expertise and introductions to funders. And so we decided we were going to start one for health care. It's one of the biggest disruptive industries in public sector. Um, and so we weren't sure how it's gonna go. We partnered with Kids X. Kids X is part of the Los Angeles system for medical. And so we put out a call for startups and we had 427 startups, we were told on average and accelerating it's 50-100. So we were blown away 31 different countries. So it was really amazing. And then what we've been doing is down selecting and selecting that Top 10 for our first cohort. So we're going from 427 down to 10. And so obviously we looked at the founders themselves to see the quality of the leadership of the company, um the strength of their technology and the fit of the technology into the broader overall healthcare and healthcare ecosystem. And so we were thrilled that jennifer and one record was one of the top 10 start ups in this space that we chose to be in the, in the cohort. And so now we're going to take it to the six weeks intensive where we'll do training, helping them with AWS, provide them A W. S. Credits and then Kid X will also provide some of the health care uh subject matter >>expertise as well. Can I get some of those credits over here to maybe? >>Yes, you can actually, you can talk to me don you can't >>Talk to me, Jennifer, I gotta ask you. So you're an entrepreneur. So doing start doing cos it's like a roller coaster. So now to make the top 10 but also be in the area of his accelerator, it's a partnership, right? You're making a bet. What's your take on all this? >>Well, we've always been partners with a W. S. We started building on AWS in the very beginning. So when I was setting up the company a huge decision early on with infrastructure and when I saw the launch of the accelerator, I had to apply because we're at the point in the company that we're growing and part of growing is growing with the VW. So I was really excited to take advantage of that opportunity and now in the accelerator, it's more of thinking about things that we weren't thinking about the services that we can leverage to fill in the gaps within our platform so we can meet our customers where they are >>using award winning MSP cloud status city, your partners, great relationship with the ecosystem. So congratulations Sandi. What's the disruption for the healthcare? Because right now education and health care, the two top areas we're seeing and we're reporting on where cloud scale developed two point or whatever buzzword digital transformation you want to use is impacting heavily healthcare industry. There's some new realities. What's your, what's your vision, what's your view? >>Hey john before she does that, I have to give a plug to Claudius city because they just made premier partner as well, which is a huge deal. Uh and they're also serving public sector. So I just wanted to make sure that you knew that too. So you can congratulate. Go ahead, jennifer >>Well, so if I zoom in, I think about a P. I. S. Every day, that's what I think about and I think about microservices. So for me and for one record, what we think about is legislation. So 21st century Cures act says that you as a consumer have to be able to access your healthcare data from both your providers and from your players and not just your providers, but also the underlying technology vendors and H. I. E. S. H. I am and it's probably gonna extend to really anyone who plays within the healthcare ecosystem. So you're just going to see this explosion of A. P. I. S. And we're just your one of that. I mean for the payers that we went into effect on july 1st. So I mean when you think about the decentralization of healthcare where healthcare is being delivered plus an api economy, you're just going to have a whole new model developing and then throwing price transparency and you've got a whole new cake. >>I'm smiling because I love the peacocks. In fact, last night I shouldn't have tweeted this but there's a little tweet flames going on around A. P. Is being brittle and all this stuff and I said, hey developer experience about building great software apps are there for you. It's not a glue layer by itself. You got to build software around the so kind of a little preaching to the younger generation. But this health care thing is huge because think about like old school health care, it was anti ap I was also siloed. So what's your take on has the culture is changing health care because the user experience, I want my records, I want my privacy, I want to maintain everything confidential but access. That's hard. >>I think well health care to be used to just be paper was forget about a. P. I. Is it was just paper records. I think uh to me you think about uh patient journey, like a patient journey starts with booking an appointment and then everything after that is essentially an api call. So that's how I think about it is to all these micro transactions that are happening all the time and you want your data to go to your health care provider so they can give you the proper care, you want your data to go to your pair so they can pay for your care and then those two stakeholders want your data so that they can provide the right services at the right time to the right channel. And that is just a series of api calls that literally sits on a platform. >>What's interesting, I'd love to get your take on the where you think the progress bar is in the industry because Fintech has shown the way you got defy now behind a decentralized finance, health care seems to be moving on in a very accelerated rate towards that kind of concept of cloud, scale, decentralization, privacy. >>Yeah, I mean, that's a big question, what's interesting to me around that is how healthcare stakeholders are thinking about where they're providing care. So as they're buying up practices primary care specialty care and they're moving more and more outside of the brick and mortar of the health care system or partnering with your startups. That's really where I think you're going to see a larger ecosystem development, you could just look at CVS and walmart or the dollar store if they're going to be moving into health care, what does that look like? And then if you're seeking care in those settings, but then you're going to Mayo clinic or Kaiser permanente, there's so many new relationships that are part of your hair circle >>delivery is just what does that even mean now, delivery of health >>care. It's wherever you it's like the app economy you want to ride right now, you want a doctor right now, that's where we're heading its ease of use. >>This is this exciting startups, changing the game. Yes, I love it. I mean, this is what it's all about this health >>Care, this is what it's all about. And if you look at the funding right now from VCS, we're seeing so much funding pour into health care, we were just looking at some numbers and in the second quarter alone, the funding went up almost 700%. And the amount of funding that is pouring into companies like jennifer's company to really transform healthcare, 30% of it is going into telehealth. So when you talked about, you know, kind of ai at the edge, getting the right doctor the right expert at the right time, we're seeing that as a big trend in healthcare to >>well jennifer, I think the funding dynamics aside the opportunity for market total addressable market is massive when the application is being decomposed, you got front end, whether it's telemedicine, you got the different building blocks of healthcare being radically reconfigured. It's a re factoring of healthcare. Yeah, >>I think if you just think about where we're sitting today, you had to use an app to prove proof of vaccination. So this is not just national, this is a global thing to have that covid wallet. We at one record have a covid wallet. But just a couple years from now, I need more than just by covid vaccination. I need all my vaccinations. I need all my lab results. I need all my beds. It's opening the door for a new consumer behavior pattern, which is the first step to adoption for any technology. >>So somebody else covid wallet. So I need >>that was California. Did the, did a version of we just have a pen and it's pretty cool. Very handy. I should save it to my drive. But my phone, but I don't jennifer, what's the coolest thing you're working on right now because you're in the middle of all the action. >>I get very excited about the payer app is that we're working on. So I think by the end of the month we will be connected to almost to all the blues in the United States. So I'm very excited when a user comes into the one record and they're able to get their clinical data from the provider organization and then their clinical financial and formulary data from their payers because then you're getting a complete view, You're getting the records for someone who gave you care and you're getting the records from someone who paid for your care. And that's an interesting thing that's really moving towards a complete picture. So from a personal perspective that gets exciting. And then from a professional perspective, it's really working with our partners as they're using our API s to build out workflows and their applications. >>It's an api economy. I'd like to ask you to on the impact side to the patient. I hear a lot of people complaining that hey, I want to bring my records to the doctor and I want to have my own control of my own stuff. A lot of times, some doctors don't even know other historical data points about a patient that could open up a diagnosis and, or care >>or they can't even refer you to a doctor. Most doctors really only refer within a network of people that they know having a provider directory that allows doctors refer, having the data from different doctors outside of their, you know, I didn't really allows people to start thinking beyond just their little box. >>Cool. Well, great to have you on and congratulations on being in the top 10 saying this is a wonderful example of how the ecosystem where you got cloud city, your MSP. You mentioned the shout out to them jerry Miller and his team by working together the cloud gives you advantages. So I have to ask, we look at amazon cloud as an entrepreneur. It's kind of a loaded question, but I'm going to ask it. I love it. >>You always do it >>when you look at amazon, what do you see as opportunities as an entrepreneur? Because I'll see the easy ones. They have computing everything else. But like what's the, what does cloud do for you as an entrepreneur? What does it, what does it make you do? >>Yeah. So for been working with jerry since the beginning for me when I think about it, it's really the growth of our company. So when we start building, we really just thinking about it from a monolithic build and we move to microservices and amazon has been there every step of the way to support us as that. And now, you know, the things that I'm interested in are specifically health lake and anything that's NLP related that we could plug into our solution for when we get data from different sources that are coming in really unstructured formats and making it structured so that it's searchable for people and amazon does that for us with their services that we can add into the applications. >>Yeah, we announced that data health like and july it has a whole set of templates for analytics, focused on health care as well as hip hop compliance out of the box as well. >>The I think I think that's what's important is people used to think application first. Now it's creating essentially a data lake, then analytics and then what applications you build on top of that. And that's how our partners think about it and that's how we try and service them using amazon as our problem. So >>you're honing in on the value of the data and how that conflicts and then work within the whatever application requests might come >>in. Yes, >>it's interesting. You know, we had an event last month and jerry Chen from Greylock partners came on and gave a talk called castles in the cloud. He's gonna be cute before. He's a, he's a veces, they talk about moats and competitive manage so having a moat, The old school perimeter moz how cloud destroyed that. He's like, no, now the castles are in the cloud, he pointed snowflake basically data warehouse in the cloud red shifts there too. But they can be successful. And that's how the cloud, you could actually build value, sustainable value in the cloud. If you think that way of re factoring not just hosting a huge, huge, huge thing. >>I think the only thing he, this was customer service because health care is still very personal. So it's always about how you interact with the end user and how you can help me get to where they need to be going >>and what do you see that going? Because that's, that's a good point. >>I think that is a huge opportunity for any new company that wants to enter healthcare, customer service as a service in health care for all the different places that health care is going to be delivered. Maybe there's a company that I don't know about, but when they come out, I'd like to meet them. >>Yeah, I mean, I can't think of one cover that can think of right now. This is what I would say is great customer service for health care. >>And if there is one out there contacted me because I want to talk to you about AWS. >>Yeah. And you need the app from one record that make it all >>happen. That's where Omni channel customer service across all health care entities. Yeah, that's >>a great billion dollar idea for someone listening to our show right now. >>Right, alright. So saying they had to give you the opportunity to talk more because this is a great example of how the world's very agile. What's the next step for the AWS Healthcare accelerator? Are there more accelerators? Do you do it by vertical? >>What happens next? So, with the healthcare accelerator, this was our first go at the accelerator. So, this is our first set of cohorts, Of course, all 427 companies are going to get some help from a W. S. as well. We also you'll love this john We also did a space accelerator. Make sure you ask Clint about that. So we have startups that are synthesizing oxygen on mars to sending an outpost box to the moon. I mean, it's crazy what these startups are doing. Um, and then the third accelerator we started was around clean energy. So sustainability, we sold that one out to, we had folks from 66 different countries participate in that one. So these have been really successful for us. So it reinvent. When we talk again, we'll be announcing a couple of others. So right now we've got healthcare, space, clean energy and we'll be announcing a couple other accelerators moving forward. >>You know, it's interesting, jennifer the pandemic has changed even our ability to get stories. Just more stories out there now. So you're seeing kind of remote hybrid connections, ap ideas, whether it's software or remote interviews or remote connections. There's more stories being told out there with digital transformation. I mean there wasn't that many before pandemic has changed the landscape because let's face it, people were hiding some really bad projects behind metrics. But when you pull the pandemic back and you go, hey, everyone's kind of emperors got no clothes on. Those are bad projects. Those are good projects that cloud investment worked or I didn't have a cloud investment. They were pretty much screwed at that point. So this is now a new reality of like value, you can't show me value. >>It's crazy to me when I meet people who tell me like we want to move to the cloud of like, why are you not on the cloud? Like this really just blows my life. Like I don't understand why you have on prem or while you did start on the cloud, this is more for larger organizations, but younger organizations, you know, the first thing you have to do, it's set up that environment. >>Yeah. And then now with the migration plans and seeing here, uh whereas education or health care or other verticals, you've got, now you've got containers to give you that compatibility and then you've got kubernetes and you've got microservices, you've got land. Uh I mean, come on, that's the perfect storm innovation. There's no excuses in my opinion. So, you know, if you're out there and you're not leveraging it, then you're probably gonna be out of business. That's my philosophy. Thank you for coming up. Okay. Sandy, thank you. Thank you, john Okay. Any of his coverage here, summit here in D. C. I'm john ferrier. Thanks for watching. Mm >>mm mm mhm. I have been in the software and technology industry for over 12 years now, so I've had >>the opportunity

>>and hello, we're back. I've got my panel and we are doing things real time here. So sorry for the delay a few minutes late. So the way let's talk about things, the reason we're here and we're going around the room and introduce everybody. Got three special guests here. I got my evil or my john and the normal And we're going to talk about get ops I called it future office just because I want to think about what's the next thing for that at the end, we're gonna talk about what our ideas for what's next for getups, right? Um, because we're all starting to just get into get ups now. But of course a lot of us are always thinking about what's next? What's better? How can we make this thing better? So we're going to take your questions. That's the reason we're here, is to take your questions and answer them. Or at least the best we can for the next hour. And all right, so let's go around the room and introduce yourself. My name is Brett. I am streaming from Brett from that. From Brett. From Virginia Beach in Virginia beach, Virginia, United States. Um, and I talk about things on the internet, I sell courses on you, to me that talk about Docker and kubernetes Ive or introduce yourself. >>How's it going? Everyone, I'm a software engineer at axel Springer, currently based in Berlin and I happen to be Brett Brett's teaching assistant. >>All right, that's right. We're in, we're in our courses together almost every day. Mm john >>hey everyone, my name is john Harris, I used to work at Dhaka um, I now work at VM ware is a star field engineer. Um, so yeah, >>and normal >>awesome by the way, you are streaming from Brett Brett, >>I answered from breath to breath. >>Um I'm normal method. I'm a distinguished engineer with booz allen and I'm also a doctor captain and it's good to see either in person and it's good to see you again john it's been a little while. >>It has the pre covid times, right? You're up here in Seattle. >>Yeah. It feels, it feels like an eternity ago. >>Yeah, john shirt looks red and reminds me of the Austin T shirt. So I was like, yeah, so we all, we all have like this old limited edition doctor on E. >>T. That's a, that's a classic. >>Yeah, I scored that one last year. Sometimes with these old conference church, you have to like go into people's closets. I'm not saying I did that. Um, but you know, you have to go steal stuff, you to find ways to get the swag >>post post covid. If you ever come to my place, I'm going to have to lock the closets. That >>that's right, That's right. >>So the second I think it was the second floor of the doctor HQ in SAn Francisco was where they kept all the T shirts, just boxes and boxes and boxes floor to ceiling. So every time I went to HQ you just you just as many as you can fit in your luggage. I think I have about 10 of these. You >>bring an extra piece of luggage just for your your shirt shirt grab. Um All right, so I'm going to start scanning questions uh so that you don't have to you can you help you all are welcome to do that. And I'm going to start us off with the topic. Um So let's just define the parameters. Like we can talk about anything devops and here we can go down and plenty of rabbit holes. But the kind of, the goal here is to talk about get ups and get ups if you haven't heard about it is essentially uh using versioning systems like get like we've all been getting used to as developers to track your infrastructure changes, not just your code changes and then automate that with a bunch of tooling so that the robots take over. And essentially you have get as a central source of truth and then get log as a central source of history and then there's a bunch of magic little bits in the middle and then supposedly everything is wonderful. It's all automatic. The reality is is what it's often quite messy, quite tricky to get everything working. And uh the edges of this are not perfect. Um so it is a relatively new thing. It's probably three, maybe four years old as an official thing from. We've uh so we're gonna get into it and I'll let's go around the room and the same word we did before and um not to push on that, put you on the spot or anything. But what is, what is one of the things you either like or either hate about getups um that you've enjoyed either using it or you know, whatever for me. I really, I really love that I can point people to a repo that basically is hopefully if they look at the log a tracking, simplistic tracking of what might have changed in that part of the world or the environment. I remember many years past where, you know, I've had executive or some mid level manager wants to see what the changes were or someone outside my team went to see what we just changed. It was okay, they need access to this system into that dashboard and that spreadsheet and then this thing and it was always so complicated and now in a world where if we're using get up orbit bucket or whatever where you can just say, hey go look at that repo if there was three commits today, probably three changes happened. That's I love that particular part about it. Of course it's always more complicated than that. But um Ive or I know you've been getting into this stuff recently. So um any thoughts? Yeah, I think >>my favorite part about get ops is >>reproducibility. Um >>you know the ability to just test something and get it up and running >>and then just tear it down. >>Uh not >>being worried that how did I configure it the first time? I think that's my favorite part about >>it. I'm changing your background as we do this. >>I was going to say, did you just do it get ups pushed to like change his >>background, just a dialogue that different for that green screen equals false? Uh Change the background. Yeah, I mean, um and I mean I think last year was really my first year of actually using it on anything significant, like a real project. Um so I'm still, I still feel like I'm very new to john you anything. >>Yeah, it's weird getups is that thing which kind of crystallizes maybe better than anything else, the grizzled veteran life cycle of emotions with the technology because I think it's easy to get super excited about something new. And when I first looked into get up, so I think this is even before it was probably called getups, we were looking at like how to use guest source of truth, like everything sounds great, right? You're like, wait, get everyone knows, get gets the source of truth, There's a load of robust tooling. This just makes a sense. If everything dies, we can just apply the get again, that would be great. Um and then you go through like the trough of despair, right? We're like, oh no, none of this works. The application is super stateless if this doesn't work and what do we do with secrets and how do we do this? Like how do we get people access in the right place and then you realize everything is terrible again and then everything it equalizes and you're kind of, I think, you know, it sounds great on paper and they were absolutely fantastic things about it, but I think just having that measured approach to it, like it's, you know, I think when you put it best in the beginning where you do a and then there's a magic and then you get C. Right, like it's the magic, which is >>the magic is the mystery, >>right? >>Magic can be good and bad and in text so >>very much so yeah, so um concurrence with with john and ever uh in terms of what I like about it is the potential to apply it to moving security to left and getting closer to a more stable infrastructures code with respect to the whole entire environment. Um And uh and that reconciliation loop, it reminds me of what, what is old is new again? Right? Well, quote unquote old um in terms of like chef and puppet and that the reconciliation loop applied in a in a more uh in a cleaner interface and and into the infrastructure that we're kind of used to already, once you start really digging into kubernetes what I don't like and just this is in concurrence with the other Panelist is it's relatively new. It has um, so it has a learning curve and it's still being, you know, it's a very active um environment and community and that means that things are changing and constantly and there's like new ways and new patterns as people are exploring how to use it. And I think that trough of despair is typically figuring out incrementally what it actually is doing for you and what it's not going to solve for you, right, john, so like that's that trough of despair for a bit and then you realize, okay, this is where it fits potentially in my architecture and like anything, you have to make that trade off and you have to make that decision and accept the trade offs for that. But I think it has a lot of promise for, for compliance and security and all that good stuff. >>Yeah. It's like it's like the potentials, there's still a lot more potential than there is uh reality right now. I think it's like I feel like we're very early days and the idea of especially when you start getting into tooling that doesn't appreciate getups like you're using to get up to and use something else and that tool has no awareness of the concept so it doesn't flow well with all of the things you're trying to do and get um uh things that aren't state based and all that. So this is going to lead me to our first question from Camden asking dumb questions by the way. No dumb questions here. Um How is get apps? Not just another name for C. D. Anybody want to take that as an answer as a question. How is get up is not just another name for C. D. I have things but we can talk about it. I >>feel like we need victor foster kids. Yeah, sure you would have opinions. Yeah, >>I think it's a very yeah. One person replied said it's a very specific it's an opinionated version of cd. That's a great that's a great answer like that. Yeah. >>It's like an implement. Its it's an implementation of deployment if you want it if you want to use it for that. All right. I realize now it's kind of hard in terms of a physical panel and a virtual panel to figure out who on the panel is gonna, you know, ready to jump in to answer a question. But I'll take it. So um I'll um I'll do my best inner victor and say, you know, it's it's an implementation of C. D. And it's it's a choice right? It's one can just still do docker build and darker pushes and doctor pulls and that's fine. Or use other technologies to deploy containers and pods and change your, your kubernetes infrastructure. But get apps is a different implementation, a different method of doing that same thing at the end of the day. Yeah, >>I like it. I like >>it and I think that goes back to your point about, you know, it's kind of early days still, I think to me what I like about getups in that respect is it's nice to see kubernetes become a platform where people are experimenting with different ways of doing things, right? And so I think that encourages like lots of different patterns and overall that's going to be a good thing for the community because then more, you know, and not everything needs to settle in terms of only one way of doing things, but a lot of different ways of doing things helps people fit, you know, the tooling to their needs, or helps fit kubernetes to their needs, etcetera. Yeah, >>um I agree with that, the, so I'm gonna, since we're getting a load of good questions, so um one of the, one of the, one of the, I want to add to that real quick that one of the uh from the, we've people themselves, because I've had some on the show and one of things that I look at it is distinguishing is with continuous deployment tools, I sort of think that it's almost like previous generation and uh continuous deployment tools can be anything like we would consider Jenkins cd, right, if you if you had an association to a server and do a doctor pull and you know, dr up or dr composed up rather, or if it did a cube control apply uh from you know inside an ssh tunnel or something like that was considered considered C. D. Well get ops is much more rigid I think in terms of um you you need to apply, you have a specific repo that's all about your deployments and because of what tool you're using and that one your commit to a specific repo or in a specific branch that repo depends on how you're setting it up. That is what kicks off a workflow. And then secondly there's an understanding of state. So a lot of these tools now I have uh reconciliation where they they look at the cluster and if things are changing they will actually go back and to get and the robots will take over and will commit that. Hey this thing has changed um and you maybe you human didn't change it, something else might have changed it. So I think that's where getups is approaching it, is that ah we we need to we need to consider more than just a couple of commands that be runnin in a script. Like there needs to be more than that for a getups repo to happen anyway, that's just kind of the the take back to take away I took from a previous conversation with some people um >>we've I don't think that lost, its the last piece is really important, right? I think like for me, C d like Ci cd, they're more philosophical ideas, write a set of principles, right? Like getting an idea or a code change to environments promoting it. It's very kind of pipeline driven um and it's very imperative driven, right? Like our existing CD tools are a lot of the ways that people think about Cd, it would be triggered by an event, maybe a code push and then these other things are happening in sequence until they either fail or pass, right? And then we're done. Getups is very much sitting on the, you know, the reconciliation side, it's changing to a pull based model of reconciliation, right? Like it's very declarative, it's just looking at the state and it's automatically pulling changes when they happen, rather than this imperative trigger driven model. That's not to say that there aren't city tools which we're doing pull based or you can do pull based or get ups is doing anything creatively revolutionary here, but I think that's one of the main things that the ideas that are being introduced into those, like existing C kind of tools and pipelines, um certainly the pull based model and the reconciliation model, which, you know, has a lot in common with kubernetes and how those kind of controllers work, but I think that's the key idea. Yeah. >>Um This is a pretty specific one Tory asks, does anyone have opinions about get ops in a mono repo this is like this is getting into religion a little bit. How many repos are too many repose? How um any thoughts on that? Anyone before I rant, >>go >>for it, go for it? >>Yeah. How I'm using it right now in a monitor repo uh So I'm using GIT hub. Right, so you have what? The workflow and then inside a workflow? Yeah, mo file, I'll >>track the >>actual changes to the workflow itself, as well as a folder, which is basically some sort of service in Amman Arepa, so if any of those things changes, it'll trigger the actual pipeline to run. So that's like the simplest thing that I could figure out how to, you know, get it set up using um get hubs, uh workflow path future. Yeah. And it's worked for me for writing, you know? That's Yeah. >>Yeah, the a lot of these things too, like the mono repo discussion will, it's very tool specific. Each tool has various levels of support for branch branching and different repos and subdirectories are are looking at the defense and to see if there's changes in that specific directory. Yeah. Sorry, um john you're going to say something, >>I was just going to say, I've never really done it, but I imagine the same kind of downsides of mono repo to multiple report would exist there. I mean, you've got the blast radius issues, you've got, you know, how big is the mono repo? Do we have to pull does the tool have to pull that or cashier every time it needs to determine def so what is the support for being able to just look at directories versus you know, I think we can get way down into a deeper conversation. Maybe we'll save it for later on in the conversation about what we're doing. Get up, how do we structure our get reposed? We have super granular repo per environment, Perper out reaper, per cluster repo per whatever or do we have directories per environment or branches per environment? How how is everything organized? I think it's you know, it's going to be one of those, there's never one size fits all. I'll give the class of consultant like it depends answer. Right? >>Yeah, for sure. It's very similar to the code struggle because it depends. >>Right? >>Uh Yeah, it's similar to the to the code problem of teams trying to figure out how many repose for their code. Should they micro service, should they? Semi micro service, macro service. Like I mean, you know because too many repose means you're doing a bunch of repo management, a bunch of changes on your local system, you're constantly get pulling all these different things and uh but if you have one big repo then it's it's a it's a huge monolithic thing that you usually have to deal with. Path based issues of tools that only need to look at a specific directory and um yeah, it's a it's a culture, I feel like yeah, like I keep going back to this, it's a culture thing. Does your what is your team prefer? What do you like? What um what's painful for everyone and who's what's the loudest pain that you need to deal with? Is it is it repo management? That's the pain um or is it uh you know, is that that everyone's in one place and it's really hard to keep too many cooks out of the kitchen, which is a mono repo problem, you know? Um How do we handle security? So this is a great one from Tory again. Another great question back to back. And that's the first time we've done that um security as it pertains to get up to anyone who can commit can change the infrastructure. Yes. >>Yes. So the tooling that you have for your GIT repo and the authentication, authorization and permissions that you apply to the GIT repo using a get server like GIT hub or get lab or whatever your flavor of the day is is going to be how security is handled with respect to changes in your get ups configuration repository. So um that is completely specific to your implementation of that or ones implementation of of how they're handling that. Get repositories that the get ups tooling is looking at. To reconcile changes with respect to the permissions of the for lack of better term robot itself. Right? They get up tooling like flux or Argosy. D Um one kid would would create a user or a service account or uh other kind of authentication measures to limit the permissions for that service account that the Gaddafi's tooling needs to be able to read the repose and and send commits etcetera. So that is well within the realm of what you have already for your for your get your get um repo. Yeah. >>Yeah. A related question is from a g what they like about get apps if done nicely for a newbie it's you can get stuff done easily if you what they dislike about it is when you have too many get repose it becomes just too complicated and I agree. Um was making a joke with a team the other week that you know the developer used to just make one commit and they would pass pass it on to a QA team that would then eventually emerging in the master. But they made the commits to these feature branches or whatever. But now they make a commit, they make a pR there for their code then they go make a PR in the helm chart to update the thing to do that and then they go make a PR in the get ups repeal for Argo. And so we talked about that they're probably like four or five P. R. Is just to get their code in the production. But we were talking about the negative of that but the reality was It's just five or 4 or five prs like it wasn't five different systems that had five different methodologies and tooling and that. So I looked at it I was like well yeah that's kind of a pain in the get sense but you're also dealing with one type. It's a repetitive action but it's it's the one thing I don't have to go to five different systems with five different ways of doing it. And once in the web and one's on the client wants a command line that I don't remember. Um Yeah so it's got pros and cons I think when you >>I think when you get to the scale where those kind of issues are a problem then you're probably at the scale where you can afford to invest some time into automation into that. Right? Like what I've when I've seen this in larger customers or larger organizations if there ever at that stage where okay apps are coming up all the time. You know, there's a 10 X 100 X developer to operations folks who may be creating get repose setting up permissions then that stuff gets automated, right? Like, you know, maybe ticket based systems or whatever. Developers say I need a new app. It templates things or more often using the same model, right of reconciliation and operators and the horrific abuse of cogs that we're seeing in the communities community right now. Um You know, developers can create a crd which just says, hey, I'm creating a new app is called app A and then a controller will pick up that app a definition. It will go create a get a repo Programmatically it will add the right definitely will look up and held up the developers and the permissions that need to be able to get to that repo it will create and template automatically some name space and the clusters that it needs in the environments that it needs, depending on, you know, some metadata it might read. So I think, you know, those are definite problems and they're definitely like a teething, growing pain thing. But once you get to that scale, you kind of need to step back and say, well look, we just need to invest in time into the operational aspect of this and automating this pain away, I think. Yeah, >>yeah. And that ultimately ends in Yeah. Custom tooling, which it's hard to avoid it at scale. I mean, there's there's two, there's almost two conversations here, right. There is what I call the Solo admin Solo devops, I bought that domain Solo devops dot com because, you know, whenever I'm talking to dr khan in the real world, it's like I asked people to raise hands, I don't know how we can raise hands here, but I would ask people to raise hands and see how many of you here are. The sole person responsible for deploying the app that your team makes and like a quarter of the room would raise their hand. So I call that solo devops like those, that person can't make all the custom tooling in the world. So they really need dr like solutions where it's opinionated, the workflow is sort of built in and they don't have to wrangle things together with a bunch of glue, you know, in other words bash. Um and so this kind of comes to a conversation uh starting this question from lee he's asking how do you combine get ops with ci cd, especially the continuous bit. How do you avoid having a human uh sort of the complaint the team I was working with has, how do you avoid a human editing and get committing for every single deploy? They've settled on customized templates and a script for routine updates. So as a seed for this conference, this question I'm gonna ask you all uh instead of that specific question cause it's a little open ended. Um Tell me whether you agree with this. I I kind of look at the image, the image artifact because the doctor image or container image in general is an artifact that I I view it that way and that thing going into the registry with the right label or right part of the label. Um That tag rather not the label but the tag that to me is like one of the great demarche points of, we're kind of done with Ci and we're now into the deployment phase and it doesn't necessarily mean the tooling is a clear cut there, but that artifact being shipped in a specific way or promoted as we sometimes say. Um what do you think? Does anyone have opinions on that? I don't even know if that's the right opinion to have so mhm. >>So um I think what you're, what you're getting at is that get ups, models can trigger off of different events um to trigger the reconciliation loop. And one way to do that is if the image, if it notices a image change in the registry, the other is if there's a commit event on a specific rebo and branch and it's up to, you are up to the person that's implementing their get ups model, what event to trigger there, that reconciliation loop off of, You can do both, you can do one or the other. It also depends on the Templeton engine that you're using on top of um on top of kubernetes, such as helm or um you know, the other ones that are out there or if you're not even doing that, then, you know straight. Yeah, mo um so it kind of just depends, but those are the typically the two options one has and a combination of of those to trigger that event. You can also just trigger it manually, right? You can go into the command line and force a a, you know, a really like a scan or a new reconciliation loop to occur. So it kind of just, I don't want to say this, but it depends on what you're trying to do and what makes sense in your pipeline. Right? So if you're if you're set up where you are tag, if you're doing it based off of image tags, then you probably want to use get ups in a way that you're using the image tags. Right. And the pattern that you've established there, if you're not really doing that and you're more around, like, different branches are mapped to different environments, then triggered off of the correct branch. And that's where the permissions also come into play. Where if you don't want someone to touch production and you've got your getups for your production cluster based off of like uh you know, a main branch, then whoever can push a change to that main branch has the authority to push that change to production. Right? So that's your authentication and permissions um system same for the registry itself. Right. So >>Yeah. Yeah. Sorry, anyone else have any thoughts on that? I was about to go to the next topic, >>I was going to say. I think certain tools dictate the approach, like, if you're using Argosy d it's I think I'm correct me if I'm wrong, but I think the only way to use it right now is just through image modification. Like, the manifest changes, it looks at a specific directory and anything changes then it will do its thing. And uh Synchronize the cost there with whatever's and get >>Yeah, flux has both. Yeah, and flux has both. So it it kind of depends. I think you can make our go do that too, but uh this is back to what we were saying in the beginning, uh you know, these things are changing, right? So that might be what it is right now in terms of triggering the reconciliation loops and get ups, tooling, but there might be other events in the future that might trigger it, and it's not completely stand alone because you still need you're tooling to do any kind of testing or whatever you have in terms of like the specific pipeline. So oftentimes you're bolting in getups into some other part of broader Cfd solution. That makes sense. Yeah, >>we've got a lot of questions about secrets or people that are asking about secrets. >>So my my tongue and cheek answered the secrets question was, what's the best practices for kubernetes? Secrets? That's the same thing for secrets with good apps? Uh getups is not last time I checked and last time I was running this stuff get ups is not has nothing to do with secrets in that sense. It's just there to get your stuff running on communities. So, um there's probably a really good session on secrets at dr concept. I >>would agree with you, I agree with you. Yeah, I mean, get off stools, I mean every every project of mine handles secrets differently. Uh huh. And I think I'm not sure if it was even when I was talking to but talking to someone recently that I'm very bullish on get up actions, I love get up actions, it's not great for deployments yet, but we do have this new thing and get hub environments, I think it's called. So it allows me at least the store secrets per environment, which it didn't have the concept of that before, which you know, if you if any of you running kubernetes out there, you typically end up when you start running kubernetes, you end up with more than one kubernetes, like you're going to end up with a lot of clusters at some point, at least many multiple, more than two. Um and so if you're trying to store secret somewhere, you do have and there's a discussion happening in chat right now where people are talking about um sealed secrets which if you haven't heard of that, go look that up and just be versed on what sealed secrets is because it's a it's a fantastic concept for how to store secrets in the public. Um I love it because I'm a big P. K. I nerd but um it's not the only way and it doesn't fit all models. So I have clients that use A W. S. Secrets because they're in A W. S. And then they just have to use the kubernetes external secret. But again like like like normal sand, you know, it's that doesn't really affect get ops, get ops is just applying whatever helm charts or jahmal or images that you're, you're you're deploying, get off. It was more about the approach of when the changes happen and whether it's a push or pull model like we're talking about and you know, >>I would say there's a bunch of prerequisites to get ups secrets being one of them because the risk of you putting a secret into your git repo if you haven't figured out your community secrets architecture and start diving into getups is high and removing secrets from get repose is you know, could be its own industry, right. It's >>a thing, >>how do >>I hide this? How do I obscure this commit that's already now on a dozen machines. >>So there are some prerequisites in terms of when you're ready to adopt get up. So I think is the right way of saying the answer to that secrets being one of them. >>I think the secrets was the thing that made me, you know, like two or three years ago made me kind of see the ah ha moment when it came to get ups which, which was that the premier thing that everyone used to say about get up about why it was great. Was its the single source of truth. There's no state anywhere else. You just need to look at git. Um and then secrets may be realized along with a bunch of other things down the line that is not true and will never be true. So as soon as you can lose the dogmatism about everything is going to be and get it's fantastic. As long as you've understood everything is not going to get. There are things which will absolutely never be and get some tools just don't deal with that. They need to earn their own state, especially in communities, some controls on their own state. You know, cuz sealed secrets and and other projects like SOps and I think there are two or three others. That's a great way of dealing with secrets if you want to keep them in get. But you know, projects like vault more kind of like what I would say, production grade secret strategies. Right? And if you're in AWS or a cloud, you're more likely to be using their secrets. Your secret policy is maybe not dictated by you in large organizations might be dictated by CSO or security or Great. Like I think once if you, if you're trying to adopt getups or you're thinking about it, get the dogmatism of get as a single point of truth out of your mind and think about getups more as a philosophy and a set of best practice principles, then you will be in much better stead, >>right? Yeah. >>People are asking more questions in chat like infrastructure as code plus C d essentially get ups or C I rather, um, these are all great questions and a part of the debate, I'm actually just going to throw up on screen. I'm gonna put this in chat, but this is, this is to me the source, Right? So we worked with when they coined the term. We, a lot of us have been trying to get, if we talk about the history for a minute and then tell me if I'm getting this right. Um, a lot of us were trying to automate all these different parts of the puzzle, but a lot of them, they, some things might have been infrastructure as code. Some things weren't, some things were sort of like settings is coded, like you're going to Jenkins and type in secrets and settings or type in a certain thing in the settings of Jenkins and then that it wasn't really in get and so what we was trying to go for was a way to have almost like eventually a two way state understanding where get might change your infrastructure but then your infrastructure might also change and needs to be reflected in the get if the get is trying to be the single source of truth. Um and like you're saying the reality is that you're never gonna have one repo that has all of your infrastructure in it, like you would have to have, you have to have all your terra form, anything else you're spinning up. Right. Um but anyway, I'm gonna put this link in chat. So this guide actually, uh one of things they talk about is what it's not, so it's, it's kind of great to read through the different requirements and like what I was saying well ago um mhm. Having having ci having infrastructure as code and then trying a little bit of continuous deployment out, it's probably a prerequisite. Forget ops so it's hard to just jump into that when you don't already have infrastructure as code because a machine doing stuff on your behalf, it means that you have to have things documented and somewhere and get repo but let me put this in the in the >>chitty chat, I would like to know if the other panelists agree, but I think get apps is a okay. I would say it's a moderate level, it's not a beginner level communities thing, it's like a moderate level advanced, a little bit more advanced level. Um One can start off using it but you definitely have to have some pre recs in place or some understanding of like a pattern in place. Um So what do the other folks think about that opinion? >>I think if you're if you're trying to use get out before, you know what problem you have, you're probably gonna be in trouble. Right. It's like having a solution to it probably don't have yet. Mhm. Right. I mean if if you're just evil or and you're just typing, keep control apply, you're one person right, Get off. It doesn't seem like a big a big jump, like, I mean it doesn't like why would I do that? I'm just, I'm just gonna inside, it's the type of get commit right, I'm typing Q control apply. But I think one of the rules from we've is none of your developers and none of your admins can have cute control access to the cluster because if you can't, if you do have access and you can just apply something, then that's just infrastructure as code. That's just continuous deployment, that's, that's not really get ops um, getups implies that the only way things get into the cluster is through the get up, get automation that you're using with, you know, flux Argo, we haven't talked about, what's the other one that Victor Farsi talks about, by the way people are asking about victor, because victor would love to talk about this stuff, but he's in my next life, so come back in an hour and a half or whatever and victor is going to be talking about sys, admin list with me. Um >>you gotta ask him nothing but get up questions in the next, >>confuse them, confuse them. But anyway, that, that, that's um, it's hard, it's hard to understand and without having tried it, I think conceptually it's a little challenging >>one thing with getups, especially based off the we've works blog post that you just put up on there. It's an opinionated way of doing something. Uh you know, it's an opinionated way of of delivering changes to an environment to your kubernetes environment. So it's opinionated were often not used to seeing things that are very opinionated in this sense, in the in the ecosystem, but get apps is a opinionated thing. It's it's one way of doing it. Um there are ways to change it and like there are options um like what we were talking about in terms of the events that trigger, but the way that it's structured is an opinion opinionated way both from like a tooling perspective, like using get etcetera, but also from a devops cultural perspective, right? Like you were talking about not having anyone access cube control and changing the cluster directly. That's a philosophical opinion that get ups forces you to adopt otherwise. It kind of breaks the model and um I just I want everyone to just understand that. That is very opinion, anything in that sense. Yeah, >>polygamy is another thing. Infrastructure as code. Um someone's mentioning plummy and chat, I just had actually my life show self plug bread that live go there. I'm on Youtube every week. I did the same thing. These these are my friends um and had palami on two weeks ago uh last week, remember uh and it was in the last couple of weeks and we talked about their infrastructure as code solution. Were actually writing code instead of um oh that's an interesting take on uh developer team sort of owning coding the infrastructure through code rather than Yamil as a data language. I don't really have an opinion on it yet because I haven't used it in production or anything in the real real world, but um, I'm not sure how much they are applying trying to go towards the get up stuff. I will do a plug for Solomon hikes. Who has a, the beginning of the day, it's already happened so you can go back and watch it. It's a, it's a, what's it called? Q. Rethinking application delivery with Q. And build kit. So go look this up. This is the found co founder of Dr and former CTO Solomon hikes at the beginning of the day. He has a tool called dagger. I'm not sure why the title of the talk is delivering with Q. And built it, but the tool is showing off in there for an hour is called dagger. And it's, it's an interesting idea on how to apply a lot of this opinionated automated stuff to uh, to deployment and it's get off space and you use Q language. It's a graph language. I watched most of it and it was a really interesting take. I'm excited to see if that takes off and if they try that because it's another way that you can get a little bit more advanced with your you're get deployments and without having to just stick everything in Yemen, which is kind of what we're in today with helm charts and what not. All right. More questions about secrets, I think. I think we're not going to have a whole lot of more, a lot more about secrets basically. Uh put secrets in your cluster to start with and kubernetes in encrypted, you know, thing. And then, you know, as it gets harder, then you have to find another solution when you have five clusters, you don't wanna have to do it five times. That's when you have to go for Walton A W. S secrets and all >>that. Right? I'm gonna post it note. Yeah. Crm into the cluster. Just kidding. >>Yes, there are recordings of this. Yes, they will be later. Uh, because we're that these are all gonna be on youtube later. Um, yeah, detects secrets cushion saying detect secrets or get Guardian are absolute requirements. I think it's in reference to your secrets comment earlier. Um, Camels asking about Cuban is dropping support for Docker that this is not the place to ask for that, but it, it is uh, basically it's a Nonevent Marantz has actually just created that same plug in available in a different repos. So if you want to keep using Docker and kubernetes, you know, you can do it like it's no big deal. Most of us aren't using doctor in our communities anyway, so we're using like container D or whatever is provided to us by our provider. Um yeah, thank you so much for all these comments. These are great people helping each other and chat. I feel like we're just here to make sure the chats available so people can help each other. >>I feel like I want to pick up on something when you mentioned pollux me, I think there's a um we're talking about getups but I think in the original like the origination of that I guess was deploying applications to clusters right, picking up deployment manifest. But I think with the gloomy and I obviously terra form and things have been around a long time, folks are starting to apply this I think I found one earlier which was like um kub stack the Terror Forms get ups framework. Um but also with the advent of things like cluster A. P. I. Um in the Cuban at the space where you can declare actively build the infrastructure for your clusters and build the cluster right? We're not just talking about deploying applications, the cluster A. P. I will talk to a W. S. Spin up, VPc spin up machines, you know, we'll do the same kind of things that terra form does and and those other tools do I think applying getups principles to the infrastructure spin up right, the proper infrastructure as code stuff, constantly applying Terror form um you know, plans and whatever, constantly applying cluster Api resources spinning up stuff in those clouds. That's a super interesting. Um you know, extension of this area, I'd be curious to see if what the folks think about that. >>Yeah, that's why I picked this topic is one of my three. Uh I got I got to pick the topics. I was like the three things that there like the most bleeding edge exciting. Most people haven't, we haven't basically we haven't figured all this out yet. We as an industry, so um it's I think we're gonna see more ideas on it. Um what's the one with the popsicle as the as the icon victor talks about all the time? It's not it's another getups like tool, but it's um it's getups for you use this kubernetes limit and then we have to look it up, >>You're talking about cross plane. >>So >>my >>wife is over here with the sound effects and the first sound effect of the day that she chooses to use is one. >>All right, can we pick it? Let's let's find another question bret >>I'm searching >>so many of them. All right, so uh I think one really quick one is getups only for kubernetes, I think the main to tooling to tools that we're talking about, our Argosy D and flux and they're mostly geared toward kubernetes deployments but there's a, it seems like they're organized in a way that there's a clean abstraction in with respect to the agent that's doing the deployment and the tooling that that can interact with. So I would imagine that in the future and this might be true already right now that get ups could be applied to other types of deployments at some point in the future. But right now it's mostly focused and treats kubernetes as a first class citizen or the tooling on top of kubernetes, let's say something like how as a first class citizen? Yeah, to Brett, >>to me the field, back to you bret the thing I was looking for is cross plane. So that's another tool. Um Victor has been uh sharing a lot about it in Youtube cross plane and that is basically runs inside a kubernetes, but it handles your other infrastructure besides your app. It allows you to like get ops, you're a W. S stuff by using the kubernetes state engine as a, as a way to manage that. And I have not used it yet, but he does some really great demos on Youtube. So people are liking this idea of get off, so they're trying to figure out how do we, how do we manage state? How do we uh because the probably terra form is that, well, there's many problems, but it's always a lot of problems, but in the get outs world it's not quite the right fit yet, It might be, but you still, it's still largely as expected for people to, you know, like type the command, um, and it keeps state locally the ss, clouds and all that. And but the other thing is I'm I'm now realizing that when I saw the demo from Solomon, I'm going back to the Solomon hikes thing. He was using the demo and he was showing it apply deploying something on S three buckets, employing internet wifi and deploying it on google other things beyond kubernetes and saying that it's all getups approach. So I think we're just at the very beginning of seeing because it all started with kubernetes and now there's a swarm one, you can look up swarm, get office and there's a swarm, I can't take the name of it. Swarm sink I think is what's called swarm sink on git hub, which allows you to do swarm based getups like things. And now we're seeing these other tools coming out. They're saying we're going to try to do the get ups concepts, but not for kubernetes specifically and that's I think, you know, infrastructure as code started with certain areas of the world and then now then now we all just assume that you're going to have an infrastructure as code way of doing whatever that is and I think get off is going to have that same approach where pretty soon, you know, we'll have get apps for all the clouds stuff and it won't just be flexor Argo. And then that's the weird thing is will flex and Argo support all those things or will it just be focused on kubernetes apps? You know, community stuff? >>There's also, I think this is what you're alluding to. There is a trend of using um kubernetes and see rDS to provision and control things that are outside of communities like the cloud service providers services as if they were first class entities within kubernetes so that you can use the kubernetes um focus tooling for things that are not communities through the kubernetes interface communities. Yeah, >>yeah, even criticism. >>Yeah, yeah, I'm just going to say that sounds like cross plane. >>Yeah, yeah, I mean, I think that's that's uh there were, you know, for the last couple of years, it's been flux and are going back and forth. Um they're like frenemies, you know, and they've been going back and forth with iterating on these ideas of how do we manage this complicated thing? That is many kubernetes clusters? Um because like Argo, I don't know if the flux V two can do this, but Argo can manage multiple clusters now from one cluster, so your, you can manage other clusters, technically external things from a single entity. Um Originally flux couldn't do that, but I'm going to say that V two can, I don't actually >>know. Um I think all that is gonna, I think that's going to consolidate in the future. All right. In terms of like the common feature set, what Iver and john what do you think? >>I mean, I think it's already begun, right, I think haven't, didn't they collaborate on a common engine? I don't know whether it's finished yet, but I think they're working towards a common getups engine and then they're just going to layer on features on top. But I think, I mean, I think that's interesting, right, because where it runs and where it interacts with, if we're talking about a pull based model, it shouldn't, it's decentralized to a certain extent, right? We need get and we need the agent which is pulling if we're saying there's something else which is orchestrating something that we start to like fuzzy the model even right. Like is this state living somewhere else, then I think that's just interesting as well. I thought flux was completely decentralized, but I know you install our go somewhere like the cargo has a server as well, but it's been a while since I've looked in depth at them. But I think the, you know, does that muddy the agent only pull model? >>I'm reading a >>Yeah, I would say that there's like a process of natural selection going on as as the C. N. C. F. Landscape evolves and grows bigger and a lot of divide and conquer right now. But I think as certain things kind of get more prominent >>and popular, I think >>it starts to trend and it inspires other things and then it starts to aggregate and you know, kind of get back into like a unified kind of like core. Maybe like for instance, cross plane, I feel like it shouldn't even really exist. It should be, it like it's a communities add on, but it should be built in, it should be built into kubernetes, like why doesn't this exist already >>for like controlling a cloud? >>Yeah, like just, you know, having this interface with the cloud provider and be able to Yeah, >>exactly. Yeah, and it kinda, you're right. That kinda happens because you do, I mean when you start talking about storage providers and networking providers was very specific implementations of operators or just individual controllers that do operate and control other resources in the cloud, but certainly not universally right. Not every feature of AWS is available to kubernetes out of the box. Um and you know, it, one of the challenges across plane is you gotta have kubernetes before you can deploy kubernetes. Like there's a chicken and egg issue there where if you're going to use, if you're going to use our cross plane for your other infrastructure, but it's gotta, but it has to run on kubernetes who creates that first kubernetes in order for you to put that on there. And victor talks about one of his videos, the same problem with flux and Argo where like Argo, you can't deploy Argo itself with getups. There has to be that initial, I did a thing with, I'm a human and I typed in some commands on a server and things happened but they don't really have an easy deployment method for getting our go up and running using simply nothing but a get push to an existing system. There's something like that. So it's a it's an interesting problem of day one infrastructure which is again only day one, I think data is way more interesting and hard, but um how can we spend these things up if they're all depending on each other and who is the first one to get started? >>I mean it's true of everything though, I mean at the end of that you need some kind of big bang kind of function too, you know, I started running start everything I >>think without going over that, sorry, without going off on a tangent. I was, I was gonna say there's a, if folks have heard of kind which is kubernetes and Docker, which is a mini kubernetes cluster, you can run in a Docker container or each container will run as a as a node. Um you know, that's been a really good way to spin up things like clusters. KPI because they boot strap a local kind, install the manifests, it will go and spin up a fully sized cluster, it will transfer its resources over there and then it will die itself. Right? So that, that's kind of bootstrapping itself. And I think a couple of folks in the community, Jason to Tiberius, I think he works for Quinyx metal um has, has experimented with like an even more minimal just Api server, so we're really just leveraging the kubernetes ideas of like a reconciliation loop and a controller. We just need something to bootstrap with those C R D s and get something going and then go away again. So I think that's gonna be a pattern that comes up kind of more and more >>Yeah, for sure. Um, and uh, the next, next quick answer to the question, Angel asked what your thoughts on getups being a niche to get or versus others vcs tools? Well, if I knew anyone who is using anything other than get, I would say no, you know, get ops is a horrible name. It should just be CVS office, but that doesn't or vcs ops or whatever like that, but that doesn't roll off the tongue. So someone had to come up with the get ups phrase. Um but absolutely, it's all about version control solutions used for infrastructure, not code. Um might get doctor asks a great question, we're not gonna have time for it, but maybe people can reply and chat with what they think but about infrastructure and code, the lines being blurred and that do develop, how much of infrastructure does developer do developers need to know? Essentially, they're having to know all the things. Um so unfortunately we've had way more questions like every panel here today with all the great community, we've got way more questions we can handle in this time. So we're gonna have to wrap it up and say goodbye. Go to the next live panel. I believe the next one is um on developer, developer specific setups that's gonna be peter running that panel. Something about development in containers and I'm sure it's gonna be great. Just like this one. So let's go around the room where can people find you on the internet? I'm at Brett fisher on twitter. That's where you can usually find me most days you are? >>Yeah, I'm on twitter to um, I'll put it in the chat. It's kind of confusing because the TSR seven. >>Okay. Yeah, that's right. You can't just say it. You can also look at the blow of the video and like our faces are there and if you click on them, it tells you our twitter in Arlington and stuff, john >>John Harris 85, pretty much everywhere. Get hub Twitter slack, etc. >>Yeah >>and normal, normal faults or just, you know, living on Youtube live with Brett. >>Yeah, we're all on the twitter so go check us out there and thank you so much for joining. Uh thank you so much to you all for being here. I really appreciate you taking time in your busy schedule to join me for a little chit chat. Um Yes, all the, all the cheers, yes. >>And I think this kid apps loop has been declarative lee reconciled. >>Yeah, there we go. And with that ladies and gentlemen, uh bid you would do, we will see you in the next, next round coming up next with Peter >>bye.

>>Hi, everyone. Good afternoon. Thank you for joining this session. I feel honored to be invited to speak here today. And I also appreciate entity research Summit members for organ organizing and giving this great opportunity. Please let me give a quick introduction. First, I'm a Takashi from Marvin American population, and I'm leading technology scouting and global ation with digital health companies such as Business Alliance and Strategically Investment in North America. And since we started to focus on this space in 2016 our team is growing. And in order to bring more new technologies and services to Japan market Thesis year, we founded the new service theories for digital health business, especially, uh, in medical diagnosis space in Japan. And today I would like to talk how health care has been transformed for my micro perspective, and I hope you enjoy reasoning it. So what's happened since the US identify the first case in the middle of January, As everyone knows, unfortunately, is the damaged by this pandemic was unequal amongst the people in us. It had more determined tal impact on those who are socially and economically vulnerable because of the long, long lasting structural program off the U. S. Society and the Light Charity about daily case rating elevator country shows. Even in the community, the infection rate off the low income were 4.5 times higher than, uh, those of the high income and due to czar straight off the Corvette, about 14 million people are unemployed. The unique point off the U. S. Is that more than 60% of insurance is tied with employment, so losing a job can mean losing access to health care. And the point point here is that the Corvette did not create healthcare disparity but, uh nearly highlighted the underlying program and necessity off affordable care for all. And when the country had a need to increase the testing capacity and geographic out, treat the pharmacies and retails joined forces with existing stakeholders more than 90% off the U. S Corporation live within five miles off a community pharmacy such as CVS and Walgreen, so they can technically provide the test to everyone in all the community. And they also have a huge workforce memory pharmacist who are eligible to perform the testing scale, and this very made their potential in community based health care. Stand out and about your health has provided on alternative way for people to access to health care. At affordable applies under the unusual setting where social distancing, which required required mhm and people have a fear of infection. So they are afraid to take a public transportacion and visit >>the doctor the same thing supplied to doctor and the chart. Here is a number of total visit cranes by service type after stay at home order was issued across the U. S. By Ali April patient physical visits to doctor's offices or clinics declined by ALAN 70%. On the other hand, that share, or telehealth, accounted for 25% of the total total. Doctor's visit in April, while many states studied to re opening face to face visit is gradually recovering. And overall Tele Health Service did not offset the crime. Physician Physical doctor's visit and telehealth John never fully replace in person care. However, Telehealth has established a new way to provide affordable care, especially to vulnerable people, and I don't explain each player's today. But as an example, the chart shows the significant growth of the tell a dog who is one of the largest badger care and tell his provider, I believe there are three factors off paradox. Success under the pandemic. First, obviously tell Doc could reach >>the job between those patients and doctors. Majority of the patients who needed to see doctors who are those who have underlying health conditions and are high risk for Kelowna, Bilis and Secondary. They showed their business model is highly scalable. In the first quarter of this year, they moved quickly to expand their physical physicians network to increase their capacity and catch up growing demand. To some extent, they also contributed to create flexible job for the doctors who suffered from Lydia's appointment and surgery. They utilized. There are legalism to maximize the efficiency for doctors and doing so, uh, they have university maintained high quality care at affordable applies Yeah, and at the same time, the government recognize the body of about your care and de regulated traditional rules to sum up she m s temporary automated to pay a wide range of tell Her services, including hospital visit and HHS temporarily waived hip hop minorities for telehealth cases and they're changed allowed provider to use communication tools such as facetime and the messenger. During their appointment on August start, the government issued a new executive order to expand tell his services beyond the pandemic. So the government is also moving to support about your health care. So it was a quick review of the health care challenges and somewhat advancement in the pandemic. But as you understand, since those challenges are not caused by the pandemic, problems will stay remain and events off this year will continuously catalyze the transformation. So how was his cherished reshaped and where will we go? The topic from here can be also applied to Japan market. Okay, I believe democratization and decentralization healthcare more important than ever. So what does A. The traditional healthcare was defined in a framework over patient and a doctor. But in the new normal, the range of beneficiaries will be expanded from patient to all citizens, including the country uninsured people. Thanks to the technology evolution, as you can download health management off for free on iTunes stores while the range of the digital health services unable everyone to participate in new health system system. And in this slide, I put three essential element to fully realize democratization and decentralization off health care, health, literacy, data sharing and security, privacy and safety in addition, taken. In addition, technology is put at the bottom as a foundation off three point first. Health stimulus is obviously important because if people don't understand how the system works, what options are available to them or what are the pros and cons of each options? They can not navigate themselves and utilize the service. It can even cause a different disparity. Issue and secondary data must be technically flee to transfer. While it keeps interoperability ease. More options are becoming available to patient. But if data cannot be shared among stakeholders, including patient hospitals in strollers and budget your providers, patient data will be fragmented and people cannot yet continue to care which they benefited under current centralized care system. And this is most challenging part. But the last one is that the security aspect more players will involving decentralized health care outside of conventional healthcare system. So obviously, both the number of healthcare channels and our frequency of data sharing will increase more. It's create ah, higher data about no beauty, and so, under the new health care framework, we needed to ensure patient privacy and safety and also re examine a Scott write lines for sharing patient data and off course. Corbett Wasa Stone Catalyst off this you saved. But what folly. Our drivers in Macro and Micro Perspective from Mark Lowe. The challenges in healthcare system have been widely recognized for decades, and now he's a big pain. The pandemic reminded us all the key values. Misha, our current pain point as I left the church shores. Those are increasing the population, health sustainability for doctors and other social system and value based care for better and more affordable care. And all the elements are co dependent on each other. The light chart explained that providing preventive care and Alan Dimension is the best way threes to meet the key values here. Similarly, the direction of community based care and about your care is in line with thes three values, and they are acting to maximize the number of beneficiaries form. A micro uh, initiative by nonconventional players is a big driver, and both CBS and Walmart are being actively engaged in healthcare healthcare businesses for many years. And CBS has the largest walking clinic called MinuteClinic, Ottawa 1100 locations, and Walmart also has 20 primary clinics. I didn't talk to them. But the most interesting things off their recent innovation, I believe, is that they are adjusted and expanded their focus, from primary care to community health Center to out less to every every customer's needs. And CBS Front to provide affordable preventive health and chronic health monitoring services at 1500 CBS Health have, which they are now setting up and along a similar line would Mark is deploying Walmart Health Center, where, utilizing tech driven solutions, they provide affordable one stop service for core healthcare. They got less, uh, insurance status. For example, more than 40% of the people in U. S visit will not every big, so liberating the huge customer base and physical locations. Both companies being reading decentralization off health care and consumer device company such as Apple and Fitbit also have helped in transform forming healthcare in two ways. First, they are growing the boundaries between traditional healthcare and consumer product after their long development airport available, getting healthcare device and secondary. They acted as the best healthcare educators to consumers and increase people's healthcare awareness because they're taking an important role in the enhancement, health, literacy and healthcare democratization. And based on the story so far, I'd like to touch to business concept which can be applied to both Japan and the US and one expected change. It will be the emergence of data integration plot home while the telehealth. While the healthcare data data volume has increased 15 times for the last seven years and will continuously increase, we have a chance to improve the health care by harnessing the data. So meaning the new system, which unify the each patient data from multiple data sources and create 360 degrees longitudinal view each individual and then it sensitized the unified data to gain additional insights seen from structure data and unable to provide personal lives care. Finally, it's aggregate each individual data and reanalyzed to provide inside for population health. This is one specific model I envision. And, uh, health care will be provided slew online or offline and at the hospital or detail store. In order to amplify the impact of health care. The law off the mediator between health care between hospital and citizen will become more important. They can be a pharmacy toe health stand out about your care providers. They provide wide range of fundamental care and medication instruction and management. They also help individuals to manage their health care data. I will not explain the details today, but Japan has similar challenges in health care, such as increasing healthcare expenditure and lack of doctors and care givers. For example, they people in Japan have physical physician visit more than 20 times a year on average, while those in the U. S. On >>the do full times it sounds a joke, but people say because the artery are healthy, say visit hospitals to see friends. So we need to utilize thes mediators to reduce cost while they maintained social place for citizens in Japan, the government has promoted, uh, usual family, pharmacist and primary doctors and views the community based medical system as a policy. There was division of dispensing fees in Japan this year to ship the core load or pharmacist to the new role as a health management service providers. And so >>I believe we will see the change in those spaces not only in the U. S, but also in Japan, and we went through so unprecedented times. But I believe it's been resulting accelerating our healthcare transformation and creating a new business innovation. And this brings me to the end of my presentation. Thank you for your attention and hope you could find something somehow useful for your business. And if you have any questions >>or comments, please for you feel free to contact me.

>>Hi, everyone. Good afternoon. Thank you for joining this session. I feel honored to be invited to speak here today. And I also appreciate entity research Summit members for organ organizing and giving this great opportunity. Please let me give a quick introduction. First, I'm a Takashi from Marvin American population, and I'm leading technology scouting and global ation with digital health companies such as Business Alliance and Strategically Investment in North America. And since we started to focus on this space in 2016 our team is growing. And in order to bring more new technologies and services to Japan market Thesis year, we founded the new service theories for digital health business, especially, uh, in medical diagnosis space in Japan. And today I would like to talk how health care has been transformed for my micro perspective, and I hope you enjoy reasoning it. So what's happened since the US identify the first case in the middle of January, As everyone knows, unfortunately, is the damaged by this pandemic was unequal amongst the people in us. It had more determined tal impact on those who are socially and economically vulnerable because of the long, long lasting structural program off the U. S. Society and the Light Charity about daily case rating elevator country shows. Even in the community, the infection rate off the low income were 4.5 times higher than, uh, those of the high income and due to czar straight off the Corvette, about 14 million people are unemployed. The unique point off the U. S. Is that more than 60% of insurance is tied with employment, so losing a job can mean losing access to health care. And the point point here is that the Corvette did not create healthcare disparity but, uh nearly highlighted the underlying program and necessity off affordable care for all. And when the country had a need to increase the testing capacity and geographic out, treat the pharmacies and retails joined forces with existing stakeholders more than 90% off the U. S Corporation live within five miles off a community pharmacy such as CVS and Walgreen, so they can technically provide the test to everyone in all the community. And they also have a huge workforce memory pharmacist who are eligible to perform the testing scale, and this very made their potential in community based health care. Stand out and about your health has provided on alternative way for people to access to health care. At affordable applies under the unusual setting where social distancing, which required required mhm and people have a fear of infection. So they are afraid to take a public transportacion and visit >>the doctor the same thing supplied to doctor and the chart. Here is a number of total visit cranes by service type after stay at home order was issued across the U. S. By Ali April patient physical visits to doctor's offices or clinics declined by ALAN 70%. On the other hand, that share, or telehealth, accounted for 25% of the total total. Doctor's >>visit in April, while many states studied to re opening face to face visit is gradually recovering. And overall Tele Health Service did not offset the crime. Physician Physical doctor's visit and telehealth John never fully replace in person care. However, Telehealth has established a new way to provide affordable care, especially to vulnerable people, and I don't explain each player's today. But as an example, the chart shows the significant growth of >>the tell a dog who is one of the largest badger care and tell his provider, I believe there are three factors off paradox. Success under the pandemic. First, obviously tell Doc could reach >>the job between those patients and doctors. Majority of the patients who needed to see doctors who are those who have underlying health conditions and are high risk for Kelowna, Bilis and Secondary. They showed their business model is highly scalable. In the first quarter of this year, they moved quickly to expand their physical physicians network to increase their capacity and catch up growing demand. To some extent, they also contributed to create flexible job for the doctors who suffered from Lydia's appointment and surgery. They utilized. There are legalism to maximize the efficiency for doctors and doing so, uh, they have university maintained high quality care at affordable applies Yeah, and at the same time, the government recognize the body of about your care and de regulated traditional rules to sum up she m s temporary automated to pay a wide range of tell Her services, including hospital visit and HHS temporarily waived hip hop minorities for telehealth cases and they're changed allowed provider to use communication tools such as facetime and the messenger. During their appointment on August start, the government issued a new executive order to expand tell his services beyond the pandemic. So the government is also moving to support about your health care. So it was a quick review of the health care challenges and somewhat advancement in the pandemic. But as you understand, since those challenges are not caused by the pandemic, problems will stay remain and events off this year will continuously catalyze the transformation. So how was his cherished reshaped and where will we go? The topic from here can be also applied to Japan market. Okay, I believe democratization and decentralization healthcare more important than ever. So what does A. The traditional healthcare was defined in a framework over patient and a doctor. But in the new normal, the range of beneficiaries will be expanded from patient to all citizens, including the country uninsured people. Thanks to the technology evolution, as you can download health management off for free on iTunes stores while the range of the digital health services unable everyone to participate in new health system system. And in this slide, I put three essential element to fully realize democratization and decentralization off health care, health, literacy, data sharing and security, privacy and safety in addition, taken. In addition, technology is put at the bottom as a foundation off three point first. Health stimulus is obviously important because if people don't understand how the system works, what options are available to them or what are the pros and cons of each options? They can not navigate themselves and utilize the service. It can even cause a different disparity. Issue and secondary data must be technically flee to transfer. While it keeps interoperability ease. More options are becoming available to patient. But if data cannot be shared among stakeholders, including patient hospitals in strollers and budget your providers, patient data will be fragmented and people cannot yet continue to care which they benefited under current centralized care system. And this is most challenging part. But the last one is that the security aspect more players will involving decentralized health care outside of conventional healthcare system. So obviously, both the number of healthcare channels and our frequency of data sharing will increase more. It's create ah, higher data about no beauty, and so, under the new health care framework, we needed to ensure patient privacy and safety and also re examine a Scott write lines for sharing patient data and off course. Corbett Wasa Stone Catalyst off this you saved. But what folly. Our drivers in Macro and Micro Perspective from Mark Lowe. The challenges in healthcare system have been widely recognized for decades, and now he's a big pain. The pandemic reminded us all the key values. Misha, our current pain point as I left the church shores. Those are increasing the population, health sustainability for doctors and other social system and value based care for better and more affordable care. And all the elements are co dependent on each other. The light chart explained that providing preventive care and Alan Dimension is the best way threes to meet the key values here. Similarly, the direction of community based care and about your care is in line with thes three values, and they are acting to maximize the number of beneficiaries form. A micro uh, initiative by nonconventional players is a big driver, and both CBS and Walmart are being actively engaged in healthcare healthcare businesses for many years. And CBS has the largest walking clinic called MinuteClinic, Ottawa 1100 locations, and Walmart also has 20 primary clinics. I didn't talk to them. But the most interesting things off their recent innovation, I believe, is that they are adjusted and expanded their focus, from primary care to community health Center to out less to every every customer's needs. And CBS Front to provide affordable preventive health and chronic health monitoring services at 1500 CBS Health have, which they are now setting up and along a similar line would Mark is deploying Walmart Health Center, where, utilizing tech driven solutions, they provide affordable one stop service for core healthcare. They got less, uh, insurance status. For example, more than 40% of the people in U. S visit will not every big, so liberating the huge customer base and physical locations. Both companies being reading decentralization off health care and consumer device company such as Apple and Fitbit also have helped in transform forming healthcare in two ways. First, they are growing the boundaries between traditional healthcare and consumer product after their long development airport available, getting healthcare device and secondary. They acted as the best healthcare educators to consumers and increase people's healthcare awareness because they're taking an important role in the enhancement, health, literacy and healthcare democratization. And based on the story so far, I'd like to touch to business concept which can be applied to both Japan and the US and one expected change. It will be the emergence of data integration plot home while the telehealth. While the healthcare data data volume has increased 15 times for the last seven years and will continuously increase, we have a chance to improve the health care by harnessing the data. So meaning the new system, which unify the each patient data from multiple data sources and create 360 degrees longitudinal view each individual and then it sensitized the unified data to gain additional insights seen from structure data and unable to provide personal lives care. Finally, it's aggregate each individual data and reanalyzed to provide inside for population health. This is one specific model I envision. And, uh, health care will be provided slew online or offline and at the hospital or detail store. In order to amplify the impact of health care. The law off the mediator between health care between hospital and citizen will become more important. They can be a pharmacy toe health stand out about your care providers. They provide wide range of fundamental care and medication instruction and management. They also help individuals to manage their health care data. I will not explain the details today, but Japan has similar challenges in health care, such as increasing healthcare expenditure and lack of doctors and care givers. For example, they people in Japan have physical physician visit more than 20 times a year on average, while those in the U. S. On the do full times it sounds a joke, but people say because the artery are healthy, say visit hospitals to see friends. So we need to utilize thes mediators to reduce cost while they maintained social place for citizens in Japan, the government has promoted, uh, usual family, pharmacist and primary doctors and views the community based medical system as a policy. There was division of dispensing fees in Japan this year to ship the core load or pharmacist to the new role as a health management service providers. And so I believe we will see the change in those spaces not only in the U. S, but also in Japan, and we went through so unprecedented times. But I believe it's been resulting accelerating our healthcare transformation and creating a new business innovation. And this brings me to the end of my presentation. Thank you for your attention and hope you could find something somehow useful for your business. And if you have any questions >>or comments, please for you feel free to contact me. Thank you.

(lively music) >> Narrator: From San Francisco, it's theCUBE. Covering GitLab Commit 2020. Brought to you by GitLab. >> Hi, I'm Stu Miniman. And this is the theCUBE's exclusive coverage of GitLab Commit 2020, here in San Francisco. You might notice it's a little chilly in San Francisco today. Welcome to the program, first time against Vince Stammegna who is the senior director of engineering at Axway and you can tell by the GitLab Commit jacket that he's a speaker at the show and good thing to wear that one today, yes, Vince? >> Yes, it's very very chilly here. But we're all having a great time. >> Yeah, absolutely. It's the warmth of the community that that's keeping everyone going. First of all, I believe it's first time we have Axway on our program, so people that don't know, tell us a little bit about Axway. >> Sure, Axway is in the business of helping save your company, basically, and help them through the digital transformation. So if you've ever deposited a check electronically on your phone, you've probably, there's a 90% chance you've crossed one of our API gateways or Managed File Transfer systems. So we've helped banks, we've helped hospitals, healthcare, lots of verticals and assisting them through their digital transformation. >> Awesome, so yeah, we love talking about digital transformation. Your presentation here at Commit is actually about journey to cloud. So tell us a little bit about what that means, gets a little bit of you inside what you're going to be sharing with the community here. >> Sure, journey to the cloud is a program that we conceived a couple years ago. And it's all about bringing our company into the cloud native space as well as bringing our existing product line into the cloud, so it can run, it can scale, easy to deploy day to operations. So what we're going to talk about today is basically Axway's journey from, as an ISV going from quarterly and semi-annual deliveries to daily deployments, low change failure rates, fast lead time for changes, so. >> Yeah, it's wonderful things if you hear about DevOps it's all about how we can shorten those release cycles and have those continuous feedback loops. So how long have you been with Axway? >> I've been with Axway for four years now. >> Okay, so yeah, bring us inside a little bit that journey is, what are the ripple effects as you try to tighten things down and not get on the train but just ship and ship and ship. (chuckling) >> Yeah, absolutely. I can say that it's a journey that really requires vigilance. It's constant practice, continuous learning to be lean. So if I were to describe the journey, it's about contributing together, working as one team to build one platform. And that's across DevOps and security. We'll go into a bit about how we really shift, shift in security-left this year by working closely with them. We really took the time to seek to understand their needs as well as the security team understanding our needs in terms of continuous deployment. And we work together on a solution called the Continuous Security Review, allows us to get to the deployment frequency of multiple times per day versus the deployment frequency before that we still followed the traditional initial security review, final security review. We could only release once a sprint, two weeks. >> Yeah, a mantra we've heard at many of the shows we go to is, "security is everyone's responsibility." Was there a lot of training that needed to be done? Did you have to, did the security people kind of lock everybody in the room and make them watch films? Or how did you work through some of these changes? >> That's a great question. So there are a lot of things that our product security group does along with our cloud security team. They do have training globally for Axway not only for the development team, operations team as well. They also, we also have built cross-functional teams within our scrum teams. So our scrum teams contain what's called a SPOC, a security point of contact, DevOps point of contact, the quality point of contact. And those members of the team help that scrum team have full ownership of that service. So when you say security is everybody's job, it's really security, quality, reliability, scalability, and stability is everybody's job. And when you build those cross-functional teams, you're able to provide the team the capability to have the ownership to take those services into the cloud on a daily basis. >> All right, Vince, help us connect the dots. Axway and GitLab, what's the connection there? >> Another great question. So we became a GitLab customer back in 2015. We were on SVN primarily and through lots of acquisitions, either CVS or SVN, and we were looking at the next generation source control management tool. We actually invested and purchased GitLab for Axway in 2015 because it had non-premise offering and we needed to store all of our source code on-premise. We have contracts with the governments around the world and so that's how our journey started. But what we couldn't have imagine was how it was going to evolve. And that's why we're so happy with GitLab. They really take our feedback seriously. A lot of things that we've asked them to go ahead and implement, they've gone and iterated and implemented those things. Allowed us to test features, get faster feedback. One of the things we were looking for was EKS recently as a native way to, basically, plug an EKS as a GitLab runner and run your workloads there. That was implemented, I think, within the last release or two releases ago. So we really appreciate GitLab's responsiveness with their product. >> Okay, yes, you're talking about Amazon's Kubernetes. >> Yes. >> Of course they're so, you talked about on-premises, what is your cloud deployment? Are you multicloud now or, what's and where does Kubernetes fit in that overall discussion? >> Another great question. So our journey to cloud native started with a product called AMPLIFY Central. And what we did was, we start out with docker swarm. We evolved to cops. At the time when we had first gotten our production deployment running on cops, EKS was just in its initial phases of rolling out. We're an Amazon Premier Technology partner. And we actually help them with their evaluation of the initial bit of EKS, give them feed back. A year later, we're looking at it as a way to consolidate platform and allow our teams to focus on building a better product rather than having infrastructure overhead of upgrading infrastructure to, and going through those cycles we can just test the infrastructure before we roll it out. >> All right, so Vince, you're talking a lot about your journey to cloud, what advice do you give to your peers as they're heading down their own journey. >> The advice I give to my peers is to keep calm (chuckles) and we'll go over that in our presentation. But really, it's about behavior change. So it's not just a words that are on some paper that you walk into and you look at. You really have to embody those behaviors and have those feelings about what you're doing. And that's going to change your values and attitudes about how you act and work and help each other out. And that's how you break down silos, and ultimately that's what changes culture. It's your values, attitudes, beliefs, and behaviors that culminate to build a one team, operating as one team to deliver one platform. >> Okay, so you're speaking at the show, obviously you've used GitLab quite a bit. What else, what brings you to this show? What are you hoping to get out of it? >> Just to see what our peers and fellow practitioners are doing in a cloud. See how GitLab's evolving. It was really great keynote this morning from Todd and Sid. So it's great to keep abreast as to what, even some of our customers are here today and to hear their story about how they're moving to the cloud and how might parallel and some things that we can learn from them. That's one of the key behaviors when you move towards cloud native is creating a culture of learning and that's how you grow. >> All right, well, Vince, thanks so much sharing your journey. >> Appreciate it. >> Great to meet you. >> Thanks so much too. >> Best luck with your presentation. And I'm Stu Miniman. This is GitLab Commit 2020. Thanks so much for watching theCUBE. (lively music)

>>from Las Vegas. It's the cues covering quality security Conference 2019. Bike. Wallace. >>Hey, welcome back it. Ready? Geoffrey here with the Q worth the Bellagio Hotel in Las Vegas for the quality security conference. This thing's been going on for 19 years. I had no idea. It's our first time here, but it's pretty interesting out. Felipe and the team have evolved this security company over a lot of huge technological changes and security changes, and they're still clipping along, doing a lot of cool things in cloud and open source. We're excited of our next guest. She's Laurie McCarthy, the EVP of worldwide field >>operations. Lori, great to see you. >>Thanks. Glad to be here. >>Absolutely. So first off, congratulations in doing some homework for this. I was going through the earnings call. The last turning call, which A was a nice earnings call. You're making money buying back stock. Also, you were promoted or the announcement of your promotion on that call and really some nice, complimentary words from Philippe and the team about the work that you've done actually >>very grateful. Thank you. And >>one of the things we >>talked about, which is unique in your background as you came from a customer. Not It's always a day ago. These shows we have people that I came from customers that went to the vendor, and then we have people that rest of Endor and they went over to the customers. There's a lot of that kind of movement, but he really complimented your execution at CVS as a big reason why you got the promotion that you did. So again. Congrats. But let's talk about, you know, kind of the CVS experience from when you were running it. Not when you're on the quality side. Yeah, that the threats. And CBS is in class nationwide, all kinds of stuff. >>Yeah, well, I mean, you know, just like any other company that's in that health care vertical, you've got so many different things to think about. Additionally, we were also in the retail vertical, so we had a lot of compliance. E's to worry about p c p c i p. I s O. A lot of the programs had been very much, uh, checkbox driven prior to the team that moved in there, including myself, and kind of changed that. So I helped to rebuild the vulnerability program there. And we started to do it in such a way that it was for the sake of security, not just checking a box. And we were really innovated how they do things. A lot of my friends are still there, and they have their own stock now, and we kind of brought everything in house. So a lot of that was outsourced. >>So what was the catalyst to make the change To move from beyond simple compliance and check in the box, Actually making a strategic part of the execution? >>Yeah, at the time and a new sea so had been put into place. And it was someone with that vision, and I think that's what really drove it. I came in just after that and was brought in on the premise that this is what we're going to change and move toward. So I was part of that process from that >>point, right? It clearly, qualities was part of the solution. So what? What did you use calls for their and how is the solution changed? You know, kind of >>so back then when >>you want to call it, >>we're talking. In 9 4010 2011 Right around there. If you opened up the quality platform, you had three things to choose from. Versus today, when you log in, you've got 18 or more, depending. And S O CVS used a little bit of all of that with the mainstay having been the vulnerability management. So I ran to full vulnerability management programs there because we had to keep our pharmacy benefit company and our retail companies separate. So I sort of did double duty, >>Right? So what you doing now on field operations? >>So is the E V p of worldwide for Wallace. I'm running all of the technical account managers for our company way have a unique sales model here, so it's a little different. So everyone in the field to service is our clients rolls up to me, and then that also includes some additional teams, like our federal team, our strategic alliances team and also our subject matter experts >>today. So you said a couple >>times you guys have your account management structure is different than maybe traditional. Kind of >>walk through. Yeah, absolutely. So versus a traditional sales model. We have a salesperson. You have client service person. You have a technical, you know, social architect kind of person. We service our clients all with one person. We have a technical account manager. We break them up into two flavors. We have a presales who are very technical folks that go out and help us get our business. And then those accounts get handed over to our post sales, who are basically the farmers in our business, maintaining and growing our existing clients. What that allows for, which is really special, is we can go in and really build a relationship built on trust and understanding and strategy, because we bring people into our company like myself who have done this, who have sat on that side of the table. So you know, someone comes in and says What? You know, how would you like to buy one of my gizmos? It's a lot different conversation when it's like, Look at what I do with this gizmo like it's amazing. So it's It's kind of a similar feeling that you guys >>have your kind of platform with application strategy enables you to kind of do a land and expand, and in fact you even a something that people can try for free. >>Yeah, absolutely. So we review our model as, like, try and buy. So for both our non clients are freemium service is that we offer our, you know, out of this world for people being able to just log in without even being a client and start to evaluate their environment. And then when they see the value that we bring, it's very easy to translate that into a buy and then likewise, for our clients who sign up for a service or two enabling additional trials and having them work within our new service is as they're being rolled out, is very, very simple, the way our platform is built. So it's just it's a really effortless, very natural progression of business that we that we built. And it's one of the reasons that I work here because as a client, I really enjoyed my relationship with this company because it never felt like I was being sold anything. It always felt like I was being handed solutions to my challenges, and that's what we tried to do. And that's how I lead everyone today is Let's get out, Let's listen, let's strategize and let's see where we fit in with folks, right strategies for, you know, the coming >>future. So must be a team >>approach, though, right? Because one person you know to say, trying to manage the CVS account, that would be, >>Oh, so we have a little bit of a break out in our post side. We have what a new role that I helped get implemented here at the company, which is a major account solution architect they handle are bigger, more complex accounts. So as our platform has matured, so have our clients are bigger. Clients are using more of our platform. They're using it in a more expert way. So we had to answer that with the right kind of people who could speak to that expert level of usage and be able to finance that. So that's a little bit part of it. And on our bigger clients, we do have more of a team approach. We have a product management, a project management organization. The S M E team are subject matter. Experts roll up under me. They're experts in each of our solutions. So it's a sizeable team and they are liaise between product management, engineering our fields and our clients. And that's another support mechanism. And then our support at Wallace is also something that augments our technical account managers jobs on a daily basis. >>So new opportunity with a sure that was recently announced a bundle. Yeah, you're bundled in kind of under the covers, not not really under the covers. So a little bit about how that's gonna work from kind of an account management and and from your kind of point of view, >>So it's It's actually not gonna change much of anything on the way that we are. Mom are our model is a hybrid, right? So we have direct sales that we have indirect sales, even honor in direct sales through partners through relationships like we've just built with azure MSs peas and reach whatever. We still treat every end customer and every partner like a direct customer. So we work very hard to educate her partners, to work with them, to make sure they're successful with our clients. And we're also treating our clients who are through that avenue the same way. So it's it's just gonna blend right in with what we >>d'oh Yeah, that's great, but hopefully it's a sales channel and they get more than they just bought it under the covers and start implementing. >>It's easy for them to jump in with us. And then from there we can build those relationships with perhaps, you know, prospects and folks that aren't our clients now and be able to show them more things that we do. Besides just, you know, the one thing that they might be signing up for at that time, >>right? Right. Okay, great. I want to shift gears a little bit. >>We had windy by front earlier from from Nutanix. When he's a fantastic lady, yes, and she is super super involved in in girls Who Code and women in Tech and trying to drive that kind of forward along a number of parameters everything from the board to getting people jobs, training little girls to staying at staying in the industry. I know that's a big, passionate area of yours. I wonder if you could share some of the activities you guys were doing around women. I could think more specifically, and security is a subset of all tech, but share the some of the activities you have going on. >>So personally, I try to be very involved locally. Four Children. One of them is a daughter. She's too little, quite yet for getting into tact. I have two older sons and s so I try to be really involved in middle school high school. Hey, put me in, Coach, I'll come in and talk to the kids. Generating interest in getting into this field at a young age is what we need to do. They're still aren't enough gals and, honestly, guys heading into our business in college. So I I really take it upon myself as a security professional to try to promote that specifically around women. I'm really pleased that our company supports an organization which I've been a part of for a while, and that's the Executive Woman's Forum, and we sponsor their conference every year, and we sponsor events with them. I personally am part of their mentor program, so that allows me a channel. Thio have ah, unassigned person to work with, and I really enjoy that, and our company itself is just very excellent at promoting and enabling women within our organization. And it's another reason that I really loved working here for the past eight years, >>right? Well, from the top. Because the board, I think, is either for more than half. Yemen, which is certainly half >>women CEO, is very supportive. Our presidents, two men way have a great environment. Thio grow women professionally here in my company, >>right? That's great. So, ah, year from now, when we come back, what are we gonna be talking about? What's kind of on a road map? For the next year, >>we're going to be talking about our data leak efforts, or Sim. We're gonna be talking about our improved Edie, our capabilities that are really gonna put us in the position to be a major player in that market. Um, and who knows? We have such a quick turnaround of innovation here and what we do by the way we do our business. So starting with the technical account manager's boots on the ground with our clients, when we're there listening to all of their challenges, we're also taking that back, and that drives our innovation that the company so we hear what they need, and that's what we provide. So as things changed, we're going to continue to do that digital transformation, of course, is is making that something that we have to be even quicker about. And I think we're doing a good job >>keeping up well. 19 years and counting, making money. Find back, buying back shares to help everyone else's stock delusion. So not that, but nothing but good success. It's all right. Well, Laurie, thanks for taking a few minutes of your day. And again, congratulations on your promotion as well as a terrific event. >>Thank you very much. >>All right. She's Laurie. I'm Jeff. You're watching the Cube with the quality security conference at the Bellagio and lovely >>Las Vegas. Thanks for watching. We'll see you next time.

>>Live from the Mandalay convention center in Las Vegas, Nevada. It's not cue at IBM insight 2014 >>you're all your hosts. John furrier and Dave Volante.. >>Okay. Welcome back everyone. We're here live inside the cube at IBM insight. I'm Sean with Dave Volante. We go after the events, extract the signal and noise. We go wall to wall covers what we do here. I don't, of course we're excited to have awesome gas. We talked to the executives, entrepreneurs, but we get the media stars in here. Uh, Katie Lyndon doll. Welcome to the cube. You are with CNN, the today show. You're the tech correspondent and you get a lot of energy. I could just tell this is going to be fun. It's been fun to hear the last few days. So I mean, Watson is the geeky story of any what, what are you seeing? Let me get the wife in a second. But outside of Watson, what's the coolest thing you've seen? >>I'm constantly on the hunt for the latest innovations in technology and I think that's probably the best part about my job. And always chasing down high level stories. I recently just came back for a dive with NASA. I learned that NASA astronauts actually train underwater to simulate microgravity and I'm like, Oh my gosh, no way. And they're like, do you want to come down to the world's only Marine underwater habitat? I was like, yes, please. So went down to the Florida keys, it's an hour off the coast and was diving literally with NASA European space agency and the Canadian space agency underwater. And again, it's the world's only underwater Marine habitat and seeing how they train in everything from asteroid mining to um, underwater surgery to actually seeing how the body responds to exercise. I guess water simulates one sixth of gravity. So it was a pretty dynamic shoot. >>I was doing that for NBC news and it's just I, those are the types of stories. I, I am a diver. I actually was doing a story on big data last year and it required me to get my dive certs and the Island of Bermuda feel very bad. It was a presentation that I was speaking on here at insight a, there was all this crowdsourced information about how the lion fish, if you've ever heard of the lion fish has been, it's an invasion in the Atlantic ocean. I took all of this information and metrics and made a story for CNN and it required me to get my advanced dive certs. So now I'm getting all these dive stories cause there's not a lot of us dive reporters. So the lion fish story for CNN too. Another good example of a piece that I go after. >>So you, you bring a lot of energy. What do you see here? I mean you see a lot of stories and you get pitched stories. I can imagine that your email box flux, I mean it's like, Oh >>I have 78,000 unread emails right now. I'm not proud of that. But yes, constantly being pitched. >>I had 40,000 I'm a little bit blind. I'm going to give that to you in the today show. Not too shabby. But what do you do? You get pitched all the time and so you got the vet stories. What's your formula for vetting stories? I mean, what gets your attention and how do you go outside your comfort zone to select good stories? What your attention. It's funny, >>you know, so I've been in television for the last 10 years and I feel like now I have this internal barometer and knowing when something's very good and the scope of the things that I cover from, you know, in the past month alone when I was talking about the NASA piece and then I'll flip the next day and do top Halloween gadgets on today's show. So it's, it's very vast, but I can instantly tell and it's, it's come through experience and being in a background in technology and knowing what's gonna work for the consumer and knowing a hot product. When I see it and I I T I gotten pretty good I think at it spotting a product that a consumer is going to love but also finding a story that is, maybe it's super nerdy, but my job is to take it and to bring it down to a level that's entertaining for any kind of audience, whether it be CNN or whether it be today. >>So it says your Guinness book of world record holder, share that in little nugget with the folks in. Yes, that is a true story. I have a Guinness world record holder in the most high fives and one minute. Okay, so this probably solicit some like how the heck did that happen? I've always been fascinated with Guinness world records and I always wanted one and I've always been obsessed with a high five like I am paranoid of huggers, there's nothing that scares me more or good high five just go for the five. I don't want to bring it in and okay, it's a little OCD. I will completely aware. So anyways, I found that this Guinness world record was held by a clown in England for the most high fives and one minute. So I convinced I was hosting a show on spike TV and I convinced them to allow me to break this record. >>So we had all these people line up in the MTV cafeteria and you have a Guinness world record adjudicator come onsite, you get two tries and if you win you get a plaque in a formal ceremony. The cube before we should do the most consecutive interviews to having a drink of water. We want to just come here and we could break something able to break something or like you said, it's his official. Yeah, we started to get like real nervous and like hot and yeah, so I had two tribes. Oh I was, I was giving him a big ass big fitness person. So I was like ready. And if clown beats me at this point, it's over your careers. division. You'll never work again because I beat it on the first try and then I advanced it on a single hand or you go, there's a whole process as you can imagine with the adjudicator's she's like real intense. >>She's like counting with her clicker on the high five so I go down this line of people and it has to be over there can't be like a mailed in like you know like a high five you go for the five names and then I got a couple that were disqualified, you know like a couple didn't count because it wasn't like a full on five four so like a film replay. Super slow motion. I like argued a few. I was like no, I was for sure up on that one. The flag, it was sponsored by PRL. It wasn't but it should have been but it was fun. So I have a plaque how many? 107 heard rumors that it's been broken but I didn't care as long as I've got a plan to that plan at one point. Okay. Let's cut to about IBM because Watson is the coolest thing I'll say is pretty mainstream. >>It hits your wheelhouse. I'll see for the day I've seen jeopardy. Absolutely. Now how does that translate into a story for sure. Stuff going on here. What do you, so what's very cool about Watson? I called my boyfriend because I've had a relationship with him now over the last few years, a few years ago on CVS. I actually got to challenge Watson on a full game of jeopardy and I think that was of course the most, the most memorable part of Watson when he took on the two, you know, jeopardy champions. But so this is like a lifetime moment for me. I got a full game of jeopardy, me Watson and another individual smoked me and actually I was doing okay and then it was like tennis vocab. I was like, Oh, I got this. You know, like I've been in sports my whole life. I've been worked at ESPN for seven years. >>I got this in the bag, I was doing good. And then they were like, Oh, we had them on the low setting. I was like, all right, really? Like really? Like I was just feeling good about myself. I finished with $2, two bucks. Um, and I thought it was so cool how gimmicky it was, you know, in a healthy beach in the tennis category. Oh, you smoking, you never in the low setting for sure. I got a few of those, a few. I actually got set in Tennessee vocab. You're going to have it right. Even watching tennis your whole life. Right. ESPN is embarrassing and disappointing. And then I weighed you too much and then the double jeopardy. Anyways, I digress. So how cool is it that I got to play Watson but then now years later seeing the power in it in many different developments and most notably I work over at as a volunteer at Sloan Memorial Kettering cancer center for a small group called Candlelighters that works with individuals that come in from around the world for cancer treatments. >>Now Sloan is one of those powerful cancer centers in the world is actually using it as predictive analysis. So here and I work with these kids and I, it's very complex. When they go in for a diagnosis, there's lots of different problems that they have and really it's, it's, it's, it's, it's guesswork for a doctor now. They can put all of these things that are happening with it, with a child into a machine, and they can pump out a hypotheses. Of course, you're going to have to have the human interaction tailored with that to have the emotional side, but I had been fascinated, especially on the medical side, watching your boyfriend at this point. That's interesting. We'll get that to the world of Facebook. It's complicated. I heard rumors that he's talks back and we'll listen to this a true statement. He's a lot smarter than I am. >>I'm intimidated by that, but what's the coolest demo with Watson that you've seen besides jeopardy? Yeah, that would have, well I actually learned something new from a few developers that I met yesterday about the new chef app. So being able to go into your pantry and to do some recipe from what you have, the ingredients you have insider, I think that's a little more consumer friendly. So I was kind of like, um, I'm excited to check that one out. Looking at the tech landscape, what are you most excited about? I mean, what's the coolest kind of consumer meats like gadget, short door, tech cloud. If you could pull a few favorites at what's, what's drawing your attention? Uh, one that we actually had here that's probably popped into mind. There's so many to choose from, but in the world of Oculus rift, and the reason I say that is not for the gaming aspect, but more for the potential in the landscape of physical therapy. >>The first time I got on Oculus raft, I was actually training on a Navy boat and I was doing a segment where all my camera men were all around me. I lost track of reality and I got so immersed into virtual reality and being there and even as a huge diver, I get very motion sick and I got motion sick on the boat. Being in this physical, this augmented reality world, we're actually shooting this at the birthplace of Oculus rift. So we really diving behind the scenes into the actual, uh, software and hardware and it was such a cool, immersive experience and realize that what this could do for physical therapy or even at the dentist at a lower end, I think the capabilities for augmented reality and taking yourself out of that moment are huge. So I think that's very exciting. How about drones? >>Oh my gosh. So yes, let's talk to, and my nephew the other day and he said, do you want to see the drone that I built? And I said, yeah, it's got this four or five quadcopter. It's a quadcopter. Yup. I said, where'd you get the software for? He goes, I'll download it. It's all open source. I hacked it a little bit. I actually have several drones. Okay. Nominal. Because this blew me away. I probably have what I consider is the best prosumer drone. It's a DGI Phantom, a DJI Phantom two and I have got some incredible aerial footage over the mountains of Montana and also over a Bermuda, the Island of Bermuda. I sent it up, put it over a shipwreck, gorgeous. And for me as a flake, being in photo and video and going out and getting my own video and not having to rely on a cop, a copter for, you know, that would be thousands of dollars worth of footage or relying on a cameraman. >>I just sent that baby up. I'm like, please don't hit anybody. It's a little hard to operate when you get the one, the higher end models. I have a couple of the parents too. There are a lot easier to operate and do it right from my iPhone, but I am just like, I'm so into it now. I think it's a little gimmicky when we talk about Amazon and pizza deliveries and taco deliveries and beer deliveries with a drone shooting surprises. Texas man, what am, I don't know about that. But uh, I think it's fascinating. I think it's a really cool technology. And again, I've personally saved tens and thousands of dollars using my drones. So you, when you flew over these sites yet proximate, so you had visual concepts. So the Phantom Jerome that I have, that's my favorite one. I actually attach a GoPro to it so I can send it up and I use the gyroscope or just kind of move my GoPro around in mid air. It goes hundreds of feet high. I mean, you've really got to get a grasp on it and know what you're doing. I had it out in a field well before I took it out to an Island on a beach. But I'm not, a drive is not something you really, it's not a remote control car. Now did you build it? Oh no. Goodness. Aww, that's totally on the market. Yeah, I got it at B and H photo >>sending them out. So in San Francisco off their balconies and then they're going out to, you know, angel Island, Alcatraz, and literally they're flying out then unregulated. It's like someday there'll be drone collisions, let's say this is unregulated. This is a huge, people are geeking out with the drones. It's super exciting. Dave camera's shooting down him sending him into football venues or you know, the world series delivering packages. But mom's a streaker. I mean Amazon. I like that. Okay. So what else is new for you? Tell us more about some, some cool behind the scenes at a today's show. Any sad night live, uh, opportunities for you next been >>to Saturday night live. Oh my gosh. By the way, that's like the hottest ticket in New York to get. I've had the opportunity to go to two shows cause my friend's a cameraman over there. The rehearsal for it is like amazing. I know that's a huge digression, but talking about something to see in person, that's one of my bucket lists. Phenomenal. Yeah. Phenomenal. What else is new in New York and the scene there? Uh, Oh, we constantly covering a lot of different pieces. Uh, one, I just came back from Africa a little bit ago. I was doing a number of pieces over there from an elephant orphanage to one of my favorite pieces that we'll be rolling out soon. I did it for cnn.com and also working on a video piece of it. I went in embedded myself in the second poorest part of the entire world in the slums of Kibera, Kenya, and it was amazing to see that in these very poor areas, 70 to 80% cell penetration. A lot of people don't think that a smartphone would be prevalent. It sure is. And these kids, yeah, absolutely. There's cell towers everywhere. These kids were, you know, they don't have much, but they have e-reader devices and they can have thousands of books when they're walking 10 miles to school. You walk into the school that doesn't have any electricity, it's a hundred degrees, but they all have e-readers, Kindles right on their desk. I was blown away. I went to several different schools around Eastern Kenya. Fascinating story to be able to cover. So >>yeah, that's a really good point. In mobile penetration. If I was talking to this startup that where their business plan is to build, sell a solar battery recharging stations because they have the exact points, like they have all these devices but it's not, they don't have the traditional electricity and the parks >>one outlet in the entire school. So fortunately for, you know, with wifi off it's about a week charge on a Kindle. So it is, >>yeah, I think, I think that's a great market opportunity. Certainly in emerging countries, the mobile penetration, I'm so suites about the IBM show here. Is this your first time here or, >>I have had the luxury and the opportunity to be a part of several IBM events and everyone is so uniquely different. And this one all about developers obviously. So something I get to nerd out in myself in that is an it girl and also a developer. It's fun to be able to learn. I picked up so much new information so I just kind of like, they're like, you can, you're done with, I'm like, I'm going to hang out for a little bit longer. >>You know, you know you're a, you know, you're a geek when you're geeking out, when you're off the clock, you know Steve and I the same way. We're like we should stop rookies now let's keep going. So CES, UFC, yes, >>yes, every year for sure. And for anyone that hasn't been to CF, it's kind of on the bucket list for anybody that's attending technology, 35 football fields full of gadgets. Amazing. Yeah, it's always one of my biggest times of the year. So we'll be back here. >>now do you enjoy CES or is it a hard slog for you because you must have to really get down and dirty for CS, I mean a lot of stuff to cover. >>I did and I tried to make it to like the most random boosts. I find someone of my best technology products and like the ma and PA type shops that don't have the million dollar booth and like you know that are really back in a corner and I'm like zero in, >>you go on to cover, by the way, do you go into cover? You kind of sneak in there and you go into the camera guys. No, I go for it. You go for it. Okay. Time. Okay. All right guys. Um, that's awesome. Well can. Thanks for coming on the cube. We really appreciate spending the time. We'd love the personality. I love the energy. I mean Dave and I think you know, we're, first of all we're huge fans of your work. Especially the ESPN part. No, we're, we're big sports fans. In fact we call this the ESPN of tech cause it's our kind of version of like trying to be like ESPN. But we think technology is going mainstream. People at this new generation are geeks and even too, you alluded to ESPN, even sports and technology, I can't tell you how many pieces I've covered in pro athletes and how tech is entering in that space. Everywhere. Disruption in the data, the social media, you know, limiting have agents that go direct to the audience. Just super exciting. I mean I'm real big fan of media, tech, sports and entertainment. Thanks for coming on the cube. We appreciate it. We'll be right back with this after the short break here inside the cube live in Las Vegas. I'm John and Dave. We write back.