>>From the Cube Studios in Palo Alto in Boston, bringing you data-driven insights from the cube and E T R. This is breaking analysis with Dave Valante. >>Making technology predictions in 2022 was tricky business, especially if you were projecting the performance of markets or identifying I P O prospects and making binary forecast on data AI and the macro spending climate and other related topics in enterprise tech 2022, of course was characterized by a seesaw economy where central banks were restructuring their balance sheets. The war on Ukraine fueled inflation supply chains were a mess. And the unintended consequences of of forced march to digital and the acceleration still being sorted out. Hello and welcome to this week's weekly on Cube Insights powered by E T R. In this breaking analysis, we continue our annual tradition of transparently grading last year's enterprise tech predictions. And you may or may not agree with our self grading system, but look, we're gonna give you the data and you can draw your own conclusions and tell you what, tell us what you think. >>All right, let's get right to it. So our first prediction was tech spending increases by 8% in 2022. And as we exited 2021 CIOs, they were optimistic about their digital transformation plans. You know, they rushed to make changes to their business and were eager to sharpen their focus and continue to iterate on their digital business models and plug the holes that they, the, in the learnings that they had. And so we predicted that 8% rise in enterprise tech spending, which looked pretty good until Ukraine and the Fed decided that, you know, had to rush and make up for lost time. We kind of nailed the momentum in the energy sector, but we can't give ourselves too much credit for that layup. And as of October, Gartner had it spending growing at just over 5%. I think it was 5.1%. So we're gonna take a C plus on this one and, and move on. >>Our next prediction was basically kind of a slow ground ball. The second base, if I have to be honest, but we felt it was important to highlight that security would remain front and center as the number one priority for organizations in 2022. As is our tradition, you know, we try to up the degree of difficulty by specifically identifying companies that are gonna benefit from these trends. So we highlighted some possible I P O candidates, which of course didn't pan out. S NQ was on our radar. The company had just had to do another raise and they recently took a valuation hit and it was a down round. They raised 196 million. So good chunk of cash, but, but not the i p O that we had predicted Aqua Securities focus on containers and cloud native. That was a trendy call and we thought maybe an M SS P or multiple managed security service providers like Arctic Wolf would I p o, but no way that was happening in the crummy market. >>Nonetheless, we think these types of companies, they're still faring well as the talent shortage in security remains really acute, particularly in the sort of mid-size and small businesses that often don't have a sock Lacework laid off 20% of its workforce in 2022. And CO C e o Dave Hatfield left the company. So that I p o didn't, didn't happen. It was probably too early for Lacework. Anyway, meanwhile you got Netscope, which we've cited as strong in the E T R data as particularly in the emerging technology survey. And then, you know, I lumia holding its own, you know, we never liked that 7 billion price tag that Okta paid for auth zero, but we loved the TAM expansion strategy to target developers beyond sort of Okta's enterprise strength. But we gotta take some points off of the failure thus far of, of Okta to really nail the integration and the go to market model with azero and build, you know, bring that into the, the, the core Okta. >>So the focus on endpoint security that was a winner in 2022 is CrowdStrike led that charge with others holding their own, not the least of which was Palo Alto Networks as it continued to expand beyond its core network security and firewall business, you know, through acquisition. So overall we're gonna give ourselves an A minus for this relatively easy call, but again, we had some specifics associated with it to make it a little tougher. And of course we're watching ve very closely this this coming year in 2023. The vendor consolidation trend. You know, according to a recent Palo Alto network survey with 1300 SecOps pros on average organizations have more than 30 tools to manage security tools. So this is a logical way to optimize cost consolidating vendors and consolidating redundant vendors. The E T R data shows that's clearly a trend that's on the upswing. >>Now moving on, a big theme of 2020 and 2021 of course was remote work and hybrid work and new ways to work and return to work. So we predicted in 2022 that hybrid work models would become the dominant protocol, which clearly is the case. We predicted that about 33% of the workforce would come back to the office in 2022 in September. The E T R data showed that figure was at 29%, but organizations expected that 32% would be in the office, you know, pretty much full-time by year end. That hasn't quite happened, but we were pretty close with the projection, so we're gonna take an A minus on this one. Now, supply chain disruption was another big theme that we felt would carry through 2022. And sure that sounds like another easy one, but as is our tradition, again we try to put some binary metrics around our predictions to put some meat in the bone, so to speak, and and allow us than you to say, okay, did it come true or not? >>So we had some data that we presented last year and supply chain issues impacting hardware spend. We said at the time, you can see this on the left hand side of this chart, the PC laptop demand would remain above pre covid levels, which would reverse a decade of year on year declines, which I think started in around 2011, 2012. Now, while demand is down this year pretty substantially relative to 2021, I D C has worldwide unit shipments for PCs at just over 300 million for 22. If you go back to 2019 and you're looking at around let's say 260 million units shipped globally, you know, roughly, so, you know, pretty good call there. Definitely much higher than pre covid levels. But so what you might be asking why the B, well, we projected that 30% of customers would replace security appliances with cloud-based services and that more than a third would replace their internal data center server and storage hardware with cloud services like 30 and 40% respectively. >>And we don't have explicit survey data on exactly these metrics, but anecdotally we see this happening in earnest. And we do have some data that we're showing here on cloud adoption from ET R'S October survey where the midpoint of workloads running in the cloud is around 34% and forecast, as you can see, to grow steadily over the next three years. So this, well look, this is not, we understand it's not a one-to-one correlation with our prediction, but it's a pretty good bet that we were right, but we gotta take some points off, we think for the lack of unequivocal proof. Cause again, we always strive to make our predictions in ways that can be measured as accurate or not. Is it binary? Did it happen, did it not? Kind of like an O K R and you know, we strive to provide data as proof and in this case it's a bit fuzzy. >>We have to admit that although we're pretty comfortable that the prediction was accurate. And look, when you make an hard forecast, sometimes you gotta pay the price. All right, next, we said in 2022 that the big four cloud players would generate 167 billion in IS and PaaS revenue combining for 38% market growth. And our current forecasts are shown here with a comparison to our January, 2022 figures. So coming into this year now where we are today, so currently we expect 162 billion in total revenue and a 33% growth rate. Still very healthy, but not on our mark. So we think a w s is gonna miss our predictions by about a billion dollars, not, you know, not bad for an 80 billion company. So they're not gonna hit that expectation though of getting really close to a hundred billion run rate. We thought they'd exit the year, you know, closer to, you know, 25 billion a quarter and we don't think they're gonna get there. >>Look, we pretty much nailed Azure even though our prediction W was was correct about g Google Cloud platform surpassing Alibaba, Alibaba, we way overestimated the performance of both of those companies. So we're gonna give ourselves a C plus here and we think, yeah, you might think it's a little bit harsh, we could argue for a B minus to the professor, but the misses on GCP and Alibaba we think warrant a a self penalty on this one. All right, let's move on to our prediction about Supercloud. We said it becomes a thing in 2022 and we think by many accounts it has, despite the naysayers, we're seeing clear evidence that the concept of a layer of value add that sits above and across clouds is taking shape. And on this slide we showed just some of the pickup in the industry. I mean one of the most interesting is CloudFlare, the biggest supercloud antagonist. >>Charles Fitzgerald even predicted that no vendor would ever use the term in their marketing. And that would be proof if that happened that Supercloud was a thing and he said it would never happen. Well CloudFlare has, and they launched their version of Supercloud at their developer week. Chris Miller of the register put out a Supercloud block diagram, something else that Charles Fitzgerald was, it was was pushing us for, which is rightly so, it was a good call on his part. And Chris Miller actually came up with one that's pretty good at David Linthicum also has produced a a a A block diagram, kind of similar, David uses the term metacloud and he uses the term supercloud kind of interchangeably to describe that trend. And so we we're aligned on that front. Brian Gracely has covered the concept on the popular cloud podcast. Berkeley launched the Sky computing initiative. >>You read through that white paper and many of the concepts highlighted in the Supercloud 3.0 community developed definition align with that. Walmart launched a platform with many of the supercloud salient attributes. So did Goldman Sachs, so did Capital One, so did nasdaq. So you know, sorry you can hate the term, but very clearly the evidence is gathering for the super cloud storm. We're gonna take an a plus on this one. Sorry, haters. Alright, let's talk about data mesh in our 21 predictions posts. We said that in the 2020s, 75% of large organizations are gonna re-architect their big data platforms. So kind of a decade long prediction. We don't like to do that always, but sometimes it's warranted. And because it was a longer term prediction, we, at the time in, in coming into 22 when we were evaluating our 21 predictions, we took a grade of incomplete because the sort of decade long or majority of the decade better part of the decade prediction. >>So last year, earlier this year, we said our number seven prediction was data mesh gains momentum in 22. But it's largely confined and narrow data problems with limited scope as you can see here with some of the key bullets. So there's a lot of discussion in the data community about data mesh and while there are an increasing number of examples, JP Morgan Chase, Intuit, H S P C, HelloFresh, and others that are completely rearchitecting parts of their data platform completely rearchitecting entire data platforms is non-trivial. There are organizational challenges, there're data, data ownership, debates, technical considerations, and in particular two of the four fundamental data mesh principles that the, the need for a self-service infrastructure and federated computational governance are challenging. Look, democratizing data and facilitating data sharing creates conflicts with regulatory requirements around data privacy. As such many organizations are being really selective with their data mesh implementations and hence our prediction of narrowing the scope of data mesh initiatives. >>I think that was right on J P M C is a good example of this, where you got a single group within a, within a division narrowly implementing the data mesh architecture. They're using a w s, they're using data lakes, they're using Amazon Glue, creating a catalog and a variety of other techniques to meet their objectives. They kind of automating data quality and it was pretty well thought out and interesting approach and I think it's gonna be made easier by some of the announcements that Amazon made at the recent, you know, reinvent, particularly trying to eliminate ET t l, better connections between Aurora and Redshift and, and, and better data sharing the data clean room. So a lot of that is gonna help. Of course, snowflake has been on this for a while now. Many other companies are facing, you know, limitations as we said here and this slide with their Hadoop data platforms. They need to do new, some new thinking around that to scale. HelloFresh is a really good example of this. Look, the bottom line is that organizations want to get more value from data and having a centralized, highly specialized teams that own the data problem, it's been a barrier and a blocker to success. The data mesh starts with organizational considerations as described in great detail by Ash Nair of Warner Brothers. So take a listen to this clip. >>Yeah, so when people think of Warner Brothers, you always think of like the movie studio, but we're more than that, right? I mean, you think of H B O, you think of t n t, you think of C N N. We have 30 plus brands in our portfolio and each have their own needs. So the, the idea of a data mesh really helps us because what we can do is we can federate access across the company so that, you know, CNN can work at their own pace. You know, when there's election season, they can ingest their own data and they don't have to, you know, bump up against, as an example, HBO if Game of Thrones is going on. >>So it's often the case that data mesh is in the eyes of the implementer. And while a company's implementation may not strictly adhere to Jamma Dani's vision of data mesh, and that's okay, the goal is to use data more effectively. And despite Gartner's attempts to deposition data mesh in favor of the somewhat confusing or frankly far more confusing data fabric concept that they stole from NetApp data mesh is taking hold in organizations globally today. So we're gonna take a B on this one. The prediction is shaping up the way we envision, but as we previously reported, it's gonna take some time. The better part of a decade in our view, new standards have to emerge to make this vision become reality and they'll come in the form of both open and de facto approaches. Okay, our eighth prediction last year focused on the face off between Snowflake and Databricks. >>And we realized this popular topic, and maybe one that's getting a little overplayed, but these are two companies that initially, you know, looked like they were shaping up as partners and they, by the way, they are still partnering in the field. But you go back a couple years ago, the idea of using an AW w s infrastructure, Databricks machine intelligence and applying that on top of Snowflake as a facile data warehouse, still very viable. But both of these companies, they have much larger ambitions. They got big total available markets to chase and large valuations that they have to justify. So what's happening is, as we've previously reported, each of these companies is moving toward the other firm's core domain and they're building out an ecosystem that'll be critical for their future. So as part of that effort, we said each is gonna become aggressive investors and maybe start doing some m and a and they have in various companies. >>And on this chart that we produced last year, we studied some of the companies that were targets and we've added some recent investments of both Snowflake and Databricks. As you can see, they've both, for example, invested in elation snowflake's, put money into Lacework, the Secur security firm, ThoughtSpot, which is trying to democratize data with ai. Collibra is a governance platform and you can see Databricks investments in data transformation with D B T labs, Matillion doing simplified business intelligence hunters. So that's, you know, they're security investment and so forth. So other than our thought that we'd see Databricks I p o last year, this prediction been pretty spot on. So we'll give ourselves an A on that one. Now observability has been a hot topic and we've been covering it for a while with our friends at E T R, particularly Eric Bradley. Our number nine prediction last year was basically that if you're not cloud native and observability, you are gonna be in big trouble. >>So everything guys gotta go cloud native. And that's clearly been the case. Splunk, the big player in the space has been transitioning to the cloud, hasn't always been pretty, as we reported, Datadog real momentum, the elk stack, that's open source model. You got new entrants that we've cited before, like observe, honeycomb, chaos search and others that we've, we've reported on, they're all born in the cloud. So we're gonna take another a on this one, admittedly, yeah, it's a re reasonably easy call, but you gotta have a few of those in the mix. Okay, our last prediction, our number 10 was around events. Something the cube knows a little bit about. We said that a new category of events would emerge as hybrid and that for the most part is happened. So that's gonna be the mainstay is what we said. That pure play virtual events are gonna give way to hi hybrid. >>And the narrative is that virtual only events are, you know, they're good for quick hits, but lousy replacements for in-person events. And you know that said, organizations of all shapes and sizes, they learn how to create better virtual content and support remote audiences during the pandemic. So when we set at pure play is gonna give way to hybrid, we said we, we i we implied or specific or specified that the physical event that v i p experience is going defined. That overall experience and those v i p events would create a little fomo, fear of, of missing out in a virtual component would overlay that serves an audience 10 x the size of the physical. We saw that really two really good examples. Red Hat Summit in Boston, small event, couple thousand people served tens of thousands, you know, online. Second was Google Cloud next v i p event in, in New York City. >>Everything else was, was, was, was virtual. You know, even examples of our prediction of metaverse like immersion have popped up and, and and, and you know, other companies are doing roadshow as we predicted like a lot of companies are doing it. You're seeing that as a major trend where organizations are going with their sales teams out into the regions and doing a little belly to belly action as opposed to the big giant event. That's a definitely a, a trend that we're seeing. So in reviewing this prediction, the grade we gave ourselves is, you know, maybe a bit unfair, it should be, you could argue for a higher grade, but the, but the organization still haven't figured it out. They have hybrid experiences but they generally do a really poor job of leveraging the afterglow and of event of an event. It still tends to be one and done, let's move on to the next event or the next city. >>Let the sales team pick up the pieces if they were paying attention. So because of that, we're only taking a B plus on this one. Okay, so that's the review of last year's predictions. You know, overall if you average out our grade on the 10 predictions that come out to a b plus, I dunno why we can't seem to get that elusive a, but we're gonna keep trying our friends at E T R and we are starting to look at the data for 2023 from the surveys and all the work that we've done on the cube and our, our analysis and we're gonna put together our predictions. We've had literally hundreds of inbounds from PR pros pitching us. We've got this huge thick folder that we've started to review with our yellow highlighter. And our plan is to review it this month, take a look at all the data, get some ideas from the inbounds and then the e t R of January surveys in the field. >>It's probably got a little over a thousand responses right now. You know, they'll get up to, you know, 1400 or so. And once we've digested all that, we're gonna go back and publish our predictions for 2023 sometime in January. So stay tuned for that. All right, we're gonna leave it there for today. You wanna thank Alex Myerson who's on production and he manages the podcast, Ken Schiffman as well out of our, our Boston studio. I gotta really heartfelt thank you to Kristen Martin and Cheryl Knight and their team. They helped get the word out on social and in our newsletters. Rob Ho is our editor in chief over at Silicon Angle who does some great editing for us. Thank you all. Remember all these podcasts are available or all these episodes are available is podcasts. Wherever you listen, just all you do Search Breaking analysis podcast, really getting some great traction there. Appreciate you guys subscribing. I published each week on wikibon.com, silicon angle.com or you can email me directly at david dot valante silicon angle.com or dm me Dante, or you can comment on my LinkedIn post. And please check out ETR AI for the very best survey data in the enterprise tech business. Some awesome stuff in there. This is Dante for the Cube Insights powered by etr. Thanks for watching and we'll see you next time on breaking analysis.

>>The Cube presents Ignite 22, brought to you by Palo Alto Networks. >>Welcome back to Vegas. Guys. We're happy that you're here. Lisa Martin here covering with Dave Valante, Palo Alto Networks Ignite 22. We're at MGM Grand. This is our first day, Dave of two days of cube coverage. We've been having great conversations with the ecosystem with Palo Alto executives, with partners. One of the things that they have is unit 42. We're gonna be talking with them next about cyber intelligence. And the threat data that they get is >>Incredible. Yeah. They have all the data, they know what's going on, and of course things are changing. The state of play changes. Hold on a second. I got a text here. Oh, my Netflix account was frozen. Should I click on this link? Yeah. What do you think? Have you had a, it's, have you had a little bit more of that this holiday season? Yeah, definitely. >>Unbelievable, right? A lot of smishing going on. >>Yeah, they're very clever. >>Yeah, we're very pleased to welcome back one of our alumni to the queue. Wendy Whitmore is here, the SVP of Unit 42. Welcome back, Wendy. Great to have >>You. Thanks Lisa. So >>Unit 42 created back in 2014. One of the things that I saw that you said in your keynote this morning or today was everything old is still around and it's co, it's way more prolific than ever. What are some of the things that Unit 42 is seeing these days with, with respect to cyber threats as the landscape has changed so much the last two years alone? >>You know, it, it has. So it's really interesting. I've been responding to these breaches for over two decades now, and I can tell you that there are a lot of new and novel techniques. I love that you already highlighted Smishing, right? In the opening gate. Right. Because that is something that a year ago, no one knew what that word was. I mean, we, it's probably gonna be invented this year, right? But that said, so many of the tactics that we have previously seen, when it comes to just general espionage techniques, right? Data act filtration, intellectual property theft, those are going on now more than ever. And you're not hearing about them as much in the news because there are so many other things, right? We're under the landscape of a major war going on between Russia and Ukraine of ransomware attacks, you know, occurring on a weekly basis. And so we keep hearing about those, but ultimately these nations aid actors are using that top cover, if you will, as a great distraction. It's almost like a perfect storm for them to continue conducting so much cyber espionage work that like we may not be feeling that today, but years down the road, they're, the work that they're doing today is gonna have really significant impact. >>Ransomware has become a household word in the last couple of years. I think even my mom knows what it is, to some degree. Yeah. But the threat actors are far more sophisticated than they've ever written. They're very motivated. They're very well funded. I think I've read a stat recently in the last year that there's a ransomware attack once every 11 seconds. And of course we only hear about the big ones. But that is a concern that goes all the way up to the board. >>Yeah. You know, we have a stat in our ransomware threat report that talks about how often victims are posted on leak sites. And I think it's once every seven minutes at this point that a new victim is posted. Meaning a victim has had their data, a victim organization had their data stolen and posted on some leak site in the attempt to be extorted. So that has become so common. One of the shifts that we've seen this year in particular and in recent months, you know, a year ago when I was at Ignite, which was virtual, we talked about quadruple extortion, meaning four different ways that these ransomware actors would go out and try to make money from these attacks in what they're doing now is often going to just one, which is, I don't even wanna bother with encrypting your data now, because that means that in order to get paid, I probably have to decrypt it. Right? That's a lot of work. It's time consuming. It's kind of painstaking. And so what they've really looked to do now is do the extortion where they simply steal the data and then threaten to post it on these leak sites, you know, release it other parts of the web and, and go from there. And so that's really a blending of these techniques of traditional cyber espionage with intellectual property theft. Wow. >>How trustworthy are those guys in terms of, I mean, these are hackers, right? In terms of it's really the, the hacker honor system, isn't it? I mean, if you get compromised like that, you really beholden to criminals. And so, you >>Know, so that's one of the key reasons why having the threat intelligence is so important, right? Understanding which group that you're dealing with and what their likelihood of paying is, what's their modus operandi. It's become even more important now because these groups switch teams more frequently than NFL trades, you know, free agents during the regular season, right? Or players become free agents. And that's because their infrastructure. So the, you know, infrastructure, the servers, the systems that they're using to conduct these attacks from is actually largely being disrupted more from law enforcement, international intelligence agencies working together with public private partnerships. So what they're doing is saying, okay, great. All that infrastructure that I just had now is, is burned, right? It's no longer effective. So then they'll disband a team and then they'll recruit a new team and it's constant like mixing and matching in players. >>All that said, even though that's highly dynamic, one of the other areas that they pride themselves on is customer service. So, and I think it's interesting because, you know, when I said they're not wanting to like do all the decryption? Yeah. Cuz that's like painful techni technical slow work. But on the customer service side, they will create these customer service portals immediately stand one up, say, you know, hey it's, it's like an Amazon, you know, if you've ever had to return a package on Amazon for example, and you need to click through and like explain, you know, Hey, I didn't receive this package. A portal window pops up, you start talking to either a bot or a live agent on the backend. In this case they're hu what appeared to be very much humans who are explaining to you exactly what happened, what they're asking for, super pleasant, getting back within minutes of a response. And they know that in order for them to get paid, they need to have good customer service because otherwise they're not going to, you know, have a business. How, >>So what's the state of play look like from between nation states, criminals and how, how difficult or not so difficult is it for you to identify? Do you have clear signatures? My understanding in with Solar Winds it was a little harder, but maybe help us understand and help our audience understand what the state of play is right now. >>One of the interesting things that I think is occurring, and I highlighted this this morning, is this idea of convergence. And so I'll break it down for one example relates to the type of malware or tools that these attackers use. So traditionally, if we looked at a nation state actor like China or Russia, they were very, very specific and very strategic about the types of victims that they were going to go after when they had zero day. So, you know, new, new malware out there, new vulnerabilities that could be exploited only by them because the rest of the world didn't know about it. They might have one organization that they would target that at, at most, a handful and all very strategic for their objective. They wanted to keep that a secret as long as possible. Now what we're seeing actually is those same attackers going towards one, a much larger supply chain. >>So, so lorenzen is a great example of that. The Hafnia attacks towards Microsoft Exchange server last year. All great examples of that. But what they're also doing is instead of using zero days as much, or you know, because those are expensive to build, they take a lot of time, a lot of funding, a lot of patience and research. What they're doing is using commercially available tools. And so there's a tool that our team identified earlier this year called Brute Rael, C4 or BRC four for short. And that's a tool that we now know that nation state actors are using. But just two weeks ago we invested a ransomware attack where the ransomware actor was using that same piece of tooling. So to your point, yak can get difficult for defenders when you're looking through and saying, well wait, they're all using some of the same tools right now and some of the same approaches when it comes to nation states, that's great for them because they can blend into the noise and it makes it harder to identify as >>Quickly. And, and is that an example of living off the land or is that B BRC four sort of a homegrown hacker tool? Is it, is it a, is it a commercial >>Off the shelf? So it's a tool that was actually, so you can purchase it, I believe it's about 2,500 US dollars for a license. It was actually created by a former Red teamer from a couple well-known companies in the industry who then decided, well hey, I built this tool for work, I'm gonna sell this. Well great for Red teamers that are, you know, legitimately doing good work, but not great now because they're, they built a, a strong tool that has the ability to hide amongst a, a lot of protocols. It can actually hide within Slack and teams to where you can't even see the data is being exfiltrated. And so there's a lot of concern. And then now the reality that it gets into the wrong hands of nation state actors in ransomware actors, one of the really interesting things about that piece of malware is it has a setting where you can change wallpaper. And I don't know if you know offhand, you know what that means, but you know, if that comes to mind, what you would do with it. Well certainly a nation state actor is never gonna do something like that, right? But who likes to do that are ransomware actors who can go in and change the background wallpaper on a desktop that says you've been hacked by XYZ organization and let you know what's going on. So pretty interesting, obviously the developer doing some work there for different parts of the, you know, nefarious community. >>Tremendous amount of sophistication that's gone on the last couple of years alone. I was just reading that Unit 42 is now a founding member of the Cyber Threat Alliance includes now more than 35 organizations. So you guys are getting a very broad picture of today's threat landscape. How can customers actually achieve cyber resilience? Is it achievable and how do you help? >>So I, I think it is achievable. So let me kind of parse out the question, right. So the Cyber Threat Alliance, the J C D C, the Cyber Safety Review Board, which I'm a member of, right? I think one of the really cool things about Palo Alto Networks is just our partnerships. So those are just a handful. We've got partnerships with over 200 organizations. We work closely with the Ukrainian cert, for example, sharing information, incredible information about like what's going on in the war, sharing technical details. We do that with Interpol on a daily basis where, you know, we're sharing information. Just last week the Africa cyber surge operation was announced where millions of nodes were taken down that were part of these larger, you know, system of C2 channels that attackers are using to conduct exploits and attacks throughout the world. So super exciting in that regard and it's something that we're really passionate about at Palo Alto Networks in terms of resilience, a few things, you know, one is visibility, so really having a, an understanding of in a real, as much of real time as possible, right? What's happening. And then it goes into how you, how can we decrease operational impact. So that's everything from network segmentation to wanna add the terms and phrases I like to use a lot is the win is really increasing the time it takes for the attackers to get their work done and decreasing the amount of time it takes for the defenders to get their work done, right? >>Yeah. I I call it increasing the denominator, right? And the ROI equation benefit over or value, right? Equals equals or benefit equals value over cost if you can increase the cost to go go elsewhere, right? Absolutely. And that's the, that's the game. Yeah. You mentioned Ukraine before, what have we learned from Ukraine? I, I remember I was talking to Robert Gates years ago, 2016 I think, and I was asking him, yeah, but don't we have the best cyber technology? Can't we attack? He said, we got the most to lose too. Yeah. And so what have we learned from, from Ukraine? >>Well, I, I think that's part of the key point there, right? Is you know, a great offense essentially can also be for us, you know, deterrent. So in that aspect we have as an, as a company and or excuse me, as a country, as a company as well, but then as partners throughout all parts of the world have really focused on increasing the intelligence sharing and specifically, you know, I mentioned Ukrainian cert. There are so many different agencies and other sorts throughout the world that are doing everything they can to share information to help protect human life there. And so what we've really been concerned with, with is, you know, what cyber warfare elements are going to be used there, not only how does that impact Ukraine, but how does it potentially spread out to other parts of the world critical infrastructure. So you've seen that, you know, I mentioned CS rrb, but cisa, right? >>CISA has done a tremendous job of continuously getting out information and doing everything they can to make sure that we are collaborating at a commercial level. You know, we are sharing information and intelligence more than ever before. So partners like Mania and CrowdStrike, our Intel teams are working together on a daily basis to make sure that we're able to protect not only our clients, but certainly if we've got any information relevant that we can share that as well. And I think if there's any silver lining to an otherwise very awful situation, I think the fact that is has accelerated intelligence sharing is really positive. >>I was gonna ask you about this cause I think, you know, 10 or so years ago, there was a lot of talk about that, but the industry, you know, kind of kept things to themselves, you know, a a actually tried to monetize some of that private data. So that's changing is what I'm hearing from you >>More so than ever more, you know, I've, I mentioned I've been in the field for 20 years. You know, it, it's tough when you have a commercial business that relies on, you know, information to, in order to pay people's salaries, right? I think that has changed quite a lot. We see the benefit of just that continuous sharing. There are, you know, so many more walls broken down between these commercial competitors, but also the work on the public private partnership side has really increased some of those relationships. Made it easier. And you know, I have to give a whole lot of credit and mention sisa, like the fact that during log four J, like they had GitHub repositories, they were using Slack, they were using Twitter. So the government has really started pushing forward with a lot of the newer leadership that's in place to say, Hey, we're gonna use tools and technology that works to share and disseminate information as quickly as we can. Right? That's fantastic. That's helping everybody. >>We knew that every industry, no, nobody's spared of this. But did you notice in the last couple of years, any industries in particular that are more vulnerable? Like I think of healthcare with personal health information or financial services, any industries kind of jump out as being more susceptible than others? >>So I think those two are always gonna be at the forefront, right? Financial services and healthcare. But what's been really top of mind is critical infrastructure, just making sure right? That our water, our power, our fuel, so many other parts of right, the ecosystem that go into making sure that, you know, we're keeping, you know, houses heated during the winter, for example, that people have fresh water. Those are extremely critical. And so that is really a massive area of focus for the industry right now. >>Can I come back to public-private partnerships? My question is relates to regulations because the public policy tends to be behind tech, the technology industry as an understatement. So when you take something like GDPR is the obvious example, but there are many, many others, data sovereignty, you can't move the data. Are are, are, is there tension between your desire as our desire as an industry to share data and government's desire to keep data private and restrict that data sharing? How is that playing out? How do you resolve that? >>Well I think there have been great strides right in each of those areas. So in terms of regulation when it comes to breaches there, you know, has been a tendency in the past to do victim shaming, right? And for organizations to not want to come forward because they're concerned about the monetary funds, right? I think there's been tremendous acceleration. You're seeing that everywhere from the fbi, from cisa, to really working very closely with organizations to, to have a true impact. So one example would be a ransomware attack that occurred. This was for a client of ours within the United States and we had a very close relationship with the FBI at that local field office and made a phone call. This was 7:00 AM Eastern time. And this was an organization that had this breach gone public, would've made worldwide news. There would've been a very big impact because it would've taken a lot of their systems offline. >>Within the 30 minutes that local FBI office was on site said, we just saw this piece of malware last week, we have a decryptor for it from another organization who shared it with us. Here you go. And within 60 minutes, every system was back up and running. Our teams were able to respond and get that disseminated quickly. So efforts like that, I think the government has made a tremendous amount of headway into improving relationships. Is there always gonna be some tension between, you know, competing, you know, organizations? Sure. But I think that we're doing a whole lot to progress it, >>But governments will make exceptions in that case. Especially for something as critical as the example that you just gave and be able to, you know, do a reach around, if you will, on, on onerous regulations that, that ne aren't helpful in that situation, but certainly do a lot of good in terms of protecting privacy. >>Well, and I think there used to be exceptions made typically only for national security elements, right? And now you're seeing that expanding much more so, which I think is also positive. Right. >>Last question for you as we are wrapping up time here. What can organizations really do to stay ahead of the curve when it comes to, to threat actors? We've got internal external threats. What can they really do to just be ahead of that curve? Is that possible? >>Well, it is now, it's not an easy task so I'm not gonna, you know, trivialize it. But I think that one, having relationships with right organizations in advance always a good thing. That's a, everything from certainly a commercial relationships, but also your peers, right? There's all kinds of fantastic industry spec specific information sharing organizations. I think the biggest thing that impacts is having education across your executive team and testing regularly, right? Having a plan in place, testing it. And it's not just the security pieces of it, right? As security responders, we live these attacks every day, but it's making sure that your general counsel and your head of operations and your CEO knows what to do. Your board of directors, do they know what to do when they receive a phone call from Bloomberg, for example? Are they supposed supposed to answer? Do your employees know that those kind of communications in advance and training can be really critical and make or break a difference in an attack. >>That's a great point about the testing but also the communication that it really needs to be company wide. Everyone at every level needs to know how to react. Wendy, it's been so great having, >>Wait one last question. Sure. Do you have a favorite superhero growing up? >>Ooh, it's gotta be Wonder Woman. Yeah, >>Yeah, okay. Yeah, so cuz I'm always curious, there's not a lot of women in, in security in cyber. How'd you get into it? And many cyber pros like wanna save the world? >>Yeah, no, that's a great question. So I joined the Air Force, you know, I, I was a special agent doing computer crime investigations and that was a great job. And I learned about that from, we had an alumni day and all these alumni came in from the university and they were in flight suits and combat gear. And there was one woman who had long blonde flowing hair and a black suit and high heels and she was carrying a gun. What did she do? Because that's what I wanted do. >>Awesome. Love it. We >>Blonde >>Wonder Woman. >>Exactly. Wonder Woman. Wendy, it's been so great having you on the program. We, we will definitely be following unit 42 and all the great stuff that you guys are doing. Keep up the good >>Work. Thanks so much Lisa. Thank >>You. Day our pleasure. For our guest and Dave Valante, I'm Lisa Martin, live in Las Vegas at MGM Grand for Palo Alto Ignite, 22. You're watching the Cube, the leader in live enterprise and emerging tech coverage.

>>Hello, welcome to the Cube here in Palo Alto, California for a special presentation on Cloud native at scale, enabling super cloud modern applications with Platform nine. I'm John Furr, your host of The Cube. We had a great lineup of three interviews we're streaming today. Meor Ma Makowski, who's the co-founder and VP of Product of Platform nine. She's gonna go into detail around Arlon, the open source products, and also the value of what this means for infrastructure as code and for cloud native at scale. Bickley the chief architect of Platform nine Cube alumni. Going back to the OpenStack days. He's gonna go into why Arlon, why this infrastructure as code implication, what it means for customers and the implications in the open source community and where that value is. Really great wide ranging conversation there. And of course, Vascar, Gort, the CEO of Platform nine, is gonna talk with me about his views on Super Cloud and why Platform nine has a scalable solutions to bring cloudnative at scale. So enjoy the program. See you soon. Hello everyone. Welcome to the cube here in Palo Alto, California for special program on cloud native at scale, enabling next generation cloud or super cloud for modern application cloud native developers. I'm John Furry, host of the Cube. A pleasure to have here, me Makoski, co-founder and VP of product at Platform nine. Thanks for coming in today for this Cloudnative at scale conversation. Thank >>You for having me. >>So Cloudnative at scale, something that we're talking about because we're seeing the, the next level of mainstream success of containers Kubernetes and cloud native develop, basically DevOps in the C I C D pipeline. It's changing the landscape of infrastructure as code, it's accelerating the value proposition and the super cloud as we call it, has been getting a lot of traction because this next generation cloud is looking a lot different, but kind of the same as the first generation. What's your view on super cloud as it fits to cloud native as scales up? >>Yeah, you know, I think what's interesting, and I think the reason why Super Cloud is a really good, in a really fit term for this, and I think, I know my CEO was chatting with you as well, and he was mentioning this as well, but I think there needs to be a different term than just multi-cloud or cloud. And the reason is because as cloud native and cloud deployments have scaled, I think we've reached a point now where instead of having the traditional data center style model where you have a few large distributions of infrastructure and workload at a few locations, I think the model is kind of flipped around, right? Where you have a large number of microsites, these microsites could be your public cloud deployment, your private on-prem infrastructure deployments, or it could be your edge environment, right? And every single enterprise, every single industry is moving in that direction. And so you gotta rougher that with a terminology that, that, that indicates the scale and complexity of it. And so I think supercloud is a, is an appropriate term for that. >>So you brought a couple of things I want to dig into. You mentioned edge nodes. We're seeing not only edge nodes being the next kind of area of innovation, mainly because it's just popping up everywhere. And that's just the beginning. Wouldn't even know what's around the corner. You got buildings, you got iot, ot, and IT kind of coming together, but you also got this idea of regions, global infras infrastructures, big part of it. I just saw some news around CloudFlare shutting down a site here. There's policies being made at scale, These new challenges there. Can you share because you can have edge. So hybrid cloud is a winning formula. Everybody knows that it's a steady state. Yeah. But across multiple clouds brings in this new un engineered area, yet it hasn't been done yet. Spanning clouds. People say they're doing it, but you start to see the toe in the water, it's happening, it's gonna happen. It's only gonna get accelerated with the edge and beyond globally. So I have to ask you, what is the technical challenges in doing this? Because there's something business consequences as well, but there are technical challenges. Can you share your view on what the technical challenges are for the super cloud or across multiple edges and regions? >>Yeah, absolutely. So I think, you know, in in the context of this, the, this, this term of super cloud, I think it's sometimes easier to visualize things in terms of two access, right? I think on one end you can think of the scale in terms of just pure number of nodes that you have deploy a number of clusters in the Kubernetes space. And then on the other axis you would have your distribution factor, right? Which is, do you have these tens of thousands of nodes in one site or do you have them distributed across tens of thousands of sites with one node at each site? Right? And if you have just one flavor of this, there is enough complexity, but potentially manageable. But when you are expanding on both these access, you really get to a point where that scale really needs some well thought out, well structured solutions to address it, right? A combination of homegrown tooling along with your, you know, favorite distribution of Kubernetes is not a strategy that can help you in this environment. It may help you when you have one of this or when you, when you scale, is not at the level. >>Can you scope the complexity? Because I mean, I hear a lot of moving parts going on there, the technology's also getting better. We we're seeing cloud native become successful. There's a lot to configure, there's a lot to install. Can you scope the scale of the problem? Because we're talking about at scale Yep. Challenges here. Yeah, >>Absolutely. And I think, you know, I I like to call it, you know, the, the, the problem that the scale creates, you know, there's various problems, but I think one, one problem, one way to think about it is, is, you know, it works on my cluster problem, right? So I, you know, I come from engineering background and there's a, you know, there's a famous saying between engineers and QA and the support folks, right? Which is, it works on my laptop, which is I tested this chain, everything was fantastic, it worked flawlessly on my machine, on production, It's not working. The exact same problem now happens and these distributed environments, but at massive scale, right? Which is that, you know, developers test their applications, et cetera within the sanctity of their sandbox environments. But once you expose that change in the wild world of your production deployment, right? >>And the production deployment could be going at the radio cell tower at the edge location where a cluster is running there, or it could be sending, you know, these applications and having them run at my customer site where they might not have configured that cluster exactly the same way as I configured it, or they configured the cluster, right? But maybe they didn't deploy the security policies, or they didn't deploy the other infrastructure plugins that my app relies on. All of these various factors are their own layer of complexity. And there really isn't a simple way to solve that today. And that is just, you know, one example of an issue that happens. I think another, you know, whole new ball game of issues come in the context of security, right? Because when you are deploying applications at scale in a distributed manner, you gotta make sure someone's job is on the line to ensure that the right security policies are enforced regardless of that scale factor. So I think that's another example of problems that occur. >>Okay. So I have to ask about scale, because there are a lot of multiple steps involved when you see the success of cloud native. You know, you see some, you know, some experimentation. They set up a cluster, say it's containers and Kubernetes, and then you say, Okay, we got this, we can figure it. And then they do it again and again, they call it day two. Some people call it day one, day two operation, whatever you call it. Once you get past the first initial thing, then you gotta scale it. Then you're seeing security breaches, you're seeing configuration errors. This seems to be where the hotspot is in when companies transition from, I got this to, Oh no, it's harder than I thought at scale. Can you share your reaction to that and how you see this playing out? >>Yeah, so, you know, I think it's interesting. There's multiple problems that occur when, you know, the two factors of scale, as we talked about, start expanding. I think one of them is what I like to call the, you know, it, it works fine on my cluster problem, which is back in, when I was a developer, we used to call this, it works on my laptop problem, which is, you know, you have your perfectly written code that is operating just fine on your machine, your sandbox environment. But the moment it runs production, it comes back with p zeros and pos from support teams, et cetera. And those issues can be really difficult to triage us, right? And so in the Kubernetes environment, this problem kind of multi folds, it goes, you know, escalates to a higher degree because you have your sandbox developer environments, they have their clusters and things work perfectly fine in those clusters because these clusters are typically handcrafted or a combination of some scripting and handcrafting. >>And so as you give that change to then run at your production edge location, like say your radio cell tower site, or you hand it over to a customer to run it on their cluster, they might not have not have configured that cluster exactly how you did, or they might not have configured some of the infrastructure plugins. And so the things don't work. And when things don't work, triaging them becomes nightmarishly hard, right? It's just one of the examples of the problem, another whole bucket of issues is security, which is, is you have these distributed clusters at scale, you gotta ensure someone's job is on the line to make sure that these security policies are configured properly. >>So this is a huge problem. I love that comment. That's not not happening on my system. It's the classic, you know, debugging mentality. Yeah. But at scale it's hard to do that with error prone. I can see that being a problem. And you guys have a solution you're launching. Can you share what Arlon is this new product? What is it all about? Talk about this new introduction. >>Yeah, absolutely. Very, very excited. You know, it's one of the projects that we've been working on for some time now because we are very passionate about this problem and just solving problems at scale in on-prem or at in the cloud or at edge environments. And what arlon is, it's an open source project, and it is a tool, it's a Kubernetes native tool for complete end to end management of not just your clusters, but your clusters. All of the infrastructure that goes within and along the site of those clusters, security policies, your middleware, plug-ins, and finally your applications. So what our LA you do in a nutshell is in a declarative way, it lets you handle the configuration and management of all of these components in at scale. >>So what's the elevator pitch simply put for what dissolves in, in terms of the chaos you guys are reigning in, what's the, what's the bumper sticker? Yeah, what >>Would it do? There's a perfect analogy that I love to reference in this context, which is think of your assembly line, you know, in a traditional, let's say, you know, an auto manufacturing factory or et cetera, and the level of efficiency at scale that that assembly line brings, right? Our line, and if you look at the logo we've designed, it's this funny little robot. And it's because when we think of online, we think of these enterprise large scale environments, you know, sprawling at scale, creating chaos because there isn't necessarily a well thought through, well structured solution that's similar to an assembly line, which is taking each component, you know, addressing them, manufacturing, processing them in a standardized way, then handing to the next stage. But again, it gets, you know, processed in a standardized way. And that's what arlon really does. That's like the deliver pitch. If you have problems of scale of managing your infrastructure, you know, that is distributed. Arlon brings the assembly line level of efficiency and consistency for >>Those. So keeping it smooth, the assembly on things are flowing. See c i CD pipe pipelining. Exactly. So that's what you're trying to simplify that ops piece for the developer. I mean, it's not really ops, it's their ops, it's coding. >>Yeah. Not just developer, the ops, the operations folks as well, right? Because developers, you know, there is, developers are responsible for one picture of that layer, which is my apps, and then maybe that middleware of applications that they interface with, but then they hand it over to someone else who's then responsible to ensure that these apps are secure properly, that they are logging, logs are being collected properly, monitoring and observability integrated. And so it solves problems for both >>Those teams. Yeah. It's DevOps. So the DevOps is the cloud needed developer's. That's right. The option teams have to kind of set policies. Is that where the declarative piece comes in? Is that why that's important? >>Absolutely. Yeah. And, and, and, and you know, ES really in introduced or elevated this declarative management, right? Because, you know, s clusters are Yeah. Or your, yeah, you know, specifications of components that go in Kubernetes are defined a declarative way, and Kubernetes always keeps that state consistent with your defined state. But when you go outside of that world of a single cluster, and when you actually talk about defining the clusters or defining everything that's around it, there really isn't a solution that does that today. And so Arlon addresses that problem at the heart of it, and it does that using existing open source well known solutions. >>And do I want to get into the benefits? What's in it for me as the customer developer? But I want to finish this out real quick and get your thoughts. You mentioned open source. Why open source? What's the, what's the current state of the product? You run the product group over at Platform nine, is it open source? And you guys have a product that's commercial? Can you explain the open source dynamic? And first of all, why open source? Yeah. And what is the consumption? I mean, open source is great, People want open source, they can download it, look up the code, but maybe wanna buy the commercial. So I'm assuming you have that thought through, can you share open source and commercial relationship? >>Yeah, I think, you know, starting with why open source? I think it's, you know, we as a company, we have, you know, one of the things that's absolutely critical to us is that we take mainstream open source technologies components and then we, you know, make them available to our customers at scale through either a SaaS model or on-prem model, right? But, so as we are a company or startup or a company that benefits, you know, in a massive way by this open source economy, it's only right, I think in my mind that we do our part of the duty, right? And contribute back to the community that feeds us. And so, you know, we have always held that strongly as one of our principles. And we have, you know, created and built independent products starting all the way with fision, which was a serverless product, you know, that we had built to various other, you know, examples that I can give. But that's one of the main reasons why opensource and also open source, because we want the community to really firsthand engage with us on this problem, which is very difficult to achieve if your product is behind a wall, you know, behind, behind a block box. >>Well, and that's, that's what the developers want too. And what we're seeing in reporting with Super Cloud is the new model of consumption is I wanna look at the code and see what's in there. That's right. And then also, if I want to use it, I'll do it. Great. That's open source, that's the value. But then at the end of the day, if I wanna move fast, that's when people buy in. So it's a new kind of freemium, I guess, business model. I guess that's the way that long. But that's, that's the benefit. Open source. This is why standards and open source is growing so fast. You have that confluence of, you know, a way for developers to try before they buy, but also actually kind of date the application, if you will. We, you know, Adrian Karo uses the dating met metaphor, you know, Hey, you know, I wanna check it out first before I get married. Right? And that's what open source, So this is the new, this is how people are selling. This is not just open source, this is how companies are selling. >>Absolutely. Yeah. Yeah. You know, I think, and you know, two things. I think one is just, you know, this, this, this cloud native space is so vast that if you, if you're building a close flow solution, sometimes there's also a risk that it may not apply to every single enterprises use cases. And so having it open source gives them an opportunity to extend it, expand it, to make it proper to their use case if they choose to do so, right? But at the same time, what's also critical to us is we are able to provide a supported version of it with an SLA that we, you know, that's backed by us, a SAS hosted version of it as well, for those customers who choose to go that route, you know, once they have used the open source version and loved it and want to take it at scale and in production and need, need, need a partner to collaborate with, who can, you know, support them for that production >>Environment. I have to ask you now, let's get into what's in it for the customer. I'm a customer. Yep. Why should I be enthused about Arla? What's in it for me? You know? Cause if I'm not enthused about it, I'm not gonna be confident and it's gonna be hard for me to get behind this. Can you share your enthusiastic view of, you know, why I should be enthused about Arlo? I'm a >>Customer. Yeah, absolutely. And so, and there's multiple, you know, enterprises that we talk to, many of them, you know, our customers, where this is a very kind of typical story that you hear, which is we have, you know, a Kubernetes distribution. It could be on premise, it could be public clouds, native Kubernetes, and then we have our C I C D pipelines that are automating the deployment of applications, et cetera. And then there's this gray zone. And the gray zone is well before you can you, your CS c D pipelines can deploy the apps. Somebody needs to do all of that groundwork of, you know, defining those clusters and yeah. You know, properly configuring them. And as these things, these things start by being done hand grown. And then as the, as you scale, what typically enterprises would do today is they will have their home homegrown DIY solutions for this. >>I mean, the number of folks that I talk to that have built Terra from automation, and then, you know, some of those key developers leave. So it's a typical open source or typical, you know, DIY challenge. And the reason that they're writing it themselves is not because they want to. I mean, of course technology is always interesting to everybody, but it's because they can't find a solution that's out there that perfectly fits the problem. And so that's that pitch. I think Ops FICO would be delighted. The folks that we've talk, you know, spoken with, have been absolutely excited and have, you know, shared that this is a major challenge we have today because we have, you know, few hundreds of clusters on ecos Amazon, and we wanna scale them to few thousands, but we don't think we are ready to do that. And this will give us the >>Ability to, Yeah, I think people are scared. Not sc I won't say scare, that's a bad word. Maybe I should say that they feel nervous because, you know, at scale small mistakes can become large mistakes. This is something that is concerning to enterprises. And, and I think this is gonna come up at co con this year where enterprises are gonna say, Okay, I need to see SLAs. I wanna see track record, I wanna see other companies that have used it. Yeah. How would you answer that question to, or, or challenge, you know, Hey, I love this, but is there any guarantees? Is there any, what's the SLAs? I'm an enterprise, I got tight, you know, I love the open source trying to free fast and loose, but I need hardened code. >>Yeah, absolutely. So, so two parts to that, right? One is Arlan leverages existing open source components, products that are extremely popular. Two specifically. One is Arlan uses Argo cd, which is probably one of the highest and used CD open source tools that's out there. Right's created by folks that are as part of into team now, you know, really brilliant team. And it's used at scale across enterprises. That's one. Second is Alon also makes use of Cluster api cappi, which is a Kubernetes sub-component, right? For lifecycle management of clusters. So there is enough of, you know, community users, et cetera, around these two products, right? Or, or, or open source projects that will find Arlan to be right up in their alley because they're already comfortable, familiar with Argo cd. Now Arlan just extends the scope of what City can do. And so that's one. And then the second part is going back to a point of the comfort. And that's where, you know, platform line has a role to play, which is when you are ready to deploy online at scale, because you've been, you know, playing with it in your DEF test environments, you're happy with what you get with it, then Platform nine will stand behind it and provide that >>Sla. And what's been the reaction from customers you've talked to Platform nine customers with, with that are familiar with, with Argo and then rlo? What's been some of the feedback? >>Yeah, I, I think the feedback's been fantastic. I mean, I can give you examples of customers where, you know, initially, you know, when you are, when you're telling them about your entire portfolio of solutions, it might not strike a card right away. But then we start talking about Arlan and, and we talk about the fact that it uses Argo adn, they start opening up, they say, We have standardized on Argo and we have built these components, homegrown, we would be very interested. Can we co-develop? Does it support these use cases? So we've had that kind of validation. We've had validation all the way at the beginning of our land before we even wrote a single line of code saying this is something we plan on doing. And the customer said, If you had it today, I would've purchased it. So it's been really great validation. >>All right. So next question is, what is the solution to the customer? If I asked you, Look it, I have, I'm so busy, my team's overworked. I got a skills gap. I don't need another project that's, I'm so tied up right now and I'm just chasing my tail. How does Platform nine help me? >>Yeah, absolutely. So I think, you know, one of the core tenets of Platform nine has always been been that we try to bring that public cloud like simplicity by hosting, you know, this in a lot of such similar tools in a SaaS hosted manner for our customers, right? So our goal behind doing that is taking away or trying to take away all of that complexity from customers' hands and offloading it to our hands, right? And giving them that full white glove treatment, as we call it. And so from a customer's perspective, one, something like arlon will integrate with what they have so they don't have to rip and replace anything. In fact, it will, even in the next versions, it may even discover your clusters that you have today and you know, give you an inventory. And that will, >>So if customers have clusters that are growing, that's a sign correct call you guys. >>Absolutely. Either they're, they have massive large clusters, right? That they wanna split into smaller clusters, but they're not comfortable doing that today, or they've done that already on say, public cloud or otherwise. And now they have management challenges. So >>Especially operationalizing the clusters, whether they want to kind of reset everything and remove things around and reconfigure Yep. And or scale out. >>That's right. Exactly. And >>You provide that layer of policy. >>Absolutely. >>Yes. That's the key value here. >>That's right. >>So policy based configuration for cluster scale up, >>Well profile and policy based declarative configuration and lifecycle management for clusters. >>If I asked you how this enables supercloud, what would you say to that? >>I think this is one of the key ingredients to super cloud, right? If you think about a super cloud environment, there's at least few key ingredients that that come to my mind that are really critical. Like they are, you know, life saving ingredients at that scale. One is having a really good strategy for managing that scale, you know, in a, going back to assembly line in a very consistent, predictable way so that our lot solves then you, you need to compliment that with the right kind of observability and monitoring tools at scale, right? Because ultimately issues are gonna happen and you're gonna have to figure out, you know, how to solve them fast. And arlon by the way, also helps in that direction, but you also need observability tools. And then especially if you're running it on the public cloud, you need some cost management tools. In my mind, these three things are like the most necessary ingredients to make Super Cloud successful. And you know, our alarm fills in >>One. Okay. So now the next level is, Okay, that makes sense. Is under the covers kind of speak under the hood. Yeah. How does that impact the app developers and the cloud native modern application workflows? Because the impact to me, seems the apps are gonna be impacted. Are they gonna be faster, stronger? I mean, what's the impact if you do all those things, as you mentioned, what's the impact of the apps? >>Yeah, the impact is that your apps are more likely to operate in production the way you expect them to, because the right checks and balances have gone through, and any discrepancies have been identified prior to those apps, prior to your customer running into them, right? Because developers run into this challenge to their, where there's a split responsibility, right? I'm responsible for my code, I'm responsible for some of these other plugins, but I don't own the stack end to end. I have to rely on my ops counterpart to do their part, right? And so this really gives them, you know, the right tooling for that. >>So this is actually a great kind of relevant point, you know, as cloud becomes more scalable, you're starting to see this fragmentation gone of the days of the full stack developer to the more specialized role. But this is a key point, and I have to ask you because if this RLO solution takes place, as you say, and the apps are gonna be stupid, they're designed to do, the question is, what did does the current pain look like of the apps breaking? What does the signals to the customer Yeah. That they should be calling you guys up into implementing Arlo, Argo and, and all the other goodness to automate? What are some of the signals? Is it downtime? Is it, is it failed apps, Is it latency? What are some of the things that Yeah, absolutely would be indications of things are effed up a little bit. Yeah. >>More frequent down times, down times that are, that take longer to triage. And so you are, you know, the, you know, your mean times on resolution, et cetera, are escalating or growing larger, right? Like we have environments of customers where they're, they have a number of folks on in the field that have to take these apps and run them at customer sites. And that's one of our partners. And they're extremely interested in this because they're the, the rate of failures they're encountering for this, you know, the field when they're running these apps on site, because the field is automating their clusters that are running on sites using their own script. So these are the kinds of challenges, and those are the pain points, which is, you know, if you're looking to reduce your meantime to resolution, if you're looking to reduce the number of failures that occur on your production site, that's one. And second, if you are looking to manage these at scale environments with a relatively small, focused, nimble ops team, which has an immediate impact on your budget. So those are, those are the signals. >>This is the cloud native at scale situation, the innovation going on. Final thought is your reaction to the idea that if the world goes digital, which it is, and the confluence of physical and digital coming together, and cloud continues to do its thing, the company becomes the application, not where it used to be supporting the business, you know, the back office and the maybe terminals and some PCs and handhelds. Now if technology's running, the business is the business. Yeah. Company's the application. Yeah. So it can't be down. So there's a lot of pressure on, on CSOs and CIOs now and boards is saying, How is technology driving the top line revenue? That's the number one conversation. Yep. Do you see that same thing? >>Yeah. It's interesting. I think there's multiple pressures at the CXO CIO level, right? One is that there needs to be that visibility and clarity and guarantee almost that, you know, that the, the technology that's, you know, that's gonna drive your top line is gonna drive that in a consistent, reliable, predictable manner. And then second, there is the constant pressure to do that while always lowering your costs of doing it, right? Especially when you're talking about, let's say retailers or those kinds of large scale vendors, they many times make money by lowering the amount that they spend on, you know, providing those goods to their end customers. So I think those, both those factors kind of come into play and the solution to all of them is usually in a very structured strategy around automation. >>Final question. What does cloudnative at scale look like to you? If all the things happen the way we want 'em to happen, The magic wand, the magic dust, what does it look like? >>What that looks like to me is a CIO sipping at his desk on coffee production is running absolutely smooth. And his, he's running that at a nimble, nimble team size of at the most, a handful of folks that are just looking after things, but things are >>Just taking care of the CIO doesn't exist. There's no ciso, they're at the beach. >>Yep. >>Thank you for coming on, sharing the cloud native at scale here on the cube. Thank you for your time. >>Fantastic. Thanks for >>Having me. Okay. I'm John Fur here for special program presentation, special programming cloud native at scale, enabling super cloud modern applications with Platform nine. Thanks for watching. Welcome back everyone to the special presentation of cloud native at scale, the cube and platform nine special presentation going in and digging into the next generation super cloud infrastructure as code and the future of application development. We're here with Bickley, who's the chief architect and co-founder of Platform nine Pick. Great to see you Cube alumni. We, we met at an OpenStack event in about eight years ago, or later, earlier when OpenStack was going. Great to see you and great to see congratulations on the success of platform nine. >>Thank you very much. >>Yeah. You guys have been at this for a while and this is really the, the, the year we're seeing the, the crossover of Kubernetes because of what happens with containers. Everyone now has realized, and you've seen what Docker's doing with the new docker, the open source Docker now just the success Exactly. Of containerization, right? And now the Kubernetes layer that we've been working on for years is coming, bearing fruit. This is huge. >>Exactly. Yes. >>And so as infrastructures code comes in, we talked to Bacar talking about Super Cloud, I met her about, you know, the new Arlon, our, our lawn, and you guys just launched the infrastructures code is going to another level, and then it's always been DevOps infrastructures code. That's been the ethos that's been like from day one, developers just code. Then you saw the rise of serverless and you see now multi-cloud or on the horizon, connect the dots for us. What is the state of infrastructure as code today? >>So I think, I think I'm, I'm glad you mentioned it, everybody or most people know about infrastructures code. But with Kubernetes, I think that project has evolved at the concept even further. And these dates, it's infrastructure is configuration, right? So, which is an evolution of infrastructure as code. So instead of telling the system, here's how I want my infrastructure by telling it, you know, do step A, B, C, and D instead with Kubernetes, you can describe your desired state declaratively using things called manifest resources. And then the system kind of magically figures it out and tries to converge the state towards the one that you specified. So I think it's, it's a even better version of infrastructures code. >>Yeah. And that really means it's developer just accessing resources. Okay. That declare, Okay, give me some compute, stand me up some, turn the lights on, turn 'em off, turn 'em on. That's kind of where we see this going. And I like the configuration piece. Some people say composability, I mean now with open source so popular, you don't have to have to write a lot of code, this code being developed. And so it's into integration, it's configuration. These are areas that we're starting to see computer science principles around automation, machine learning, assisting open source. Cuz you got a lot of code that's right in hearing software, supply chain issues. So infrastructure as code has to factor in these new dynamics. Can you share your opinion on these new dynamics of, as open source grows, the glue layers, the configurations, the integration, what are the core issues? >>I think one of the major core issues is with all that power comes complexity, right? So, you know, despite its expressive power systems like Kubernetes and declarative APIs let you express a lot of complicated and complex stacks, right? But you're dealing with hundreds if not thousands of these yamo files or resources. And so I think, you know, the emergence of systems and layers to help you manage that complexity is becoming a key challenge and opportunity in, in this space. >>That's, I wrote a LinkedIn post today was comments about, you know, hey, enterprise is a new breed. The trend of SaaS companies moving our consumer comp consumer-like thinking into the enterprise has been happening for a long time, but now more than ever, you're seeing it the old way used to be solve complexity with more complexity and then lock the customer in. Now with open source, it's speed, simplification and integration, right? These are the new dynamic power dynamics for developers. Yeah. So as companies are starting to now deploy and look at Kubernetes, what are the things that need to be in place? Because you have some, I won't say technical debt, but maybe some shortcuts, some scripts here that make it look like infrastructure is code. People have done some things to simulate or or make infrastructure as code happen. Yes. But to do it at scale Yes. Is harder. What's your take on this? What's your view? >>It's hard because there's a per proliferation of methods, tools, technologies. So for example, today it's very common for DevOps and platform engineering tools, I mean, sorry, teams to have to deploy a large number of Kubernetes clusters, but then apply the applications and configurations on top of those clusters. And they're using a wide range of tools to do this, right? For example, maybe Ansible or Terraform or bash scripts to bring up the infrastructure and then the clusters. And then they may use a different set of tools such as Argo CD or other tools to apply configurations and applications on top of the clusters. So you have this sprawl of tools. You, you also have this sprawl of configurations and files because the more objects you're dealing with, the more resources you have to manage. And there's a risk of drift that people call that where, you know, you think you have things under control, but some people from various teams will make changes here and there and then before the end of the day systems break and you have no idea of tracking them. So I think there's real need to kind of unify, simplify, and try to solve these problems using a smaller, more unified set of tools and methodologies. And that's something that we try to do with this new project. Arlon. >>Yeah. So, so we're gonna get into Arlan in a second. I wanna get into the why Arlon. You guys announced that at AR GoCon, which was put on here in Silicon Valley at the, at the community meeting by in two, they had their own little day over there at their headquarters. But before we get there, vascar, your CEO came on and he talked about Super Cloud at our in AAL event. What's your definition of super cloud? If you had to kind of explain that to someone at a cocktail party or someone in the industry technical, how would you look at the super cloud trend that's emerging? It's become a thing. What's your, what would be your contribution to that definition or the narrative? >>Well, it's, it's, it's funny because I've actually heard of the term for the first time today, speaking to you earlier today. But I think based on what you said, I I already get kind of some of the, the gist and the, the main concepts. It seems like super cloud, the way I interpret that is, you know, clouds and infrastructure, programmable infrastructure, all of those things are becoming commodity in a way. And everyone's got their own flavor, but there's a real opportunity for people to solve real business problems by perhaps trying to abstract away, you know, all of those various implementations and then building better abstractions that are perhaps business or applications specific to help companies and businesses solve real business problems. >>Yeah, I remember that's a great, great definition. I remember, not to date myself, but back in the old days, you know, IBM had a proprietary network operating system, so of deck for the mini computer vendors, deck net and SNA respectively. But T C P I P came out of the osi, the open systems interconnect and remember, ethernet beat token ring out. So not to get all nerdy for all the young kids out there, look, just look up token ring, you'll see, you've probably never heard of it. It's IBM's, you know, connection for the internet at the, the layer two is Amazon, the ethernet, right? So if T C P I P could be the Kubernetes and the container abstraction that made the industry completely change at that point in history. So at every major inflection point where there's been serious industry change and wealth creation and business value, there's been an abstraction Yes. Somewhere. Yes. What's your reaction to that? >>I think this is, I think a saying that's been heard many times in this industry and, and I forgot who originated it, but I think that the saying goes like, there's no problem that can't be solved with another layer of indirection, right? And we've seen this over and over and over again where Amazon and its peers have inserted this layer that has simplified, you know, computing and, and infrastructure management. And I believe this trend is going to continue, right? The next set of problems are going to be solved with these insertions of additional abstraction layers. I think that that's really a, yeah, it's gonna >>Continue. It's interesting. I just, when I wrote another post today on LinkedIn called the Silicon Wars AMD stock is down arm has been on a rise. We remember pointing for many years now that arm's gonna be hugely, it has become true. If you look at the success of the infrastructure as a service layer across the clouds, Azure, aws, Amazon's clearly way ahead of everybody. The stuff that they're doing with the silicon and the physics and the, the atoms, the pro, you know, this is where the innovation, they're going so deep and so strong at ISAs, the more that they get that gets come on, they have more performance. So if you're an app developer, wouldn't you want the best performance and you'd wanna have the best abstraction layer that gives you the most ability to do infrastructures, code or infrastructure for configuration, for provisioning, for managing services. And you're seeing that today with service MeSHs, a lot of action going on in the service mesh area in in this community of, of co con, which will be a covering. So that brings up the whole what's next? You guys just announced our lawn at Argo Con, which came out of Intuit. We've had Mariana Tessel at our super cloud event. She's the cto, you know, they're all in the cloud. So they contributed that project. Where did Arlon come from? What was the origination? What's the purpose? Why our lawn, why this announcement? >>Yeah, so the, the inception of the project, this was the result of us realizing that problem that we spoke about earlier, which is complexity, right? With all of this, these clouds, these infrastructure, all the variations around and, you know, compute storage networks and the proliferation of tools we talked about the Ansibles and Terraforms and Kubernetes itself. You can, you can think of that as another tool, right? We saw a need to solve that complexity problem, and especially for people and users who use Kubernetes at scale. So when you have, you know, hundreds of clusters, thousands of applications, thousands of users spread out over many, many locations, there, there needs to be a system that helps simplify that management, right? So that means fewer tools, more expressive ways of describing the state that you want and more consistency. And, and that's why, you know, we built our lawn and we built it recognizing that many of these problems or sub problems have already been solved. So Arlon doesn't try to reinvent the wheel, it instead rests on the shoulders of several giants, right? So for example, Kubernetes is one building block, GI ops, and Argo CD is another one, which provides a very structured way of applying configuration. And then we have projects like cluster API and cross plane, which provide APIs for describing infrastructure. So arlon takes all of those building blocks and builds a thin layer, which gives users a very expressive way of defining configuration and desired state. So that's, that's kind of the inception of, And >>What's the benefit of that? What does that give the, what does that give the developer, the user, in this case, >>The developers, the, the platform engineer, team members, the DevOps engineers, they get a a ways to provision not just infrastructure and clusters, but also applications and configurations. They get a way, a system for provisioning, configuring, deploying, and doing life cycle management in a, in a much simpler way. Okay. Especially as I said, if you're dealing with a large number of applications. >>So it's like an operating fabric, if you will. Yes. For them. Okay, so let's get into what that means for up above and below the the, this abstraction or thin layer below as the infrastructure. We talked a lot about what's going on below that. Yeah. Above our workloads. At the end of the day, you know, I talk to CXOs and IT folks that are now DevOps engineers. They care about the workloads and they want the infrastructures code to work. They wanna spend their time getting in the weeds, figuring out what happened when someone made a push that that happened or something happened. They need observability and they need to, to know that it's working. That's right. And is my workloads running effectively? So how do you guys look at the workload side of it? Cuz now you have multiple workloads on these fabric, >>Right? So workloads, so Kubernetes has defined kind of a standard way to describe workloads and you can, you know, tell Kubernetes, I want to run this container this particular way, or you can use other projects that are in the Kubernetes cloud native ecosystem like K native, where you can express your application in more at a higher level, right? But what's also happening is in addition to the workloads, DevOps and platform engineering teams, they need to very often deploy the applications with the clusters themselves. Clusters are becoming this commodity. It's, it's becoming this host for the application and it kind of comes bundled with it. In many cases it is like an appliance, right? So DevOps teams have to provision clusters at a really incredible rate and they need to tear them down. Clusters are becoming more, >>It's kinda like an EC two instance, spin up a cluster. We very, people used words like that. That's >>Right. And before arlon you kind of had to do all of that using a different set of tools as, as I explained. So with Armon you can kind of express everything together. You can say I want a cluster with a health monitoring stack and a logging stack and this ingress controller and I want these applications and these security policies. You can describe all of that using something we call a profile. And then you can stamp out your app, your applications and your clusters and manage them in a very, so >>Essentially standard creates a mechanism. Exactly. Standardized, declarative kind of configurations. And it's like a playbook. You deploy it. Now what's there is between say a script like I'm, I have scripts, I could just automate scripts >>Or yes, this is where that declarative API and infrastructures configuration comes in, right? Because scripts, yes you can automate scripts, but the order in which they run matters, right? They can break, things can break in the middle and, and sometimes you need to debug them. Whereas the declarative way is much more expressive and powerful. You just tell the system what you want and then the system kind of figures it out. And there are these things about controllers which will in the background reconcile all the state to converge towards your desire. It's a much more powerful, expressive and reliable way of getting things done. >>So infrastructure has configuration is built kind of on, it's as super set of infrastructures code because it's >>An evolution. >>You need edge's code, but then you can configure the code by just saying do it. You basically declaring and saying Go, go do that. That's right. Okay, so, alright, so cloud native at scale, take me through your vision of what that means. Someone says, Hey, what does cloud native at scale mean? What's success look like? How does it roll out in the future as you, not future next couple years? I mean people are now starting to figure out, okay, it's not as easy as it sounds. Could be nice, it has value. We're gonna hear this year coan a lot of this. What does cloud native at scale >>Mean? Yeah, there are different interpretations, but if you ask me, when people think of scale, they think of a large number of deployments, right? Geographies, many, you know, supporting thousands or tens or millions of, of users there, there's that aspect to scale. There's also an equally important a aspect of scale, which is also something that we try to address with Arran. And that is just complexity for the people operating this or configuring this, right? So in order to describe that desired state and in order to perform things like maybe upgrades or updates on a very large scale, you want the humans behind that to be able to express and direct the system to do that in, in relatively simple terms, right? And so we want the tools and the abstractions and the mechanisms available to the user to be as powerful but as simple as possible. So there's, I think there's gonna be a number and there have been a number of CNCF and cloud native projects that are trying to attack that complexity problem as well. And Arlon kind of falls in in that >>Category. Okay, so I'll put you on the spot road that CubeCon coming up and obviously this will be shipping this segment series out before. What do you expect to see at Coan this year? What's the big story this year? What's the, what's the most important thing happening? Is it in the open source community and also within a lot of the, the people jogging for leadership. I know there's a lot of projects and still there's some white space in the overall systems map about the different areas get run time and there's ability in all these different areas. What's the, where's the action? Where, where's the smoke? Where's the fire? Where's the piece? Where's the tension? >>Yeah, so I think one thing that has been happening over the past couple of cons and I expect to continue and, and that is the, the word on the street is Kubernetes is getting boring, right? Which is good, right? >>Boring means simple. >>Well, well >>Maybe, >>Yeah, >>Invisible, >>No drama, right? So, so the, the rate of change of the Kubernetes features and, and all that has slowed but in, in a, in a positive way. But there's still a general sentiment and feeling that there's just too much stuff. If you look at a stack necessary for hosting applications based on Kubernetes, there are just still too many moving parts, too many components, right? Too much complexity. I go, I keep going back to the complexity problem. So I expect Cube Con and all the vendors and the players and the startups and the people there to continue to focus on that complexity problem and introduce further simplifications to, to the stack. >>Yeah. Vic, you've had an storied career, VMware over decades with them obviously in 12 years with 14 years or something like that. Big number co-founder here at Platform. Now you guys have been around for a while at this game. We, man, we talked about OpenStack, that project you, we interviewed at one of their events. So OpenStack was the beginning of that, this new revolution. And I remember the early days it was, it wasn't supposed to be an alternative to Amazon, but it was a way to do more cloud cloud native. I think we had a cloud ERO team at that time. We would to joke we, you know, about, about the dream. It's happening now, now at Platform nine. You guys have been doing this for a while. What's the, what are you most excited about as the chief architect? What did you guys double down on? What did you guys tr pivot from or two, did you do any pivots? Did you extend out certain areas? Cuz you guys are in a good position right now, a lot of DNA in Cloud native. What are you most excited about and what does Platform nine bring to the table for customers and for people in the industry watching this? >>Yeah, so I think our mission really hasn't changed over the years, right? It's been always about taking complex open source software because open source software, it's powerful. It solves new problems, you know, every year and you have new things coming out all the time, right? OpenStack was an example when the Kubernetes took the world by storm. But there's always that complexity of, you know, just configuring it, deploying it, running it, operating it. And our mission has always been that we will take all that complexity and just make it, you know, easy for users to consume regardless of the technology, right? So the successor to Kubernetes, you know, I don't have a crystal ball, but you know, you have some indications that people are coming up of new and simpler ways of running applications. There are many projects around there who knows what's coming next year or the year after that. But platform will a, platform nine will be there and we will, you know, take the innovations from the the community. We will contribute our own innovations and make all of those things very consumable to customers. >>Simpler, faster, cheaper. Exactly. Always a good business model technically to make that happen. Yes. Yeah, I think the, the reigning in the chaos is key, you know, Now we have now visibility into the scale. Final question before we depart this segment. What is at scale, how many clusters do you see that would be a watermark for an at scale conversation around an enterprise? Is it workloads we're looking at or, or clusters? How would you, Yeah, how would you describe that? When people try to squint through and evaluate what's a scale, what's the at scale kind of threshold? >>Yeah. And, and the number of clusters doesn't tell the whole story because clusters can be small in terms of the number of nodes or they can be large. But roughly speaking when we say, you know, large scale cluster deployments, we're talking about maybe hundreds, two thousands. >>Yeah. And final final question, what's the role of the hyperscalers? You got AWS continuing to do well, but they got their core ias, they got a PAs, they're not too too much putting a SaaS out there. They have some SaaS apps, but mostly it's the ecosystem. They have marketplaces doing over $2 billion billions of transactions a year and, and it's just like, just sitting there. It hasn't really, they're now innovating on it, but that's gonna change ecosystems. What's the role the cloud play in the cloud native of its scale? >>The, the hyperscalers, >>Yeahs Azure, Google. >>You mean from a business perspective? Yeah, they're, they have their own interests that, you know, that they're, they will keep catering to, they, they will continue to find ways to lock their users into their ecosystem of services and, and APIs. So I don't think that's gonna change, right? They're just gonna keep, >>Well they got great I performance, I mean from a, from a hardware standpoint, yes, that's gonna be key, right? >>Yes. I think the, the move from X 86 being the dominant way and platform to run workloads is changing, right? That, that, that, that, and I think the, the hyperscalers really want to be in the game in terms of, you know, the the new risk and arm ecosystems and the platforms. >>Yeah, not joking aside, Paul Morritz, when he was the CEO of VMware, when he took over once said, I remember our first year doing the cube. Oh the cloud is one big distributed computer, it's, it's hardware and he got software and you got middleware and he kind over, well he's kind of tongue in cheek, but really you're talking about large compute and sets of services that is essentially a distributed computer. >>Yes, >>Exactly. It's, we're back on the same game. Vic, thank you for coming on the segment. Appreciate your time. This is cloud native at scale special presentation with Platform nine. Really unpacking super cloud Arlon open source and how to run large scale applications on the cloud Cloud Native Phil for developers and John Furrier with the cube. Thanks for Washington. We'll stay tuned for another great segment coming right up. Hey, welcome back everyone to Super Cloud 22. I'm John Fur, host of the Cuba here all day talking about the future of cloud. Where's it all going? Making it super multi-cloud clouds around the corner and public cloud is winning. Got the private cloud on premise and edge. Got a great guest here, Vascar Gorde, CEO of Platform nine, just on the panel on Kubernetes. An enabler blocker. Welcome back. Great to have you on. >>Good to see you >>Again. So Kubernetes is a blocker enabler by, with a question mark. I put on on that panel was really to discuss the role of Kubernetes. Now great conversation operations is impacted. What's interest thing about what you guys are doing at Platform nine? Is your role there as CEO and the company's position, kind of like the world spun into the direction of Platform nine while you're at the helm? Yeah, right. >>Absolutely. In fact, things are moving very well and since they came to us, it was an insight to call ourselves the platform company eight years ago, right? So absolutely whether you are doing it in public clouds or private clouds, you know, the application world is moving very fast in trying to become digital and cloud native. There are many options for you do on the infrastructure. The biggest blocking factor now is having a unified platform. And that's what we, we come into, >>Patrick, we were talking before we came on stage here about your background and we were gonna talk about the glory days in 2000, 2001, when the first as piece application service providers came out, kind of a SaaS vibe, but that was kind of all kind of cloudlike. >>It wasn't, >>And and web services started then too. So you saw that whole growth. Now, fast forward 20 years later, 22 years later, where we are now, when you look back then to here and all the different cycles, >>I, in fact you, you know, as we were talking offline, I was in one of those ASPs in the year 2000 where it was a novel concept of saying we are providing a software and a capability as a service, right? You sign up and start using it. I think a lot has changed since then. The tooling, the tools, the technology has really skyrocketed. The app development environment has really taken off exceptionally well. There are many, many choices of infrastructure now, right? So I think things are in a way the same but also extremely different. But more importantly now for any company, regardless of size, to be a digital native, to become a digital company is extremely mission critical. It's no longer a nice to have everybody's in the journey somewhere. >>Everyone is going digital transformation here. Even on a so-called downturn recession that's upcoming inflation's here. It's interesting. This is the first downturn in the history of the world where the hyperscale clouds have been pumping on all cylinders as an economic input. And if you look at the tech trends, GDPs down, but not tech. >>Nope. >>Cuz the pandemic showed everyone digital transformation is here and more spend and more growth is coming even in, in tech. So this is a unique factor which proves that that digital transformation's happening and company, every company will need a super cloud. >>Everyone, every company, regardless of size, regardless of location, has to become modernize their infrastructure. And modernizing Infras infrastructure is not just some new servers and new application tools, It's your approach, how you're serving your customers, how you're bringing agility in your organization. I think that is becoming a necessity for every enterprise to survive. >>I wanna get your thoughts on Super Cloud because one of the things Dave Ante and I want to do with Super Cloud and calling it that was we, I, I personally, and I know Dave as well, he can, I'll speak from, he can speak for himself. We didn't like multi-cloud. I mean not because Amazon said don't call things multi-cloud, it just didn't feel right. I mean everyone has multiple clouds by default. If you're running productivity software, you have Azure and Office 365. But it wasn't truly distributed. It wasn't truly decentralized, it wasn't truly cloud enabled. It didn't, it felt like they're not ready for a market yet. Yet public clouds booming on premise. Private cloud and Edge is much more on, you know, more, more dynamic, more real. >>Yeah. I think the reason why we think super cloud is a better term than multi-cloud. Multi-cloud are more than one cloud, but they're disconnected. Okay, you have a productivity cloud, you have a Salesforce cloud, you may have, everyone has an internal cloud, right? So, but they're not connected. So you can say okay, it's more than one cloud. So it's you know, multi-cloud. But super cloud is where you are actually trying to look at this holistically. Whether it is on-prem, whether it is public, whether it's at the edge, it's a store at the branch. You are looking at this as one unit. And that's where we see the term super cloud is more applicable because what are the qualities that you require if you're in a super cloud, right? You need choice of infrastructure, you need, but at the same time you need a single pain, a single platform for you to build your innovations on regardless of which cloud you're doing it on, right? So I think Super Cloud is actually a more tightly integrated orchestrated management philosophy we think. >>So let's get into some of the super cloud type trends that we've been reporting on. Again, the purpose of this event is to, as a pilots, to get the conversations flowing with with the influencers like yourselves who are running companies and building products and the builders, Amazon and Azure are doing extremely well. Google's coming up in third cloudworks in public cloud. We see the use cases on premises use cases. Kubernetes has been an interesting phenomenon because it's become from the developer side a little bit, but a lot of ops people love Kubernetes. It's really more of an ops thing. You mentioned OpenStack earlier. Kubernetes kind of came out of that open stack. We need an orchestration and then containers had a good shot with, with Docker. They re pivoted the company. Now they're all in an open source. So you got containers booming and Kubernetes as a new layer there. What's the, what's the take on that? What does that really mean? Is that a new defacto enabler? It >>Is here. It's for here for sure. Every enterprise somewhere else in the journey is going on. And you know, most companies are, 70 plus percent of them have won two, three container based, Kubernetes based applications now being rolled out. So it's very much here, it is in production at scale by many customers. And the beauty of it is, yes, open source, but the biggest gating factor is the skill set. And that's where we have a phenomenal engineering team, right? So it's, it's one thing to buy a tool >>And just be clear, you're a managed service for Kubernetes. >>We provide, provide a software platform for cloud acceleration as a service and it can run anywhere. It can run in public private. We have customers who do it in truly multi-cloud environments. It runs on the edge, it runs at this in stores are thousands of stores in a retailer. So we provide that and also for specific segments where data sovereignty and data residency are key regulatory reasons. We also un OnPrem as an air gap version. >>Can you give an example on how you guys are deploying your platform to enable a super cloud experience for your >>Customer? Right. So I'll give you two different examples. One is a very large networking company, public networking company. They have, I dunno, hundreds of products, hundreds of r and d teams that are building different, different products. And if you look at few years back, each one was doing it on a different platforms but they really needed to bring the agility and they worked with us now over three years where we are their build test dev pro platform where all their products are built on, right? And it has dramatically increased their agility to release new products. Number two, it actually is a light out operation. In fact the customer says like, like the Maytag service person cuz we provide it as a service and it barely takes one or two people to maintain it for them. >>So it's kinda like an SRE vibe. One person managing a >>Large 4,000 engineers building infrastructure >>On their tools, >>Whatever they want on their tools. They're using whatever app development tools they use, but they use our platform. >>What benefits are they seeing? Are they seeing speed? >>Speed, definitely. Okay. Definitely they're speeding. Speed uniformity because now they're building able to build, so their customers who are using product A and product B are seeing a similar set of tools that are being used. >>So a big problem that's coming outta this super cloud event that we're, we're seeing and we've heard it all here, ops and security teams cuz they're kind of too part of one theme, but ops and security specifically need to catch up speed wise. Are you delivering that value to ops and security? Right. >>So we, we work with ops and security teams and infrastructure teams and we layer on top of that. We have like a platform team. If you think about it, depending on where you have data centers, where you have infrastructure, you have multiple teams, okay, but you need a unified platform. Who's your buyer? Our buyer is usually, you know, the product divisions of companies that are looking at or the CTO would be a buyer for us functionally cio definitely. So it it's, it's somewhere in the DevOps to infrastructure. But the ideal one we are beginning to see now many large corporations are really looking at it as a platform and saying we have a platform group on which any app can be developed and it is run on any infrastructure. So the platform engineering teams, >>You working two sides of that coin. You've got the dev side and then >>And then infrastructure >>Side side, okay. >>Another customer like give you an example, which I would say is kind of the edge of the store. So they have thousands of stores. Retail, retail, you know food retailer, right? They have thousands of stores that are on the globe, 50,000, 60,000. And they really want to enhance the customer experience that happens when you either order the product or go into the store and pick up your product or buy or browse or sit there. They have applications that were written in the nineties and then they have very modern AIML applications today. They want something that will not have to send an IT person to install a rack in the store or they can't move everything to the cloud because the store operations has to be local. The menu changes based on, It's a classic edge. It's classic edge. Yeah. Right. They can't send it people to go install rack access servers then they can't sell software people to go install the software and any change you wanna put through that, you know, truck roll. So they've been working with us where all they do is they ship, depending on the size of the store, one or two or three little servers with instructions that >>You, you say little servers like how big one like a net box box, like a small little >>Box and all the person in the store has to do like what you and I do at home and we get a, you know, a router is connect the power, connect the internet and turn the switch on. And from there we pick it up. >>Yep. >>We provide the operating system, everything and then the applications are put on it. And so that dramatically brings the velocity for them. They manage >>Thousands of them. True plug and play >>Two, plug and play thousands of stores. They manage it centrally. We do it for them, right? So, so that's another example where on the edge then we have some customers who have both a large private presence and one of the public clouds. Okay. But they want to have the same platform layer of orchestration and management that they can use regardless of the location. So >>You guys got some success. Congratulations. Got some traction there. It's awesome. The question I want to ask you is that's come up is what is truly cloud native? Cuz there's lift and shift of the cloud >>That's not cloud native. >>Then there's cloud native. Cloud native seems to be the driver for the super cloud. How do you talk to customers? How do you explain when someone says what's cloud native, what isn't cloud native? >>Right. Look, I think first of all, the best place to look at what is the definition and what are the attributes and characteristics of what is truly a cloud native, is CNC foundation. And I think it's very well documented where you, well >>Con of course Detroit's >>Coming here, so, so it's already there, right? So, so we follow that very closely, right? I think just lifting and shifting your 20 year old application onto a data center somewhere is not cloud native. Okay? You can't put to cloud native, you have to rewrite and redevelop your application and business logic using modern tools. Hopefully more open source and, and I think that's what Cloudnative is and we are seeing a lot of our customers in that journey. Now everybody wants to be cloudnative, but it's not that easy, okay? Because it's, I think it's first of all, skill set is very important. Uniformity of tools that there's so many tools there. Thousands and thousands of tools you could spend your time figuring out which tool to use. Okay? So I think the complexities there, but the business benefits of agility and uniformity and customer experience are truly them. >>And I'll give you an example. I don't know how clear native they are, right? And they're not a customer of ours, but you order pizzas, you do, right? If you just watch the pizza industry, how dominoes actually increase their share and mind share and wallet share was not because they were making better pizzas or not, I don't know anything about that, but the whole experience of how you order, how you watch what's happening, how it's delivered. There were a pioneer in it. To me, those are the kinds of customer experiences that cloud native can provide. >>Being agility and having that flow to the application changes what the expectations of the, for the customer. >>Customer, the customer's expectations change, right? Once you get used to a better customer experience, you learn >>Best car. To wrap it up, I wanna just get your perspective again. One of the benefits of chatting with you here and having you part of the Super Cloud 22 is you've seen many cycles, you have a lot of insights. I want to ask you, given your career where you've been and what you've done and now the CEO platform nine, how would you compare what's happening now with other inflection points in the industry? And you've been, again, you've been an entrepreneur, you sold your company to Oracle, you've been seeing the big companies, you've seen the different waves. What's going on right now put into context this moment in time around Super >>Cloud. Sure. I think as you said, a lot of battles. Cars being been, been in an asp, been in a realtime software company, being in large enterprise software houses and a transformation. I've been on the app side, I did the infrastructure right and then tried to build our own platforms. I've gone through all of this myself with a lot of lessons learned in there. I think this is an event which is happening now for companies to go through to become cloud native and digitalize. If I were to look back and look at some parallels of the tsunami that's going on is a couple of paddles come to me. One is, think of it, which was forced to honors like y2k. Everybody around the world had to have a plan, a strategy, and an execution for y2k. I would say the next big thing was e-commerce. I think e-commerce has been pervasive right across all industries. >>And disruptive. >>And disruptive, extremely disruptive. If you did not adapt and adapt and accelerate your e-commerce initiative, you were, it was an existence question. Yeah. I think we are at that pivotal moment now in companies trying to become digital and cloudnative that know that is what I see >>Happening there. I think that that e-commerce was interesting and I think just to riff with you on that is that it's disrupting and refactoring the business models. I think that is something that's coming out of this is that it's not just completely changing the game, it's just changing how you operate, >>How you think, and how you operate. See, if you think about the early days of eCommerce, just putting up a shopping cart didn't made you an eCommerce or an E retailer or an e e customer, right? Or so. I think it's the same thing now is I think this is a fundamental shift on how you're thinking about your business. How are you gonna operate? How are you gonna service your customers? I think it requires that just lift and shift is not gonna work. >>Mascar, thank you for coming on, spending the time to come in and share with our community and being part of Super Cloud 22. We really appreciate, we're gonna keep this open. We're gonna keep this conversation going even after the event, to open up and look at the structural changes happening now and continue to look at it in the open in the community. And we're gonna keep this going for, for a long, long time as we get answers to the problems that customers are looking for with cloud cloud computing. I'm Sean Feer with Super Cloud 22 in the Cube. Thanks for watching. >>Thank you. Thank you, John. >>Hello. Welcome back. This is the end of our program, our special presentation with Platform nine on cloud native at scale, enabling the super cloud. We're continuing the theme here. You heard the interviews Super Cloud and its challenges, new opportunities around the solutions around like Platform nine and others with Arlon. This is really about the edge situations on the internet and managing the edge multiple regions, avoiding vendor lock in. This is what this new super cloud is all about. The business consequences we heard and and the wide ranging conversations around what it means for open source and the complexity problem all being solved. I hope you enjoyed this program. There's a lot of moving pieces and things to configure with cloud native install, all making it easier for you here with Super Cloud and of course Platform nine contributing to that. Thank you for watching.

>>Welcome back everyone to the cubes coverage here in Seattle, Washington, AWS's marketplace seller conference. It's the big news within the Amazon partner network, combining with marketplaces, forming the Amazon partner organization, part of a big reorg as they grow the next level NextGen cloud mid-game on the chessboard. Cube's got cover. I'm John fur, host of Cub, a great guests here from data bricks, both cube alumnis, Jack Anderson, GM of the and VP of the data bricks partnership team. For ADOS, you handle that relationship and Joel Minick vice president of product and partner marketing. You guys are the, have the keys to the kingdom with data, bricks, and AWS. Thanks for joining. Thanks for good to see you again. Thanks for >>Having us back. Yeah, John, great to be here. >>So I feel like we're at reinvent 2013 small event, no stage, but there's a real shift happening with procurement. Obviously it makes it's a no brainer on the micro, you know, people should be buying online self-service cloud scale, but Amazon's got billions being sold to their marketplace. They've reorganized their partner network. You can see kind of what's going on. They've kind of figured it out. Like let's put everything together and simplify and make it less of a website marketplace merge our partner to have more synergy and friction, less experiences so everyone can make more money and customer's gonna be happier. >>Yeah, that's right. >>I mean, you're run relationship. You're in the middle of it. >>Well, Amazon's mental model here is that they want the world's best ISVs to operate on AWS so that we can collaborate and co architect on behalf of customers. And that's exactly what the APO and marketplace allow us to do is to work with Amazon on these really, you know, unique use cases. >>You know, I interviewed Ali many times over the years. I remember many years ago, I think six, maybe six, seven years ago, we were talking. He's like, we're all in ons. Obviously. Now the success of data bricks, you've got multiple clouds. See that customers have choice, but I remember the strategy early on. It was like, we're gonna be deep. So this is speaks volumes to the, the relationship you have years. Jack take us through the relationship that data bricks has with AWS from a, from a partner perspective, Joel, and from a product perspective, because it's not like you got to Johnny come lately new to the new, to the scene, right? We've been there almost president creation of this wave. What's the relationship and has it relate to what's going on today? >>So, so most people may not know that data bricks was born on AWS. We actually did our first 100 million of revenue on Amazon. And today we're obviously available on multiple clouds, but we're very fond of our Amazon relationship. And when you look at what the APN allows us to do, you know, we're able to expand our reach and co-sell with Amazon and marketplace broadens our reach. And so we think of marketplace in three different aspects. We've got the marketplace, private offer business, which we've been doing for a number of years. Matter of fact, we we're driving well over a hundred percent year over year growth in private offers and we have a nine figure business. So it's a very significant business. And when a customer uses a private offer that private offer counts against their private pricing agreement with AWS. So they get pricing power against their, their private pricing. >>So it's really important. It goes on their Amazon bill in may. We launched our pay as you go on demand offering. And in five short months, we have well over a thousand subscribers. And what this does is it really reduces the barriers to entry it's low friction. So anybody in an enterprise or startup or public sector company can start to use data bricks on AWS and pay consumption based model and have it go against their monthly bill. And so we see customers, you know, doing rapid experimentation pilots, POCs, they're, they're really learning the value of that first use case. And then we see rapid use case expansion. And the third aspect is the consulting partner, private offers C P O super important in how we involve our partner ecosystem of our consulting partners and our resellers that are able to work with data bricks on behalf of customers. >>So you got the big contracts with the private offer. You got the product market fit, kind of people iterating with data coming in with, with the buyers you go. And obviously the integration piece all fitting in there. Exactly. Exactly. Okay. So that's that those are the offers that's current and what's in marketplace today. Is that the products, what are, what are people buying? I mean, I guess what's the Joel, what are, what are people buying in the marketplace and what does it mean for >>Them? So fundamentally what they're buying is the ability to take silos out of their organization. And that's, that is the problem that data bricks is out there to solve, which is when you look across your data landscape today, you've got unstructured data, you've got structured data, you've got real time streaming data, and your teams are trying to use all of this data to solve really complicated problems. And as data bricks as the lake house company, what we're helping customers do is how do they get into the new world? How do they move to a place where they can use all of that data across all of their teams? And so we allow them to begin to find through the marketplace, those rapid adoption use cases where they can get rid of these data, warehousing data lake silos they've had in the past, get their unstructured and structured data onto one data platform and open data platform that is no longer adherent to any proprietary formats and standards and something. >>They can very much, very easily integrate into the rest of their data environment, apply one common data governance layer on top of that. So that from the time they ingest that data to the time they use that data to the time they share that data inside and outside of their organization, they know exactly how it's flowing. They know where it came from. They know who's using it. They know who has access to it. They know how it's changing. And then with that common data platform with that common governance solution, they'd being able to bring all of those use cases together across their real time, streaming their data engineering, their BI, their AI, all of their teams working on one set of data. And that lets them move really, really fast. And it also lets them solve challenges. They just couldn't solve before a good example of this, you know, one of the world's now largest data streaming platforms runs on data bricks with AWS. >>And if you think about what does it take to set that up? Well, they've got all this customer data that was historically inside of data warehouses, that they have to understand who their customers are. They have all this unstructured data, they've built their data science model, so they can do the right kinds of recommendation engines and forecasting around. And then they've got all this streaming data going back and forth between click stream data from what the customers are doing with their platform and the recommendations they wanna push back out. And if those teams were all working in individual silos, building these kinds of platforms would be extraordinarily slow and complex, but by building it on data bricks, they were able to release it in record time and have grown at, at record pace >>To not be that's product platform that's impacting product development. Absolutely. I mean, this is like the difference between lagging months of product development to like days. Yes. Pretty much what you're getting at. Yeah. So total agility. I got that. Okay. Now I'm a customer I wanna buy in the marketplace, but I also, you got direct Salesforce up there. So how do you guys look at this? Is there channel conflict? Are there comp programs? Because one of the things I heard today in on the stage from a Davis's leadership, Chris was up there speaking and, and, and moment I was, Hey, he's a CRO conference, chief revenue officer conversation, which means someone's getting compensated. So if I'm the sales rep at data bricks, what's my motion to the customer. Do I get paid? Does Amazon sell it? Take us through that. Is there channel conflict? Is there or an audio lift? >>Well, I I'd add what Joel just talked about with, with, you know, what the solution, the value of the solution our entire offering is available on AWS marketplace. So it's not a subset, the entire data bricks offering and >>The flagship, all the, the top, >>Everything, the flagship, the complete offering. So it's not, it's not segmented. It's not a sub segment. It's it's, you know, you can use all of our different offerings. Now when it comes to seller compensation, we, we, we view this two, two different ways, right? One is that AWS is also incented, right? Versus selling a native service to recommend data bricks for the right situation. Same thing with data bricks. Our Salesforce wants to do the right thing for the customer. If the customer wants to use marketplace as their procurement vehicle. And that really helps customers because if you get data bricks and five other ISVs together, and let's say each ISV is spending, you're spending a million dollars, you have $5 million of spend, you put that spend through the flywheel with AWS marketplace. And then you can use that in your negotiations with AWS to get better pricing overall. So that's how we, >>We do it. So customers are driving. This sounds like, correct. For sure. So they're looking at this as saying, Hey, I'm gonna just get purchasing power with all my relationships because it's a solution architectural market, right? >>Yeah. It makes sense. Because if most customers will have a primary and secondary cloud provider, if they can consolidate, you know, multiple ISV spend through that same primary provider, you get pricing >>Power, okay, Jill, we're gonna date ourselves. At least I will. So back in the old days, it used to be, do a Barney deal with someone, Hey, let's go to market together. You gotta get paper, you do a biz dev deal. And then you gotta say, okay, now let's coordinate our sales teams, a lot of moving parts. So what you're getting at here is that the alternative for data bricks or any company is to go find those partners and do deals versus now Amazon is the center point for the customer so that you can still do those joint deals. But this seems to be flipping the script a little bit. >>Well, it is, but we still have VAs and consulting partners that are doing implementation work very valuable work advisory work that can actually work with marketplace through the C PPO offering. So the marketplace allows multiple ways to procure your >>Solution. So it doesn't change your business structure. It just makes it more efficient. That's >>Correct. >>That's a great way to say it. Yeah, >>That's great. So that's so that's it. So that's just makes it more efficient. So you guys are actually incented to point customers to the marketplace. >>Yes, >>Absolutely. Economically. Yeah. >>E economically it's the right thing to do for the customer. It's the right thing to do for our relationship with Amazon, especially when it comes back to co-selling right? Because Amazon now is leaning in with ISVs and making recommendations for, you know, an ISV solution and our teams are working backwards from those use cases, you know, to collaborate, land them. >>Yeah. I want, I wanna get that out there. Go ahead, Joel. >>So one of the other things I might add to that too, you know, and why this is advantageous for, for companies like data bricks to, to work through the marketplace, is it makes it so much easier for customers to deploy a solution. It's, it's very, literally one click through the marketplace to get data bricks stood up inside of your environment. And so if you're looking at how do I help customers most rapidly adopt these solutions in the AWS cloud, the marketplace is a fantastic accelerator to that. You >>Know, it's interesting. I wanna bring this up and get your reaction to it because to me, I think this is the future of procurement. So from a procurement standpoint, I mean, again, dating myself EDI back in the old days, you know, all that craziness. Now this is all the, all the internet, basically through the console, I get the infrastructure side, you know, spin up and provision. Some servers, all been good. You guys have played well there in the marketplace. But now as we get into more of what I call the business apps, and they brought this up on stage little nuance, most enterprises aren't yet there of integrating tech on the business apps, into the stack. This is where I think you guys are a use case of success where you guys have been successful with data integration. It's an integrator's dilemma, not an innovator's dilemma. So like, I want to integrate, so now I have integration points with data bricks, but I want to put an app in there. I want to provision an application, but it has to be built. It's not, you don't buy it. You build, you gotta build stuff. And this is the nuance. What's your reaction to that? Am I getting this right? Or, or am I off because no, one's gonna be buying software. Like they used to, they buy software to integrate it. >>Yeah, >>No, I, cause everything's integrated. >>I think AWS has done a great job at creating a partner ecosystem, right. To give customers the right tools for the right jobs. And those might be with third parties, data bricks is doing the same thing with our partner connect program. Right. We've got customer, customer partners like five tra and D V T that, you know, augment and enhance our platform. And so you, you're looking at multi ISV architectures and all of that can be procured through the AWS marketplace. >>Yeah. It's almost like, you know, bundling and unbundling. I was talking about this with, with Dave ante about Supercloud, which is why wouldn't a customer want the best solution in their architecture period. And it's class. If someone's got API security or an API gateway. Well, you know, I don't wanna be forced to buy something because it's part of a suite and that's where you see things get suboptimized where someone dominates a category and they have, oh, you gotta buy my version of this. Yeah. >>Joel, Joel. And that's Joel and I were talking, we're actually saying what what's really important about Databricks is that customers control the data. Right? You wanna comment on that? >>Yeah. I was say the, you know what you're pushing on there we think is extraordinarily, you know, the way the market is gonna go is that customers want a lot of control over how they build their data stack. And everyone's unique in what tools are the right ones for them. And so one of the, you know, philosophically I think really strong places, data, bricks, and AWS have lined up is we both take an approach that you should be able to have maximum flexibility on the platform. And as we think about the lake house, one thing we've always been extremely committed to as a company is building the data platform on an open foundation. And we do that primarily through Delta lake and making sure that to Jack's point with data bricks, the data is always in your control. And then it's always stored in a completely open format. And that is one of the things that's allowed data bricks to have the breadth of integrations that it has with all the other data tools out there, because you're not tied into any proprietary format, but instead are able to take advantage of all the innovation that's happening out there in the open source ecosystem. >>When you see other solutions out there that aren't as open as you guys, you guys are very open by the way, we love that too. We think that's a great strategy, but what's the, what am I foreclosing? If I go with something else that's not as open what what's the customer's downside as you think about what's around the corner in the industry. Cuz if you believe it's gonna be open, open source, which I think opens our software is the software industry and integration is a big deal, cuz software's gonna be plentiful. Let's face it. It's a good time to be in software business, but cloud's booming. So what's the downside from your data bricks perspective, you see a buyer clicking on data bricks versus that alternative what's potentially is should they be a nervous about down the road if they go with a more proprietary or locked in approach? Well, >>I think the challenge with proprietary ecosystems is you become beholden to the ability of that provider to both build relationships and convince other vendors that they should invest in that format. But you're also then beholden to the pace at which that provider is able to innovate. And I think we've seen lots of times over history where, you know, a proprietary format may run ahead for a while on a lot of innovation. But as that market control begins to solidify that desire to innovate begins to, to degrade, whereas in the open format. So >>Extract rents versus innovation. Exactly. >>Yeah, exactly. >>But >>I'll say it in the open world, you know, you have to continue to innovate. Yeah. And the open source world is always innovating. If you look at the last 10 to 15 years, I challenge you to find, you know, an example where the innovation in the data and AI world is not coming from open source. And so by investing in open ecosystems, that means you were always going to be at the forefront of what is the >>Latest, you know, again, not to date myself again, but you look back at the eighties and nineties, the protocol stacked for proprietary. Yeah. You know, SNA at IBM deck net was digital, you know, the rest is, and then TCP, I P was part of the open systems, interconnect, revolutionary Oly, a big part of that as well as my school did. And so like, you know, that was, but it didn't standardize the whole stack. It stopped at IP and TCP. Yeah. But that helped interoperate, that created a nice defacto. So this is a big part of this mid game. I call it the chessboard, you know, you got opening game and mid game. Then you got the end game and we're not there. The end game yet cloud the cloud. >>There's, there's always some form of lock in, right. Andy jazzy will, will address it, you know, when making a decision. But if you're gonna make a decision you want to reduce as you don't wanna be limited. Right. So I would advise a customer that there could be limitations with a proprietary architecture. And if you look at what every customer's trying to become right now is an AI driven business. Right? And so it has to do with, can you get that data outta silos? Can you, can you organize it and secure it? And then can you work with data scientists to feed those models? Yeah. In a, in a very consistent manner. And so the tools of tomorrow will to Joel's point will be open and we want interoperability with those >>Tools and, and choice is a matter too. And I would say that, you know, the argument for why I think Amazon is not as locked in as maybe some other clouds is that they have to compete directly too. Redshift competes directly with a lot of other stuff, but they can't play the bundling game because the customers are getting savvy to the fact that if you try to bundle an inferior product with something else, it may not work great at all. And they're gonna be they're onto it. This is >>The Amazon's credit by having these, these solutions that may compete with native services in marketplace, they are providing customers with choice, low >>Price and access to the S and access to the core value. Exactly. Which the >>Hardware, which is their platform. Okay. So I wanna get you guys thought on something else. I, I see emerging, this is again kind of cube rumination moment. So on stage Chris unpacked, a lot of stuff. I mean this marketplace, they're touching a lot of hot buttons here, you know, pricing compensation, workflows services behind the curtain. And one of the things he mentioned was they talk about resellers or channel partners, depending upon what you talk about. We believe Dave and I believe on the cube that the entire indirect sales channel of the industry is gonna be disrupted radically because those players were selling hardware in the old days and software, that game is gonna change. You know, you mentioned you guys have a program, want to get your thoughts on this. We believe that once this gets set up, they can play in this game and bring their services in which means that the old reseller channels are gonna be rewritten. They're gonna be refactored with this new kinds of access. Cuz you've got scale, you've got money and you've got product and you got customers coming into the marketplace. So if you're like a reseller that sold computers to data centers or software, you know, value added reseller or V or business, >>You've gotta evolve. >>You gotta, you gotta be here. Yes. How are you guys working with those partners? Cuz you say you have a part in your marketplace there. How do I make money? If I'm a reseller with data bricks with eight Amazon, take me through that use case. >>Well I'll let Joel comment, but I think it's, it's, it's pretty straightforward, right? Customers need expertise. They need knowhow. When we're seeing customers do mass migrations to the cloud or Hadoop specific migrations or data transformation implementations, they need expertise from consulting and SI partners. If those consulting SI partners happen to resell the solution as well. Well, that's another aspect of their business, but I really think it is the expertise that the partners bring to help customers get outcomes. >>Joel, channel big opportunity for re re Amazon to reimagine this. >>For sure. Yeah. And I think, you know, to your comment about how to resellers take advantage of that, I think what Jack was pushing on is spot on, which is it's becoming more about more and more about the expertise you bring to the table and not just transacting the software, but now actually helping customers make the right choices. And we're seeing, you know, both SI begin to be able to resell solutions and finding a lot of opportunity in that. Yeah. And I think we're seeing traditional resellers begin to move into that SI model as well. And that's gonna be the evolution that >>This gets at the end of the day. It's about services for sure, for sure. You've got a great service. You're gonna have high gross profits. And >>I think that the managed service provider business is alive and well, right? Because there are a number of customers that want that, that type of a service. >>I think that's gonna be a really hot, hot button for you guys. I think being the way you guys are open this channel partner services model coming in to the fold really kind of makes for kind of that super cloudlike experience where you guys now have an ecosystem. And that's my next question. You guys have an ecosystem going on within data bricks for sure. On top of this ecosystem, how does that work? This is kinda like hasn't been written up in business school and case studies yet this is new. What is this? >>I think, you know, what it comes down to is you're seeing ecosystems begin to evolve around the data platforms and that's gonna be one of the big kind of new horizons for us as we think about what drives ecosystems it's going to be around. Well, what is the, what's the data platform that I'm using and then all the tools that have to encircle that to get my business done. And so I think there's, you know, absolutely ecosystems inside of the AWS business on all of AWS's services, across data analytics and AI. And then to your point, you are seeing ecosystems now arise around data bricks in its Lakehouse platform, as well as customers are looking at well, if I'm standing these Lakehouse up and I'm beginning to invest in this, then I need a whole set of tools that help me get that done as well. >>I mean you think about ecosystem theory, we're living a whole nother dream and I'm, and I'm not kidding. It hasn't yet been written up and for business school case studies is that we're now in a whole nother connective tissue ecology thing happening where you have dependencies and value proposition economics connectedness. So you have relationships in these ecosystems. >>And I think one of the great things about relationships with these ecosystems is that there's a high degree of overlap. Yeah. So you're seeing that, you know, the way that the cloud business is evolving, the, the ecosystem partners of data bricks are the same ecosystem partners of AWS. And so as you build these platforms out into the cloud, you're able to really take advantage of best of breed, the broadest set of solutions out there for >>You. Joel, Jack, I love it because you know what it means the best ecosystem will win. If you keep it open. Sure. You can see everything. If you're gonna do it in the dark, you know, you don't know the outcome. I mean, this is really kind we're talking about. >>And John, can I just add that when I was in Amazon, we had a, a theory that there's buyers and builders, right? There's very innovative companies that want to build things themselves. We're seeing now that that builders want to buy a platform. Right? Yeah. And so there's a platform decision being made and that ecosystem gonna evolve around the >>Platform. Yeah. And I totally agree. And, and, and the word innovation get kicks around. That's why, you know, when we had our super cloud panel was called the innovators dilemma with a slash through it called the integrated dilemma, innovation is the digital transformation. So absolutely like that becomes cliche in a way, but it really becomes more of a, are you open? Are you integrating if APIs are the connective tissue, what's automation, what's the service message look like. I mean, a whole nother set of kind of thinking goes on and these new ecosystems and these new products >>And that, and that thinking is, has been born in Delta sharing. Right? So the idea that you can have a multi-cloud implementation of data bricks, and actually share data between those two different clouds, that is the next layer on top of the native cloud >>Solution. Well, data bricks has done a good job of building on top of the goodness of, and the CapEx gift from AWS. But you guys have done a great job taking that building differentiation into the product. You guys have great customer base, great grow ecosystem. And again, I think in a shining example of what every enterprise is going to do, build on top of something operating model, get that operating model, driving revenue. >>Yeah. >>Well we, whether whether you're Goldman Sachs or capital one or XYZ corporation >>S and P global NASDAQ, right. We've got, you know, these, the biggest verticals in the world are solving tough problems with data breaks. I think we'd be remiss cuz if Ali was here, he would really want to thank Amazon for all of the investments across all of the different functions, whether it's the relationship we have with our engineering and service teams. Yeah. Our marketing teams, you know, product development and we're gonna be at reinvent the big presence of reinvent. We're looking forward to seeing you there again. >>Yeah. We'll see you guys there. Yeah. Again, good ecosystem. I love the ecosystem evolutions happening this next gen cloud is here. We're seeing this evolve kind of new economics, new value propositions kind of scaling up, producing more so you guys are doing a great job. Thanks for coming on the Cuban, taking time. Chill. Great to see you at the check. Thanks for having us. Thanks. Going. Okay. Cube coverage here. The world's changing as APN comes to give the marketplace for a new partner organization at Amazon web services, the Cube's got a covered. This should be a very big growing ecosystem as this continues, billions of being sold through the marketplace. Of course the buyers are happy as well. So we've got it all covered. I'm John furry, your host of the cube. Thanks for watching.

>>The queue presents Coon and cloud native con Europe, 2022, brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Licia Spain, a Coon cloud native con Europe, 2022. I'm your host, Keith Townson, along with Paul Gillon senior editor, enterprise architecture for Silicon angle. Paul, we're gonna talk to some amazing people this week. Coon, what the energy here, what, what, what, what would you say about >>It? I'd say it's reminiscent of, of early year, uh, early stage conferences I've seen with other technologies. There is a lot of startup activity. Here's a lot of money in the market, despite the sell off in the stock market lately. Uh, a lot of anticipation that there are, there could be big exits. There could be big things ahead for these companies. You don't see that when you go to the big established conferences, uh, you see just, uh, anticipation here that I don't think you see, uh, you you'll see maybe in a couple years, so it's fun to be here right now. I'm sure it'll be a very different experience in two or three years. >>So welcome to our guest cube alum. Batam Tobar the founder and CEO of Upbound. Welcome back. >>Thank you. Yeah, pleasure to be on, on the show again. >>So Paul, tell us the we're in this phase of migrations and, and moving to cloud native stacks. Are we another replatforming generation? I mean, we've done, the enterprise has done this, you know, time and time again, whether it's from Java to.net or do net to Java or from bare metal to VMs, but are we in another age of replatforming? >>You know, it's interesting. Every company has now become a tech company and every tech company needs to build a very model, you know, modern digital platform for them to actually run their business. And if they don't do that, then they'll probably be out of business. And, um, it is interesting to think about how companies are platforming and replatforming. Like, you know, as you said, just a, a few years back, you know, we were on people using cloud Foundry or using Heroku, you hear Heroku a lot, or, you know, now it's cloud native and Kubernetes and, and it, it begs the question, you know, is this the end? That to your point, is this, you know, do we have a, you know, what, what makes us sure that this is the, you know, the last platform or the future proof platform that, that people are building, >>There's never a last platform, right? There's always something around the core. The question is, is Kubernetes Linux, or is it windows? >>That, that's a good question. Um, it's more like more like Linux. I think, um, you know, the, you know, you've heard this before, but people talk about Kubernetes as a platform off platforms. Um, you can use it to build other platforms and if you know what you're doing, you can probably put, assemble a set of pieces around it and arrive at something that looks and can work for your business, but it requires a ton of talent. It requires a lot of people that actually can act, you know, know how to put this stick together to, to work for your business. It is, there's not a lot of guidance. I, we were, I think we were chatting earlier about the CSCF landscape and, and, um, how there are all these different projects and companies around it, but, but they don't come together in meaningful ways that you have, they act the enterprise itself has to figure out how to bring them together. Right. And that's the combination of what they do there organically or not is their platform. Right. And that changes. It can change over time. >>Do you think they really do. They really want to put these things together? I mean, there's, that's not what enterprise is like to do. They want to find someone who's gonna come in and, uh, turnkey do it all for them. >>Yeah. And, and if there was, this is the, this is the things like EV every week now you hear about another platform that says, this is the new Heroku. This is the new cloud Foundry, this replaces every, you know, some vendor has, and you can see them all around here. You know, companies that are basically selling platform solutions, um, that do put 'em together. And the problem with it is that you typically outgrow these, like you are, um, it might solve 80% of the use cases you care about, but the other 20% are not represented. And so you end up outgrowing the platform itself, right? And the, the choice has been mostly around, you know, do you buy something off the shelf that solves 80% of your use cases, or do you build something on your own? And then you have to spend all your resources actually going through and building all of it. And that's been the dilemma, you know, people who talk about this as a platform dilemma, but it's been, it's been the way for a long time. Like you, every, we go through this cycle every few years and, you know, people end up essentially oscillating between buying something off the, you know, that's off the shelf or building it, building it themselves. >>So what's the payoff. If I'm a CIO and I'm looking at the landscape, I don't need to understand, you know, I don't know to know what a pod is to know that looking at 200 plus projects in co and at, in cloud native, uh, foundation and the bevy of, of co-located projects and, and conferences before they, even the start of this, what's the payoff >>Increasing the pace of innovation. I mean, that literally is when we talk to customers, they all say roughly the same thing. They want something that works for their business. They want something that helps them take their, you know, line of business applications to production in a much quicker way, lets them innovate, lets them create higher engineers that can, don't have to understand everything about every system, but can actually specialize and focus on the, the parts that they sh they care about. Um, but it's all in the context of, you know, people want to be able to innovate at a very high pace, otherwise they get disrupted. >>So I was at the, you know, my favorite part of, of Coon in general is the hallway track and talking to people on the ground, doing cool things. I was talking to a engineer who was able to take their Java, stack their, their, uh, net stack and start to create APIs between and break 'em into microservices. Now teams are working across from one another realizing that, that, that promise of innovation, but that was the end point. They they're there. Yeah. As companies are thinking about replatforming where like, where do we start? I mean, looking at the, the CNCF, the, the map and it's 200 plus projects, where do I start? >>Do you typically today start with Kubernetes and, and um, a lot of companies have now deployed Kubernetes to production as a container orchestrator, whether they're going through a vendor or not, but now you are seeing all the things around it, whether it's C I C D or GI ops that they're looking at, you know, or the starting to build consoles around, you know, their, their platforms or looking at managing more than just containers. And that's a theme that, you know, we're seeing a lot now, people want, people want to actually bring this modern stack to manage, not just container workloads, but start looking at databases and cloud workloads and everything else that they're doing around it. Honestly, everybody's trying to do the same thing. They're trying to arrive at a single point of control, a single, you know, a platform that can do it all that they can centralize policy centralized controls to compliance governance, cost controls, and then expose a self-service experience to developers. Like they're all trying to build what we probably call an internal cloud platform. They don't know, they talk about it in different ways, but almost everyone is trying to build some internal platform that sits on top of, on premises. And on top of cloud, depending on their scenarios, >>You make an interesting point, which is that everyone here is to some extent trying to do the same thing. And there's fine points of granularity between now they're approaching it as you walk around this floor. Do you understand what all of these companies are doing? >>I'm not sure I understand all of them, but I, I do. I do recognize a lot of them. Yes. >>And in terms of your approach, you, you use the term control plane, uh, what is distinctive about your approach? >>Very good question. So, you know, we, we end up out take a, um, we we're trying to solve, uh, this problem as well. We're trying to help people build their own platforms. Um, but let me, let me, you know, there's a lot to it. So let me actually step back and talk about the architecture of this. But if you were to look at any cloud platform, let's take the largest one. AWS, if you peek behind the scenes at AWS, you know, um, it's basically a set of independent services, EC two S3 databases, et cetera, um, that are, you know, essentially working on different parts of, you know, like offer completely different pricing, different services, et cetera. They come together because they all integrate into a control plan. >>It's the thing that serves an API. It's the thing that gives it all a common field. It's where you do access control. It's where you do, um, billing, metering, cost control policy, et cetera. Right? And so our realization was if the enterprises are platforming and replatforming, why shouldn't they build their platform in the same way that the cloud vendors build theirs? And so we started this project almost four years ago, now three and a half years, um, called cross plain, which is a, essentially an open source control plane that can become the integration point for all services. And essentially gives you a universal control plane for cloud. >>So you mentioned the idea of the orchestrating or managing stuff other than containers, as I think about companies that built amazing platforms, enterprise companies, building amazing applications on AWS 10 years ago, and they're adopting the AWS control plane. And now I'm looking at Kubernetes is Kubernetes the way to multi-cloud to be able to control those discrete applic, uh, services in a AWS or Google cloud Azure or Oracle cloud is cetera. >>We kind of have the tease it, the parts. So there are really two parts to Kubernetes and everybody thinks of Kubernetes as a container orchestration platform. Right? And, um, you know, there is a sense that people say, if I was to run Kubernetes on everywhere and can build everything on top of containers, that I get some kind of portability across clouds, right. That I can put things in containers. And then they magically run, you know, in different environments. Um, in reality, what we've seen is not everything fits in containers. It's not gonna be the world is not gonna look like containers on the bottom. Everything else is on top. Instead, what we're gonna see is essentially a set of services that people are using across the different vendors. So if you look at like, you could be at AWS shop primarily, but I bet you're using confluent or elastic or data breaks or snowflake or Mongo or other services. >>I bet you're using things that are on premises, right? And so when you look at that and you say to build my platform as an enterprise, I have to consume services from multiple vendors. Even it's just one major cloud vendor, but I'm consuming services from others. How do I bring them together in meaningful ways so that I can, you know, build my platform on top of the collection of them and offer something that my developers can consume. And self-service on. That's not a, that's not just containers. What's interesting though, is if you look at Kubernetes and, you know, look inside it, Kubernetes built a control plane. That's actually quite useful and applicable outside of container scenarios. So this whole notion of CRDs and controllers, if you've heard that term, um, the ability, you know, like there are two parts to Kubernetes, there is the control plane, and then there's the container container, uh, workloads and the control plane is generic. >>It could be used literally across, you know, you can use it to manage things that are completely outside of container workloads. And that's what we did with cross plain. We took the control plane of Kubernetes and then built bindings providers that connected to AWS, to Google, to Azure, to digital ocean, to all these different environments. So you can bring the way of managing, you know, the style of managing that Kubernetes invented to more than just containers. You can now manage cloud services, using the same approach that you are now using with Kubernetes and using the entire ecosystem of tooling around it. >>Enterprise have been under pressure replatform for a long time. It was first go to Unix then to Linux and virtualize then to move to the cloud. Now, Kubernetes, do you think that this is the stack that enterprises can finally commit to? >>I think if you take the orientation of your deploying a control plane within your enterprise, that is extensible, that enables you to actually connect it to all the things that are under your domain, um, that that actually can be a Futureproof way of doing a platform. And, you know, if you look at the largest cloud platforms, AWS has been around for at least 15 years now, uh, and they really haven't changed the architecture of AWS significantly. It's still a control plane, a set of control planes that are managing services. >>It's a legacy >>They've added a lot of services. They've have a ton of diversity. They've added so many different things, but the architecture is still a hub and spoke that they've built, right? And if the enterprise can take the same orientation, put a control plane, let it manage all the things that are, you know, about today, arrive at a single point of control, have a single point where you can enforce policy compliance, cost controls, et cetera, mm-hmm <affirmative>, and then expose a self-service experience to your developers that actually can become future proof. >>So we've heard this promise before the cloud of clouds, basically. Yes, the, the, to be able to manage everything, what we find is the devils in the details. The being able to say, you know, a load balancer issuing a, a command to, to deploy a load balancer in AWS is different than it is in Azure, which is different than it is in GCP. How do, how do enterprises know that we can talk to a single control plane to do that? I mean, that just seems extremely difficult to manage. Oh >>Yeah. That, um, the approach is not, you're not trying to create a lowest common denominator between clouds. That's a really, really hard problem. And in fact, you get relegated to just using this, you know, really shallow features of each, if you're, if you're gonna do that, like your, your example of load balancers, load balances look completely different between between cloud vendors. Um, the approach that we kind of advocate for is that you shouldn't think of them as you shouldn't try to unify them in a way that makes them, you know, there's a, uh, there's a global abstraction that says, oh, there's a load balancer. And it somehow magically works across the different cloud vendors. I think that's a really, really hard thing to say, to do as you point out. However, if you bring them all under a same control plane, As different as they are, you're able to now apply policies. You're able to set cost controls. You're able to expose a self-service experience on top of them, even, even if they are very different. And that's, that's something that I think is, you know, been hard to do in the past. >>So BAAM, we'll love to dig deeper into this in future segments. And I'm gonna take a look at the, the, the product and project <laugh> and see where you folks land in this conversation from Valencia Spain, I'm Keith towns. And along with Paul Gillon, and you're watching the leader in high tech.

>>The cube presents, Coon and cloud native con Europe 22, brought to you by the cloud native computing foundation. >>Welcome to vincia Spain in Coon cloud native con Europe, 2022. I'm Keith towns alongside en Rico senior. Etti senior it analyst for giong welcome back to the show en >>Rico. Thank you again for having me here. >>First impressions of QAN. >>Well, great show. As, as I mentioned before, I think that we are really in this very positive mode of talking with each other and people wanting to see, you know, the projects, people that build the projects at it's amazing. I mean, a lot of interesting conversation in the show floor and in the various sessions, very positive move. >>So this is gonna be a fun one. We have some amazing builders on the show this week, and none other than William Morgan, CEO of buoyant. What's your role in the link D project? >>So I was one of the original creators of link D but at this point I'm just the, the beautiful face of the project. >>Speaking of beautiful face of the project, linker D just graduated from as a CNCF project. >>Yeah, that's right. So last year we, we became the first service mesh to graduate in the CNCF. Very proud of that. And that's thanks, you know, largely to the incredible community around Linky that is just excited about the project and, you know, wants to talk about it and wants to be involved. >>So let's talk about the significance of that link D not the only service mesh project out there. Talk to me about the level effort to get it to the point that it's graduated. That's you don't see too many projects graduating CNCF in general. So let's talk about kind of the work needed to get Nier D to this point. >>Yeah. So, you know, the, the, the bar is high and it's mostly a measure, not necessarily of like the, the project being technically good or bad or anything, but it's really a measure of maturity of the community around it. So is it being adopted by organizations that are really relying on it in a critical way? Is it, you know, being adopted across industries, you know, is it having kind of a significant impact on the cloud native community? And so for us, you know, there was the, the work involved in that was really not any different from the work involved in, in kind of maintaining ity and growing the community in the first place, which is you try and make it really useful. You try and make it really easy to get started with you, try and be supportive and to, you know, have a, a friendly and welcoming community. And if you do those things and, you know, you kind of naturally get yourself to the point where it's a, it's a really strong community full of people who are excited about it. >>So from the of view of, you know, users adopting the, this technology, so we are talking about everybody, or do you see really, you know, large organization, large Kubernetes yeah. Clusters infrastructure adopting it. >>Yeah. So that's the answer to that is changed a little bit over time. But at this point we see Linky adoption across industries, across verticals, and we see it from very small companies to very large ones. So, you know, one of the talks I'm really excited about at this conference is from the folks at Xbox cloud gaming, who talked about, who are gonna talk about how they deployed Linky across, you know, 22,000 pods around the world to serve, you know, basically on demand video games, never a use case I would ever have imagined for Linky. And at the previous Kuan, you know, virtually Kuan EU, we had a whole keynote about how Linky was used to combat COVID 19. So all sorts of uses. And it really doesn't, you know, whether, whether it's a small cluster or large cluster it's equally applicable. >>Wow. So as we talk about link D service match, we obviously are gonna talk about security application control, etcetera. But in this climate Software supply chain is critical, right. And as we think about open source software supply chain, talk to us about the recent security audit of link dealer. >>Yeah. So one of the things that we do as part of a CNCF project, and also as part of, I, I think our relationship with our community is we have regular security audits, you know, where we, we engage security professionals who are very thorough and, you know, dig into all the details. Of course the source code is all out there, you know, so anyone can read through the code, but they'll build threat model analyses and things like that. And then we take their, their report and we publish it. We say, Hey, look, here's, you know, here's the situation. So we have earlier reports online, and this newest one was done by a company called trail of bits. And they built a whole threat model and looked through all the different ways that Linky could go wrong. And they always find issues. Of course, you know, it's, it would be very scary, I think, to get a report that was like, no, we didn't find yeah. Earth clean, you know? Yeah. Everything's fine. You know, should be okay. I don't know. Right. But they, you know, they did not find anything critical. They found some issues that we rapidly addressed and then, you know, everything gets written up in the report and, and then we publish it, you know, as part of an open source artifact >>Are, you let's say, you know, do they give you and add something? So if something happens so that you can act on the code before, you know, somebody else discovers the >>Yeah, yeah. They'll give you a preview of what they found. And then often, you know, it's not like you're going before the judge and the judge makes a judgment and then like off the jail, right. It's, it's a dialogue because they don't necessarily understand the project. Well, they definitely don't understand it as well as you do. So you are helping them, you know, understand which parts and, and your, you know, are, are interesting to look at from the security perspective, which parts are not that interesting. They do their own investigation of course, but it's a dialogue the entire time. So you do have an opportunity to say, oh, you told me that was a, a, a minor issue. I actually think that's larger or, or vice versa. You know, you, you think that's a big problem. Actually, we thought about that, and it's not a big problem because of whatever. So it's a collaborative process. >>So link D been around, like, when I first learned about service me link D was the project that I learned about. Yeah. It's been there for a long time, but just mentioned 22,000 clusters. That's just mind boggling pod, 22,000 pods, the pods. Okay. >>Clusters would be >>Great. Yeah. Yeah. Clusters would be great too, but filled 22 thousands pods, big deployment. That's the big deployment of link D but all the way down to the small, smallest set of pods as well. What are some of the recent project updates from of the learnings you bought back from the community and updated the, the project as a result? >>Yeah. So a big one for us, you know, on the topic of security link, a big driver of link adoption is security and, and less on the supply chain side and more on the traffic, like live traffic security. So things like mutual TLS. So you can encrypt the communication between pods and make sure it's authenticated. One of the recent feature additions is authorization policy. So you can lock down connections between services and you can say service a is only allowed to talk to service B. And I wanna do that. Not based on network identity, you know, and not based on like IP addresses, cuz those are spoof. And you know, we've kind of like as an industry moved, moved, we've gotten a little more advanced from that, but actually based on the workload identity, you know, as captured by the mutual TLS certificate exchange. So we give you the ability now to, to, to restrict the types of communication that are allowed to happen on your cluster. >>So, okay. This is what happened. What about the future? Can you give us, you know, into suggestion of what is going to happen in the medium and long term? >>I think we're done, you know, we graduated, so we're just gonna >>Stop there's >>What else is there to do? There's no grad school, you know? No, no. So for us, there's a clear roadmap ahead, continuing down the, the security realm, for sure. We've given you kind of the very first building block, which at the service level, but coming up in, in the two point 12 release, we'll have route based policy as well, as you can say, this service is only allowed to call these three, you know, routes on this end point and we'll be working later to do things like mesh expansion so we can run the data plane outside of Kubernetes. You know, so the control plane will stay in in Kubernetes, but the data plane will, you'll be able to run that on VMs and, and, and things like that. And then of course in the, you know, we're also starting to look at things like I like to make a fun of WAM a lot, but we are actually starting to look at WAM in, in the ways that that might actually be useful for Linky users. >>So we talk a lot about the flexibility of a project, like link D you can do amazing things with it from a security perspective, but we're talking still to a DevOps type cloud of, of, of developers who are spread thin across their skillset. How do you help balance the need for the flexibility, which usually becomes more nerd knobs and servicing a crowd that wants even higher levels of abstraction and simplicity. >>Yeah. Yeah. That's a great question. And this is, this is what makes Linky so unique in the service mesh spaces. We have a laser focus on simplicity and especially on operational simplicity. So our audience, you know, we can make it easy to install Linky, but what we really care about is when you're running it and you're on call for it and it's sitting in this critical, vulnerable part of your infrastructure, do you feel confident in that? Do you feel like you understand it? Do you feel like you can observe it? Do you feel like you can predict what it's gonna do? And so every aspect of Linky is designed to be as operationally simple as possible. So when we deliver features, you know, that's always our, our primary consideration is, you know, we have to reject the urge. You know, we have an urge as, as engineers to like want to build everything, you know, it's an ultimate platform to solve all problems and we have to really be disciplined and say, we're not gonna do that. >>We're gonna look at solving the minimum possible problem with a minimum set of features because we need to keep things simple. And, and then we need to look at the human aspect to that. And I think that's been a part of, of Link's success. And then on the buoyant side, of course, you know, I don't just work on link day. I also work on, on buoyant, which helps organizations adopt Linky and, and increasingly large organizations that are not service mesh experts don't wanna be service mesh experts that, you know, they wanna spend their time and energy developing their business, right. And, and building the business logic that powers their company. So for them, we have actually re recently introduced, fully managed. Linky where we can take on, even though Linky has to run on your cluster, right? The, the, the, the sidecar proxies has to be alongside your application. We can actually take on the operational burden of, of upgrades and trust, anchor rotation, and installation. And you can effectively treat it as a utility, right. And, and, and have a, a hosted, like, experience, even though the, the actual bits, at least most of them, not all of them, most of 'em have to live on your cluster. >>I love the focus of most CNCF projects, you know, it's, it's peanut butter or jelly, not peanut butter. Yeah. Trying to be become jelly. Right. What's the, what's the, what's the peanut butter to link D's jelly. Like where does link D stop and some of the things that customers should really consider yeah. When looking at service mesh. >>Yeah. No, that's a great way of looking at it. And I, I actually think that that philosophy comes from Kubernetes. I think Kubernetes itself, one of the reasons it was so successful is because it had some clearly delineated, it said, this is what we're gonna do. Right. And this is what we're not gonna do. So we're gonna do layer three, four networking. Right. But we're gonna stop there. We're not gonna do anything with layer seven. And that allowed the service mesh. So I guess if I were to go down the, the bread, the bread of the sandwich has Kubernetes, and then Linky is the, is the peanut butter, I guess, and then the jelly, you know, so I think the jelly is every other aspect of, of building a platform. Right. So if you are the, the audience for Linky, most of the time, it's a platform owners, right. They're building a platform, an internal platform for their developers to write code. And so, as part of that, of course, you've got Kubernetes, you've got Linky, but you've also got a C I CD system. You've also got a, you know, a code repository, if it's GitLab or, or GitHub or wherever you've got, you know, other kind of tools that are enforcing various other constraints. All of that is the jelly, you know, in the, this is, analogy's getting complicated now. And like the, the platform sandwich that, you know, that you're serving. >>So talk to us about trans and service mesh from the, from the, as we think of the macro. >>Yeah. Yeah. So, you know, it's been an interesting space because we were talking a little bit about, you know, about this before the show, but the, there was so much buzz, you know, and then what we, what we saw was basically it took two years for that buzz to become actual adoption, you know, and now a lot of the buzz is off on other exciting things. And the people who remain in the Linky space are, are very focused on, oh, I actually have a, a real problem that I need to solve and I need to solve it now. So that's been great. So in terms of broader trends, you know, I think one thing we've seen for sure is the service mesh space is kind of notorious for complexity, you know, and a lot of what we've been doing on the Linky side has been trying to, to reverse that, that, that idea, you know, because it doesn't actually have to be complex. There's interesting stuff you can do, especially when you get into the way we handle the sidecar model. It's actually really, it's a wonderful model operationally. It's really, it feels weird at first. And then you're like, oh, actually this makes my operations a lot easier. So a lot of the trends that I see at least for Linky is doubling down on the sidecar model, trying to make side cards as small and as thin as possible and try and make them, you know, kind of transparent to the rest of the application. So >>Well, William Morgan, one of the coolest Twitter handles I've seen at WM on Twitter, that's actually a really cool Twitter handle. Thank you, CEO of buoyant. Thank you for joining the cube again. Cube alum from Valencia Spain. I'm Keith towns, along with en Rico, and you're watching the cube, the leader in high tech coverage.

>>The cube presents, Coon and cloud native con Europe 22 brought to you by the cloud native computing foundation. >>Welcome to Licia Spain in Coon cloud native con Europe, 2022. I'm your host, Keith Townson, along with Paul Gillon senior editor, enterprise architecture for Silicon angle. Paul, we're gonna talk to some amazing people this week. Coon, what the energy here, what, what, what would you say about >>It? I'd say it's reminiscent of, of early year, early stage conferences I've seen with other technologies. There is a lot of startup activity. Here's a lot of money in the market, despite the selloff in the stock market lately, a lot of anticipation that there are, there could be big exits. There could be big things ahead for these companies. You don't see that when you go to the big established conferences, you see just anticipation here that I don't think you see you you'll see maybe in a couple of years. So it's fun to be here right now. I'm sure it'll be a very different experience in two or three years. >>So welcome to our guest Q alum. BAAM Tobar the founder and CEO of Upbound. Welcome back. >>Thank you. Yeah, pleasure to be on, on the show again. >>So Paul, tell us the we're in this phase of migrations and, and moving to cloud native stacks. Are we another re-platforming generation? I mean, we've done, the enterprise has done this, you know, time and time again, and whether it's from Java to.net or net to Java or from bare metal to VMs, but are we in another age of replatforming? >>You know, it's interesting. Every company has now become a tech company and every tech company needs to build a very model, you know, modern digital platform for them to actually run their business. And if they don't do that, then they'll probably be out of business. And it is interesting to think about how companies are platforming and replatforming. Like, you know, as you said, just a, a few years back, you know, we were on people using cloud Foundry or using Heroku, you hear Heroku a lot, or, you know, now it's cloud native and Kubernetes and, and it, it begs the question, you know, is this the end that the tr point is this, you know, do we have a, you know, what, what makes us sure that this is the, you know, the last platform or the future proof platform that, that people are building, >>There's never a last platform, right? There's always something around the core. The question is, is Kubernetes Linux, or is it windows? >>That, that's a good question. It's more like more like Linux. I think, you know, the, you know, you've heard this before, but people talk about Kubernetes as a platform off platforms, you can use it to build other platforms. And if you know what you're doing, you can probably put, assemble a set of pieces around it and arrive at something that looks and can work for your business. But it requires a ton of talent. It requires a lot of people that actually can act, you know, know how to put the stick together to, to work for your business. It is, there's not a lot of guidance. I, we were, I think we were chatting earlier about the CSCF landscape and, and how there all these different projects and companies around it. But, but they don't come together in meaningful ways that you have, they act the enterprise itself has to figure out how to bring them together. Right. And that's the combination of what they do there organically or not is their platform. Right. And that changes. It can change over time. >>Do you think they really do. They really want to put these things together? I mean, there's, that's not what enterprise is like to do. They want to find someone who's gonna come in and turnkey do it all for >>Them. Yeah. And, and if there were, this is the, this is the things like EV every week now you hear about another platform that says, this is the new Heroku. This is the new cloud Foundry. This replaces every, you know, some vendor has, and you can see them all around here. You know, companies that are basically selling platform solutions that do put 'em together. And the problem with it is that you typically outgrow these, like you are, it might solve 80% of the use cases you care about, but the other 20% are not represented. And so you end up outgrowing the platform itself, right? And the, the choice has been mostly around, you know, do you buy something off the shelf that solves 80% of your use cases? Or do you build something on your own? And then you have to spend all your resources actually going through and building all of it. And that's been the dilemma, you know, people who talk about this as a platform dilemma, but it's been, it's been the way for a long time. Like you, every, we go through this cycle every few years and, you know, people end up essentially oscillating between buying something off the, you know, that's off the shelf or building it, building it themselves. >>So what's the payoff. If I'm a CIO and I'm looking at the landscape, I don't need to understand, you know, I don't know what a pod is to know that looking at 200 plus projects in co and at, in cloud native foundation and the bevy of, of co-located projects and, and conferences before the, even the start of this, what's the payoff >>Increasing the pace of innovation. I mean, that literally is when we talk to customers, they all say roughly the same thing. They want something that works for their business. They want something that helps them take their, you know, line of business applications to production in a much quicker way, lets them innovate, lets them create higher engineers that can, don't have to understand everything about every system, but can actually specialize and focus on the, the parts that they sh they care about. But it's all in the context of, you know, people want to be able to innovate at a very high pace. Otherwise they get disrupted. >>So I was at the, you know, my favorite part of coan in general is the hallway track and talking to people on the ground, doing cool things. I was talking to a engineer who was able to take their Java, stack their, their.net stack and start to create APIs between and break 'em into microservices. Now teams are working across from one another realizing that, that, that promise of innovation, but that was the end point. They they're there. Yeah. As companies are thinking about replatforming where like, where do we start? I mean, I'm looking at the, the C CNCF, the, the map and it's 200 plus projects. Where, where do I start? >>You typically today start with Kubernetes. And, and a lot of companies have now deployed Kubernetes to production as a container orchestrator, whether they're going through a vendor or not. But now you're seeing all the things around it, whether it's C I C D or GI ops that they're looking at, you know, or they're starting to build consoles around, you know, their, their platforms or looking at managing more than just containers. And that's a theme that, you know, we're seeing a lot now, people want, people want to actually bring this modern stack to manage, not just container workloads, but start looking at databases and cloud workloads and everything else that they're doing around it. Honestly, everybody's trying to do the same thing. They're trying to arrive at a single point of control, a single, you know, a platform that can do it all that they can centralize policies, centralized controls to compliance governance, cost controls, and then expose a self-service experience to the developers. Like they're all trying to build what we probably call an internal cloud platform. They don't know, they talk about it in different ways, but almost everyone is trying to build some internal platform that sits on top of, on premises. And on top of cloud, depending on their scenarios, >>You make an interesting point, which is that everyone here is to some extent trying to do the same thing. And there's fine points of granularity between now they're approaching it as you walk around this floor. Do you understand what all of these companies are doing? >>I'm not sure I understand all of them, but I, I do. I do recognize a lot of them. Yes. >>And in terms of your approach, you, you use the term control plane. What is distinctive about your approach? >>Very good question. So, you know, we, we end, Upbound take a, we we're trying to solve this problem as well. We're trying to help people build their own platforms, but let me, let me, you know, there's a lot to it. So let me actually step back and, and talk about the architecture of this. But if you were to look at any cloud platform, let's take the largest one. AWS, if you peek behind the scenes at AWS, you know, it's basically a set of independent services, EC two S three databases, et cetera, that are, you know, essentially working on different parts of, you know, like offer completely different pricing, different services, et cetera. They come together because they all integrate into a control plan. >>It's the thing that serves an API. It's the thing that gives it all a common feel. It's where you do access control. It's where you do billing metering, cost control policy, et cetera. Right? And so our realization was if the enterprises are platforming and replatforming, why shouldn't they build their platform in the same way that the cloud vendors build theirs? And so we started this project almost four years ago, now three and a half years called cross plain, which is a, essentially an open source control plane that can become the integration point for all services. And essentially gives you a universal control plane for cloud. >>So you mentioned the idea of if orchestrating or managing stuff other than containers, as I think about companies that built amazing platforms, enterprise companies, building amazing applications on AWS 10 years ago, and they're adopting the AWS control plane. And now I'm looking at Kubernetes is Kubernetes the way to multi-cloud to be able to control those discrete services in a AWS or Google cloud Azure or Oracle cloud, is that true? >>We kind have the tease it, the parts. So there are really two parts to Kubernetes and everybody thinks of Kubernetes as a container orchestration platform. Right? And you know, there is a sense that people say, if I was to run Kubernetes on everywhere and can build everything on top of containers, that I get some kind of portability across clouds, right. That I can put things in containers. And then they magically run, you know, in different environments. In reality, what we've seen is not everything fits in containers. It's not gonna be the world is not gonna look like containers on the bottom. Everything else is on top. Instead, what we're gonna see is essentially a set of services that people are using across the different vendors. So if you look at like, you could be at AWS shop primarily, but I bet you're using confluent or elastic or data breaks or snowflake or Mongo or other services. >>I bet you're using things that are on premises, right? And so when you look at that and you say to build my platform as an enterprise, I have to consume services from multiple vendors. Even if it's just one major cloud vendor, but I'm consuming services from others. How do I bring them together in meaningful ways so that I can, you know, build my platform on top of the collection of them and offer something that my developers can consume. And self-service on. That's not a, that's not just containers. What's interesting though, is if you look at Kubernetes and, you know, look inside it, Kubernetes built a control plane. That's actually quite useful and applicable outside of container scenarios. So this whole notion of CRDs and controllers, if you've heard that term, the ability, you know, like there are two parts to Kubernetes, there is a control plane, and then there's the container container workloads. >>And the control plane is generic. It could be used literally across, you know, you can use it to manage things that are completely outside of container workloads. And that's what we did with cross mind. We took the control plane of Kubernetes and then built bindings providers that connected to AWS, to Google, to Azure, to digital ocean, to all these different environments. So you can bring the way of managing, you know, the style of managing that Kubernetes invented to more than just containers. You can now manage cloud services, using the same approach that you are now using with Kubernetes and using the entire ecosystem of tooling around it. >>Enterprise has been under pressure to replatform for a long time. It was first go to Unix then to Linux and virtualize then to move to the cloud. Now, Kubernetes, do you think that this is the stack that enterprises can finally commit to? >>I think if you take the orientation of your deploying a control plane within your enterprise, that is extensible, that enables you to actually connect it to all the things that are under your domain, that that actually can be a Futureproof way of doing a platform. And, you know, if you look at the largest cloud platforms, AWS has been around for at least 15 years now, and they really haven't changed the architecture of AWS significantly. It's still a control plane, a set of control planes that are managing services. >>It's a legacy >>They've added a lot of services. They've have a ton of diversity. They've added so many different things, but the architecture is still a hub and spoke that they've built, right? And if the enterprise can take the same orientation, put a control plane, let it manage all the things that are, you know, about today, arrive at a single point of control, have a single point where you can enforce policy compliance, cost controls, et cetera, and then expose a self-service experience to your developers that actually can become future proof. >>So we've heard this promise before the cloud of clouds, basically, yes, the, the, to be able to manage everything, what we find is the devils in the details. The being able to say, you know, a load balancer issuing a, a command to, to deploy a load balancer in AWS is different than it is in Azure, which is different than it is in GCP. How do, how do enterprises know that we can talk to a single control plane to do that? I mean, that just seems extremely difficult to manage. >>Oh yeah. That the approach is not, you're not trying to create a lowest common denominator between clouds. That's a really, really hard problem. And in fact, you get relegated to just using this, you know, really shallow features of each, if you're, if you're gonna do that, like your, your example of load balancers, load balances look completely different between between cloud vendors, the approach that we kind of advocate for is that you shouldn't think of them as you shouldn't try to unify them in a way that makes them, you know, there's a, there's a global abstraction that says, oh, there's a load balancer. And it somehow magically works across the different cloud vendors. I think that's a really, really hard thing to say, to do as you pointed out. However, if you bring them all under a same control plane, as different as they are, you're able to now apply policies. You're able to set cost controls. You're able to expose a self-service experience on top of them, even, even if they are very different. And that's, that's something that I think is, you know, been hard to do in the past. >>So BAAM, we'll love to dig deeper into this in future segments. And I'm gonna take a look at the, the, the product and project and see where you folks land in this conversation from Valencia Spain, I'm Keith towns, along with Paul Gillon and you're watching the leader in high tech coverage.

>>Yeah. Hello and welcome to the Cuba's International Women's Showcase, featuring International Women's Day. I'm John, host of the Kiwi here in California. Great remote guest. She's amazing founder and C e O of Cuba, and great to see you. Okay, thanks for coming on. Um, good to see you. >>You as well. Always a pleasure. You >>know, International Women's Day is the big celebration. We're doing a lot of interviews with great people making things happen, moving and shaking things. Um, but every day, International Women's Day, As far as I'm concerned, it's happening all around the world. But these are stories of innovation, the stories of changes, the stories of transformation for the better. You've been doing a lot of things. Um and I want to get into that. But let's start with your background. Tell us a bit about who you are and what you've got going on. >>Yeah, my background is a little strange. I used to be a maritime archaeologists. So dumb shit breaks for a little bit. That was amazing. I always just It's only partial just because it's actually a bit of truth to it, that learning how to, you know, handle things at depth really does train you to be a C e o. Because you learn to control your breath and and focus on the things that matter and not be so reactive because it's three activity that will panic that will kill you. Uh, always knowing how to reframe. Return to the basics. Um, there's a really good things to hold on to, even in the world of business. Right? So I at some point, ended up doing doing a lot of things. Largely business development, following my time diving and amazing woman. Um, another woman for International Women's Day named Doctor who was a biotech entrepreneur from Japan, stepping down as her role at the helm of her company. Um, and she wanted to launch a space for a young innovators from around the world who are doing amazing work to tackle this very complex challenges we all know exist, um, and figure out a way to give them time and space to do their best work and pursue their their highest visions for change. We decided that we would focus on for-profit companies largely who were using sustainable, scalable business models to pursue both profit and purpose. Um creating a virtuous cycle between the return of money to a company and putting that into to go even further and faster towards, um, solving a problem. Um, so we now have companies over 200 companies from around the world that we have helped support tackling every single, sustainable development goal. Um, and I'm proud to say, you know, particularly related to the subject that fifty-nine percent of our companies have a woman founder or CO-FOUNDER. Um, and 69% of the founder of color. Um, so we're working with entrepreneurs from every every area of the world. Many approximate to the problem that they are trying to solve, so they intimately understand it. Um, and they're doing amazing things. >>Yeah, you can help the great mission. You have a lot of other things going on your helping women encouraging them to your career in the tech sector. Um, good statistics could be better, right? Is higher and better. So, um, what are you guys doing? What, you specifically to help and encourage women to forge their career and tech? >>Yeah. I mean, look, the good news is I do think that it's getting better. I particularly think that we will see the adventure is improving. Um, it takes a while because the companies that have been funded up until now are still working in the biggest amount in the later stages. So I think that percentage hasn't been shifting. But I have to believe that that's a bit of an illusion, and then a couple of years, we're going to start to sea level out. But you know as well as I do that they're pretty poultry statistics in terms of the amount of venture that women like cos. Capture, Um, and the other ways that women are doubted, um, in terms of their ability and potential. Um, so we we love to work with any underrepresented group of entrepreneurs, and there's ways that we do that whether it's helping them sort of find their power and hold space and be confident. And, um, you know, be able to pitch to any room, talk to any investor, talk to any customer but also working to be directed about some of the systemic challenges, both in terms of talking to existing investors and trying to educate them to see the opportunities that they're missing because there is a an economic imperative to them understanding what they're missing. Um, but there's also some things that we're doing in-house to make sure that we're also helping to close capital gaps for all our entrepreneurs. So we actually now have a suite of three capital mechanisms that are entrepreneurs can access on the back end of our incubator, a microphone fund, which is very quick turnaround, small amounts of capital for entrepreneurs who existing opportunities owns, which is a tax destination. Just this in the U. S. But that's meant to be deployed so that they can access capital towards revenue without credit checks, collateral being put up, a slow moving pace of banks and C. D. S s. It's particularly useful for people who may not raise venture. And it's useful for, uh, you know, people who maybe don't have that friends and family check that they can expect similar. We've got a great angel network who look at the best impact deals from around the world. Um, and it doesn't have to be a housing company, just a great venture that's pursuing impact on profit. Um, and then lastly, we're just about to announce that we have a fund of our own on the back end of our incubator that funds only healthy and companies. Um, it's an early stage fund. Um, but watch this space because our pipeline is just increasing your every year. We used to sort of just 16 companies here. Now, we're serving 60 this year, so, um, yeah, it's really exciting. Um, and so obviously, it's really great that, you know, we're going to be able to help scale the impact that we want to see. Uh, ideally a lot. A lot faster. >>Well, you definitely taking control. I remember when we had a few years ago. I think four years ago, you just thinking about getting going and going now with great tailwind. Um, >>and the diversity >>of sources of capital as well as diversity of firms is increasing. That's helping, uh, that we're seeing, but you're also got the back end fun for the housing companies. But also, you've been involved in we capital for a long time. Can you talk about that? Because that's a specific supporting women entrepreneurs initiative. Um, yeah. What's up with capital share? That >>was That was another venture that I-i embarked on with such coz. Um as well as Sheila Johnson and Jonny Adam, Person who runs Rethink Impact. We capital is a group of about 16 women that I pulled together women investors to invest through rethink impact, which is another fun that is looking for impact businesses but predominantly looking for those businesses that are led by women. So this investment group is women supporting women. Um, through the use of deployment of capital, um, they're doing amazingly well. They've had some really stunning news recently that I'll let you dig up. >>I'll definitely thanks for the lead there. I'm gonna go jump on that story. >>Yeah, >>the Okay, Thanks for that lead on that trend, though in Silicon Valley and certainly in other areas that are hot like New York, Boston and D. C. Where you're at, um, you're seeing now multiple years in almost a decade in of the pioneers of these women, only funds or women only firms and your investment. Um, and it's starting to increase to under all underrepresented minorities and entrepreneurs. Right? So take us through how you see that because it's just getting more popular. Is that going to continue to accelerate in your mind? Are their networks of networks. They cross pollinating. >>Yeah, I think you know, it's It's I'm glad to see it. And, you know, it's been a long time coming. I think you know, I think we all look forward to a future where it's not necessary. Um, and you know, funds. Just invest in everyone Until then, making sure that we have specific pools of capital allocated to ensure that that, you know, those entrepreneurs who have not always been equally represented get to pursue their ideas not just because they deserve to pursue their ideas, but because the world needs their ideas. Right. And as I mentioned, there is a business imperative, right? We've got lots of examples of businesses like banks that you wouldn't have gotten a shot just because the investors just didn't understand the opportunity. Um, and I think that's normal. That's human. It happens to everyone. You are successful as an investor largely because you recognize patterns. And if something is, you know, outside of your life experience, you are not going to identify it. So it's very important that we create different kinds of capital run by different types of people. Um, and, uh, and you know. I know lots of investors have every type that are investing in these funds because they recognize that, you know, perhaps the highest growth potential is gonna come out of these, you know, particular kind of funds, which is really exciting. >>That's super important, because half the world is women, and that's just like the population is inspired by many new ventures. And that's super exciting trend. I wanna ask you about your other areas of doing a lot of work in the queue has been to buy multiple times, um, initially reporting on a region out there, and that's certainly isn't important part of the world. Um, you've got a lot of good news going on there. Can you share what's going on with, uh, the social entrepreneurship going on in Bahrain around the region? >>Yeah, I'm happy to. We we've actually been so privileged to work with a W S for a very long time. Almost since the start of the incubator they've supported are entrepreneurs, all of our entrepreneurs with access to cloud credits and services. Um, and we've sort of double down with a W S in the last couple of years in areas where We both want to create an uplift, um, for small businesses and rapidly growing tax solutions to these these social environmental problems. We see. So there's been an excellent partner to do that. And one of the areas we did in the water was with rain, particularly with women, tech startups, women tech startups in Bahrain. Yeah, we did that last year. We had an amazing group of women over in D. C. Um, and we continue to support them. One of them is actually in the process of raising. I think she just closed her seed round recently. And that's why for, um, al yet, um, and she created playbook, which is an amazing, uh, platform for women to take master classes and network and really sort of level up, as one says, Um, but also, um, the mall of work. Um uh, just really talented women over in Bahrain, um, pushing the envelope and all sorts of directions, and it was wonderful to get the opportunity to work with them. Um, that has now spawned another set of programs serving entrepreneurs in the Middle East in North Africa. They were also working on with us as well as the U S. State Department. Um, so we're going to be working for the next two years with entrepreneurs to help our recovery from covid. Um, in China. Um, and then I'm also proud to say that we're working with a W s in South Africa because there is just an extraordinary energy, you know, in the continent, Um, and some amazing entrepreneurial minds working on, you know, the many problems and opportunities that they're facing and recognizing. Um So we're supporting, you know, companies that are working on finding, um, skilled refugees to be able to help them resettle and use their talents and make money. Um, sadly, are very relevant company now with what's going on in Ukraine. Um, but also, uh, zombie and satellite company, um, companies that are preventing food, food waste by providing, um, solar-powered refrigerators to rural areas in South Africa. Um, so a lot of, um, you know, just incredible talent and ideas that we're seeing globally. Um, and happy to be doubling down on that with the help of a W s. >>That's awesome. Yeah, following the work when we met in D. C. And again, you always had this international view um it's International Women's Day. It's not North America >>Women's Day. It's >>International Women's Day. Can you share your thoughts on how that landscape is changing outside the U. S. For example, and around the world and how the international peace is important and you mentioned pattern matching? Um, you also, when you see patterns, they become trends. What do you see forming that have been that that are locked in on the U. C they're locked in on that are happening that are driving. What are some of those trends that you see on the international side that's evolving? >>Yeah. You know, I think the wonderful opportunity with the Internet and social media is that, you know, both, uh, we can be more transparent about areas for improvement and put a little pressure where maybe things are moving fast enough. We've all seen the power of that, Um, the other, um, you know, things that certainly in countries where women maybe as free to move and operate, they can still acquire skills education they can set up cos they can do so so much. Um, you know, through these amazing technologies that we now have at our disposal growing an amazing rates. Um, they can connect via zoom. Right? I think that while the pandemic definitely set women back and we should acknowledge that, um, uh, the things that the pandemic perhaps helped us to exponentially scale will move women forward. And perhaps that's the target to hang on to, to feel optimistic about where we're headed. >>And also, there's a lot of problems to solve. And I think one of the things we're seeing you mentioned the Ukraine situation. You're seeing the geopolitical landscape changing radically with technology driving a lot of value. So with problems comes opportunities. Um, innovation plays a big role. Can you share some of the successful stories that you were inspired by that you've seen, um, in the past couple of years. And as you look forward, what What some of those innovation stories look like? And what are you inspired by? >>Yeah. I mean, there's so, so many. Um, you know, we just, uh, had a couple of entrepreneurs, and just the last year, Um, you know, after I think everyone sort of took an initial breath with the pandemic, They realize that they either had an opportunity or they had a problem to solve to your point. Um, and they did that well or not. And or some of them, you know, just didn't didn't have any more cards to play and had to really pivot. Um, it was really interesting to see how everyone handled handled that particular moment in time. One company that I think of is everywhere. Um, and she had created a wearable device that you can just put on your ear. It looks like an earring right at the top of your ear. Um, and it was for her for herself because she suffered from pulmonary complications. And, uh, without more discreet wearable, you know, had to wear a huge device and look around and oxygen tank and, you know, just to sort of have a good quality of life. Um, it turns out, obviously, during covid, that is a very useful item, not just for patients suffering from covid and wanting to know what their oxygen levels were doing, but also potentially athletics. So, um, she's really been able to double down as a result of the trends from the pandemic. Um, and I'm really proud of part of her. And that's actually where another great one that we just just came through. Our last 15 is Maya. Um, and she had a brick and mortar store. Um, uh, called Cherry Blossom. Intimate where she helped women have an enjoyable experience finding, uh, and fitting bras post mastectomy to include sort of, you know, the necessary, um, prosthetics and things like that. Um, she even made it so that you could go with your friends who haven't had a mistake, and she could also find some lovely luxury. Um, but the pandemic meant that that experience was sort of off the table. Um, and what they did was she decided to make it a technological one. So now she's she's essentially will be part of it. You can, you know, go to my, um, online. And you can, um, you know, order, uh, measure yourself, work with a specialist, all online, get a few different options, figure out the one that's perfect for you and the rest back. Um, and I don't think without the pandemic, that would not have happened. So she's now able to serve exponentially more. Um, you know, women who deserve to feel like themselves post it to me. >>That's also a model and inspirational. I have to ask you for the young women out there watching. What advice would you share with them as they navigate into a world that's changing and evolving and getting better with other women, mentors and entrepreneurs and or just an ecosystem of community? What advice would you give them as they step into the world and have to engage and experience life? >>Yeah, gosh, part of me always wants to resist that they don't listen to anyone to do you follow your heart, follow your gut, or at least be careful who you listen to because a lot of people will want to give you advice. I would >>say, Uh, that's good advice. Don't take my advice. Well, you've been a great leader. Love the work, you're doing it and I'll say N D. C. But all around the world and again, there's so much change going on with innovation. I mean, just the advances in technology across the board, from with machine learning and AI from linguistics and understanding. And I think we're going to be a bigger community. Your thoughts on as you see community organically becoming a big part of how people are engaging. What's your what's your view As you look out across the landscape, communities becoming a big part of tribes. What's your vision on how the role of communities place? >>You know, we we actually do you think a lot about community and healthy. And we say that are you know, alchemy really is providing space, you know, physical and mental space to think, um, access access to capital access to networks, Um, community, Um, and the community piece is very, very important. Are entrepreneurs leave us like the number one thing that they miss is being among like-minded, um, you know, slightly slightly crazy audacious people. Um, and I often joked that we're building a kind army because it is, you know, it's people who want to do it differently if people want to do it with integrity. Is people who are in it for a very different motivations than just money. Um, and, you know, you start to feel the power of that group together and its entirety and what that might look like as as a community solving global problems. Um, and it really is inspiring. Um, I do think that people are starving for FaceTime and people time, real human time after the pandemic, I think they won't go away. It's a great tool, but we all want a little bit of that, and I will mention just along those lines. And if you don't mind a quick plug for an event that we're having March 16, Um, also in partnership with a W s called Build her relevant to International Women's Day as well. People can, either. If they're in the city, they can come in person. But we also have a virtual program, and we'll be listening to some of the most inspiring. Women leaders and entrepreneurs both in government and also the private sector share their knowledge on the side of the pandemic for for, you know, the next tribal group of women entrepreneurs and leaders. >>That's great. Well, you are on our website for sure. >>Thank you. Thank you. Appreciate it. >>And we love the fact that you're in our community as well. Doing great work. Thanks for spending time with the Cube and on International Women's Day celebration. Thanks for coming on and sharing. >>Thank you, John. >>Okay. The Cube International showcase Women's Day, featuring some great guests all around the world, Not just in the U S. But all over the world. I'm your host. Thanks for watching. Yeah, Yeah, yeah, hm, Yeah.

>>Yeah. Hello. Welcome to the Cubes International Women's Showcase, featuring International Women's Day. I'm John for your host of the queue here in Palo Alto, California. And we have three great guests videoing in from Kuala Lumpur as well as Bangkok. Johann Kwa, group CEO of K s K Group. It's just a Christina Equal, co founder and head of K s, K C Labs and Cindy, co founder of Sunday Insurance in Bangkok. Ladies. Thanks for coming on the cue. Appreciate you coming on. Thanks for Thanks for joining me on this special day. >>Thank you. Thank you so much. You >>guys are three sisters, trailblazing and the insurance and real estate through digital transformation in the cloud taking a three decade old family business to the next level raising the bar, as they say in the cloud business. Congratulations. Tell us how it all started. What's going on now? What does it look like? Where did it come from? Tell the Storey. >>Okay, so maybe I'll start, Uh, you know, since I'm at the group CEO level. So, um, as a quick introduction, you know? Okay. SK group, uh, were about 30 years old now, as a group three decades. Um, we started off as an insurance, uh, nonlife insurance company. Um, and then over the years, um, you know, we we operate in in South East Asia, So we are based in the US and markets. That message is also sitting in, um, and very quickly over the years, you know, we decided to actually venture into property development as well. Um, and really across the journey. Um, you know, we we've always been very, um, obsessed over the customers. You know, uh, and, you know, during this time and age, you know, all the customers are really digital natives now, and and, you know, the tech is very, very interesting. And so So starting in the year of 2017, we decided, um, to actually venture. Cindy and I at least we decided to start up our own, uh, tech, uh, called Sunday. Uh, Cindy is now the full time CEO and co founders. Um, and, you know, uh, it's an exciting journey from then on, uh, where now The first full stack ensure attack in in the whole of of the Asian market, uh, starting off in Thailand. Um, And then when Christine came back, to join the business. You know, since we were already in real estate, we decided, taking on from the inspiration of what we did with Sunday, how about we do the same in in in property? Because we obviously saw, you know, there was super loads of opportunities that we could we could we could do. And and a year ago, we gave birth to cast a city lapse. Um, now a prop tech company based in Malaysia. >>Christine and Cindy tell the storey here because this is actually fascinating. Storey, your sisters, your entrepreneurial. So you know each other? You're related and you've got ups and downs with the startups and growing companies changing landscape. A lot of challenges. You all gotta get along all the time. How's it going? What's it like? Mm. >>Maybe I'll start. I think I think for me I'm probably the newest addition to the trio in the, you know, working together kind of space. So for me, I think it's all about really learning how to, you know, separate your professional and personal life. And like you mentioned, you know, we live together. But we also work together. So for me, I think I took a >>lot of advice >>and direction. Um, both from Johann and, >>uh, help >>me a lot. Um, so So I think that's been my experience. Been great So far, Um, they've been really, really supportive. And I think going through this journey of, you know, like, founding a company together, it's obviously very challenging. And so I feel very fortunate to have two sisters who have already gone through it once, you know? >>So for the other guests is trying to get on the cube here. Over there. Um, sounds like fun. Uh, Christine. So on the city labs, you gotta cheque side of it there in the in the property tech. That's exciting. How's it going over there? >>Uh, super, Super cool. Super fun. Uh, has been one heck of a journey building a company from scratch, let alone in tech. I think you know, we created K s K C d lives because we really wanted to modernise the real estate industry, uh, and create, like, super transformative solutions, uh, many for two reasons. You know, one is to improve the quality of life, um, of the community around us. Uh, and secondly, really to harness all the technology and this unused data right in the real estate industry. And try and say, how can we use that to make more intelligent business decisions? Yeah, so So really, Um, I guess for us, it's been really exciting because we've launched two products. Uh, you know, one of which is Ai driven, dynamic pricing engine. And we realised that actually, the way that homes are priced today, uh, in real estate is super RK right? You only use a few basic variables. Like, how big is your house? What views do you have? But then we realised that, actually hey, with a I where you suddenly can use, like, hundreds of variables, um, and even, you know, consisting of wellness variables, for example. Um, and you can really customise pricing all the way down to a single unit level. Uh, and we realise that by doing this, we could actually unlock, um, ferret prices for our customers while also constantly kind of tracking the financial health of the company. >>Awesome. Cindy, I wanna get you in here. A co founder, Sunday Insurance. That was the origination. But a lot of change data drives everything machine learning. You gotta have the state of the art. What's going on with you? >>Yeah, I think for us, essentially, uh, we're operating in a very old industry. Um, it's one of the oldest industries globally. And if you look at the entire insurance value chain, um, every part of the process can actually, it's all about data. You can. It can be disrupted. Um, but yet every inch of the value chain is also regulated. So I think essentially what we're trying to do is, um, we're trying to really innovate the customer journey. So imagine if, um, even in the States now and even coming back to Asia, a lot of how people buy insurance is still very face to face agency. But I think in the future is going to be remote online on your app, through any partners as well. So I think, uh, we're trying to adopt any machine learning to really scale and automate, uh, the journey of anyone who's trying to buy insurance. But at the same time for insurance companies were also trying to help them automate that function itself. So imagine if banks are trying to dish out loans and you're trying to predict. What's the credit risk of every, um, single customer? That's exactly what insurance company needs to do as well. Um, And I guess insurance is all about buying a service as well. >>It's unlike you >>know, I'm gonna buy an apple. It comes to the hardware, >>right? So we're >>selling a service. So essentially you're service has to also dramatically changed. And I think these days, especially when we're operating in, uh, Thailand, Indonesia is one of the highest adoption rates for mobile these days. Everyone does. Everything lives on on the apps. So, um, insurance companies also needs to really on board their journey on that as well as increased engagement. So I don't just want to be an insurance company where, um, I speak to you and I have an issue with my claim. I want to really build a relationship with you and engage you differently. So I think it's actually that's the mission for a Sunday. So I think Imagine if imagine an insurance company 50 years in the future. How would it be? Uh, that's our mission. >>This is a great example. You guys, First of all, you're very dynamic. Thanks for sharing your storey. But when you get into the tech here, if industries that are transforming because of the digital transformation, the consumers expect the apps. You guys, as co founders and entrepreneurs now running this big business have to meet the demands and leverage the technology. How have you done that? How are you guys manage that? What kinds of decisions have you made? And you share some either experiences or observations of how to navigate and how you're riding that wave. >>Yeah. So I think if you hear from what Cindy and Christine has just mentioned, I mean, uh, we were playing in, you know, two of the oldest and largest industries in the world. Real estate and insurance. And, uh, you know, in both industries, as I said earlier, you know, it's really all about the customers, right? Um you know, in in the past, we used to think of of businesses as you know, what's your vertical and the horizontal today? Um, at least four k s k and and and all the all these, um, you know, tech ventures that we are now venture building. We're really thinking about it from the customer land. So really thinking about it from a customer ecosystem perspective. So instead of, you know, creating products and and having that push out to the customers, you know, we use tech and data and and especially data today and the right amount of data and what type of data that we want understanding that and really, um, building that product and really the services, uh, for the customers. So once you know the customer enters our ecosystem, whether you know, in your real estate, um, ecosystem or whether it's in your insurance ecosystem, we want you to to continue to stay with us, um, and to trust us. Um, and so it's not just about selling you a product, but really, you know, like, what Cindy says building a relationship with you because we think that, you know, obviously you know when insurance is something you really need when when when things go wrong in your life, we don't only want to be there. When things go wrong in your life and for real estate, you know everybody needs a shelter. So so so that's why we think that building relationships are very important and from really true, that lands is when you really think about the ecosystem and you think about data. I think Cindy Increasing gave some examples of how we're approaching it. Um, a lot of people start from from from a, you know, from a traditional business and from within. But for us, um, we decided to actually take it outside. Um, and, you know, take the approach of venture building from a startup, um, but really have, on the back end, really have that Connexion to the core businesses. Because what the core businesses understand is, you know, lifetime and experience of how customers feel and and, you know, um, in insurance, it's really about how to run a financial institution in real estate is really how to build buildings, and that is something that we can't take away. But, you know, you use technology to enable and to power. But what venture and start ups do extremely well is really the way we are extremely nimble and the way you use tech and data to navigate the quick changes of customer demands. And and you know, one thing an app and it's all about quick iterations. Right? When you build a super app, how do you incorporate all the features that are coming in, you have to keep on, you know, iterating changing, innovating, um, and innovating small with quick wins and then taking on a larger scale. And so the way we position ourselves is when you have to start up and you combine that with the core. Um, and putting the two together is how, how, how we look at things and that four minutes, the whole ecosystem >>that's awesome and being agile as fast and speed is key if you want to be there. Startup. But at the core business, that's going kind of slow. You got to kind of make everything go faster. That's a great, great insight. Let's talk about the disruption of the property industry again. That's real estate now with the Internet of things, technologies and also people expect technology. They wanna have access. I don't wanna have all these passwords and, you know they want to have easy in and out. They want good efficiency, save money. What's the disruption angle on? Um, the property neck. Christine, what's your How do you see that? The big disruption going? >>Yeah. So I think as Johann already mentioned before, you know um I think our customers we know are becoming, um, digital natives. Right? And they expect very convenient lifestyles. And we're all about our customers. So, actually, that's why we launched also another product, right where we're taking all of these things that you just mentioned, you know, about Iot into account. So what we found is, um, that actually, today, um, you know, the village about real estate is that we all live through that life as well, so we can experience that. Uh, we found that residents today, um, they find it quite challenging to request, you know, basic services like housekeeping managing, um, their defects, their tenants. Um, you know, even the financial planning and even getting into the building, right, they want more convenience. Um, but we realised that actually, all these services in the real estate industry right now and even in the prop tech space, they are very, very segmented. They're all discussed across multiple different apps. So what we really try to do is hey, let's try and consolidate all of this into one single app, which we have done, which is really cool, And it helps our residents really stay engaged and connected with our property. Um, what we did also was on the Iot front. We we were actually the first developer in Malaysia to also integrate, You know, future proof solutions like remote lift calling as well, um, into the mobile app. And that's to really go like, push on the Iot front. For us as well. >>Must be great for retention. It's all the gadgets are built into the of course. You have good WiFi fibre in their everyone's got good band with >>for sure >>It's like water and plumbing. Uh, I'd like to get everyone everyone loves that. I gotta ask Now, on the on the on the on The disruption is great. Now you've got the clouds, the clouds here for actually Amazon. You guys are big customer because you guys can move fast and they do all the heavy lifting. How are you guys seeing that helped modernise in the industry of insurance? Because that's a big vertical for a W s and you guys are doing is Cindy. What is the What is the modernisation? Um, half that you guys have taken with a W s. >>Yeah, sure. So I think essentially, for insurance, it's a product development. And when we talk about product development means, um how do you price, um, every certain individual or company very differently, right, Because everyone has very different risks surrounding them. Uh, currently, what we face is that it's a flat pricing fixed pricing. Um, and it's not really personalised to you. If you are a very good behaviour and safe kind of customer, it doesn't translate to any premium savings for you. Um, so I think, uh, part of insurance is to give, for example, affordable access to health care. But if your premiums isn't sustainable for health insurance, then it doesn't really need the point. So, uh, for Sunday, like, how we're trying to trying to do it differently is, for example, we use some AWS cloud solutions and AWS Lambda too, really power our machine learning Savalas and Cloud infrastructure. So, for example, uh, Sunday we are a serious bee companies sober and the growth stage. So at any point in time, we need to ensure that our infrastructure is able to support a huge spike in transaction volume, and we're working with large scale partners like telcos, e commerce companies, or even within our organic channels. So our AI machine learning risk prediction model, which is basically, um, powering our premium pricing engines whenever there's any requests coming in front of the Web for foreign quotation. For example, if someone wants to buy health insurance, um, it can go up and spike. But also, the data model is actually pricing, uh, processing billions of calculations, ingesting a lot of data points. Uh, it needs to do that within seconds, so yeah, I think a w s. We've been using it from day one since we launched. It's been, uh, helping us on >>that and make it go faster. That's the big thing. I gotta ask you when you guys have this family business now, three decades, you got a lot going on extending that legacy and sustaining the family legacy. I love the Storey. So who decides whether to do the startup and you guys draw straws? Is that you guys flip a coin? You gotta who runs the big business? How do you guys decide that? Mm. >>Um, maybe I'll >>I >>would say maybe it came very naturally to us. Really? I guess Here we don't have to disclose. Our age is a little bit, so I mean, I mean, we all actually the background and really all three of us. Before we came into the family business, we were all working professionals in very different fields. I was a I was in banking. Cindy was a lawyer, and Christine was a a doctor, actually, Um um, but, you know, I came back first. I'm the eldest, so after, you know, walking outside and looking into the family business. So I came back first, and and And from there, I took over the insurance business and looking at it, it was a very lonely place to be. So, um, you know, after a couple of years of Cindy being a professional life, you know, we said, Hey, would you like to come back? And let's, uh, take a different journey with insurance and see how we can build something different? Uh, since we know a lot about insurance, but let's make make make a difference and and and, you know, be sustainable, but also evolve over time and show the world that insurance is actually pretty sexy, actually. Um, and then, you know, Christine saw the fund that the two of us were having, uh, already started building a real estate on on my end. Uh, and then, uh, she came back. And, you know, we have a conversation, and we said, Look, looking at you know what we're doing in Sunday? You know, building pricing engines and being able to price to a single customer level. Um, we saw that opportunity in real estate, and, uh so I asked her. I said, Look, would you like to do this? You know, because I think there is something cool. Um, the three of us can band together and still inspire each other share ideas across each other. That's an opportunity that a lot of people don't get right. I mean, to all these industries in the world being able to cross share ideas. Uh, and sometimes inspirations and ideas don't come from the same industry. Uh, and so I think. And that's how we started. Really, John, it's not. Maybe we're lucky, and we should be grateful for >>that. You're all power women. I love the storey, and it is good that you come together, and I think the entrepreneurial kind of twist makes it more fun. But not everyone is cut out with the entrepreneurship, but it also gives you more risk management. You can. You can go after opportunities I love. I love the strategy there. You guys are great leaders. Any advice for other aspiring women leaders and entrepreneurs out there who want to make a difference? Make an impact? The world is. Change is getting better for everyone. And and again, entrepreneurial could be in big companies and also big companies doing startups. There's a whole new world. What advice would you guys give other aspiring women leaders? Okay, >>I'll keep it short from my end. I think for me it's about really following your passion following your ambition. And lastly, I think not to try and not feel like you need to conform to any gender stereotypes because I think in male dominated industries such as real estate, our are attack. I think people might have some ideas about you know what a what a tech leader or what a real estate leader might have to look like. But you don't have to conform to that. So that's probably my advice. Uh, >>yeah, I I fully agree with Chris right there. I think, um, gender isn't an issue here. If you have a passion and you identify, there is a market opportunity that you can, you know, you can really do something about it. Just just pursue it. I think most importantly, if you ever want to be an entrepreneur and start your own business or your own, start up. Uh, so long as you have the confidence, I think you're you're good to go. Um, there's a lot of talk out that that or, you know, um, women led start ups are not >>attracting >>funds, but we haven't faced that anyway. In this part of Asia, I think there's a lot of, um, I think it attracts even more attention. If you're a woman in a male dominated that industry like, hey, then you know it's it's quite unique. So I think you have a strength there, and I think there's a lot of diverse talent out there. Um, post pandemic. A lot of people are looking for changes as well, so I think it is a lot of a lot of opportunity out there. >>Yeah, Joanne, you know, you know, the thing is with cloud computing, it's a level centre. It really because if you can come together, whether it's sisters like you guys, powerful sisters and professional experience coming together leverage technology to re factor old industries. It's all about the numbers and the performance. At the end of the day, you know, you move faster and you take territory and beat the competition. >>Ultimate >>the ultimate uh, leveller. Well, congratulations. You guys are great. Thanks for coming on The Cube Sisters. You guys are amazing. Great Storey Love it. Thanks for coming out and celebrating International Women's Day feature today as part of our international women's showcase here in the Cube. Thank you so much. >>Thank you. Thank you for having us. >>Okay. The Cubes International Women's showcase Going on all year, this time featuring International Women's Day The big celebration. I'm John Ferrier, host of the Cube here in Palo Alto, California. Thanks for watching. Mm mm

>>Hello and welcome back to the cubes coverage of Splunk dot com virtual. I'm john Kerry host of the cube we are here in the Splunk studios in Silicon Valley where all the execs are here, it's basically a spunk studio. It's everyone's here telling the stories. We also got some remote guests coming in, customers partners and other Splunk execs. We've got Katie bianchi senior vice president of customer success. Welcome back to the cube. Thank great to see you. >>Thanks john Great to be here. >>Yeah, I love the customer success stories because at the end of the day customers vote with their wallet and when basically like solutions, they'll this customer examples and customer testimonials. There's one thing I've learned covering Splunk over the past decade and done in many dot coms. It's you guys have very happy customers and over the years have continuing to have great customer success organically now have to high end on the enterprise now with cloud scale lots changing, lots growing the world that's going completely cloud. Um, and again, data is at the center of the value proposition as it always was more important than ever. So what's new with the customers? What are some of the successful is that you're seeing what's new in your world? >>Yeah, Thanks for thanks for asking, john I think, You know, we've been talking about how things have been changing over the past 18 months. And if I over simplify our customer obsession means that everything we do is designed to make sure we're helping customers get the most out of their investment was flunk every single day. So we do this across our global team and our partner ecosystem who are providing both the right adoption and technical services and were architected and deploying thousands of Splunk environments to help our customers get to ongoing value. But in the world that we're living with today, I talked to so many customers who are doing amazing things with Splunk but dealing with really tough challenges right? So through the pandemic, everyone is dealing with more complexity, more change in the velocity that we have never seen before. And on top of all this, shifting to a fully digital business model, there's whole new challenges to effectively monitoring infrastructure and applications and maintaining security posture with this to customers that I'm talking to are also having to figure out ways to do a lot more with less. I think we all know it's an incredibly competitive talent market out there. So our customers are relying on Splunk and customer success more and more to make it easier and faster to get to value, to investigate, to monitor, to detect and to remediate. So that pace and all that change of what's happening means that we have to continually check ourselves to be that right strategic partners that can move at the pace of our customers because customers are counting on us to provide right services at the right time for every stage of their journey with us. >>Great point, great insight there. I want to ask you because Splunk has always had this kind of in their D. N. A. Because when Splunk started was always something new and it wasn't a new thing. That new thing never seen before. Now as the world can you guys continue to do that? You bring something new to the market, you operationalize, you bring value to customers then it happens again and again and again. But now more than ever the data rolls of cloud and and customer applications is new for customers. So you have a diverse customer base. I know you're obsessed with customer service but how do you how do you have a customer success? How do you deal with the fact that sometimes things are so new and there may or may not be a benchmark there and you can't go with the proven former. Sometimes you can sometimes you can't how do you solve? It's new to me problem that customers want this new thing. >>Yeah, I think you know a lot of what we see today is that the power as long as a data platform to bring in complex data allows customers to do many different things. Whether it's infrastructure monitoring, whether it's security, use cases or whether its application performance monitoring and all of that is new for our customers. So oftentimes like you said we grew up having customers use us for single use case when we're bringing this much data into the platform and they see what can be unlocked through the value of Splunk, what we have to make sure that they can do is most seamlessly move from use case and value point. So that means from a C. S. Perspective we have to continually make sure that we're doing what customers are asking us to do which is having the right services that deliver the right outcomes that are as prescriptive as possible and that we're doing that across the domain of all of our empire portfolio. So we spend a lot of time making sure that our technical services are scaling to the needs of customers but also everything that we do around success planning and adoption and use case guidance and best practices as well as our education and enablement are as prescriptive as possible for customers whether they are new to Splunk or whether they are scaling Splunk across multiple use cases and multiple areas of their business. >>Certainly a lot of not of multi vendor, multi vendor activities. Modern application development, security is a big part of it. So I have to ask you given all that, what are the top things, top three things for instance that your customers are asking from you guys from C. S perspective customer success >>perspective great question. So I think over, I think what we hear the most frequently is give me a more seamless buying experience with services that are really easy to consume and speed my time to value second and I just mentioned this is I need services that aren't task, just task based to work. I need services that deliver the outcome that I need for the business problem or business opportunity that I am trying to solve for. So make sure that your portfolio lines up with our outcomes And I think 3rd is all about more prescriptive guidance. The world is hard, the world is complex, data is only getting more complex while the opportunity is big, our role is all about prescription and making it as easy as possible. >>So I have to ask you the question that I'm observing, many people are in the industry as well is that Splunk is changing as a company. Um everyone knows the vibe of Splunk is very cool, very chill, very organic, big community vibe, good customer success, everything's going great. You continue to knock it out of the park over the years, but now you're mature company now, Scale is coming in, your customers are getting bigger and bigger. You have existing customers getting new customers, you have new offerings. There's a whole another Splunk coming another level. >>Yeah. How do you, how >>do you view that from a custom respect and you can, you share your reaction to that? >>Yeah, I, you know, I think it's an honor to be part of a company that has such a strong culture and has such great partnership with our customers and it really is all because of who our customers are and I think who are people are internally. But I think growing and scaling and making sure that we are able to deliver the right services at scale is a critical component of what we have to do to help customers along this journey. So the role of you keep saying this, but the role of customer success is to make the complex easy and we do that by making sure that we as an organization have the right data, the right prescription, the right way to serve our customers and the right coverage model no matter where customers are on the journey or who they are and getting and getting the most prescription to them at the right time. And that's that's quite frankly how we scale. But also what our customers asked for. They're asking for more module arised content and they're asking us for more ways that they can drive best practices and use case guidance from right within the product. And those are things that we are working on to help continue to scale out what we're able to do. >>That's a great point. Taking the complexity, make it simple and enable them to be successful. I think data does that you guys are offering that platform which is a great business model by the way, if you can provide those kind of value that's always a winning formula, Make things easy, reduce the steps it takes to do things and make it fast and simple. Uh I have to ask because you mentioned earlier, the top of this interview about digital business, we're here Splunk canceled the conference now is virtual. Were coming in remotely here on site at the studio. They they have a virtual student there now in the media business, which is a data business. You know, you guys are now doing tv with CUBA's here. Um everyone is realizing the pandemic. That digital business now is standard. You're seeing the impact of the instrumentation you mentioned. So as the digital business transformation is accelerated here and this time, not for everybody, it's going to change how customers are behaving. What have you what have you observed at the pandemic? Because it's kind of panel has cleared the runway a little bit for people to to do this properly because you can see what's not working. So what's your thoughts on this whole digital business? Everyone's connected and data is at the center of it. What's your thoughts? >>Yeah, absolutely. I I look, I think, you know what we have seen over the last 12-18 months with this acceleration to a digital business model, is that things and the other dynamics going on or that things are only getting more complex. Right? So strong customers can come to Splunk cloud because we know it reduces complete with complexity in their moves because we are that data platform that allows them to search, investigate and monitor across cloud across multi cloud and across hybrid environments but that's complex. Over the last year we've seen customers get too much quicker value um, in in Splunk cloud right there going through large complex transformation. One of the easiest things you can do is shed the amount of time and money you're spending, managing, monitoring your infrastructure. So coming to Splunk cloud helps accelerate time to value for them in that way. But let's make no mistake, that is really complex. And so part of what we are doing is ramping up our level of focus on those modernization services for customers. So customers who are choosing to come to Splunk cloud for those benefits. We are there from planning and cut over and beyond with more prescriptive tools, more automation and how we move data, more resources and more experts to get customers to Splunk cloud more seamlessly. And that for us from a modernization perspective is one thing that we are hearing clearly customers asking asking for specific in the space so they can take more advantage and move more quickly. >>One of the trends that we're reporting on and I'll get to the headline in silicon angle in a minute, what's reporting on this event is there's more, more surface area, there's more data, there's more tools and tools are important for helping people automate but at the same time if you have more tools you have more blind spots or silos. So when you get into this world of architecture, customers are struggling that we talked to around trying to find the ideal equation of okay balancing architecture platform and tools that's equilibrium if you will by getting access to the data. What's your reaction to that? Because this becomes one of those decisions. I think Splunk shines where you can kind of have the best of a platform at the same time use tooling where relevant to accelerate whether it's automation or other other jobs versus buying tools for everything. >>Yeah and I and so I think part of the part of the thing that we continue to see is with the proliferation of data and data sources and a different degree of complexity in tooling the decisions around what's important and what's not important become much more much more complex for customers and much more difficult for customers to make. So we're changing a lot on the product and pricing side to sort of facilitate that piece. But I think when you're talking about how do I get the most value immediately, what we do across our go to market organization is make sure that we're partnering with customers to say what are the outcomes that you want from you want a need as a priority from a monument infrastructure monitoring for an application performance security perspective and then how do we make sure that we're prioritizing your maturity journey very prescriptively to say here the use cases that are most material here are the data sources that are most material and here's a success plan that helps you get deployed to your priorities so you can start the journey with us and build on that as we go. So again, it's really about how do we make the complex really easy through higher degrees of prescription but really making sure that we're doing our job and tying the prescription to what our customers need most when they need it. >>That's a great segment of my next question. In fact, my final question because because you know the headline on silicon angle dot com that we're reporting for this event is I'll read it to you. Splunk doubles downs on multi cloud data access, observe ability and security at its annual summit. Okay, so balancing the shiny new toy in the North Star Direction vision to practical prescriptive customer journeys is always a balance because you want to talk to customers about the future. Multi cloud, obviously observe ability super important. And honestly if security gonna be built in, okay, we all know that back to the mainstream customer, you're in the customer success. So you want to show them the North Star, show them the headroom, whatever metaphor you want to use at the same time they're dealing with problems and things that they're trying to solve right now. What's your what's your thoughts on on customer success knowing that there's a lot of cool new things coming. >>Yeah, I think our job like I excited, I'll start and in the same sort of started in the same way. Um our job at the end of the day is to help customers get the most out of their current investment was blank and that does and that is all about working on what that maturity journey looks like, prioritizing outcomes that our customers care about and starting and starting that journey. So there's foundational work that needs to be done aligned to priorities. That's where we start and then if we're doing what we need to be doing, creating those prescriptive plans and those success plans, then all of how we deliver to that value is prioritized through what customers need the most when they need it and that is our role and then we believe that by doing that and moving as quickly as we can with customers to get to that value, then we're enabling them to continue on that journey for all the new stuff that's out there that they can explore and get more value from. >>Its always good to have that North star and that china new toy, new technology. So, I have to ask your final final question because I have you here, what have you learned during the pandemic that you could share with other practitioners that are watching or maybe watching this as they look at the best practice because we've seen a lot of evidence where some people have fallen to the side or failed. Didn't weren't prepared. People who were in the cloud experimenting got that tailwind and survived and thrived somewhere re factoring new business were emerging. So you kind of see a pattern, is there anything that you've noticed on your end um that you can share with, you know how to lean into something new? So you don't be left out in the cold if uh the wave comes, a new trend comes that they need to take advantage of like date at the edge or cloud scale. What are some of the things you've you've observed and learned? >>Yeah, that's a great question. So I think, you know, I think for me, my personal learning through the pandemic has been like, we always need to be looking around corners and planning specifically to for our customers and thinking for them in terms of what problems that they will have and we have to anticipate that so that we can pivot and create the right services that help them leverage to do what they need. So very early on. Um even very early on in the pandemic, our professional services team flipped within a two week period doing fully remote and virtual deployments because we knew we couldn't stop time to value given the shift to remote work, our customers were relying on us to deploy so that they could monitor infrastructure um and monitor work from home usage. And I think along with that as we started to see in through the back half digital transformations really pick up and customers move to cloud. We've been working across across the last really 12 to 15 months to really start to plan around what does it take to create the right services and the right capability, not just within Splunk but within our partner ecosystem to effectively move customers to Splunk cloud and help them navigate uh hybrid, multi cloud world with much more speed. And so for me, those are the two things that we really leaned into hard because we were always looking around corners and saying what's next for our customers based on what we're seeing happened in the external environment. >>Great insight, Katie, thank you for coming on the cube. That's awesome. And I think, you know, customers are seeing success formulas and the new ones are emerging and you guys are going the next level is always fun to talk about the future and today at the same time so great to have you on. And certainly at the end of the day the customers, the ones who are deploying and create the innovation with software and data. So thanks for sharing. >>Yeah. Thanks john um really, really happy to spend the time. There's nothing I like to do more than talk about our customers and to all of our customers, huge thank you to you for your partnership and all you're doing to continue to power the world with data. >>It's always good to have a lot of customers to tell the story for you, but I appreciate you. Coming on, congratulations on your success. It's the cube we are here live in the studio of Splunk Studios for their virtual event uh with the remote interview. We're talking all the people in the, in the industry. We can, we're bringing it in. We're going, we're doing the interviews here in person as well as a hybrid event. I'm john for the cube. Thanks for watching. Mm >>mm. Mhm.

>>mm we are back and we're continuing the coverage on H P E. Aruba's news today around the D S X six S C X 10-K with Pensando. Now we want to get the perspective of a system Integrator because they're in the front lines, they understand how to put the pieces together where you're happy to bring john Galatea of Dasher technologies dashes and in the end I. T solutions provider, they gotta focus a lot of expertise on infrastructure, jOHn welcome. Good to see you. >>Thank you for having me. Good to be here. >>That's our pleasure. So I wonder if you could give us a little bit more color on Dasher where you focus what your core companies competencies are, what industries you focus on etcetera. >>Yeah, absolutely. So a dasher, we assess architect implement and manage I. T. Solutions that digitally transform businesses. Our practice areas include cybersecurity, networking, cloud data center and we also offer pro professional services around those practice areas. We partner with all the major tech companies in the space. Some of the examples are HP, Cisco, Aruba Palo Alto eight Ws and many others that fill out the, you know that practice area. >>Well that's great. So you have a very wide observation space, that's why we like talking to SA as you have an independent mindset and you can kind of tell it like it is. But so what are you seeing with customers? It's exactly, we hear a lot about digital transformation, you mentioned security, you're obviously doing cloud that's it's almost like john these pieces are all coming together to power Digital and digital transformation and we were forced into it over the past 18 months. And now people are stepping back saying hey okay we have all these resources, how do we put them together and really transform our business? What do you see? >>Yeah, seeing similar things. So you know, our customers are telling us that they're looking for more speed, more agility, um you know, limited complexity because they're trying to do more every single day with less staffing and a sophistication of integrating functionality that breaks down I. T. Silos. Um there also evaluating security span versus effectiveness And they're moving towards zero trust. >>Yeah. So I want to, I'm gonna come back and ask you about that. So I've written a lot about this is that you look at how much we spend versus as you say the effectiveness and there's sort of an imbalance there, it's like we can't spend enough, it budgets they're not infinite. And even though security is top of top priority for ceos, they've got other things that they have to fund and then zero trust, you know, before the pandemic john that was a buzzword and now it's become a mandate. Any thoughts on that >>in terms of zero Trust? Absolutely yeah it is a mandate, we've seen more and more of our customers moving toward in this direction and defending themselves against cyber threats and yeah absolutely. It accelerated during the pandemic and is continuing to accelerate today. >>Right? And I think there's some things that were reported now going to be permanent with regard to obviously hybrid and the like, cloud security and so forth. So, okay, let's get into some of the news here. What's the big trend, john can you explain the relevance of the H P E, Aruba and Pensando news? >>Yeah, I mean when I first heard of it, you know, I I looked at it as a whole new category because it's a category that's going to deliver cloud scale distributed services closer to where applications are. It's going to simplify. One of the things we mentioned earlier was limiting complexity. So it simplifies the network um, by putting security provisions and operations in a unified management platform and it helps improve your security posture around moving towards zero trust and limits the appliance and vendor sprawl that you might ordinarily have in a in a existing network today. >>Okay, so that's kind of the business cases, you're consolidating a lot of piece parts and that's, you know, from a system integrator standpoint. You know, it's funny people often say, well, isn't that bad for the s I'm like, no, they don't want to be in the business of plumbing, they want to be in the business of, you know, more strategy if they if they just end up bolting stuff together, they're going to go out of business, They need to extend their value. So as a strategic partner, you got an early preview of this launch? The D S S D S S C X 10,000, what was your initial impression reaction you called it? A new category? What do you mean by that? >>Well, it's a new category of of of a data center switch in the digital infrastructure because it includes or incorporates security. Um And more specifically it includes security around east west traffic, which is it doesn't eliminate your perimeter firewall but it actually incorporates more functionality which leads to better simplicity and easier use of management of a platform. So for us, I'm really excited to go position and talk to our clients about this. >>Yes. So we're seeing the flattening of that network, that's even it's obviously been accelerated by the pandemic, everybody talks about that. But if you think about the traditional headquarter hierarchical network and now all of a sudden everybody's working remotely using more cloud. Using more distributed infrastructure that flattens the network. That creates security challenges because you can't just build a perimeter and say, okay, we're safe. You now have to go to where the adversary is and that's everywhere. So what's your sense as to how customers are going to react to this new category of switch? >>I think really my sense is that I've got a really positive outlook on this product. I mean hardware, firewalls are costly and deploying software agents can be very disruptive and when you're integrating it into the switch layer. So um I think the C X 10,000 provides a great alternative to an embedded accelerated services embedded in accelerate service into the D C fabric. Um, it's great for brownfield migration, um, rack pod and you know, and the standards based leaf, you know, L two, L three um, and it doesn't necessarily replace, as I mentioned earlier the perimeter security, but um, it can cap and grow with DSS and east west firewall traffic. >>Yeah. And I think we've seen when we talked to see so, so like you said, it does, it doesn't replace the traditional perimeter security but you're going to see a shift and spending priorities obviously to a comedy because as I said earlier, there's not infinite budget but john give us the big takeaway, Bring us home. What what, what do you want to leave our audience with? >>Yeah, I think, you know, the number one takeaway is that it's a massive opportunity to reduce complexity, enhanced security and lower costs in the data center by eliminating dedicated devices and embedding services through software capability in the network closer to where workloads are are moving. So that's the big takeaway for me and for, I think for our clients, um, you know, other things are, you know, you're the data center perimeter is no longer confined and open an on prem location but extends out, right. We're seeing customers extend out to the cloud and across uh, you know, disparate locations, co locations. So The traditional architecture isn't going to be well suited for this, and I think the CX- 10,000 and its feature set are going to be really great for addressing the changing market. >>Yeah, that's, that's all. I mean, again, we're seeing the democratization of everything and and networking is, is no exception. The notion of simplify simplification, john really appreciate your time. Thanks for coming on. >>Thank you for having me. >>You're welcome. Okay, keep it right. There were unpacking the changing trends in networking generally, and specifically switch networking with HP, Aruba and Pensando and the cube. Keep it right there.

>>Hello everyone Welcome to the cubes coverage of cubic on cloud native come here in person in L A 2021. I'm john ferrier, host of the Cuban Dave Nicholson host cloud host for the cube and of course former host of the cube steve minutemen. Now at red hat stew, we do our normal keynote reviews. We had to have you come back first while hazard and red hat >>john it's phenomenal. Great to see you nice to have Dave be on the program here too. It's been awesome. So yeah, a year and a day since I joined Red hat and uh, I do miss you guys always enjoyed doing the interviews in the cube. But you know, we're still in the community and still interacting lots, >>but we love you too. And Davis, your new replacement and covering the cloud angles. He's gonna bring little stew mo jokes of the interview but still, we've always done the wrap up has always been our favorite interviews to do an analysis of the keynote because let's face it, that's where all the action is. Of course we bring the commentary, but this year it's important because it's the first time we've had an event in two years too. So a lot of people, you know, aren't saying this on camera a lot, but they're kind of nervous. They're worried they're weirded out. We're back in person again. What do I feel? I haven't seen people, I've been working with people online. This is the top story. >>Yeah, john I thought they did a really good job in the keynote this morning. Normally, I mean this community in general is good with inclusion. Part of that inclusion is hey, what are you comfortable with if your remote? We still love you and it's okay. And if you're here in person, you might see there's wrist bands of green, yellow, red as in like, hey, you okay with a handshake. You want to do there or stay the f away from me because I'm not really that comfortable yet being here and it's whatever you're comfortable with. That's okay. >>I think the inclusion and the whole respect for the individual code of conduct, C N C. F and limits Foundation has been on the front end of all those trends. I love how they're taking it to a whole nother level. David, I want to get your take because now with multi cloud, we heard the same message over and over again that hey, open winds, okay. Open winds and still changing fast. What's your take? >>Open absolutely wins. It's uh, it's the present. It's the future. I know in some of the conversations we've had with folks looking back over the last seven years, a lot of things have changed. Um, whenever I think of open source anything, I go back to the foundations of Lennox and I remember a time when you had to reboot a Linux server to re scan a scuzzy bus to add a new storage device and we all sort of put our penguin hats on and kind of ignored that for a while. And uh, and, and as things are developed, we keep coming into these new situations. Multi cluster management was a big, big point of conversation in the keynote today. It's fascinating when you start thinking about something that was once sort of a back room science experiment. Absolutely. It's the center of the enterprise now from a software >>from an open tour standpoint security has been one of those front and center things. One of the day, zero events that got a lot of buzz coming at the beginning of the week was secure supply chain. So with the Solar Wind act going in there, you know, we remember cloud, wait, can I trust it with the security? Open source right now. Open source and security go together. Open source and the security in the cloud all go together. So you know that that wave of open source, obviously one of the things that brought me to red hat, I'd had a couple of decades, you know, working within the enterprise and open source and that that adoption curve which went through a few bumps in the road over time and it took time. But today, I mean open sources have given this show in this ecosystem are such proof >>points of a couple things. I noticed one, I want to do a shout out for the folks who put a nice tribute for dan Kaminsky who has passed away and we miss him. We saw on the Cube 2019, I believe he's on the Cube that year with Adam on big influence, but the inclusiveness do and the community is changing. I think security has changed a lot and I want to get your guys take on this. Security has forced a lot of things happen faster data, open data. Okay. And kubernetes to get hardened faster stew. I know your team's working on it. We know what Azure and amazon is working on it. What do you guys think about how security's been forcing the advances in kubernetes and making that stable? >>Yeah. So john security, you know, is job one, it is everyone's responsibility. We talk about it from a container and kubernetes standpoint. We think we have a relatively good handle on what's happening in the kubernetes space red hat, we made an acquisition earlier this year of stack rocks, which was one of the leading kubernetes native security pieces. But you know, john we know security isn't just a moat anymore in a wall that you put up every single piece. You need to think about it. Um, I've got a person from the stack rocks acquisition actually on my team now and have told him like hey, you need to cross train all of us. We need to understand this more from a marketing standpoint, we need to talk about it from a developer standpoint. We need to have consideration of it. It's no longer, hey, it works okay on my machine. Come on, It needs to go to production. We all know this shift left is something we've been talking about for many years. So yes, security, security, security, we cannot overemphasize how important is um, you know, when it comes to cooper, I think, you know, were relatively mature, we're crossing the chasm, the adoption numbers are there, so it's not an impediment anymore. >>It's totally next level. I don't agree with this too. David, get your thoughts on this whole adoption um, roadmap that put it together, one of the working groups that we interviewed has got that kind of navigate, kinda like trailheads for salesforce, but that speaks to the adoption by mainstream enterprises, not the hard core, >>you know, >>us devops guys, but like it goes into mainstream main main street enterprise had I. T. Department and security groups there, like we got a program faster. How do you see the cloud guys in this ecosystem competing and making that go faster. >>So it's been interesting over the last decade or more often, technology has been ahead of people's comfort level with that technology for obvious reasons, it's not just something went wrong, it's something went wrong. I lost my job. Really, really bad things happened. So we tend to be conservative. Rightfully so in the sometimes there are these seminal moments where a shift happens go back sort of analogous go back to a time when people's main concern with VM ware was how can I get support from Microsoft and all of a sudden it went from that within weeks to how can I deploy this in my enterprise very, very quickly. And I'm fascinated by this concept of locking down the supply chain of code, uh sort of analogous to https, secure, http. It's the idea of making sure that these blocks of code are validated and secure as they get implemented. You mentioned, you mentioned things like cluster and pad's security and infrastructure security. >>Well, David, you brought up a really good point. So get off is the instance creation of that. How can I have my infrastructure as code? How can I make sure that I don't have drift? It's because I could just, it'll live and get hub and therefore it's version controlled. If I try to do something, it will validate that it's there and keep me on version because we know john we talked about it for years on the cube, we've gone beyond human scale if I don't build automation into it, if I don't have the guard rails in place because humans will mess things up so we need to make sure that we have the processes and the automation in place and kubernetes was built for that automation at its core, putting in, we've seen get up the Argosy, D was only went graduated, you know, the one dato was supported as coupon europe. Earlier this year, we already had a number of our customers deploying it using it. Talking publicly >>about it too. I want to get the kid apps angle and that's a good call out there and, and mainly because when we were on the cute, when you work, you post with with us, we were always cheerleading for Cuban. It we love because we've been here every single coupon. We were one saying this is gonna be big trust us and it is, it happens to so, but now we've been kind of, we don't have to sell it anymore. We don't, I mean not that we're selling it, but like we don't have to be a proponent of something we knew was going to happen, it happened. You're now work for a vendor red hat you talk to customers. What is that next level conversation look like now that they know it's real, they have to do it. How is the tops and then modern applications development, changing. What are your observations? Can you share with us from a redhead perspective as someone who's talking to customers, you know, what does real look like? >>Yeah. So get off is a great example of that. So, you know, certain of our government agencies that we work with, you know, obviously very secured about, you know, we want zero trust who do we put in charge of things. So if they can have, you know that that source of truth and know that that is maintained and lockdown and not await some admin is gonna mess something up on us either maliciously or oops, by accident or anything in between. That's why they were pushing that adoption of that kind of technology. So absolutely they, for the most part john they don't want to have to think about the infrastructure piece anymore. What if developers want the old past days was I want to be able to, you know, write once deploy anywhere, live anywhere, containers helps that a little bit. We even have in the container space. Now you can, you can use a service deployment model with Okay. Natives, the big open source project that, you know, VM ware ourselves are working on google's involved in it. So, you know, having us be able to focus on the business and not, you know, running the plumbing anymore. >>That's exactly, that's exactly, that's what we're so psyched for. Okay guys, let's wrap this up and and review the keynote day will start with you. What do you think of the keynote? What were the highlights? What do you take away from the taste keynote? >>So you touched on a couple of things, uh inclusion from all sorts of different angles. Really impressive. This sort of easing back into the world of being face to face. I think they're doing a fantastic job at that. The thing that struck me was something I mentioned earlier. Um moving into multi cluster management in a way that really speaks to enterprise deployments and the complexity of enterprise deployments moving forward? It's not just, it's not just, I'm a developer, I'm using resources in the cloud. I'm doing things this way, the rest of the enterprises doing it a legacy way. It's really an acknowledgement that these things are coming together increasingly. That's what really struck me >>to do. What's your takeaway from the end? >>So there's been a discussion in the industry, you know, what do the next million cloud customers look like we've crossed the chasm on kubernetes. One of the things they announced the keynote is they have a new associate level certification because I tell you before the keynote, I stopped by the breakfast area, saturday table, talk to a couple people. One guy was like, hey, I'm been on amazon for a bunch of years, but I'm a kubernetes newbie, I'm here to learn about that. It's not the same person that five years ago was like, I'm gonna grab all these projects and pull them down from getting, build my stack and you know, have a platform team to manage it from a red hat standpoint, we're delivering our biggest growth areas in cloud services where hey, I've got an SRE team, they can manage all that because can you do it? Sure you got people maybe you'll hire him, but wouldn't you rather have them work on, you know, that security initiative or that new application or some of these pieces, you know, what can you shift to your vendor? What can you offload from your team because we know the only constant is that things are gonna there's gonna be gonna be new pieces and I don't want to have to look at, oh there's another 20 new projects and how does that fit? Can I have a partner or consultant in sc that can help me integrate that into my environment when it makes sense for me because otherwise, oh my God, cloud, So much innovation. How do I grasp what I want? >>Great stuff guys, I would just say my summary is that okay? I'm excited this community has broken through the pandemic and survived and thrived people were working together during the pandemic. It's like a V. I. P. Event here. So that my keynote epiphany was this is like the who's who some big players are here. I saw Bill Vaz from amazon on the on the ground floor on monday night, He's number two at a W. S. I saw some top Vcs here. Microsoft IBM red hat the whole way tracks back. Whole track is back and it's a hybrid event. So I think we're here for the long haul with hybrid events where you can see a lot more in person, V. I. P. Like vibe people are doing deals. It feels alive too and it's all open. So it's all cool. And again, the team at C. N. C. F. They do an exceptional job of inclusion and making people feel safe and cool. So, great job. Thanks for coming on. I appreciate it. Good stuff. Okay. The keynote review from the cube Stupid Man shot for Dave Nicholson. Thanks for watching >>mm mm mm.

>>from the bellagio hotel in Las Vegas >>it's the >>cube >>covering Ui >>Path Forward four brought to you >>by Ui Path. >>Welcome back to las Vegas. The cube is live with you. I Path forward four at the bellagio lisa martin with Dave Volonte. We're gonna be talking about you I Path integration suite, we have a couple of guests joining us here. Mark Jeannie is here the GM of Ui Path, formerly the co founder and Ceo of cloud elements and Peter Villeroy also joins us Director of Global I. T. Automation practice at UI Path guys welcome to the program. >>Thanks lisa. Great to hear. >>So Mark, let's go ahead and start with you. The Cloud elements acquisition was done in about the last six months. Talk to us about why you chose to be acquired by Ui Path and where things are today. Some big announcements yesterday. >>Yeah absolutely. So yeah if you go back six months ago um you know we have been in conversations with you I Path for for quite a while and um you know as we were looking at our opportunities as an api integration platform. So cloud elements just to step back a little bit um was a leader in helping companies take a P. I. S integrate applications together and bed that into their into their apps and um you know I Path approached us about the combination of what's happening in the automation world and you know these these have been a society as the marine Fleming from I. D. C. Mentioned this morning integration and DARPA have been separate swim lanes and what we saw and what you I. Path approaches with was ability to combine these together and really be the first company to take and take ui automation and seamlessly connected together with A. P. I. Automation or api integration >>Peter What's been some of the feedback? We know you guys are more than 9000 customers strong now we've had a whole bunch of amount yesterday and today. What's been the feedback so far on the cloud elements acquisition? So >>there's a huge amount of interest. We've had very positive feedback on that lisa the combination of Ui driven automation and A. P. I. Uh Native Integrations is is key especially to the I. T. Leadership that I work with. Um some of whom have traditionally compartmentalized you ipads platform in the Ui space and legitimately think about their own internal processes as being having very little to do with the user interface right. And so combining Ui driven automation together with uh api integration really helps too pick them up where they are and show them the power of that kind of a hyper automation platform that can deliver value in a number of spaces. And you guys ever >>see the movie Blindside? All right. You know what I'm talking about with joe. Theismann gets hit from the blind side and then his career is over and and that's when people realized oh my gosh the left tackle for right handed quarterback is so important and it's subsequent drafts when somebody would pick a left tackle like a good left all the rest went and that's what's happening in in the automation business today. You guys took the lead, you you set the trend. People said wow this is actually going to be a huge market. And then now we're seeing all this gonna occur. And a lot of it from these big software companies who believe every dollar of software should go to them saying hey we can actually profit from this within our own vertical stacks. So what do you make of all the M. And A. That's going on in particular? There was one recently where private equity firm is mashing together a long time R. P. A vendor with a long time integration firm. So it looks like you guys, you know on the right >>side of history in this regard. Your thoughts. Yeah. Absolutely. I mean if you think about automation right you've got to obviously help people do their jobs better. But if you're going to automate a process and a department you needed connect the applications that they use that those people use otherwise you can't accomplish it. And where ap is fit in as is automation and ui automation has become more and more mission critical and it's become bigger and bigger part of enterprise I. T. Wants to get involved. And so enterprise gets involved and what's their stack. It's api based their technology stack is how you connect back is through api so more and more companies are seeing what you I path saw is that if you're gonna automate every process and every department for every person you need to connect to every application that they're using and that's why this is now becoming right. Three companies now just recently have done these types of acquisitions of bringing an integration platform in and combining them together are trying to combine them together. >>All mps are not created equally as we know. Some are sort of half baked lot of them. Many of them don't have decent documentation so there's sort of a spectrum there. How do you, how do you think about prioritizing? How do you think about the landscape? Do you just kind of ignore the stuff that's not well documented and eventually that will take care of itself. How should we think about there have always >>been layers of integration right. Especially working with the ICTy organizations. So you've got our native integrations would make it easy to drag and drop activities and then you've got the A. P. I. Is that we can consume with various activities. That area has really grown through the acquisition of cloud elements and then you've got that third layer where when all else fails, you go on to the user interface and interact with the application like a human does and what you see is that our our interaction with college elements really enables a great enhancement of that lower base level um which is mildly interesting to the lines of business very important. I Yeah, for sure. >>So the reason I asked that question is I was talking to one of your customers this big ASAP customers said I love you ipad. The problem I have is I got so many custom mods and so it's just you know orally documented and I can't I wanna put automation in there but I can't. So to those parts of the tech stack become like the main frame of you know what I mean? And just sort of they live there and they just keep doing their thing but there's so much innovation that pops up around it. How do you how do you see that? >>Well that's part of the agility that comes with the platform like you ipads is that you can interact with the very clean uh swagger documented restful aPI s and you can interact with SCP on their proprietary ages old A. P. I. S. Um Those are things that we've traditionally done decently well, but again through this acquisition we could do that on a grander scale um with bidirectional triggering and all the goodness that you >>solve that problem today that your customer and this is a couple of years ago, you can solve that problem with cloud elements. Is that right? >>Yeah, absolutely. The the ability to integrate too these enterprise platforms like ASAP you need multiple tools to do the job. Right. So ui automation is great but if you've customized ui significantly or other things like that then the A. P. I can be a great structure for it and other cases where um that api provides a resiliency in a in a scale to it that um opens up new processes as well to those corporate systems. Right? So the balance of being able to bring these two worlds together is where you can unlock more because you got >>east west automation >>that's very good overhead and now >>you're going north south with cloud elements is deeper. Right, >>bottom line from the VP of its point of view, the more that can be done from a machine to machine communication the better. So sure. >>What's the opportunity for the existing cloud elements customers to take advantage of here? >>Yeah, absolutely. Um We've continued to support, brought our customers over with us. Uh Part of our customer base has actually been a significant number of software customers. Uh cos S. A. P. S. One of them doc you sign gain site, you know, so household names in the world of software as well as large financial services institutions like US Bank and Capital One and american Express, all of them had that common need where um they wanted to have an api centric approach to being able to connect to customers and partners and leverage our platform to do that. So we will continue to support that extend that. But we see opportunities where again we couldn't automate everything for our customers just threw a PS And uh you know for example one of our major financial services institutions were working with wants to take um and provide a robot for their uh customers and commercial payments to be able to automatically kick off in A. P. I. And so that seamless integration where we can combine that automation with robots leveraging and kicking off a P. I. S automatically takes us further into automating those processes for those >>customers. So you guys six months right. Uh talk about how that integration api integration company better gone smoothly. But what was that like you guys are getting the knack of M and a talk about that, what you learn maybe what you would do differently to even accelerate further, How'd it go? Uh >>That's the best answer from you having been on the >>acquisition side. Um Well we how well it went is six months later, which I think is really unheard of in the technology world, we're introducing our combined offering you I Path integration service that essentially takes what cloud elements built embeds it right into automation. Cloud studio in the Ui Path products. We and uh it's been a global effort. Right? So we had the Ui Path team was based in Hyderabad Denver and Dallas and then we've got um Ui Path engineers working with that cloud elements team that are in Bucharest Bellevue and bangalore and with the miracles of zoom and uh that type of thing, never meeting anyone in person, we were able to integrate the product together and launch it here today >>six months is a fast turnaround time frame was how much of that was accelerated by the, by the fact of the global situation that we're in. >>Yeah, well you know in some respects that that helped right? Because we um um we didn't have to waste time traveling and we could hop on zoom calls instantly. We spent a lot of time even over zoom making sure there was a cultural fit. You I path has a, you know, not only the humble, bold and type of values but it's a very collaborative environment, very open and collaborative environment as Brent can attest to. And that collaboration, I think in that spirit of collaboration really helped us feel welcome and move quickly to pull this together. And also >>the necessity is the mother of innovation right. Uh you ipad traditionally being popular in the CFOs organization were becoming the C I O s best friend and the timing was right to introduce this kind of capability to combine with what we traditionally do well and really move into their picking up like I said the customer where they are and leading them into that fully end to end automation capability and this was integral. So it wasn't time to kick the tires but to get moving >>and my right, there's a governance play here as well because I. T. Is kind of generally responsible for governance if you make it easier for them to whatever governance systems they're using >>governance privacy >>security that now you can just connect. They don't have to rip and replace. Is there an angle there? >>Sure, yeah. So nothing is more important than I. T. Than than control and governments and change management and half of the uh conversations we're having out there on the floor are around that right um uh ensuring that all of the good governance is in place um and we have a lot of the uh integrations and frameworks necessary to help that through your devops pipeline and doing proper ci cd and test automation um and you know introducing that integration layer in addition to what we already have just helps all of that to uh move more smoothly and bring more value to our customers. >>Mark talk to me about some of the feedback from customers that you mentioned, doc Watson. S A P probably I imagine joint customers with you. I path now there you're working together, what's the what's in it for them? >>Yeah, no the feedback has been tremendous. Right, so um api automation is not new to you. I path but customers have been asking for more capability. So one of them is in that governance area that we were just talking about, right, the ability to create connections centrally enable them disable them. Right? You got mission critical corporate applications. You want to be able to make sure that those applications are being controlled and monitored. Right? So that was one aspect. And by bringing this as a cloud based service, we can accomplish that. Um the other area is that this eventing capability, the ability to kick off workflows and processes based on changes to corporate applications, a new employees added in workday. I want to kick off a process to onboard that new employee and that triggered eventing service has been really well received and then um yeah, so that I'd say with the ability to also create new connections more simply was the third big factor. Uh we created a standardized authentication service. So no matter where you are in the UI Path product line, you get a consistent way to create a new connection, whether it's a personal connection by a business user too, you know, google docs or Microsoft office or your C O E R I T. Creating a connection to uh an important corporate system. >>How about the partner? I know you guys had partner day here leading into forward for they must be stoked about this gives you a lever to even add new partners. What was those >>conversations like? Yeah, yeah, no, absolutely. The partners are excited about those same features but um they're also excited about something in our roadmap which we expect to be previewing early next year and that's a connector builder. So the ability for partners to uh more quickly than ever create their own connectors. That'll work just like first party connectors that we ui Path build and add them into catalogs, share them in the market place. So there's new revenue opportunities, new opportunities for partners to create reusable assets that they can leverage and yeah so um lots of things, lots of work to continue to do, right? It's only been six months and uh but that's that's gonna be a big initiative going forward. >>So integration service as you mentioned, announced at this conference, we know that that's the first step obviously accomplished as we also talked about very quickly in a six month time period. But what does the future hold for api automation and integration service? >>So um one of the key areas just continue to expose the integration service um more broadly in the Ui Path product portfolio. Now that we have this service, more Ui Path products will be able to leverage it. Right? We're starting off with studio and orchestrator but that we can all use and share that common common capability. Um The other is to make access to complex business systems easier. So you think about it right. A uh to get a purchase order from net suite might take five or six api calls to do. Well, a citizen developer doesn't know what those five or six things you have to do. So we'll be creating these business activities or just get me open purchase orders that will work seamlessly in the studio product. And behind the scenes. Well, chain together those 56 aPI calls to make that a simple process. Right? So taking the integration service and making it even more powerful tool for that citizen developer than nontechnical user as well. So that's >>development work you're going to do. >>That's what we're gonna do as well as enable partners to do as well. So it's a key part of our road map over time. Because >>yeah I mean the partner pieces key because when net suite changes how it you're creating that abstraction layer. So but that's value add for the partners. >>Absolutely. And they have that domain expertise, right. They can create assets, leveraging the UI path automation capabilities but also bring their knowledge about A. S. A. P. Or workday and those oracle ebs and those core business systems and then combine that together into assets that enhance integration service that they build and I can I can share with their customers and share with our market >>because the work workday developer is going to know about that well ahead of time. No, >>it's coming and they know better than we do. Right. That's their business. That's what they know really well. >>Nice nice value at opportunity, peter >>One of the things that you iPad has been known for is its being very and I've said this on the program the last two days, that's being a good use case for land and expand. You guys have 70% of revenue that comes from existing customers. Talk to me about the cloud elements acquisition as a facilitator of because you kind of mentioned, you know, we're used to be really in bed with the cfos now we're going to see us and we've heard from a number of your customers where they started in finance and it's now Enterprise White, how is this going to help facilitate that? Even more? >>It really helps, you know, touching on what Mark just mentioned about the citizen developer, right, just as one of many examples, the empowerment of end users to automate things for themselves um is critical to that land and expand um successes that we've been seeing and where from an I. T standpoint, the frustration with the citizen developer is, you know, maybe what they're building isn't so top notch right? It works for themselves. What we can't replicate that, but put making it easy to make api integration part of what they do in studio X is so key to enhancing also the reusability of what's coming out of there. So that c uh C O E S can replicate that across teams are globally within their organization and that's part of land and expand because you may find something that's valuable in one line of business replicates easily into another line of business if the tool set is in place >>pretty powerful model lisa >>it is guys. Thanks so much for joining us today, talking about the club elements acquisition, what you're uh, doing with integration service, What's to come the opportunities in it for both sides and your partners? We appreciate your time. >>Great. Thank you. Thank you very much. I >>appreciate it. Thank you for >>David Want I'm lisa martin. You're watching the cube live in las Vegas at the bellagio Ui Path forward for stick around. We'll be right back. Yeah. Mhm. Mhm mm.

>>mm Welcome back to the huge covered cubes coverage of VM world 2021. The virtual edition tom gillis is back on the cube. He's in S. V. P at VM ware and the GM of network and advanced security at the company. Tom. Always a pleasure to see you. Thanks for coming on. >>Hey, thanks for having me. It's always a pleasure to be back here on the cube. I really enjoyed it. We've we've been, we've known each other for I don't want to count how many years but more than a few. Uh it's always an interesting conversation. >>We've had a lot of face to face interactions a couple years in a row were virtual. We'll be back together at some point. I'm >>calling. Yeah. Yeah. I'm actually on the road with customers. So it's starting to happen. >>Yeah, us too. We did uh we did public sector summit in D. C. This week. I'm heading out to Vegas next week for a show. So it is, it is starting to happen. So just a matter of time hey, >>when I start >>with with your your scope of responsibilities? Network and advanced security, you're kind of putting those two areas together. Very important. It makes sense synergistically. But how are you guys thinking about that? Maybe you could add some color. >>Yeah, sure thing. Um So network in advance security means all things security of Myanmar. So it's carbon black with our endpoint product, NsX in the data center. It's our tons of service mesh for cloud native applications to all the security stuff that goes into our anywhere workspace. Um and you know, I think you you probably get the message here dave at the end where there's three big waves that we're trying to ride. You know, multi cloud computing platform, which is our hallmark, is what we're known for running out across every cloud. It's the cloud native applications, building tools for new modern apps. And then really kind of the future of both networking and compute is being defined by this anywhere workspace. Our mission is to put security and connectivity into all of that. That makes it work. That makes it work well at scale. And so it made sense to put all that under one roof. Uh, I'm the guy and that's what we're doing. >>Yeah, you talk about that anywhere workspace, which, You know, it was always kind of a great vision and then it was somewhat aspirational, but then it became not only reality, but a mandate over the past 15, 18 months and that has that ripples through two implications on networking, even getting flatter and the security implications. So, all those things are coming together >>there really are. You know, I think we can't under estimate the profound impact that covid and the kind of work from home has had on our lives on society were still turning through what those implications are, but in networking it's cause for a fundamental rethink and for 20 years I've been doing networking and for 20 years we had this notion of a demarcation point networks defined as something that it was a DMZ, right? And, and on one side of that, TMZ was a dirty, untrusted internet, who would scary the other side is the clean, blissful corporate network where you know, only butterflies and unicorns exist and you know, wherever you were in the world, your traffic would be back hauled through that dems so that it could be scrubbed. And if you ever used tools like we're using now zoom, you know, you realize that that experience of back hauling traffic through traditional VPN is pretty simple. And so, so across the industry, enterprises are saying, you know what, there's got to be a different way instead of moving by traffic to the security services. What if I turn that upside down, That's what we're doing a VM ware, which we're taking those security services that we live in the DFc. We're doing what VM ware does well, which is defined them as software and then running them in hundreds of points of presence around the world. Hundreds. And so we effectively moved the security close to the users wherever the users are instead of the other way around. And that's the way we think we'll be building networks in a post pandemic world. >>Yeah. And that talks to the trend of this hyper decentralized system that's basically everywhere now, you know, even even out to the edge. And so, so you now have this, you know, zero trust used to be a buzzword and, and again, it's become this, this mandate. You guys actually did some, I think it was you who did some really interesting research post the solar winds hack on. Talking about things like island hopping and explaining how malware was getting in self forming and some of the insidious ways in which the, the adversaries and, and that is a function of a lot of things. The adversaries are obviously highly capable. Uh, they're motivated because it's lucrative and, and, and they keep upping the game on the good guys if you will. >>Yeah, it's nuts. But, and so so think about the impact that ransomware has had. Uh, and also to your point about the anywhere workspace. I'm right now in boston, I could, you know, tomorrow I'm going to be in texas and the day after that I'll be in san Francisco. So I'm popping all over the place, you know, we're back meeting customer's going wherever they want us to be. But wherever I am, I'm able to connect and, and my traffic needs to be protected. Now in boston it was a ransomware attack against the ferry. We're not talking about a bank or like a sophisticated, you know, sort of organization, it's a ferry that moves people from Cape Cod to an island across the water and it disrupted that ferry for days. So so at VM ware, we're measuring all the inner workings of what's happening in the data center and we collect more than eight trillion with a T eight trillion events per week and that allows us to be able to identify these anomalies like ransomware. And so just in the last 90 days we've stopped more than a million ransomware attacks. 1.1 million ransomware attacks that we stopped within six seconds, More than a million ransomware attacks in the last 90 days. To give you a sense of the magnitude of this problem it's everywhere. And you you reference Zero Trust. Zero Trust is a concept, it's a philosophy, is not a product by Zero Trust. You implement a Zero Trust model which says in a deep perimeter Rised world in a world where people like tom or hopscotch on all over the place and Dave's in boston and you know, I could be in san Francisco, we have to make the assumption that somehow some way, you know, our machine or a user has been compromised. And so you wrap each little piece of the infrastructure, each little piece of the application, you wrap it a protective armor to assume that everything around it is hostile and that's how we stop somewhere. That's how we can keep your infrastructure safe. And this is something you have and where does very uniquely because of the intrinsic attributes of our platform, our virtualization platform and our multi cloud platform. >>Yeah. You talk about the ferry anybody who's ever taken the ferry to Nantucket knows it's a pretty low tech operation and when that ferry goes down, it's one thing, it's, it's whether you can kind of understand that but people's lives get ruined, their vacations get ruined, they can't get off the island. Commerce comes to a grinding halt. It's extremely, extremely expensive really. >>For days, >>for days it was >>Like it wasn't a 20 minute outage. You know, it was like a fairy is not running for a couple things like that. That is a huge, huge, very high impact thing. And the fact that it was so pedestrian, like they don't have billions of dollars in the bank and you know, sort of super secret defense technologies, it's a ferry, you know, right, come on rental cars everywhere. So everywhere >>talk about your software approach two networking and security a little bit more. How that changes the experience for organizations generally, and developers specifically. >>So in a multi cloud world you can't always count on having physical infrastructure that you can touch. And in fact, do you really want to touch that stuff. And so our idea is that if you think about infrastructure, its job is to support the needs of the application. And so for example, in Kubernetes, we have the ability for developers say, look, here's my cool new application and this peace talks to this peace talks to this piece and nothing else. And so we can implement those types of controls using what we call a service smash, which allows us to, to make those connections smooth and seamless across clouds. Some of it could run on amazon, some of them could be running in a private cloud infrastructure. Some of them could be running in the traditional VM and in fact many complication applications do just that. So we can facilitate that communication back and forth and we have the ability to look for stuff that you just never happened because when you understand how an application is supposed to work, it allows you to spot, hey, wait a minute. That's not right. That's that, that's that, that don't like someone trying to manipulate the ferry system rather than somebody trying to board the ferry and get off. And I think, you know, there's a really interesting observation here, which is when you, when you, if you can see the inner workings of an application, like it looks for example, let's think about a mortgage payment application filed, a mortgage payment application and the Attackers has stolen a credential. They're going to get in. It's really hard to figure out a friend from foe. But once they get into mortgage payment application, I'm not going to pay my mortgage right? They do crazy anomalous things like wildly anomalous things. If you can see them, you can stop them and we have the unique ability to see them because we put the telemetry, the observation into our virtualization platform that runs on every cloud that runs wherever the user is. Right and pulling all that together into a central issue. That's something I think the N word to do uniquely and this is why we're having such success insecurity. >>I wonder if you could talk a little bit more about securing containers. You just sort of reference that but containers are moving target just a few short years ago, containers are ephemeral. You weren't you weren't gonna be running you know, your mission critical or business critical postgres in containers. But now that's changed. You're getting state. But so that's a moving target. How are you thinking about handling? You know, those kind of changes And what about the architecture allows you to be kind of future proof if you will. Sorry to use that >>word? No, no, it's a good question. So you've articulated right. So if you think about a traditional application, we used to always talk about three tiered web app, there's a web server is app server and the database a little more complicated than that. But you can usually go in and you could touch those three tiers. This box is the web tier. This box step here. This big box, is that it. And so security controls were built around this idea that you could you could wrap that relatively easily. We talk about a container based application And all these microservices. It's not three tiers anymore. It's 300 tears or maybe 3000 tears. Bitty little things, these little services that turn up and turn down and they all have a piece and so our view is that the A P is the new endpoint, the ap is where the action happens and not just the ap that faces the internet but all the inner workings, all the internal apps. And so because we put that application together, because we help the developers create those apaches, we have a unique understanding of how those apps are used and we're just introducing the ability to provide visibility around how are these epi is being used and then we can do anomaly detection and we are seeing a whole new set of attacks that are using legitimate apiece. They're not appease that are that are that are broken or malformed but the Attackers are finding ways to extract data from an API that maybe they shouldn't remember some of the facebook stuff where they had these Attackers were profiling users and there's no limit to how they could profile users and they were just expecting huge amounts of data that's an ap breach. These are the kind of problems that we can solve for our customers with these built in Tan Xue uh service mesh and api security controls >>you think about all these trends we're talking about and I want to ask you about how it's affected go to market because kind of the old days you had box sellers, they, you know, they would integrate VM ware or whatever. They you might have a specialist that was really good at ST for instance, S. A. P. And they were good partners. So that kind of value add developers have become a new channel for you and I wonder how you think about that, how they're now influencing their go to market. >>Yeah, that's that's a clear trend in the industry are absolutely right on, we call it moving left, right. So it's getting earlier and earlier in the development process. And so one of the things that renouncing at the show here is that the tons of community edition that makes it super easy for developers without putting down a credit card or making a big expensive commitment. They can start using these tools and get productive right away. And so so on top of that we build security controls that understand the total life cycle. So as the developers writing code, we're checking that code to make sure is this compliant doesn't have any known vulnerabilities. This is gonna break something. If you if you put it out there and then when you go to hit commit and say, all right, I'm ready to go, we've already done the homework to make sure the code is clean, we'll put it in the right place. So placing it into production in a way that is wrapped with the security that it needs the guardrails are in place and now we have this this X ray vision, this ability to look at the inner workings and understand the Ap is what's happening inside the application and identify anomalies. And lastly, once the thing is up and running we actually have the ability to measure we called posture and make sure that it doesn't drift from its intended configuration. All of this is done across every cloud. So this is, this is how we think we have a kind of new and very holistic approach to securing collaborative applications. >>Tom I want to ask you about telco transformation, I mean N F V kind of just barely scratched the surface in my view and now we're seeing with the edge and five G and the cloud there's some oh ransom. Really interesting opportunities going on in in telco say what you want about telcos? Yeah, there, you know the connectivity and Okay, fine. But one thing you say about the telco networks as they work, you know, and it actually did a great job during the pandemic. They had to pivot to landlines and and so when it comes to reliability and rock solid nous, those guys kinda kinda get it but they've got to be more flexible. So you see those two worlds colliding what's going on in in telco and and where does VM ware play? >>Yeah, sure thing. A huge amount of emphasis on telco, we've won some very large telco deals. Five G is not just a faster version of four G. 5G is a new take on what an edge network can do. It has the ability to run extremely high performance network connections and the ability to control the performance. So this idea of what's called network slicing, so you can guarantee a certain amount of latency or a certain amount of bandwidth. So combine that with this explosion of IOT devices. We're going to have an infinite number of devices. Every device you can imagine has a computer in it and it's spitting off giant amounts of data. We keep coming up with new and interesting ways to analyze that data to do things like, you know, control the self driving car to do things like create a customized retail experience to do things like help guide research for an oil company on the oil platform. Okay. These are all examples of edge computing. Now, the infrastructure that you need to protect those workloads is what we're defining and software. And putting it everywhere, Not just in the traditional data center where you might be in 1020 locations, we're talking about hundreds going into thousands of locations. And this is what the industry is calling sassy or secure access services. Edge. So where's your firewall? Your web proxy the controls that you need to protect those apps, where do they live? They're gonna live in the telco infrastructure And that stuff all runs on X 86 servers. So if you put in the data center services into this distributed architecture and you've got tons and tons of data that's being produced produced locally. Why would you want to remove the compute there and we think you can and will and this is this is why VM ware with our telco partners is uniquely suited to build the groundwork for this edge computing infrastructure. And I think edge computing is going to be the next big wave. So we went from private clouds to public clouds and public cloud was built on, you know, the scale out fault tolerant model as we move to edge computing, edge computing is going to be around applications that need huge amounts of data, very low latency and they're highly distributed. So they're going to run not in 10 or 20 locations but in 1000 more. And we can do all of this with our tons of kubernetes with our virtual networking infrastructure and our anywhere workspace and the secure access services, Edge, the pops that we're building and I think VM ware is probably one of the few if any companies that have all of these pieces that we can put together to make the Edge actually work. >>Yeah, exciting times and and all that data ai influencing at the edge of new processor models and you guys are thinking about all that stuff tom we got to leave it there. Thanks so much for coming back in the queue. Great conversation. >>Always a pleasure. Thanks very much. David, Take care >>Alright you to keep it right there, everybody. This is Dave Volonte. For the Cubes coverage of VM World 2021. The virtual edition will be right back.