>>From around the globe covering Google cloud. Next on there. >>Hi, I'm Stu Miniman and this is the cube coverage of Google cloud. Next 20 on air it's week seven of nine. Google of course took their event that was supposed to be in person and Moscone, spread it out online. It's all available on demand. Every Tuesday they've been dropping it in the cube. We've got a great lineup that we're going to share with you of our coverage thought event. This is our analysis segment, joining me to help dig into where Google cloud is. Everything happening in the ecosystem. Having to bring in Dave Alante and John furrier, our co-founders co-CEOs and, uh, always hosts of the program, John and Dave. Uh, it was, uh, it was great last year being in the middle of the show floor, uh, with the whole team and the great glam beautiful booth that Google built well, we're remote, but we're still in the middle of all the topics, the big waves and everything like that. So thanks so much for joining me and look forward to digging into it. >>Hey Stu, great to see you remotely. We got to get these events back. His virtual events are nine weeks, three weeks for Ws all day events. DockerCon virtual orders, nobody ecosystem support. I mean, this is really an interesting time and I think Google has laid out an interesting experiment with their multi. I call it summer of cloud program nine weeks with just a sustained demand for your attention. It's going to been a challenge. >>The question always, John, can they keep their attention? John, you laid out, you know, the cube three 65 were, there is 365 days a year, help extract the signal from the noise, help engage with the community. So absolutely want to kind of peel back the onion and see what we think of the event. But let let's, let's start with Google. Dave, you know, you've been digging through the numbers as you always do. Uh, we're we're more than a year since Thomas Kurian came in and you know, what are you hearing? What's the data showing you as to, you know, where Google really sits in the marketplace? How are they doing >>Well still you're right. I mean, Thomas curious now I think he's about 18 months in and in one of my previous breaking analysis, I kind of laid out a four point plan for, for Google. And we can talk about sort of how they're doing there, but, but really the first one is product maturity and there's, there's a number of things that we can assess as it relates to product maturity. The second we talk about it all the time is, is, is go to market. I think the third one is really around differentiation. How does Google uniquely differentiate from the other cloud service providers? And I think the fourth and we saw this earlier this year with Looker is, you know, Google's got a war chest and you know, they can use that to really beef up the cloud. And I think if, if, if you, if you look at it, you know, Google's done a pretty good job with things like fed ramp. >>I mean, these are table stakes in the big cloud. You know, they're starting to do more things around SAP of VMware, uh, windows. I mean, again, these are basic things that you have to do as part of any large cloud provider. I think the other thing we talked about go to market, they've done a number of things there. Karen's really focused on partnerships. He wants to be a hundred percent channel, uh, at the same time they're hiring salespeople. I think they're up over 1500 salespeople right now, uh, which is, you know, we're getting there. I think it was less than that. Obviously when he came on, that's kind of the benchmark, although we don't really know exactly what, what the numbers are. They've kind of launched into public sector. They see what's happening with Amazon there, they see great opportunities. They see, you know, what, what Microsoft is doing. And so public sector, they have to put out bakeoffs so you gotta be in there and at differentiations still a lot of, okay, how can we leverage alphabet our search business and retail, our business and healthcare, um, and edge things like autonomous vehicles. There's, there's some opportunities there. And then as I said, they're doing some M and a two plus billion dollars for Looker, you know, great capability. So I think they're, they're executing on those four and we can talk about what that means in terms of, you know, revenue and position in the market. >>Well, yeah, Dave, maybe it makes sense to let let's, let's walk through the revenue, just so that people understand, you know, where they sit for the longest time it's been, you know, the number three or the number four where Alibaba said, uh, compared to them, but they are still far behind, uh, AWS and Azure. Uh, and have they been closing the gap at all? >>Well, if guys, if you could bring up that chart, that first one, uh, this is are, we really are estimates. You remember now AWS, every quarter gives us a clean number for their infrastructure as a service. And what we've got here is an estimate for full year 2018, 2019 that's calendar year, the growth rates, and then, uh, with a trailing 12 month view. And I think there's a couple of points here. One is you can see the growth. Google grew 89% last year. They were 70% in Q one 59% in Q two. So, so even though it's somewhat declining, they're growing faster than both Azure and AWS, of course, from a smaller base. I think the other thing, if you, if you go back and look at 2019, relative to AWS, Google was one 10th, the size of AWS. Now they're, you know, there's only eight X, so they're starting to close that gap, but still very much a, a quite a distance from the leaders. >>Yeah. Uh, John, maybe if we look at Google under Thomas Currian, of course there's been a real, uh, growth in hiring. So, you know, you're there in the Valley, John, we know lots of really smart people that have joined Google's great enterprise, uh, you know, pedigrees there as well as the ecosystem, uh, that, that wants to be able to partner with Google. You know, what are you seeing? What are you hearing? I like one of the interviews that you did, uh Suneel prody, uh, it was, it was the number two over at Nutanix. Uh, and now we've got an important role in Google cloud, >>Google hiring great people. I got to say, one of the things I'm impressed with is I've always liked the product people. They have great product chops. I'll ask the Google has come from a position of strength on the tech side being Google. Um, and, but the enterprise business is hard too, and they got to hire more enterprise DNA. They're trying to do that at the same time. They're trying to make the table stakes stuff done, move fast during the product side. And then at the same time, create the game changing product with like ant those for instance, um, and then have all those new features. So they're running as fast as they can. Um, they're building product as fast as they can. So you got, you know, developer and operator efficiency, which I love the strategy. However, when you run that fast, there's definitely debt. >>You take on both technical and market debt around trying to make a shortcut. So Google to me, the word in the Valley is great stuff with the people. Product is awesome, getting better, good product people, but still those enterprise features product reliability in terms of not sunsetting products early to, you know, making sure the right support levels are there. These are like the little details that make the difference between an enterprise player and someone who is essentially, you know, moving too fast, get new products being to agile. So yeah, it's a double edged sword for Google. We've said this all the time, but overall I'd give them a solid number three position and still haven't seen the breakout yet. I think ant those can be that if they keep pushing on this operator efficiency, but I just don't think the enterprise is ready for Google yet. And I think there's issues there. >>Yeah. John, you bring up a great point. I know the last couple of times we've been at the show, I feel like I'm scratching my head. It was like, wait, when did lift and shift become sexy? Yes, you want to meet the enterprises where they are, but how is that different from the message that we hear from Microsoft that we hear from AWS? Uh, one of the bigger announcements during the infrastructure week, uh, was about a new program, the rapid assessment and migration plan or ramp, uh, to help customers get from where they are, where they need to be. Uh, it's interesting because of course, if you, you know, for reinvent for years, we had all the systems integrators, helping customers move and migrate, uh, both AWS and Azure have lots of migration solutions out there. So, you know, how will Google differentiate themselves and make different there? >>Well, they don't, they don't really know. I mean, they have put stuff down on paper, but here's the problem that Google has to overcome to make it a truly a fast growing cloud player. They got to nail the product features that they need to be in the marketplace. And the ecosystem really wants to work with Google. I see retail is lay up for them and they're doubling down on that. They've got smart people working on this, but the ecosystem and adding product features are two major heavy lifts ecosystems about moneymaking. At the end of the day. I know that sounds kind of greedy in this era of empathy and missions and values, but at the end of the day, if you're not making your ecosystem money, which means keep products around support for a certain number of >>Years and have incentives economically for people to build software. They're not going to work on your platform. And I think Google needs to understand that. Clearly. I just don't see it. I mean, I just don't see people saying, I love Google so much. I'm making so much cash and success. Um, and they got some good products. You know, I, like I said, products on ecosystem are things they're going to ratchet up super fast. Well, there's a couple of places, a couple of partners they violated, like I said, durian wants to be a hundred percent channel-based channel fulfillment. And when you talk to the channel, they do tell you, yo Google there they're being aggressive. Deloitte, you know, they chart chart out as a big partner HCL. Now of course, those guys are all working with everybody, but they're starting to put resources around that in terms of training and certification. >>And of course, other, you know, much smaller resellers and partners. So that's, that's interesting, right? That being really super channel friendly, that's a differentiator to your point, John, that's making be do that because they're not coming from a position of strength channel. No, they are channel friendly. Can, you can say you're channel friendly, but if your product doesn't work, the channel will reject you instantly. They're, they're a, they're a tough critic and they need to have reliability. So again, this is not really a problem with Google. It's just a product is evolving fast at the same time, they're trying to roll out a channel. So if you want to have a good rental strategy, you gotta have a good one posture and programs, but the product has to be enabling and reliable. And if someone's building software on top of a cloud platform and stuff doesn't work or changes, that's more cost more cost means more training, more hiring. >>If someone leaves, how does it scale? These are like really important things around channel. Cause they have to sell to the customer and support their name's on the line. So again, channels and easy to say thing to do, but to actually do it with a product is hard. And I think Google has that challenge. And again, it's a challenge that they overcome. It will be a great opportunity. Well, and I think that's a good point because it wasn't, it was 2019 when I was like VMware SAP, full blown windows support. I mean, that's, that's really late to the game. And so as I say, product maturity is critical, but there are some, some winners there obviously in analytics, uh, I think big query as get, gets very, very high marks. So there's, there's some real pockets of, of, of positive positivity there. But you know, I would agree though, the maturity is a key factor for the channel to really go on. >>Well, right. If you look, John, you mentioned anthro Santos was the story last year. Uh, and it's, we're all talking about multicloud. Uh, much of the multi-cloud discussion has been, uh, due to Kubernetes. And if it wasn't for Google, we wouldn't have Kubernetes. The concern of course, is that Google took it, it open source. The CNCF took it as a foundation and customers went nuts with it and the other public cloud and even, you know, smaller cloud providers are getting as if not more value than Google is. So what you hear in the back channels, when you say, boy, Google brought this technology out district really help enable their platform. Well, AWS is still winning. AWS has plenty of solutions. They've got interesting things to get, you know, deep solutions, leveraging Kubernetes. Uh, and if you look at Google, they announced anthros last year, it's gone through some updates this year. >>Uh, you know, you both mentioned, uh, working with the partners. One of the things that jumped out at me, uh, there's now something called ant those attached clusters, which means that if I have somebody else's, you know, Kubernetes that is fully certified, I can, I can plug that in and work with Anthem. It was one of the gaps that I saw last year. You hear Google saying, we're partnering with VMware, we're partnering pivotal, but here's. And if you want to use OpenShift or PKS, you know, you need to come over to work with Anthem here. We are understanding that customers are going to have multiple environments and often multiple different Kubernetes solutions out there. Uh, you know, Dave, you mentioned like VMware, of course is a really important solution. VMware moving along and supporting more Kubernetes. Uh, and the, the update for the solution is the Google cloud VMware engine. >>And absolutely the number one use case they talked about is take your VMs, get them in the cloud and then start using those data and analytic services that are in the public cloud. So we're seeing some maturity here, but you know, Dave, if we look at the multicloud market, you know, it, Google's not the first company that typically comes to mind, you know, VMware, red hat, even Microsoft probably are a little bit higher on people's thoughts. You know, what have you been seeing? It's an area we've been spending a lot of time last couple of years hybrid and multicloud. >>Well, we have some data on this guys, if you would pull up that next graphic and this, this is observing data from our data partner ETR and what this shows on the vertical axis is the spending momentum. So are you spending more or less? And then it's really a net score, which in other words, to subtract the less from the morning when we have leftover that's, the vertical axis high is higher, is better. And then the horizontal axis is markets, bear really presence in the data set, and you can see the hyperscaler guys, you know, that's where you want to be Microsoft AWS. They're always sort of separating from the pack. You'd love to see Google. Is there a hyperscaler out there with those guys, but they're not one of the interesting things that we're seeing in the dataset Stu and John VMware cloud on AWS has really popped up. >>So this thing of this notion of hybrid as part of the cloud ecosystem and multi-cloud is really starting to have legs. And you can also see red hat with, with open shift and believe it or not even OpenStack as a telco, you see in that pop up as well as VMware cloud, which is comprises cloud foundation and other components. So you see that hybrid and multicloud zone. And I think, I think you got to put Google, you know, right there, you can see where IBM and Oracle are for just for context, they don't have the momentum, they don't have the market presence in cloud, but they have a cloud. So that's kind of how the landscape is. And I think Google, from a standpoint of ant dos, they, again, they have to be trying to be open, leverage their Coopernetties chops and try to differentiate from certainly AWS. I think your point is right on, I think Microsoft has a pretty strong story there, but Google's got a clean story and they're investing and I think it's a good position for them. Not as, not as good as the other two, but you're when you're coming from behind, you have to try to differentiate and they are. >>Yeah, well, Dave, you've always said the rich get richer when these markets, but now with COVID that they are getting richer. Amazon honestly, stock I'm billion trillion, $2 billion valuation for Apple Google on the cloud side. This is, I think that if they had more product leadership in certain areas, I think they'd be doing more, more with their cloud, but they have some IP that could come out of this post COVID growth strategy for them, where it could be a game changer. So if you look at security and you look at identity, and one of the things that caught my attention in the anthesis announcement was this, uh, this, uh, identity service that they have, which is like, uh, open ID kind of connect thing. Identity will be critical because Google has so much IP around, um, you know, um, user login information around the mobile on the mobile side. >>I mean, Jennifer Lynn on this many times that they could leverage that and really helped the edge secure. And from a user access standpoint, having identification in the Anthem would be great. And this whole modern application trend is kind of where the puck is going. So you're there kind of skating to that puck area. And also they're focused on operators. This multicloud thing hits a home run with operators, because if you can create an abstraction layer between multiple clouds and have this modern kind of top layer to it, you're in a good position, but the insiders here in Silicon Valley and in the industry that I talked, they were all saying that Google has huge IP in their network. They have a very solid network. So what's interesting to me, as a Google can take leverage some of those network pain points and then bring anthesis that connective tissue. They got a real opportunity, but they've got to pull it off, right? So covert hitting, probably the worst thing that could have happened to Google because they were just a couple feet from the goal line on this, on this market in terms of really exploding. But I think they're well positioned. I'm not down on Google at all. >>I think that, you know, I'm glad you brought that up, John, because I think Cove was a two edged sword for them. I just published last week in my breaking analysis this weekend, actually that there were three big tailwinds insecurity as a result of coal go away. And identity was one of those cloud of course, was, was the other one. And then endpoint security was the third. And so that's a, that's, that's a, you know, kind of good news for, for, for identity. The flip side of it is if you go back and look at where Amazon and Microsoft were in terms of their growth, relative to where Google is now, Amazon and Microsoft appear to have been growing larger. Now these things go in an S curve, you know, it's kind of an old guy that starts out slow and then gets really steep. So we may actually see Google accelerate. Uh, but >>I think you wait in that it may have to wait until after COVID. So it's really a Jewish store, good news on the identity side. And Google's well positioned, but necessarily bad news from a growth standpoint. Well, there's three areas to that. You know, you and I have been riffing on lately and we've, haven't published a lot yet because we're going to wait until we have our event cube con event in October. But there's three areas, I think ant those points too. And they even say this kind of in their own way, um, multicloud, which is customers, connecting customers anywhere and finding device and whatnot. So customer connection points, customer enterprises, improved developer, modernized developer, the developer market, and then three operators, three areas that are all moving trains. They're all shifting under their feet. So I think they're doing great on developer side because they have great traction. >>We've covered that with coop con and other areas have done amazing work operator efficiency, no problem. I think they got a lot of great credit there and are building and adding new stuff. It's the customer piece that's weak. They, I think they really got to continue to double down on what is the customer deployment, because let's face it, enterprise customers aren't as savvy as Google or the hyperscaler. So when you roll into main street enterprise, especially with Cova Dave, as you pointed out, are they sitting there really grokking Coobernetti's on bare metal? And at those they're like, shit, how do I keep my network alive? So it, I just think isn't a long yet operationally on the customer side. And I think that is a weakness, um, and on Google's formula and they got to just make that easier. >>Yeah, no, no great, great points there. Absolutely. In, in talking to a lot of the cloud customers, if they already have an existing relationship that's expanding or accelerating, that is a lot easier than choosing a new environment. So as Dave said, the rich get richer. Um, I mentioned that at, at the start, this is week seven of nine of what Google is doing. Um, we want to get both your, your viewpoints on this event, how they laid it out nine weeks, it's all done on demand. I know when they had the opening keynote, there was a decent rally point. You saw the usual Twitter stream out there. They had a nice median analyst program that kicked off at the beginning. For me personally, there's been some stuff that I've gone back infrastructure week. I watch this week for app modernization. There's definitely some announcements that I'm digging into, but I think overall what I see out there is people rallied at the beginning and then they kind of forgot that the event was going on. Um, you know, what are you seeing? You know, what, what's the new best practice on, you know, how long should an event be? How do you deliver it? How do you get engagement? >>Well, I mean, just to, you know, Tim, Dave will weigh in, but I'm pretty hardcore on my criticism of most of these virtual events, mainly because virtual event platforms and virtual event executions or whatnot, well known as a first kind of generation problem. No one's really been under this kind of disruption when they got to replicate their business value as quickly in an environment they weren't optimized or have the personnel for. So you're seeing a lot of gaps in these virtuals, kinda like multi-cloud and high, where you have tens of different definitions of how to do it. I think Google went to nine weeks cause they really didn't know what to do. And they left a lot of their ecosystem hanging out there because normally Google next is a huge show with great content presentations. Everything's up on YouTube anyway. So on demand is not a build value. >>The real value of Google next was the face to face interactions. The show floor, the ecosystem, the expo hall that is completely absent from the show here. And this is consistent with other events. And honestly, it's over nine weeks, Amazon re-invent, it's going to be over three weeks. And last year they had a music festival. How are they going to replicate that again, this is a huge negative shift for these vendors because they rely so much on these events to get the word out. So it's really hard. Um, so I, I I'm really impressed with the nine week program and the sense of kind of staging it out and kind of the summer of cloud, I would have done things a little bit differently if I was them in terms of making it more exciting, but it's just really difficult to command attention for the audience over nine weeks. >>And I think that's, if they had to go back and do a Mulligan, I would've, they would've probably would've done more activation around the digital rather than a bunch of on demand video. So at least I did something and didn't cancel now the good news is there's a slew of news. We can collaborate on, um, the virtual spaces, the internet. So people are talking, it's just that it's all distributed. No one knows who's there, right? So it's not like an industry event. It's just an online collection of videos like on YouTube. So I felt that lack of intimacy was probably my, my biggest critique. Um, but again, I think he just wanted to move forward and get this behind them. >>I think you nailed it, John. I mean, on the one hand they made it harder for themselves stretching it out over nine weeks. On the other hand, they kind of took the easy way out is putting it up on all on demand. I guess they have analyst programs too, but I felt like they, weren't certainly not even close to what you have in physical. And it's really hard to obviously replicate physical, but I've seen other programs where the intimacy with the analyst and the journalist was much higher and opportunities to have interactions with executives. I felt it was just a little bit removed, actually quite a bit removed would have loved to have seen just a more intimate one-on-one activity. Maybe not one-on-one, but, but one, one to many with a smaller group of analysts and journalists, I think that would have gone a long way. Um, and that, that was missing for me anyway. >>I mean, they could have done nine micro events every week with like a rallying point is to pointed out, um, just really a difficult, I mean, who, who was executing this event? I mean, they have an events team that's used to doing physical events, Moscone and whatever. It's just, they didn't, I don't think had the time to figure it out. Be honest with you. I mean, Google is a company known for search relevance, find what you're looking for and uh, organizing content. I just think they didn't do a good job at all. And I think I didn't have any much attention cycles to it because I was kind of keying in the news, but I didn't know where my friends were. Who's rallying is Stu there. I didn't even, do's tweeting, I'm not following it. Or I missed his tweet. So there's a lot of asynchronous, um, stuff going on with was no, you know, gravity around a community or ecosystem kind of moment where I could schedule an hour at 10 o'clock or multiple times >>Does the day to check in and go to the watering hole or some stuff, >>You know, hub or instance like that. So, you know, something that we're thinking a lot about David's, you know, and I think this is a moving, moving target, but what's clear is that you can create synchronicity and still have the asynchronous programs. So at least we learned that with the Docker con event that we did and the software that we're building. So, you know, virtual events, isn't about just the events, but what happens on inside the event, outside the event, after the event, I think people are too hung up on this. I got to have a portal walled garden model. So I think it's going to be a learning curve for everybody. And I think Google may or may not do nine weeks. We'll see what re-invent does with three weeks. How do you keep people's attention? But three weeks when they're not in Vegas? >>Well, you know, no, I think that physical or virtual, it's your opportunity to write the narrative, to set the tone or set the narrative. And you're seeing this with the conventions, with the political conventions, you know, they're, they're actually, you know, you don't necessarily watch the whole thing, but you get a good sense, you know, post virtual event, what the narrative is. And I think that's cause you know, the media picks it up and I think it's, it's imperative to really do a good job of interacting with the media. You know, the analysts, the ecosystem, the partners, I haven't talked to a ton of partners who have been totally engaged other than, you know, their one-on-one activity. So I think there's an opportunity there to, to really write that narrative, to set that narrative and keep it alive and that, that entices people to go back and watch the man. Then I didn't feel that hook here. >>Yeah, here's the problem that I see with has Google has this problem and Docker con did not have the problem and you know, self-serving, we did that software, but we designed it for this purpose. When I go to an event, you do guys too. But personally, when I go to an event face to face, I like to get a sense of what the collective group at the event is thinking. I fly there, I'm present. I can see the presentation. I can see the pack breakout sessions. I know it's not back. I can get a sense visually. And with my senses on what the collective voice of the group is at an event, does it suck? Is it good? How's the band? What it's, what's the hallway conversation. So I can feel that I had none of that with Google next. Okay. Like, I didn't know, five, no, I had no other than some random things on Twitter, I had no sense what the collective ecosystem thought of the event. >>And I think a lot of the events have that problem where you can do both. You could have the rallying moment where there's a group collective coming together and send people to do that and still have the asynchronous consumption, organizing the content. But that's one of the main benefits. What is what's, what's going on with it? What's the voice of this collective? How are people thinking about this? And who's there? Who can I connect with and maybe follow up with, I didn't feel that this was simply a bunch of videos posted fundamental. Yeah, absolutely. John, >>If you can't feel that energy, is there a Slack channel, is there some chat group, uh, is there some way that, that you can be involved? Uh, definitely a missed opportunity, especially Google's got great collaboration tools. They're tied into all of our calendars would have been something that they could, uh, make ways that we could engage and find out. All right, John and Dave, thank you so much for helping us, uh, you know, really dig through a lot, going on. As we said, this nine week event, uh, we we've got a playlist, uh, that we're, we're going to be broadcasting for some of the key executives. Got, got a lot of the news here. And after this week, which was at modernization, we do have a couple other interviews that will be, uh, coming out, uh, when we have them, but be sure to check out the cube.net, uh, for all the upcoming, as well as search, to be able to find the previous, uh, content there, reach out to at furrier at diva launch date, or meet at Stu for any feedback or comments. We'd love to get your feedback, especially in these times when we can't all be together. So thanks John and Dave for joining and I'm Stu Miniman. Thank you for watching the cube.

(upbeat music) >> Announcer: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is a CUBE conversation. >> Everyone, welcome to this CUBE conversation. I'm John Furrier with theCUBE, host of theCUBE here in our Palo Alto office for remote interviews during this time of COVID-19. We're here with the quarantine crew here in our studio. We've got a great guest here from Google, Will Grannis, managing director, head of the office of the CTO with Google Cloud. Thanks for coming on, Will. Appreciate you spending some time with me. >> Oh, John, it's great to be with you. And as you said, in these times, more important than ever to stay connected. >> Yeah, and I'm really glad you came on because a couple of things. One, congratulations to Google Cloud for the success you guys had. Saw a lot of big wins under your belt, both on the momentum side, on the business side, but also on the technical side. Meet is available now for folks. Anthos is doing very, very well. Partner ecosystem's developing. Got some nice use cases in vertical markets, so I want to get in and unpack with you. But really, the bigger story here is that the world has seen the future before it was ready for it. And that is the at-scale challenge that the COVID-19 has shown everyone. We're seeing the future has been pulled forward. We're living in a virtualized environment. It's funny to say that, virtualization (laughs). Server virtualization is a tech term, but that enabled a lot of things. We're living in a virtualized world now 'cause we have to, but this is going to set in motion a series of new realities that you guys have been experiencing and supporting for many, many years. But now as a provider of Google Cloud, you guys have to operate at scale, you have. And now the whole world realizes that scale is a big deal. And so you guys have had some successes. I want to get your thoughts on the this at scale problem that the world now realizes. I mean, everyone's at home. That's a disruption that was unforecasted. Whether it's under-provisioning VPNs in IT to a surface area for security, to just work and play. And activities are now confined, so people aren't convening anymore and it's a huge issue. What's your take on all this? >> Well, I mean, to your point just now, the fact that we can have this conversation and we can have it fluidly from our respective remote locations just goes to show you the power of information technology that underlies so many of the things that we do today. And for Google Cloud, this is not a new thing. And for Google, this is not a new thing. For Google Cloud, we had a mission of trying to help companies accelerate their transformation and enable them in these new digital environments. And so many companies that we've been working with, they've already been on the path to operating in environments that are digital, that are fluid. And when you think about the cloud, that's one of the great benefits of cloud, is that scalability in common with the business demand. And it also helps the scale situation without having to do the typical, "Oh wait, "you need to find the procurement people. "We need to find the server vendors. "We need to get the storage lined up." It really allows a much more fluid response to unexpected and unforecasted situations. Whether that's customer demand or in this case a global pandemic. >> Yeah, one of the things I want to get in with you on, you have explained what your job is there 'cause obviously Google's got a new CEO now for over a year. Thomas Kurian came from Oracle, knows the enterprise up and down. You had Diane Greene before that. Again, another enterprise leader. Google Cloud has essentially rebuilt itself from the original Google Cloud to be very enterprise centric. You guys have great momentum, and this is a world where cloud-native is going to be required. I mean, everyone now sees it. The tide has been pulled out, everything's exposed, all the gaps in business from a tech standpoint is kind of exposed. And so the smart managers and companies are looking at things and saying, "Double down on that. "Let's kill that. "We don't want to pay that supplier. "They're not core to our business." This is going to be a very rapid acceleration of what I call a vetting of the new set of players that are going to emerge because the folks who don't adapt to this new cloud-native reality, whether it's app workloads for banking to whatever are going to have to reinvent themselves now and reset and tweak to come out of this crisis. So it's going to be very cloud-native. This is a big deal. Can you share your reaction to that? >> Absolutely. And so as you pointed out, there are kind of two worlds that exist right now. Companies that are moving to become more digital and transform, and you mentioned the momentum in Google Cloud just over the last year, greater than 50% revenue growth. And in a greater than $10 billion run rate business and adding customers at a really quick clip, including just yesterday, Splunk, and along the way, Telecom Italia, Major League Baseball, Vodafone, Lowe's, Wayfair, Activision Blizzard. This transformation and this digitization is not just for a few or just for any one industry. It's happening across the board. And then you add that to the implementations that have been happening across Shopify and the Spotify and HSBC, which was a early customer of ours in the cloud and it already has a little bit of a headstart into this transformation. So you see these new companies coming in and seeing the value of digital transformation. And then these other companies that have kind of lit the path for others to consider. And Shopify is a really good example of how seeing drastic uptick in demand, they're able to respond and keep roughly half a million shops up and running during a period of time where many retailers are trying to figure out how to stay online or even get online. >> Well, what is your role at Google? Obviously, you're the managing director. Title is managing director, head of the office of the CTO. We've seen these roles before, head of the CTO, obviously a technical role. Is it partnering with the CEO on strategy? Is it you're tire kicking new things? Are you overseeing any strategic initiatives? What is your role? >> So a little bit of all of those things combined into one. So I spent the first couple of decades of my career on the other side of the fence in the non-tech community, both in the enterprise. But we were still building technology and we were still digitally minded. But not the way that people view technology in Silicon Valley. And so spending a couple of decades in that environment really gave me insights into how to take technology and apply them to a specific problem. And when I came to Google five years ago, selfishly, it was because I knew the potential of Google's technology having been on the other side. And I was really interested in forming a better bridge between Google's technology and people like me who were CTOs of public companies and really wanted to leverage that technology for problems that I was solving. Whether it was aerospace, public sector, manufacturing, what have you. And so it's been great. It's the role of a lifetime. I've been able to build the team that I wanted as an enterprise technologist for decades and the entire span of technologies at our disposal. And we do two things. One is we help our most strategic customers accelerate their path to cloud. And two, we create these signals by working with the top companies moving to the cloud and digitally transforming. We learned so much, John, about what we need to build as an organization. So it also helps balance out the Google driven innovation with our customer driven innovation. >> Yeah, and I can attest. I've been watching you guys from day one. Hired a lot of great enterprise people that I personally know. So you get in the enterprise chops and stuff and you've seen some progress. I have to ask you though, because first of all, big fan of Google at scale from knowing them from when they were just a little search engine to what they are now. There was an expression a few years ago I heard from enterprise customers. It goes along the lines like this. "I want to be like Google," because you guys had a great network, you had large scale. You had all these things that were like awesome. And then they realized, "Well, we can't be like Google. "We don't have SREs. "We don't have large scale data centers." So there was a little bit of a translation, and I want to say a little bit of a overplay of the Google hand, and you guys had since realized that it wasn't just people are going to bang at your doorstep and be adopting Google Cloud because there was a little bit of a cultural disconnect from wanting to be like Google, then leveraging Google in their business as they transform. So as you guys have moved from that, what's changed? They still want to be like Google in the sense you have great security, got a great network, and you've got that scale. Enterprises are a little bit slower to adopt that, which you're focused on now. What is the story there? Because I think that's kind of the theme that I'm hearing. Okay, Google now understands me. They know I'm not as fast as Google. They got super great people (laughs). We are training our people. We're retraining them. This is the transformation that they're going through. So you might be a little bit ahead of them certainly, but now they need to level up. How do you respond to that? >> Well, a lot of this is the transformation that Thomas has been enacting over the last year plus. And it comes in kind of three very operational or tactical pillars that I think of. First, we expanded our customer and we continue to expand our customer facing teams. Three times what they were before because we need to be there. We need to be in those situations. We need to hear from the customer. We need to learn more about the problems they're trying to solve. So we don't just take a theoretical principle and try to overlay it onto a problem. We actually get very visceral understanding of what they're trying to solve. But you have to be there to gain that empathy and that understanding. And so one is showing up, and that has been mobilizing a much larger engine of customer facing personnel from Google. Second, it's also been really important that we evolve our own. Just as Google brought SRE principles and principles of distributed systems and software design out to the world, we also had a little bit to learn about transitioning from typical customer support and moving to more customer experience. So you've seen that evolution under Thomas as well with cloud changing... Moving from talking about support to talking about customer experience, that white glove experience that our customers get and our partners get from the beginning of their journey with us all the way through. And then finally making sure that our product roadmap has the solutions that are relevant across key priority industries for us. Again, that only comes from being present from having a focus in those industries and then developing the solutions that progress those companies. This isn't about taking a principle and trying to apply it blindly. This is about adding that connection, that really deep connection to our customers and our partners and letting that connection manifest the things that we have to do as a product company to best support them over a long period of time. I mean, look at some of these deals we've been announcing. These are 10-year, five-year, multi-year strategic partnerships that go across the canvas of all of Google. And those are the really exciting scaled partnerships. But to your point, you can't just take SRE from Google and apply it to company X, but you can things like error budgets or how we think about the principles of SRE, and you can apply them over the course of developing technology, collaborating, innovating together. >> Yeah, and I think cloud-native is going to be a key thing. It's just my opinion, but I think one of those situations where the better mouse trap will win. If you're cloud-native and you have APIs and you have the kind of services, people will beat it to your doorstep. So I got to ask you, with Thomas Kurian on board, obviously, we've been following his career as well at Oracle. He knows what he's doing. Comes into Google, it's being built out. It's like a rocket ship at this point. What bet is he making and what bet are you guys making on behalf of your customers? If you had to boil it down to Google Cloud's big bet, what is the bet on the technology side? And what's the bet on the business side? >> Sure. Well, I've already mentioned... I've already hinted at the big strategy that Thomas has brought in. And that's, again, those three pillars. Making sure that we show up and that we're present by having a scaled customer facing organization. Again, making sure that we transition from a typical support mindset into more of a customer experience mindset and then making sure that those solutions are tailored and available for our priority industries. If I was to add more color to that, I think one of the most important changes that Thomas has personally been driving is he's been converting us to a partner-led business and a partner-led organization. And this means a lot of investments in large global systems integrators like Accenture and Deloitte. But this also means that... Like the Splunk announcement from yesterday, that isn't just a sell to. This is a partnership that goes deep across go-to market product and sell to. And then we also bring in very specific partners like Temenos in Europe for financial services or a CETA or a Rackspace for migrations. And as a result, already, we're seeing really incredible lifts. So for example, nearly 200% year over year increase in partner influenced revenue in Google Cloud and almost like a 13X year over year increase in new customers won by partners. That's the kind of engine that builds a real hyper-scale business. >> Interesting you mentioned Splunk. I want to get to that in a second, but I also noticed there was a deal with TELUS Group on eSIM subscriptions, which kind of leads me into the edge piece. There's a real edge component here with Google Cloud, and I think I had a conversation with Jennifer Lynn a few years ago, really digging into the built-in security and the value of the Google network. I mean, a lot of the scuttlebutt around the Valley and the industry is Google's got an amazing network. Software-defined networking is going to be a hot programmable area. So you got programmable networking and you got edge and edge security. These are killer areas that need innovation. Could you comment on what you guys are doing there and do you agree? Obviously, you have a killer network and you're leveraging it. Can you just give some insight into what's going on in those two areas? Network and then the edge. >> Yeah, I think what you're seeing is the manifestation of the progression of cloud generally. And what do I mean by that? It started out as like get everything to the data center. We kind of had this thought that maybe we could take all the workloads and we could get them to these centralized hubs and that we could redistribute out the results and drive the latency down over time so we can expand the portfolio of applications and services that would become relevant over time. And what we've seen over the last decade really in cloud is an evolution to more of a layered architecture. And that layered architecture includes kind of core data centers. It includes CDN capacity, points of presence, it includes edge. And just in that list of customers over the last year I mentioned, there were at least three or four telcos in there. And you've also probably heard and seen quite a bit of telco momentum coming from us in recent announcements. I think that's an indication that a lot of us are thinking about, how can we take technology like Anthos, for example, and how could we orchestrate workloads, create a common control plane, manage services across those three shells, if you will, of the architecture? And that's a very strategic and important area for us. And I think generally for the cloud industry, is expanding beyond the data center as the place where everything happens. And you can look at Google Fi, you can look at Stadia. You can look at examples within Google that go well beyond cloud as to how we think about new ways to leverage that kind of criteria. >> All right, so we saw some earnings come out on Amazon side as Google, both groups and Microsoft as well, all three clouds are crushing it on the cloud side. That's a tailwind, I get that. But as it continues, we're expecting post-COVID some redistribution of development dollars in projects. Whether it's IT going cloud-native or whatever new workloads. We are predicting a Cambrian explosion of new things from core to edge. And this is going to create some lifts. So I want to get your thoughts on you guys' strategy with go-to market, as well as your customers as they now have the ability to build workloads and apps with AI and data. There seems to be a trend towards the verticalization of whether it's sales and go-to market and/or specialism because you have horizontal scalability with cloud and you now have data that has distinct (chuckles) value in these verticals. So it's really seems to be... I won't say ratification, but in a way, that seems to be the norm. Whether you come into a market and you have specialization, but the data is there so apps can be more agile. Are you guys seeing that? And is that something that you guys are considering from an organization standpoint? And how do customers think about targeting vertical industries and their customers? >> Yeah, I bring this to... And where you started going there at the end of the question is exactly the way that we think about it as well. Which is we've moved from, "Here are storage offers for everybody, "and here's basic infrastructure for everybody." And now we've said, "How can we make sure "that we have solutions that are tailored "to the very specific problems that customers "are trying to solve?" And we're getting to the point now where performance and variety of technologies are available to be able to impose very specific solutions. And if you think about the substrate that has to be there, we mentioned you have to have some really great partners, and you have to have a roadmap that is focused on priority solution. So for example, at Google Cloud, we're very focused on six priority vertical areas. So retail, financial services, healthcare, manufacturing and industrials, healthcare life sciences, public sector. And as a result of being very focused in those areas, we can make more targeted investments and also align our entire go-to market system and our entire partner ecosystem... Excuse me, ecosystem around those bare specific priority areas. So for example, we work with CETA and HDA Healthcare very recently to develop and maintain a national response portal for COVID-19. And that's to help better inform communities and hospitals. We can use Looker to help with like a Commonwealth Care Alliance nonprofit and that helps monitor patient symptoms and risk factors. So we're using a very specific focus in healthcare and a partner ecosystem to develop very tailored solutions. You can also look at... I mentioned Shopify earlier. That's another great example of how in retail, they can use something like Google Meet, inherent reliability, scalability, security, to connect their employees during these interesting times. But then they can also use GCP, Google Cloud Platform to scale out. And as they come up with new apps and experiences for their shoppers, for their shops, they can rapidly deploy, to your point. And those solutions and how the database performs and how those tiers perform, that's a very tight-knit feedback loop with our engineering teams. >> Yeah, one of the things I'm seeing obviously with the virtualization of the COVID is that when the world gets back to normal, it'll be a hybrid. And it'll be a hybrid between reality, not physical and a hundred percent virtual, hybrid. And that's going to impact events too, media, to everything. Every vertical will be impacted. And I want to point out the Splunk deal and bring that back in because I want you to comment on the relevance of the Splunk deal in context to Splunk has a cloud. And they've got a great slogan, "Data for everywhere." "Data to everywhere," I think it is. But theCUBE, we have a cloud. Every company will have a cloud scale. At some level, we'll progress to having some sort of cloud because they have data. How are you guys powering those clouds? Because I think the Splunk deal is interesting. Their partner, their stock price was up out on the news of the deal. Nice bump there for Splunk, shout out to those guys. But they're a data company and now they're cross-platform. But they're not Google, but they have a cloud. So you know what I'm saying? So they need to play in all the clouds, but they need infrastructure (laughs), they need support. So how do you guys talk to that customer that says, "Hey, the next pandemic that comes, "the next crisis that's going to cause some "either social disruption or workflow disruption "or supply chain disruption. "I need to be agile. "I need to have full cloud scale. "And so I need to talk to Google." What do you say to them? What's the pitch? And does the Splunk deal mirror some of those capabilities? Or tie that together for us, the Splunk deal and how it relates to how to proof themselves for the future. Sorry. >> For example, with the Splunk cloud deal, if you take a look at what Google is already really good at, data processing at scale, log analytics, and you take a look at what Splunk is doing with their events and security incident monitoring and the rest, it's a really great mashup because they see by platforming on Google Cloud, not only do they get highly performing infrastructure. But they also get the opportunity to leverage data tools, data analytics tools, machine learning and AI that can help them provide enhanced services. So not just about capacity going up and down through periods of demand, but also enhancing services and continuing to offer more value to their customers. And we see that as a really big trend. And this gets at something, John, a little bit bigger, which is kind of the two views of the world. And we talked about very tailored, focused solutions. Splunk is an example of taking a very methodical approach to a partnership, building a solution specifically with partners. And in this case, Splunk on the security event management side. But we're always going to provide our data processing platform, our infrastructure for companies across many different industries. And I think that addresses one part of the topic, which is, how do we make sure that in periods of demand rapidly changing, and this goes back to the foundational elements of infrastructure as a service and elasticity. We're going to provide a platform and infrastructure that can help companies move through periods of... It's hard to forecast, and/or demand may rise and fall in very interesting ways. But then there's going to be times where we... Because we're not necessarily a focused use case where it may just be generalized platform versus a focused solution. So for example, in the oil and gas industry, we don't develop custom AI, ML solutions that facilitate upstream extraction, for example. But what we do do is work with renewable energy companies to figure out how they might be able to leverage some of our AI machine learning algorithms from our own data centers to make their operations more efficient and to help those renewable energy companies learn from what we've learned building out what I consider to be a world leading renewable energy strategy and infrastructure. >> It's a classic enablement model where you're enabling your platform for your customers. Okay, so I've got to ask the question. I asked this to the Microsoft guys as well because Amazon has their own SaaS stuff. But really more of end to end. The better product's usually on the ecosystem side. You guys have some killer SaaS. G Suite, we're a customer. We use the G Suite really deeply. We also use some Bigtable as well. I want to build a cloud, we have a cloud, CUBE cloud. But you guys have Meet. So I want to build my product on Google Cloud. How do I know you're not going to compete with me? Do you guys have those conversations around the trade-off between the pure Google services, which provide great value for the areas where the ecosystem needs to develop those new areas that are going to be great markets, potentially huge markets that are out there. >> Well, this is the power of partnership. I mentioned earlier that one of the really big moves that Thomas has made has been developing a sense of partners. And it kind of blurs the line between traditional, what you would call a customer and what you would call a partner. And so having a really strong sense of which industries we're in, which we prioritize, plus having a really strong sense of where we want to add value and where our customers and partners want to add that value. That's the foundational, that's the beginning of that conversation that you just mentioned. And it's important that we have an ability to engage not just in a, "Here's the cloud infrastructure piece of the puzzle." But one of the things Thomas has also done and a key strategy of his has been to make sure that the Google Cloud relationship is also a way to access all amazing innovation happening across all of Google. And also help bring a strategic conversation in that includes multiple properties from across Google so that an HSBC and Google and have a conversation about how to move forward together that is comprehensive rather than having to wonder and have that uncertainty sit behind the projects that we're trying to get out and have high velocity on because they offer so much to retail bank, for example. >> Well, I've got a couple more questions and then I'll let you go. I know you got some other things going on. I really appreciate you taking the time, sharing this great insight and updates. As a builder, you've been on the other side of the table. Now you're at Google heading up the CTO. Also working with Thomas, understanding the go-to market across the board and the product mix. As you talk to customers and they're thinking... The good customers are thinking, "Hey, "I want to come out of this COVID on an upward trajectory "and I want to use this opportunity "to reset and realign for the future." What advice do you have for those enterprises? They could be small, medium-sized enterprises to the full large big guys. And obviously, cloud-native, we've talked some of that already, but what advice would you have for them as they start to really prioritize, as some things are now exposed? The collaboration, the tooling, the scale, all these things are out there. What have you seen and what advice would you give a CXO or CSO or a leader in the industry to think about and how they should come out of this thing, how they should plan, execute, and move forward? >> Well, I appreciate the question because this is the crux of most of my day job, which is interacting with the C-suite and boards of companies and partners around the world. And they're obviously very interested to learn or get a data point from someone at Google. And the advice generally goes in a couple of different directions. One, collaboration is part of the secret sauce that makes Google what it is. And I think you're seeing this right now across every industry, and whether you're a small, medium-sized business or you're a large company, the ability to connect people with each other to collaborate in very meaningful ways, to share information rapidly, to do it securely with high reliability, that's the foundation that enables all of the projects that you might choose to... Applications to build, services to enable, to actually succeed in production and over the long haul. Is that culture of innovation and collaboration. So absolutely number one is having a really strong sense of what they want to achieve from a cultural perspective and collaboration perspective and the people because that's the thing that fuels everything else. Second piece of advice, especially in these times where there's so much uncertainty, is where can you buy down uncertainty with...? You can learn without a high penalty. This is why cloud I think is really, really finding super scale. It was already on the rise, but what you're seeing now as you've laid back to me during this conversation, we're seeing the same thing, which is a high increase in demand of, "Let's get this implemented now. "How can we do this more? "This is clearly one way to move through uncertainty." And so look for those opportunities. I'll give you a really good example. Mainframes, (chuckles) one of the classic workloads of the on-premise enterprise. There are all sorts of potential magic solves for getting mainframes to the cloud and getting out of mainframes. But a practical consideration might be maybe you just front-end it with some Java. Or maybe you just get closer to other data centers within a certain amount of milliseconds that's required to have a performant workload. Maybe you start chunking at art and treat the workload a little bit differently rather than just one thing. But there are a lot of years and investments in our workload that might run on a mainframe. And that's a perfect example of how biting off too much might be a little bit dangerous, but there is a path to... So for example, we brought in a company called Cornerstone to help with those migrations. But we also have partnerships with data center providers and others globally plus our own built infrastructure to allow even a smaller step per se for more close proximity location of the workload. >> It's great. Everything kind of has a technical metaphor connection these days when you have a internet, digitally connected world. We're living in the notion of a digital business, was a research buzzword that's been kicked around for years. But I think now COVID-19, you're seeing the virtual or digital, it's really digital, but virtual reality, augmented reality is going to come fast too. Really get people to go, "Wow. "Virtualization of my business." So we've been kind of kicking around this term business virtualization just almost as a joke, but it's really more about, okay, this is about a new world, new opportunity to think about when we come out of this, we're going to still go back to our physical world. Now, the hybrid now kicks in. This kind of connects all aspects of business in every vertical. It's not like, "Hey, I'm targeting this industry." So there might be unique solutions in those industries, but now the world is virtualized. It's connected, it's a digital environment. These are huge concepts that I think has kind of been a lunatic fringe idea, but now it's brought mainstream. This is going to be a huge tailwind for you guys as well as developers and entrepreneurs and application software. This is going to be, we think, a big thing. What's your reaction to that? Based on your experience, what do you see happening? Do you agree with it? And do you have anything you might want to add to that? >> Maybe one kind of philosophical statement and then one more... I bruised my shins a lot in this world and maybe share some of the black and blue coloration. First from a philosophical standpoint, the greater the crisis, the more open-minded people become and the more creative people get. And so I'm really excited about the creativity that I'm seeing with all of the customers that I work with directly, plus our partners, Googlers. Everybody is rallying together to think about this world differently. So to your point, a shift in mindset, there are very few moments where you get this pronounced change and everyone is going through it all at the same time. So that creates an opportunity, a scenario where you're bold thinking new strategies, creativity. Bringing people in in new ways, collaborating in new ways and offer a lot of benefits. More practically speaking and from my experience, building technology for a couple decades, it has an interesting parallel to building tightly coupled, really large maybe monoliths versus microservices and the debate around, "Do we build small things "that can be reconfigured and built out by others "or built upon by others more easily? "Or do we create a golden path and a more understood development environment?" And I'm not here to answer the question of which one's better because that's still a raging debate. But I can tell you that the process of going through and taking a service or an application or a thing that we want to deliver to a customer, that one of our customers wants to deliver to their customer. And thinking about it so comprehensively that you're able to think about it in, what are its core functions? And then thinking methodically about how to enable those core functions. That's a real opportunity, and I think technology to your point is getting to the place where if you want to run across multiple clouds, this is the Anthos conversation were recently GA'ed. Global scale platform, multicloud platform, that's a pretty big moment in technology. And that opens up the aperture to think differently about architectures and that process of taking an application service and making it real. >> Well, I think you're right on the money. I think philosophically, it's a flashpoints opportunity. I think that's going to prove to be accelerating and to see people win faster and lose faster. You're going to to see that quickly happen. But to your point about the monolith versus service or decoupled based systems, I think we now live in a world where it's a systems view now. You can have a monolith combined with decoupled systems. That's distributed computing. I think this is the trend, it's a system. It's not one thing or the other. So I think the debate will continue just like VI versus Emacs (chuckles). We don't know, right? People are going to have the debate, but if you think about it as a system, the use case defines your architecture. That's the beautiful thing about the cloud. So great insight, I really appreciate it. And how's everything going over there at Google Cloud? You've got Meet that's available. How's your staff? What's it like inside the Googleplex and the Google Cloud team? Tell us what's going on over there. People still working, working remote? How's everyone doing? >> Well, as you can tell from my scenario here, my backdrop, yes, still part at work. And we take this as a huge responsibility. These moments as a huge responsibility because there are educators, loved ones, medical professionals, critical life services that run on services that Google provides. And so I can tell you we're humbled by the opportunity to provide the backbone and the platform and the people and the curiosity and the sincere desire to help. And I mentioned a couple of ways already just in this conversation where we've been able to leverage some of our investments technology to help form people that really gets at the root of who we are. So while we just like any other humans are going through a process of understanding our new reality, what really fires us up and what really charges us up is because this is a moment where what we do really well is very, very important for the world in every geo, in every vertical, in every use case, in every solution type. We're taking that responsibility very seriously. And at the same time, we're trying to make sure that all of our teams as well as all of the teams that we work with and our customers and partners are making it through the human moment, not just the technology moment. >> Well, congratulations and thanks for spending the time. Great insight, Will. Appreciate, Will Grannis, managing director, head of technology office of the CTO at Google Cloud. This certainly brings to the mainstream what we've been in the industry been into for a long time, which is DevOps, large scale, role of data and technology. Now we think it's going to be even more acute around societal benefits. And thank God we have all those services for the frontline workers. So thank you so much for all that effort and thanks for spending the time here in theCUBE Conversation. Appreciate it. >> Thanks for having me, John. >> Okay, I'm John Furrier here in Palo Alto studios for remote CUBE Conversation with Google Cloud, getting the update. Really looking at the future as it unfolds. We are going to see this moment in time as an opportunity to move to the next level, cloud-native and change not only the tech industry but society. I'm John Furrier, thanks for watching. (upbeat music)

from the cube studios in Palo Alto in Boston connecting with thought leaders all around the world this is a cube conversation run welcome to this cube conversation I'm John Fourier with the cube host the cube here in our Palo Alto office for remote interviews during this time of covin 19 we're here with the quarantine crew here in our studio we got a great guest here from Google we'll Grannis managing director head of the office of the CTO with Google cloud thanks for coming on we'll appreciate you you spend some time with me Oh John's great to be with you and as you said in these times more important than ever to stay connected yeah and I'm really glad you came on because a couple things one congratulations to Google cloud for the success you guys had so a lot of big wins under your belt both on the momentum side on the business side but also on the technical side meat is available now for folks anthos is doing very very well partner ecosystem is developing got some nice used cases in vertical marker so I want to get in and unpack with you but really the bigger story here is that the world has seen the future before was ready for it and that is the at scale challenge that the Cova 19 has shown everyone we're seeing you know the future has been pulled forward we're living in a virtualized environment it's funny to say that virtualization has a server virtualization is a tech term but that enabled a lot of things we're living in a virtualized world now because we have to but this is gonna set in motion a series of new realities that you guys have been experiencing and supporting for many many years but now as a provider of Google cloud you guys have to operate at scale you have and now the whole world realizes that scale is a big deal and so you guys have had some successes I want to get your thoughts on the this at scale problem that the world now realizes I mean everyone's at home that's a disruption that was unfortunate whether it's under provisioning VPNs NIT to a surface area for security to just work and play and activities are now confined so people aren't convening anymore and it's a huge issue what's your take on all this well I mean to your point just now the fact that we can have this conversation we can have it blue idli from our respective remote locations just goes to show you the power of information technology that underlies so many of the things that we say and for Google Cloud this is not a new thing and for Google this is not a new thing for Google cloud we add a mission of trying to help companies accelerate their transformation and enable them in these new digital environments and so many companies that we've been working with they've already been on the path to operating an environments that are digital that are fluid and you think about the cloud that's one of the great benefits loud is that scalability income with the business demand and it also helps the scale situation without having to you know do the typical what you need to find the procurement people we need to find server vendors we need to get the storage lined up it really allows a much more fluid response to unexpected and unfortunate situations whether that's customer demand or you know in this case the global endemic yeah one of the things I want to get in with you I want to get you have explained your job is there because I see Google's got a new CEO now for over a year Tom's Korean came from Oracle knows the enterprise up and down you had Diane Greene before that again another enterprise leader Google Cloud has essentially rebuilt itself from the original Google cloud to be very enterprise centric you guys have great momentum and and this is a world where cloud native is going to be required I mean everyone now sees it the the tide has been pulled out there everything's exposed all the gaps in business from a tech standpoint it's kind of exposed and so the smart managers and companies are looking at things and saying double down on that let's kill that we don't want to pay that supplier they're not core to our business this is going to be a very rapid acceleration of what I call a vetting of the new the new set of players that are going to emerge because the folks who don't adapt to this new cloud native reality whether it's app workloads for banking to whatever they're gonna have to have to reinvent themselves now and reset and tweek to come out of this crisis so it's gonna be very cloud native this is a big deal can you share your your reaction to that absolutely and so as you pointed out there are kind of two worlds that exist right now companies that are moving to become more digital and transform and you mentioned the momentum I mean in Google cloud just over the last year greater than 50 percent revenue growth and you know and I greater than 10 billion dollar run rate business and adding customers that are really quick flip you know including you know just yesterday slung and you know along the way Telecom Italia Major League Baseball Vodafone Lowe's Wayfarer Activision Blizzard's so this is not you this transformation and this digitization is not just for you know a few or just for any one industry it's happening across the board and then you add that to the implementations that have been happening across you know Shopify and the Spotify and HSBC which was a early customer of ours in the cloud and it you know already has a little bit of a head start of this transformation so you see these new companies coming in and seeing the value of digital transformation and then these other companies that have kind of lit the path for others to consider and you know Shopify is a really good example of how seeing you know drastic uptick in demand they're able to responding you know roughly half a million shops up and running you know during a period of time where many retailers are trying to figure out how to stay online or you can get online well what is your role at Google I see you're the managing director title is managing director ahead of the office of the CTO we've seen these roles before you know head of this CTO you're off see technical role is it partnering with the CEO on strategy is it you kick tire kicking new things are you overseeing any strategic initiatives what is what is your role so a little bit of all those things combined into one so I I spent the first couple decades of my career on the other side of the in the non-tech you know community no in the enterprise where we were still building technology and we were still you know digitally minded but not the way that people view technology in Silicon Valley and so you know spending a couple decades in that environment really gave me insights into how to take technology and apply them to a specific problem and when I came to Google five years ago yeah selfishly it was because I knew the potential of Google's technology having been on the other side and I was really interested in forming a better bridge between Google's technology and people like me who were CTOs of public companies and really wanted the leverage that technology for problems that I was solving whether it was aerospace public sector manufacturing what-have-you and so it's been great it's the it's the role of a lifetime I've been able to build the team that I wanted as an enterprise technologist for decades and the entire span of technologies at our disposal and we do two things one is we help our most strategic customers accelerate their path loud and 2 we create these signals by working with the top companies moving to the cloud and digitally transforming we learned so much John about what we need to build as an organization so it also helps balance out the Google driven innovation with our customer driven innovation yeah and I could I can attest that we didn't watching you guys from the from day one hired a lot of great enterprise people that I personally know so you getting the enterprise chops and staff and getting you seeing some progress I have to ask you though because I first of all a big fan of Google at the scale from knowing them from when they were just a little search engine to what they are now the there was an expression a few years ago I heard from enterprise customers it was goes along the lines like this I want to be like Google because you guys had a great network you had large-scale you've had all these things that were like awesome and then they realized what we can't be like Google we don't have that sorry we don't have large-scale data centers so there was a little bit of a translation and I want to say a little bit of a overplay of the Google hand and you guys had since realized that you didn't it wasn't just people gonna bang your doorstep and be adopting Google cloud because there was a little bit of a cultural disconnect from wanting to be like Google then leveraging Google in their business as they transform so as you guys have moved from that what's changed they still want to be like Google in the sense you have great security got a great network you got that scale and it prizes a little bit slower to adopt that which you're focused on now what is that the story there because I think that's kind of the theme that I'm hearing okay Google now understands me they know I'm not as fast as Google they got super great people we are training our people we're treating you know retrain them this is the transformation that they're going through so you might be a little bit ahead of them certainly but now they need to level up how do you respond to that well a lot of this is the transformation that Thomas has been enacting you know over the last year plus and it comes in kind of three very operation or technical pillars that I think the first we expanded our customer and we continue to expand our customer facing themes you know three times what they were before because we need to be there we need to be in those situations we need to hear from the customer mean to learn more about the problems they're trying to solve so we don't just take a theoretical principle and try to overlay it onto a problem we actually get very visceral understanding of what trying to solve but you have to be there the game that empathy and that understanding and so one is showing up and that you know has been mobilizing a much larger engine the customer facing out personnel from Google second it's also been really important that we evolve our own you know just as Google brought sre principles and principles of distributed systems and software design out for the world we also had a little bit to learn about transitioning from typical customer support and moving to more customer experience so you've seen you know that evolution under on this as well with cloud changing you know moving from talking about support to talking about customer experience that white glove experience that our customers get our partners get from the beginning of their journey with us all the way through and then finally making sure that our product roadmap has the solutions that are relevant across be priority industries for us and you know that's again that only comes from being present from having a focus in those industry and then developing the solutions that progress those companies so again not this isn't about taking you know a principle and trying to apply it blindly this is about adding that connection that really deep connections to our customers and our partners and letting that connection manifest the things that we have to do as a product company the best support them over a long period some of these deals we've been announcing these are 10-year five-year multi-year strategic partnerships they go across the campus of you know all of you and you know those are the really exciting scaled partnerships but you know to your point you can't just take SR re from Google and apply it to company X but you can take things like error budgets or how we think about the principles of sree and you can apply them over the course of developing technology collaborating innovating together yeah and I think cloud native is gonna be a key thing and yeah I think what it's just my opinion but I think one of those situations where the better mousetrap will win if your cloud native and you have api's and you have the kind of services that people will will know beaded to your doorstep so I have to ask you with Thomas Korean on board obviously we've been following his career as well at Oracle he knows what he's doing comes in to Google it's being built out it's like a rocket ship at this point what bet is he making and what bet are you guys making on behalf of your customers what's the if you have to boil it down to Google clouds big bet what is the bet on the technology side and what's the bet on the business side sure well I've already mentioned you know I've already Internet's you know the big strategy that Thomas is brought in and you know that is the that's again those three pillars making sure that we show up and that we're present by having a scaled customer facing organization and making sure that we transitioned from you know a typical support mindset into more of customer experience mindset and then making sure that those solutions are tailored and available for our priority industries if I was to add you know more color to that I think one of the most important changes that Thomas has personally been driving as he's been converting us to a partner LED is and a partner led organization and this means a lot of investments in large mobile systems integrators like Accenture and Deloitte but this also means that like the Splunk announcement from yesterday that isn't just the cell >> this is a partnership it goes deep across go-to-market product and self do and then we also bring in very specific partners like Temenos in Europe for financial services or a SATA or a rack space for migrations and as a result the already we're seeing really incredible lifts so for example nearly 200 percent year-over-year increase in partner influenced revenue Google cloud and almost like a 13 X year-over-year increase in new customers one-bite partners that's the kind of engine that builds a real hyper scale does it's just saying you mentioned Splunk I want to get that in a second but I also notice there was a deal with Dallas group on ECM subscriptions which kind of leads me into the edge piece there's a real edge component here with Google cloud and I think I'd Akashi edge with Jennifer Lynn a few years ago really digging into the built-in security and the value of the Google Network I mean a lot of the scuttlebutt around the valley and the industry is you know Google's got an amazing network store a software-defined networking is gonna be a hot program programmable area so you got programmable networking and you got edge and edge security these are killer areas that need innovation could you comment on what you guys are doing there and do you agree I'm out see with you have a killer Network and you're leveraging it what's the can you just give some insight into what's going on those those two areas network and then the edge yeah I think what you're seeing is the manifestation of an of the progression of cloud generally what do I mean by that you know started out as like get everything to the data center you know we kind of had this thought that maybe we could take all the workloads and we could get them to these centralized hubs and they could redistribute out the results and you know drive the latency down over time so we span the portfolio of applications and services that would be relevant over time and what we've seen over the last decade really in cloud is an evolution >> more of a layered architecture and that layered architecture includes you know poor data centers that includes CDN capacity points of presence that includes edge and just in that list of customers over the last year I there were at least three or four telcos in there and you've also probably heard and seen quite a bit of telco momentum coming from asks in recent announcements I think that's an indication that a lot of us are thinking about how can we pick big technology like anthos for example and how could we orchestrate workloads create a common control play and you know manage services across those three shells if you will of the architecture and that's a that's a very strategic and important area for us and I think generally for the cloud industry easy it was expanding beyond the data center as the place where everything happens and you can look at you know Google Phi you look at stadia you can look at examples within Google they go well beyond cloud as to how we think about new ways to leverage that kind of creature all right so we saw some earnings come out on Amazon side as Google both groups and Microsoft well all three clouds are crushing it on the cloud side that's a tailwind I get that but as it continues we're expecting post kovat some you know redistribution of development dollars and projects whether it's IT going cloud native or whatever new workloads we are predicting a Cambrian explosion of new things from core to edge and this is gonna create some lift so I want to get your thoughts on you guys strategy with go-to market as well as your customers as they now have the ability to build workloads and apps with ai and data there seems to be a trend towards the vertical ization of whether its sales and go to market and/or specialism because you have horizontal scalability with cloud and you now have data that has distinct value in these verticals so it really seems to be a I won't say ratification but in a way that seems to be the norm whether you come into a market you have specialization but the date is there so apps can be more agile do you are you guys seeing that and is that something that you guys are considering from from an organization standpoint and how do customers think about targeting vertical industries and their customers yeah I I bring this to and where you started going there at the end of the question is exactly the way that we think about it as well which is we've moved from you know here are storage offers for everybody and here's you know basic infrastructure everybody and now we've said how can we make sure that we have solutions that are tailored with very specific problems that customers are trying to solve and we're getting to the point now where your performance and variety of technologies are available to be able to compose very specific solutions and if you think about the substrate that has to be there you know we mentioned you have to have some really great partners and you have to have you know roadmap that is focused on priority solution area so for example at Google cloud you know we're very focused on six priority vertical areas so retail financial services health care manufacturing and industrials health care life sciences public sector and you know as a result of being very focused in those areas we can make more target investments and also align our entire go-to-market system and our entire partner ecosystem ecosystem around those beers specific priority areas so for example we worked with SATA and HDA Healthcare Rob very recently to develop and maintain a national response portal Berko vat19 and that's to help better inform communities and hospitals we can use looker to help with like a Commonwealth Care Alliance on nonprofit and that helps monitor patient system symptoms and risk factors so you know we're using you know a very specific focus in healthcare and a partner ecosystem - you know ferry tailored solutions you know you can also look at I mentioned Shopify earlier that's another great example of how in retail they can use something like Google meat inherent reliability scalability security to connect their employees during these interesting times but then they can also use GCP at Google cloud platform to scale out and as they come up with new apps and experiences for their shoppers for their shops they can rapidly deploy to your point and those you know those solutions and you know how the database performs and how those tiers perform you that's a very tight-knit feedback loop with our engineering teams yeah one of the things I'm seeing obviously with the virtualization of the kovat is that you know when the world gets back to normal it'll be hybrid and it'll be a hybrid between reality not physical and 100% virtual hybrid and that's going to impact events to media to everything every vertical will be impacted and I want to point out the Splunk team bring that back in because I want you to comment on the relevance of the Splunk to you and in context to Splunk has a cloud they got a great slogan data for every everywhere everywhere dated to everywhere I think it is but the cube we have a cloud every company will have a cloud scale at some level will progress to having some sort of cloud because they have data how are you guys powering those clouds because I think the Splunk deal is interesting their partner their stock price was up out on the news of the deal a nice bump their first Blunk shout out to those guys but they're a data company now they're cross-platform but they're not Google but they have a cloud so you know saying so they need to play in all the clouds but they need infrastructure they need support so how do you guys talk to that customer and that says hey the next pandemic that comes the next crisis that's going to cause some either social disruption or workflow disruption or work supply chain disruption I need to be agile I need have full cloud scale and so I need to talk to Google what do you say to them what's the pitch and as does a Splunk deal Samir some of those capabilities or tie that together for us the spunk deal and how it relates to sure for example proof themselves for the future sorry for example with the cloud deal you take a look at what Google is already really good at data processing at scale log analytics you take a look at what Splunk is doing you know with their events and security incident monitoring and the rest it a really great mashup because they see by platforming on Google cloud not only they get highly performant infrastructure but they also get the opportunity to leverage data tools data analytics tools machine learning and AI that can help them provide enhance services so not just about acity going up and down your periods of band but also enhancing services and continuing to offer more value to their customers and we see that you know it's a really big trend and you know this gets it something you know John a little bit bigger which is the two views of the world and we talked about very tailored focused solutions Splunk is an example of making a very methodical approach to a partnership developing a solution specifically you know with partners and you know in this case Splunk on the security event management side but we're always going to provide our data processing platform our infrastructure for companies across many different industries and I think that addresses one part of the topic which is you know how do we make sure that in periods of demand rapidly changing this deals back to the foundational elements of like AI infrastructure as a service and elasticity and we're gonna provide a platform infrastructure that can help companies move through periods of you know it's hard to forecast and/or demand may rise and fall you know in very interesting ways but then there's going to be funds where you know we we because they're not a necessarily a focused use case where it may just be generalized platform versus a focused solution so for example like in the oil and gas industry we don't develop custom AI ml solutions the facility upstream extraction for example but what we do do is work with renewable energy companies to figure out how they might be able to leverage some of our AI machine learning algorithms from our own data centers to make their operations more efficient and to help those renewable energy companies learn from what we've learned building out the but I consider to be a world leading renewable energy strategy and so classic and able mint model where you're enabling your platform for your customers okay so I got to ask the question I asked this to the Microsoft guys as well because Amazon you know has their own sass stuff but but really more of an tend the better products usually on the ecosystem side you guys have some killer sass cheap tree-sweet where customer if we use the g sqweep really deeply we also use some BigTable as well I want to build a cloud we have a cloud cube cloud but you guys have meat so I want to build my product on Google cloud how do I know you're not going to compete with me do you guys have those conversations around the trade-off between you know the pure Google services which provide great value for the areas where the ecosystem needs to develop those new areas that are gonna be great markets potentially huge markets that are out there well this is the power of partnership I mentioned earlier that one of the really big moves that Thomas is made has been developing a sense of partners and it kind of blurs the line between traditional what you would call a customer what you would call a partner and so having a really strong sense of which industries were in which we prioritize Plus having a really strong sense of where we want to add value and where you know our customers and partners want to add that value that's that's the foundational that's the beginning of that conversation that you just mentioned it's important that we have an ability to engage not just in a you know here's the cloud infrastructure piece of the puzzle but one of the things Thomas has also done in the East rata jia is has been to make sure that you know the Google cloud relationship is also a way to access all amazing innovation happening across all of Google and also help bring a strategic conversation in that includes multiple properties from across Google so that an HSBC and Google and have a conversation about how to move forward together that is comprehensive rather than you know having to wonder and have that uncertainty sit behind the projects that we're trying to get out and have high velocity on because they offer so much to retail bank for example well I got a couple more questions and then I'll let you go I know you got some other things going I really appreciate you digging the time sharing this great insight and updates as a builder you've been on the other side of the table now you're at Google heading up the CTO I was working with Thomas understanding them go to market across the board and the product mix as you talk to customers and they're thinking the good customers are thinking hey you know I want to come out of this Cove in on an upward trajectory and I want to use this opportunity to reset and realign for the future what advice do you have for those enterprises there could be small medium sized enterprises to the full large big guys and obviously cloud native we talked some of that already but what advice would you have for them as they start to really prioritize as some things are now exposed the collaboration the tooling the scale all these things are out there what have you seen and what advice would you give a CX o or C so or leader in the industry to think about and how they should come out of this thing how they should plan execute and move forward well I appreciate the question because this is the crux of most of my day job which is interacting with the c-suite and boards of you know companies and partners around the world and they're obviously very interested to learn or you know get a data point from someone at Google and the the advice generally goes in a couple of different directions out one collaboration is part of the secret sauce that makes Google what it is and I think you're seeing this right now across every industry and it you know whether you're a small medium-sized business or you're a large company if the ability to connect people with each other to collaborate in very meaningful ways to share information rapidly to do it securely with high reliability that that's the foundation that enables all of the projects that you might choose to you know applications to build services to enable actually succeed in production and over the long haul is that culture of innovation and collaboration so absolutely number one is you're having a really strong sense of what they want to achieve from a cultural perspective a collaboration perspective and the and the people because that's the thing that fuels everything else second piece of the you know advice especially in these times where there's so much uncertainty is where can you buy down uncertainty with vets that aren't you know that art you can you can learn without a high penalty and this is a this is why cloud I think is really really you know finding you know super scale it was our it was already on the rise but what you're seeing now and you know as you've linked back to me during this conversation we're seeing the same thing which is a high increase in demand of let's get this implemented now how can we do this more this is you know clearly one way to move through uncertainty and so look for those opportunities I'll give you a really good example mainframes one of the classic workloads of the you know on-premise enterprise and you know there's all sorts of there are all sorts of potential magic solves for getting mainframes to the cloud and getting out of mainframes but a practical consideration might be maybe you just front-end it with some Java or maybe you just get closer to other data centers within a certain amount of milliseconds that's required to have performant workload maybe you start chunking at a part and treat the workload a little bit differently rather than you know just one thing but there are a lot of years and investments in a workload that might run on a mainframe and that's a perfect example of out you know biting off too much it might be a little bit dangerous but there is a path to and so for example like we brought in a company called cornerstone to help with those migrations but we also have you know partnerships with you know data center providers and others globally from us our own built infrastructure to allow even you know a smaller stuff per site or more like post proximity location in the workload it's great you know everything had as a technical metaphor connection these days when you have a Internet digitally connected world we're living in you know the notion of a digital business was a research buzzword that's been kicked around for years but I think now kovat 19 you're seeing the virtual or digital it's really digital but you know virtual reality augmented reality is going to come fast to really get people to go WOW virtual virtualization of my business so you know we've been kind of kicking around this term business virtualization just almost as a joke but it's really more about okay this is about a new world a new opportunity to think about when we come out of this we're gonna still go back to our physical world now the hybrid now kicks in this kind of connects all aspects of business in every verticals not leahey I'm targeting like the this industry so there might be unique solutions in those industries but now the world is virtualized it's connected it's a digital environment these are huge concepts that I think has kind of been a fringe lunatic fringe idea but now it's brought mainstream this is gonna be a huge tailwind for you guys as well as developers and entrepreneurs and app application software this is gonna be we think a big thing what's your reaction to that which your based on your experience what do you see happening do you agree with it and you have any thing you might want to add maybe you know one kind of philosophical statement and then one more you know I bruised my shins a lot in this world and maybe share some of the black and blue coloration first from a philosophical standpoint the greater the crisis the more open-minded people become and the more creative people get and so I'm really excited about the creativity that I'm seeing you know with all of the customers that I work with directly plus our partners you know Googlers everybody's rallying together to think about this world differently and so to your point you know a shift in mindset you know there are there are very few moments where you get this pronounced a change and everyone is going through it all at the same time so that creates a you know an opportunity a scenario where the old thinking new strategies creativity you know bringing people in in new ways collaborating a new way and offer a lot of benefits more you know practically speaking and from my experience you know building technology for a couple decades you this is a it has an interesting parallel to you know building like tightly coupled really large maybe monoliths versus micro services and debate around you know do we build small things that can be reconfigured and you know built out by others or built on by others more easily or do we credit Golden Path and a more understood you know development environment and I'm not here to answer the question of which one's better is that's what's still a raging debate and I can tell you that the process of going through and taking a service or an application or a thing that we want to deliver the customer that one of our customers wants to deliver to their cost and thinking about it so comprehensively that you're able to think about it in its what its power its core functions and then thinking methodically about how to enable those core functions that is a you know that's a real opportunity and I think technology to your point is getting to the place where you know if you want to run across multiple clouds yeah this is the anthos conversation where you know recently g8 you know a global scale platform you know multi cloud platform that's a pretty big moment in technology and that opens up the aperture to think differently about architectures and that process of taking you know an application service and making it real well I think you're right on the money I think philosophically it's a flashpoints opportunity I think that's going to prove to be accelerating gonna see people win faster and lose faster you can see that quickly happen but to your point about the monolith versus you know service or decoupled based systems I think we allow a live in a world where it's a systems of you now you can have a monolith combined with decoupled systems that's distributed computing I think this is that the trend it's a system it's not one thing or the other so I think the debate will continue just like you know VI versus Emacs we know you don't know right so you know if people gonna have this debate but it's just if you think about as a system the use case defines the architecture that's the beautiful thing about the cloud so great insight I really appreciate it and how's everything going over there Google Cloud you got meat that's available how's your staff what's it like inside the Googleplex and the Google cloud team tell us what's going on over there people still working working remote how's everyone doing well as you can as you can tell from my scenario here my my backdrop yes still hard at work and we take this as a huge responsibility you know these moments is a huge responsibility because there are you know educators loved ones medical professionals you know critical life services that run on services that Google provides and so I can tell you were humbled by the opportunity to provide you know the backbone and the platform and the people and the curiosity and the sincere desire to help and I mentioned a couple of ways already just in this conversation where we've been able to leverage some of our investment in technology to help or people that really gets at the root of who we are so while we just like any other humans are going through a process of understanding our new reality what really fires us up and what really a chart is because is that this is a moment where what we do really well is very very important for the world in every geo in every vertical in every use case and every solution type so we're just take we're taking that responsibility very seriously and at the same time we're trying to make sure that you know all of our teams as well as all the teams that we work with our customers and partners are making it a human moment not just the technology moment well congratulations and thanks for spending the time great insight will appreciate will Grannis Managing Director head of Technology office of the CTO at Google cloud this certainly brings to the mainstream what we've been in the industry been into for a long time which is DevOps large-scale role of data and technology now we think it's going to be even more acute around societal benefits and thank God we have all those services for the frontline workers so thank you so much for all that way effort and thanks for spending the time here in the cube conversation appreciate it thanks for having John okay I'm John Farah here in Palo Alto Studios for remote cube conversation with Google cloud get in the update really looking at the future as it unfolds we are going to see this moment in time as an opportunity to move to the next level cloud native and change not only the tech industry but society I'm John Fourier thanks for watching

(upbeat music) >> Narrator: Live, from San Francisco, it's theCUBE. Covering Google Cloud Next '19. Brought to you by Google Cloud and its ecosystem partners. >> Hey, welcome back everyone. Live coverage here with theCUBE in San Francisco, California, Moscone South. I'm John Furrier with Dave Vellante. Here at Google Next 2019 we have here in theCUBE for the first time as a Google employee, Cube alumni, Amit Zavery. Head of platform for Google Cloud. Great to see you. >> No, thanks for having me. It's always a pleasure to see you guys again. >> So you're just now on the job, not even two months. 25 years, 23? >> Amit: Close to 25, yes. >> Three years at Oracle. TK's over here as CEO, part of Google. They got a lot of action going on here. >> Oh definitely, it's very exciting times. I've spent some time kind of learning and hearing about what the vision at Google has been and it's very clear they're here to win it and we have the investment that they're making, the innovation which is going on is very attractive and very exciting, I think. >> Always love our conversations in the past in theCUBE around platform You got a deep technical background. Um you've been in the business. You've seen many waves of innovation up and down the stack. So it's not, I don't think there is a move you haven't seen in the business. But Cloud, there's some new things happening, it's going to, but it's all part of other things, kind of meshing together. Pun intended, service meshes. >> Yeah. >> But as customers move to the cloud from on prem, having cloud, multiple clouds, multiple dimensions of change. >> Yes. What's your take on this because, I think, you have a unique perspective in that 20 something years at Oracle, leader in databases and software? >> Yeah. >> Google's got great leadership in tech. >> Yep. >> But now they're standing up a whole new cloud business, at a whole 'nother level. Your thoughts? >> Yeah, yeah, I think if you look at what's going on and I talk to a lot of customers and developers and IT teams and clearly, I think, they are overwhelmed with different things, you said, going on in this space, so how do you make it simple? How do you make it open? How do you make it hybrid so you have flexibility of choices? It's becoming top of the mind for many of the users nowadays. The lock-in, which many vendors currently provide, becomes very difficult for many of this uh users who kind of keep moving around and meet the business requirements. So I think having a solution and a technology stack, which is really understanding the complexity around that and making it simple enough to adopt, I think is important. >> You know, one of these things, we watch these key notes very carefully. Especially when you have a new CEO, Thomas Kurian. We follow NetApp as well as his twin brother. But his first opening line was a little you know, tip of the cap to Diane Greene, which I thought was very classy. We hear all the other things. Scale, the multi-cloud piece. And then Jennifer Lynn gave a great demo, and she said something in her demo I want to get your reaction to. What are the business benefits of Anthos' negotiating contracts? Meaning choice. >> Yes. So lock-in's shifting. This means lock-in is not your grandfather's lock-in. You know, you worked at Oracle which has an amazing lock-in spec in databases. This is a whole new world, it's capabilities, the new lock-in. Or what is the new, I mean I guess lock-in is a function of-- >> Amit: No I mean, (mumbles) Again, it's not ideas. Lock-in is definitely not the right way of kind of looking at it. The way to kind of really make sure you attract users and attract customers, is to really make a value add capabilities in there. Right and then if the customers really love it they're going to keep on using it. In respective you call it lock-in or provide some propriotariness or not. >> Value. >> Right. Value is complete, exactly. I think it's important to really think about how you build some of the services and technologies which give this value. But also give you the choice of moving if you want to. That I think, if you start from the beginning that there's no choice, then the value doesn't come out, ever. >> John: So value's the new lock-in. >> It has to be, it has to be. >> Alright, talk about apogee. because you're one of the key piece of the platform is apogee. Talk about your focus, you're still learning, getting your feet wet. But again, you've got your running shoes on, you're experienced. What is that platform that you're handling. Give a quick description. >> Apogee, an acquisition, which Google made a few years ago. And I think it's a kind of center spaced offering which allows customers to really do the life cycle and digital transformation of the technology they have in the back end. Right and uh the apogee team has done a great job of keeping, being the market leader and keeping innovating. I think the next phase for us as we look forward is one is to make it very completely integrated and make it very seamless with all the rest of Google properties we have and the assets we have and second thing is to really add other capabilities around it so that customers depending on what they want to do like line of business or IT steams to be able to now unlock a lot of the application data they have and expose it to both the customer, spotners, as well as internal employees in a simple easy manner. So a lot of wantization can happen, monitoring, all these things can be really great for them. >> John: So there's a lot of head room in apogee. >> Very very much yes. >> By technology and business benefit. >> Dave: So head of platform. You know we in the industry we hear platform and we kind of understand what it's all about. People outside the industry maybe, some of an inmorphis concept to them. So my first question though before we get into this, what attracted you to Google? >> No I think that basically if I look at the strength Google brings as a organization, be it in terms of innovation, be it in terms of investment, the infrastructure and the willingness to invest in the long term. I think that is really really attractive. I think for me to kind of have the ability to kind of invest and grow a lot of the footprint we have to offer to a customer and solve the business problems in a little more longer term than short term oriented, I think is very very exciting. >> So let's talk more about platforms. You think of platforms as a set of capabilities steeped in sort of an architectural premise, there's maybe some dog mutt in there that you've got have have these capabilities then ultimately you're going to deliver value and turn into products and customer value. What is platform to you and what's that sort of how should we think about that fly wheel effect? >> Yeah in the way that I look at the platform is basically one is capabilities the customer require, one to build an application, integrate it, and be able to secure it and manage it right? So all the different capabilities you'd acquire instead of having to get piece meal of it and have to tie it all together yourself, you can now do it with a much easier fashion and one that provides you the capability as one integrated capability right? So that's really what I think of the platform. >> So your constituencies are obviously your internal developers, your external developers. Who are you serving with that platform? >> A few audiences. No doubt to others to be able to build an application. But I think the bigger audience if you go beyond that is really, apps IT and a line of business. So to them more and more line of business at doing extension to an application. The doing integration without having the right code. And if you can provide a powerful tool where any person who is not a professional developer can do that kind of tasks and get more power out of the application of the business systems they're running, the value is immense. And that's really I think the audience we need to be able to attract and be able to now cater to so that they have a lot more benefits from using the Google platform. >> Is that part technical capability, part you know, go to market? How do you view that? >> It's definitely a lot of work to be done from the product perspective to make it simple um make it more consumable by apps IT and line of business user where such professional developers but also in terms of how you design it and make it self service and attractive enough for an audience who is not really kind of having to do deal with a lot of this themselves. >> Okay so that's presumably what we should be expecting from you. Maybe talk about your priorities and give us a little you know, how should we be, sort of, judging you down the road, judging you not the right term but what milestones should we be looking for? >> A little too early, I mean this is four weeks at Google but I think uh, the way to look at this is are we basically catering to all the new requirements you see from a lot of the next generation users and I think uh, the ability for us to kind of expand that capability in a platform offering so it's not just catering to one kind of an audience but also new buyers which we seeing as users coming into the platform. So over the next six months or nine months we start seeing some of those things which you do. >> Is this a new role? Was it sort of by committee before or? >> No I think Google has been doing a lot of these things I think when you start to think about a rationalized skew of the areas and how do you keep on expanding. There's a lot of headroom for Google cloud to go and we continue to kind of look at where we need to be and how we can keep on expanding and meet those requirements. >> Amit talk about Thomas Kurian also known as TK onstage. He's been busy, he's going to come on the queue eventually. He's talking to a lot of customers we heard. Hundreds of customers been promoted. You worked in that oracle, what's he like? Share some color commentary on TK, he set the chops obviously in enterprise. What's he like? People, he's new CEO. >> Yeah, yeah I've worked with Thomas for 18 plus years and I think he's probably one of the smartest person I've worked with for sure. But I think it's very strategic vision and clear execution. I think combination is rare for a lot of people. We have a very clear vision but how do you execute and get operationally make those things possible? I think that really what Thomas brings to any any place he gets into. Right so he has a very clear idea where we should be going, he talks to a lot of customers, get you all the input and has a clear plan in terms of how we deli, what we should be doing. And then he gets very involved wit the execution operational work we should be doing right? So that is the unique thing to bring to the table. >> John: He can get down and dirty if you want him to do it. >> Yeah oh very much, yes yes. (laughs) He's fun to work with in that way. >> So I want to ask you a personal question I know we've been following your career, certainly you got a great, great technical background as well. As you look at the cloud, and having all that enterprise experience, you see many ways in innovation, hardware, software, evolution to the cloud. As you look at the modern enterprise, you mentioned IT apps, apps IT, it's a whole new app revolution renaissance happening. You got hybrid and multi cloud. What does it mean to be enterprise ready? If you could take all the learnings in your career, as you look at the new, you know, out in the new pasture, of the next ten years plus, you see changes happening, what's your vision? >> I think that enterprise ready for us, I mean I think that's what we are doing a lot, if you saw today from Thomas' announcements, there's a lot of things we are planning and we have been doing already and we need to do as well. But I think it's understanding the existing landscape of a customer. And enterprise, let's use them on and invest on many customers we've made and systems you can't rip and replace instantly. And to be able to understand how you operate in that kind of constrains as well as context is very important when you build new generational applications. So kind of having the connectivity and the tissue of kind of making it all work together, while you kind of modernize and digitally transform your offering, I think is a critical way of thinking. And I think that's what you'll start seeing a lot more of that from the product planning, product delivery perspective and understanding that yet many customers have to pay before they can move everywhere right? So you saw today with Thomas' announcement about hybrid which allows you to kind of inter operate with existing investments. Multicloud because you might be running into multiple environments. As well as you saw some the things we doing to really make it easy and simple to integrate with the existing portfolio that customers have. >> You know what's interesting is that you know, he also mentioned industries, which you guys at Oracle certainly you know every industry's got unique requirements. What's interesting and kind of validates on a queue we've, Dave and I have talked for years that the clouds horizontally scalable yet with data and AI you can be differentiated in the industry level so you can actually have best of both worlds now. That's what I see kind of coming together at the platform 'cause you have to have a platform that enables. How do you see that? Do you agree with that? Do you see that shaping out? How would you see that ability to take advantage of the horizontal scale, the ability, connective tissue, plus enabling this horizontal specialization for industry solutions? >> Yeah, no I think you saw again some of the announcements around that, with how do you make it not pertinent to a particular end user. Alright each industry has specific data models, specific use cases and you need to be able to provide and cater to that. So you have to have a horizontal platform which can cater to multiple, different things you want to do. But then you'd have to provide the main specific content and that's when you'll start seeing as you think that Oracle does some of the things that other companies do that and we will do some of that stuff as well. >> Well that's interesting point because you're in a point of a horizontal scaling because it creates this, uh, another disruption agenda. Yeah you can disrupts search and productivity software but you can also triverse industries with your partners. We were talking about apogee before with the API economy. You can see Google and its partners getting the healthcare, financial services, autonomist vehicles, I mean virtually every industry because it's data and that to me is the exciting part of platform. >> Oh no doubt. I think Google also brings a lot strength in terms of the modeling and the AI work they've been doing for many years and that can really exhilarate capabilities around these things in a much more easier way than it could be otherwise. >> And you kind of have a clean sheet of paper in the enterprise >> That's right. >> Amit great to see you, I'm glad we can get your first public appearance at Google here in theCUBE. Appreciate the commentary, I want to finally, final question is, personal question. If you were a cloud architect for a large enterprise that had complex to simple work loads and everything in between, what would you be doing in advising and setting up and architecting, what would you, what would you do? >> I think that the best thing to do I think is to identify different categories of applications. I don't think it's one thing fits all right? So define what are the categories of applications you have. Some of them are cloud ready and make sure that you can, status are ready and adoption and moving to more agile delivery model. Second on the application which you might want to now start thinking about rewriting and then having a road map associated with that so you're not trying to go and rip and replace because that has an impact on your business and capabilities right? And then third thing we might want to look at retiring some of the staff and then hey you have to modernize, I mean there's nothing, there's no way out of it. Just like software goes through cycles of innovation and changes every ten years you see a new stack of technologies come out and you have to remain competitive by adopting some of the states. So I think that's kind of in recognizing what you have and how you adopt is probably the number one thing. >> And you'll be probably driving containers throughout >> No doubt, I think the technologies out there now with the containerization, much much simpler to kind of go and run and write one's, run anywhere kind of thing. >> Those scenarios is kind of what the guy from Kohl's was saying today in the key note >> Yeah they're very similar yeah. >> He didn't say this, this one use case of just leave it there which was interesting to me. So, do nothing was not his strategy. It is, it is for some. >> Amit Zavery here on theCUBE. Great, great insight, thanks for sharing. Thanks for taking the time out of your busy schedule. Amit Zavery head of platform at Google Cloud here on theCUBE. I'm John Furrier. See us with more day one coverage. We're here for three days. Live, we'll be right back after this short break. (upbeat music)

>> Announcer: Live from San Francisco, it's theCUBE. Covering Google Cloud Next '19. Brought to you by Google Cloud and its ecosystem partners. >> Hey welcome back everyone. It's theCUBE's live coverage here in San Francisco in Moscone South. We're on the ground floor here at Google Next, Google's Cloud conference. I'm chatting with Stu Miniman; Dave Vellante's also hosting. He's out there getting stories. Our next two guests: Dana Berg, Chief Operating Officer of SADA and Chris Lehman, Head of Engineering for SADA. Guys, welcome to theCUBE. Thanks for joining us. We're here on the ground floor. >> Thank you. >> Thank you. >> This is exciting. I feel like a movie star right here. >> It's game day here. All the tech athletes are out, Dave. If you look at the show, look at the demographics, hardcore developers, lot of IT, leaders also here, cloud architects, a lot of people trying to figure it out. We heard the keynote. Google is bringing a lot to the table. So what's new with you guys? You guys recently sold your Microsoft business, going all-in on Google. Talk about that relationship. >> We are. This is a brand new day for SADA. The energy around this place, where we are in the market, and where we are with the expanded attendance here has actually reaffirmed our business strategy to go all-in with Google. I don't know if you are aware but SADA has been around for almost 20 years. Historically have always been leaders in bringing people to the cloud even before there was really much of a cloud. We were a you know a pilot partner within Microsoft and Google and had a great thriving Microsoft business but an even bigger Google business and you know, we looked at the tea leaves, we looked at where we wanted to be, and aligned with a company that shared our mission and values and it was a clear choice. We chose Google. We made a very specific and deliberate act to sell off our Microsoft business so that we could take the horsepower of all of our engineering staff and apply them to Google. >> It's interesting you know, we've been around for 10 years doing theCUBE, go to a lot of events, I mean Dave Vellante, Stu, and I have been around for 30 years covering the IT, you guys 20 years. You guys have seen many ways of innovation come and go. Now you're going all in on Google. What is it about this wave right now that made that decision? What do you guys see? You're seeing something early here. Expand on that. Give us some color commentary because there's a wave here, right? A lot of people try. It's a combination of things. I mean, we saw the client-server thing. We saw that movement. Also the internet, we saw the web, mobile, now it's cloud. What's the big wave? What are you guys riding? >> I think there's a couple of things and I think it's unique to, philosophically, how we think of our real special relationship with Google. There is a momentum, right, and not to quote like a Bernie Sanders, but, seems like there's a revolution going on here, right, and, you know, I think, you know, what we see when we look around and we hear conversations and even with our customers, the way that we're all winning together is because we're winning the hearts and minds of the people inside of our customer base that are actually the ones responsible for inventing and the ones responsible for building, so when we're in board rooms and we're selling and along with Google, we're talking with developers, we're talking with designers, we're talking about people that are actually driving the vision for these business applications. We're not always talking to the CIO down like some of our other competitors seems to have only been able to sell that way. We're talking about the people responsible for not only constructing it but maintaining it. So that revolution is there. These folks are bubbling that up and they're seeing the real value inside of Google and what is that value from our point of view, and why did we make such a bold statement just to stick with Google is, and we saw Thomas today echo this, I think there's very few cloud providers that are bold enough to actually lead with the fact that we want our customers to have full choice whether you're using GCP or not. We want to build, architect, and manufacture a product offering that allows you to keep your stuff in your data centers, move your stuff to AWS. That power of choice is really not like what we've never heard anywhere else. >> And then on top of that, too, you got an application renaissance, right? A whole new way of coding, infrastructure that's programmable and going away, I mean if you think about what that does to the existing infrastructures, they can now mix and match and rearchitect everything from scratch and accelerate the app movement. >> Well, that's absolutely true, and a lot of that has to do with the fact that there are managed services in the cloud which makes it dramatically easier to build applications of course, so there's no question about that. Some of the offerings on GCP are particularly attractive for our clients, particularly the managed Kubernetes service. That's where we're seeing perhaps most of the interest that we're seeing, like that's a very common theme. Also the ML stack is an area that our customers are very interested in. >> Chris, can you bring us in some of those customer environments, you know, one of the things you hear, you know, most customers, it's, "I've got my application portfolio." Modernizing that is pretty challenging. There are some things that are kind of easy, some things that take a lot more work, but, you know, migration is one of those things that makes most people that have been in IT a while cringe because there's always the devil in the details and something goes wrong once you've got 95 percent done. What are you seeing, what's working, what's not working, how's the role of data changing, and all of that? >> I think migrations are usually more complex than they at first appear and so even with best intentions thinking that customers can just move their workloads seamlessly to the cloud have actually in practice been more challenging. So some of the areas that we find challenges are around data migration, especially in the context of zero downtime. That's always more difficult than with applications. So that's definitely an area that were we're spending a lot of time working with our customers to deliver. >> Just to add to that, I have to keep reminding myself of the name, but obviously the Anthos announcement today sounds incredibly intriguing as a lower barrier of effort to actually migrate. Our customers have been trying to really absorb and take a hold of Kubernetes and can it containerize methods for a long time. Some are having a harder time doing it than others. I think Anthos promises to make that endeavor much, much easier, and I think about as we leave here this week and we go back and we reeducate our own engineering teams as well as our customers, I think we might see some highly accelerated project timelines go from here down to here. >> And the demo that Jennifer Lynn did was pretty impressive. I mean, running inside of containers, whether it's VMs, and then having service patches on the horizon coming to the table is going to change the implementation delivery piece too in a massive way. I mean, you've got-- >> Oh, absolutely. >> Code, build, run on the cloud side, but this this kind of changes the equation on your end. Can you guys share the insight into that equation, because Google's clearly posturing to be partner friendly. You guys are a big partner now. You're going all-in. This is an interesting dynamic because you can focus on solving customers' problems. All this heavy lifting kind of goes away. Talk about the impact to you as a partner when you look at Anthem, Anthem migrate in particular, some of these migration challenges with containers and Kubernetes seems like it's a perfect storm right now to kind of jump in and do more, faster. >> Yeah. >> Well, it's certainly very interesting. Well, we'll want to take a really hard look at it. I mean, a very, very cool announcement. Moving to containers in the source prior to the migration obviously solves a lot of challenges so for that reason, it's definitely a move forward. >> And I think... You know, we always talk about, in this industry, the acceleration for consumption, but really that's a poor way of saying... Probably what we should be saying is an acceleration of value. So we're constantly in this battle to try and deliver value to our customers faster. That's what our customers want, right, and in essence we see Anthos as being potentially a big game-changer there so that, you know, our CIOs that we're talking with can show to their various stakeholders that they are making very good proactive moves into the cloud at lower-caught barriers of entry, right? >> Yeah. So, you brought up the the ML piece of Google. Wondering if you could help share a little bit on that. When I think back two years ago, you know, data was really at the core of what a lot of what Google was talking about. I was actually surprised not to hear a lot of it on the main stage this morning, but you know, AI, ML, what are you doing, what are your customers doing, does Google have leadership in the space? >> Google certainly has leadership in the space. Our customers, I think, relatively universally, think that their ML stack is the strongest among the competitors, but I think in practice what we're finding is there's a lot more urgency as far as just literal data migrations off of their data centers into the cloud, and I foresee a lot more AI and ML work as more move in. >> John: Yeah. >> So you might, in our booth here, not to give a plug, but we've got a booth down at the end with a full-fledged racing car, just to talk about the art of the possible with AI and ML. Our engineering teams in the race teams that we sponsor, they're there, the driver's there, you should go down and talk to 'em. We've taken all the race telemetry data for the last six months and all of his races and practices, we've aggregated that data all into GCP, run AI and ML algorithms on it to provide his racing team some very predictive ways that he can get better and that team can get better, and so I'd invite just anybody that wants to go there and take a look at, even if you're in banking, or if you're in retail, or if you're in health care, take a look at some of how that was done, because it's a very, very powerful way, to answer your question, head and shoulders down why Google is actually accelerating and exceeding in AI. >> And one of the things that Thomas Kurian showed onstage was the recent Hack-a-Thon they had with the college students with the NCAA data of the game that just finished, and throughout that experience, this is a core theme of GCP, and now Anthos, which is getting data in and using it easily, and scaling at a scale level that seems unprecedented. So this team seems to be the application... The new differentiator. >> I think it is. I think that announcement, obviously the big three takeaways for us, certainly, scale, unmatched. Certainly speed and migration with Anthos. If I could highlight one other, I was incredibly pleased with, well I've been pleased since Thomas' arrival in general by bringing an enterprise class strategy within sight of Google that I think are going to respond well to our enterprise customers, and part of enterprise class is also making sure that their partner community has amazing enhancement programs that really incentivize those partners that are actually in the full managed services space from cradle to grave, lifetime customer value. So we're very excited about even further announcements this week that no doubt have been inspired by Thomas to try and really take advantage of their partner community that are in the business of cradle to grave support of customers. >> You feel comfortable with Thomas. He's taught a lot of customers, he knows the enterprise. >> We've had an opportunity to meet with him. We've had some shared customers that have had a great privilege of getting to know him and support us and collectively them. >> John: He knows the partner equation pretty well, and the enterprise. >> Without a doubt. >> It's about partnering, because there's a monetization, the shared go to markets together. Talk about the importance of that and what's it like to be a partner. >> Yeah, without a doubt, again, you know, his embrace of the open-source community that you saw today, really taking advantage of highlighting partner value is wonderful, but I think Thomas, above anything else, knows that Google needs to scale. They need to scale, and then they have to have breadth and they have to have depth, and, you know, to get to where Google needs to be over the course of the next two, three years, it's wonderful, it's refreshing, it's 100% accurate that Google knows and Thomas knows that the path to do that is via partners; partners that share in Google's vision, that are 100% aligned to the same things that Google is aligned with, and I think that's why I'm so thankful to be at SADA, large in part, because all of the things that we care about in terms of our customer success as well as Google's success, we all share that, so it's a great trifecta. >> It's a ground-floor opportunity. Congratulations. Guys, talk about your business. What's going on? You've got some new offices I heard you opened up. What's going on in the state of the business? Obviously the Google focus you're excited about obviously. >> Yeah, yeah, yeah. >> There, at the beginning, I called Google the dark horse. I think with the tech that they have and the renewed focus on the enterprise, building on what Diane Greene had put foundationally, Thomas is meeting with hundreds of customers. He's so busy he doesn't have time to come on theCUBE, but he'll come on soon, but he's focused. This is now a great opportunity. Talk about your business. What's the state of the union there? Give an update. >> I can take that one if you don't mind. >> Go ahead. >> You can add poetic color if you want. (laughing) Yeah, so as I said, we're entering a new journey for SADA in light of renewed focus, renewed conviction to Google. We are investing more than we ever have into the common belief that Google is the one to beat in terms of momentum, drive, and ultimately winning the hearts and the minds of who we've talked about. So, over the last four months, we've opened five new offices in New York, Austin, Chicago, Denver. Our headquarters is in Los Angeles, and just recently, we just opened a brand new office in Toronto, so we can really help our Canadian customers really see the the same type of white-glove treatment we provide those customers in the States and so that's why, well, I wasn't earlier, but I'm walking around with a Canadian flag. We're very excited about the presence that we're going to have in Canada >> Its "Toronno." I always blow and I call it "Toron-to," being the American that I am. It's "Toronno." >> Dana: Glad you said it right. Good. >> Now, on the engineering side, so you guys are on the front lines as also a sales, development, there's also customer relationship, engineering side, so I'm sure you guys are hiring. There's some hard problems to solve out there. Can you guys share some color commentary on the type of solutions you guys are doing? What's the heavy? What solutions are you solving, problems that you're solving for customers, what are the key things that you got going on? >> Yeah. >> Well, a lot of cloud migrations, a lot of web and application development, custom development, and data pipelines. I'd say those are really the three key focus areas that we're working on at the moment. >> One other thing, too: so... we believe that we want 100% customer retention, always, and that goes above and beyond an implementation. So the other big area of investments that we're making is in a whole revamped technical account management team, so for those of our GCP customers that have had the privilege, we've had the privilege of working with and for, we are building out a team of individuals that will, well beyond the project, stay with that customer, work with them weekly, monthly, quarterly, and try to always find ways to expand and move workloads into the cloud. We think that provides stickiness. We think that provides ultimate value to try and help our customers identify where else they can take full advantage of the cloud, and it's a fairly new program, and large in part I just want to thank Thomas and the partner team for new programs that are coming out to help us so that we can actually reinvest in things that go you know throughout the lifecycle of the customer. So, very, very good stuff. >> Dana, Chris, thanks for coming on. Appreciate it. We'll check out your booth, the car's there, with the data. Bring that data exhaust to the table, pun intended. >> Yes. >> Analyzing with Google Cloud, Anthos. Good commentary. Thanks for sharing. >> Really appreciate being on board. Thanks for having us. >> Alright, great. CUBE coverage here live on the floor in San Francisco. Google Next 2019. This is Google's cloud conference. Customers are here. A lot of developers. More action, live on the day one of three days of coverage after this short break. Stay with us. (theCUBE Theme)

>> Announcer: Live from San Francisco, it's the Cube, covering Google Cloud Next '19. Brought to you by Google Cloud and its ecosystem partners. >> Welcome back everyone live here in San Francisco at Moscone, this is the Cube's live coverage of Google Next 2019, #googlenext19. I'm John Furrier with Stu Miniman, as well as David Vellante, who has been co-host, he's out there getting stories and getting all the scoop. We are here with two great guests, Cube alumni's, Aparna Sinha, the Group Product Manager at Google, and Chen Goldberg, director of Engineering, Google. Both the architects of the big wave that we're riding. Containers, kubernetes, and anthos. Guys, great to see you, thanks for coming on again. >> Aparna: Thanks for having us, great to be here. >> Chen: Thank you. >> So, you were smirking last night when we saw each other at the press gathering, knowing what was coming. I watched the keynote, it was awesome. I didn't get a chance to see the spotlight session you guys just had, but Anthos, obviously the rebranding and the additional integration points for making things run end to end, this is our dream come true, Devops Infrastructure as Code is happening, we've been talking about this for a while, you guys are behind it all, give us the update. >> So we've been hard at work over the last eight months since our last Next. Can you believe that it's only been eight months? Last year we were here announcing GK On Prem. This year we've rebranded CSP to Anthos and enlarged it and we've moved it to GA. So that's the big announcement. In our spotlight we actually walked through all the pieces and gave three live demos, as well as had two customers on stage and really the big difference in the eight months is while we're moving to GA now we've been working throughout this time with a set of customers. We saw unprecedented demand for what we announced last year and we've had that privilege of working with customers to build the product, which is what's unique really. So we had two of those folks up on stage talking about the transformation that Anthos is creating in their companies. >> I want to get to the customer focus a little bit later, but I want to just get it out on the record while you're here, because there's not a lot of time on stage other than the great demo Jennifer Lynn did. What actually is the difference, what's the new things, because obviously its a rebrand, some people might say, "Oh, they're just rebranding the announcement from last year", what were the new things, what are the new elements of Anthos, why is it important, what does it mean, what's under the covers, tell us what's new. >> Chen: So, first of all lets talk about, "What is Anthos?" Anthos is a Google opinionated solution that lets you right once, deploy anywhere. Really, the key thing about Anthos is choice. What we've been hearing from our customers, how much they appreciate choice in their journey to the cloud and modernization in general. The main thing that we have announced is that everything we have announced last year is GA. So talking about GKE On Prem, Anthos config management and our marketplace and the control plane from managing multiple classes, all of that has moved to GA. when thinking about choice, we've added new capabilities and one choice that customers are thinking about, "Do I need to choose a single cloud provider?" I had a discussion just yesterday with one of the customers and they said that when they exclude a cloud provider from their strategy, they're actually blocking their own innovation and that might get even a bigger risk for them. So we know that customers are adopting a multi cloud strategy. The big announcement here is that we are moving towards, or maybe we are even leaning more into multi cloud, we already had other solutions that we were talking about and definitely with Kubernetes and Istio talking about open API's, but we are leaning in towards multi cloud strategy, so that would be one. The second thing that talks about choice, is "How do we start?" One thing we are hearing from our customers is the importance that they want to innovate with what they have. So Anthos migrate, lets them take their existing applications, package applications that are running today on VM's and onboard to Anthos automatically and see value. So those are the top two announcements and I think the third one would be around all the partnerships, which is part of the people we've been working with in eight months. >> That's awesome. >> Stu: I'm sorry, the migrate piece, that's not GA yet, am I understanding? >> No, it's moving to beta. >> So Stu, you and I have been talking about applications, Renaissance, multi cloud, obviously is a reality for enterprises. Now you've got the hybrid model, this is kind of in the main themes of what this all means with anthem. So its holistically looking at the cloud, as you said, not just Google Cloud. This is a key nuance, its kind of embedded in the announcement, but its not just Google Cloud. >> That's right and I think in that sense, Anthos is a game changer, its not just an incremental improvement to something that's existing for customers. Its not like its just something faster or cheaper or adds more features, its actually something that allows them to do something they couldn't do before, which is, have a consistent platform that they can use to write once and deploy their workloads anywhere, On Prem, in GCP and that we had, but expanding that to any cloud, not just Google Cloud. >> I want to get your guys' thoughts here because you've got the brain and trust inside Google Cloud, because I've been talking on the cube about this and publicly. There seems to be confusion around what multi cloud means, and a company is an enterprise, there's a lot of things going on in the enterprise, so certainly the enterprise will have multiple workloads. There's certain situations that some people say, "Hey, this workload would be great on this cloud, this workload would be great on that cloud." So its not about having a cloud for cloud's sake. "We have to standardize on Google, we have to standardize on Amazon." Instead, what I hear, and I want to get your thoughts and reaction to is, I'd like to have a workload that has data, highly addressable, really low latency for this workload, and a cloud for this workload, but together its multi cloud, this seems to be a trend, do you guys agree with that? Is that something that you're seeing, is that the main message here? It's not so much standardized on the cloud, but have multiple clouds, pick the right cloud for the job, kind of philosophy. What's your thoughts, this is kind of a philosophical question. >> So this is exactly what we are hearing from our customers about their multicloud strategy and exactly what you are saying. This is actually for most of them is a reality, either because they have been organically building things in the cloud or they want to get to multiple geographies, and it's not only a cloud vendor, we need to remember that On Prem is where most of their workloads are still running and where they still need to innovate or when you talk about retail or banks, they have their branches and their stores where they need to have compute at. Really, services are spread all over. Now the question is, this kind of situation creates a lot of risk for our customers. Security risk and talent fragmentation, which are related, so how can I manage all of those environments? >> The risk is multi cloud, or one cloud? >> So multi cloud actually increases the risk even further, so they already have a multicloud reality. That's their strategy forward, but how can they mitigate risk with that reality? We are talking about kubernetes gave you portability of workloads, but how can you do portability of skills and making sure that your talent can really focus where it matters and not be spread too thin, so this is one example that I think Anthos is really unique about using it from our hosted control plane on GCP. >> So let the workloads decide what's best for the workloads and let the clouds naturally use kubernetes. >> Yeah, I mean one thing I've seen in our customer base is, you know the line of business wants to innovate and they want to use the best service for whatever it is that they're doing and the different clouds have different types of services, they have different strengths. So, you don't want centralized IT to say, "Hey, no actually you can't do that, you have to follow this policy." We've seen many examples where centralized IT is taking months to approve cloud services and they've got a backlong of hundreds of services that they need to approve. That's really slowing down innovation, and, "why is that happening?" Because you don't have a consistent platform that you can run and use across clouds. Like you said, kubernetes actually solves that and so that's why were introducing Anthos based on kubernetes, so that you don't have that risk, you don't have that fragmentation and you can innovate faster. >> Lets do one more question and with compounds to complexity is old procurement rules might slow it down. I've got to buy this. So the old baggage on procurement standards, Its kind of a moving train. >> Yeah, I mean enterprise has its policies, we've been talking to some of they largest banks, we had HSBC on stage with us, we had (mumbles), which is one of the largest grocers, we have kohls, these companies have policies and they have compliance requirements and these are very valid compliance requirements and they need to be adhered to. Its just, how can you speed that process up, and if you have a platform that actually spans environments, it doesn't look different in each environment, you can imagine that simplifies the process, it simplifies the approval process because the platform's already pre-approved and then new services as they come online, if they follow a certain pattern, they're kubernetes approved services, then it's much easier to approve them and it's much easier to unlock that productivity without increasing risk. >> If I could poke on that just a little bit (mumbles) approved services isn't a term I've heard yet. There are dozens of providers that have kubernetes, Anthos I know is different but if I go out there and use kubernetes from a different cloud provider or a different service provider. Kubernetes is not a magic layer, everybody builds lots of stuff on top of that and a concern is if I just have a platform that spans all of these environments. There's skillset challenges and do I also get a least common denominator. Cloud is not a utility, GCP is very different from the other clouds, how do I balance that and how do I make sure that I'm actually being able to get the most out of why I choose a specific platform or cloud. >> That's where Anthos is that layer that actually is more than kubernetes. We have, in Anthos, an opinionated platform from google that utilizes kubernetes but it isn't just pure kubernetes, as you would experience it from the open source with the fragmentation, we're working with certified kubernetes distributions and we've got this marketplace where the applications that are in the marketplace have been tested and certified and are supported by a set of partners as well as by Google Cloud to run on these different distributions that you connect and register with Anthos. >> To give maybe another perspective of that, what we have seen with kubernetes is that customers do appreciate that consistency. They have been demanding, for example, that all kubernetes distribution will be conformed. We had that announcement when we were on stage today about consistency and how we can integrate PKS into Anthos. I think what customers are telling us, they don't want us to innovate in that layer. So they appreciate us using open API's and using sensibility which is predefined and actually allows that interoperability of services and this is something that is really in the foundation of Anthos. >> Well you guys have done a great job, we've been following the progress from day one and watching the foundation of Google Enterprise. You guys have been big contributors, congratulations to your work, it's great to see the progress and it seems to be, the train's moving faster on the tracks, so congratulations. I guess my final question for you guys is, boil down Anthos. To the folks watching that are in IT, they're trying to solve some problems, a lot of people realize and wake up, "wow I've got multiple clouds." That's not (mumbles), that's reality. They see billing statements from multiple vendors how they still want maybe hybrid, what does Anthos mean to those people? What is it about, what is it? I'm trying to get bumper sticker. What's the bottom line, what is Anthos? >> So Anthos gives you a choice without the risk. That means that they can choose an existing service or a new green field service to use, On Prem or in the cloud. Containerized or uncontainerized, and they can build on top of that at their own pace. So that's the choice and they can mitigate risk by giving those tools to manage that consistently. The other thing I would say for something that we are not talking a lot about because we are focusing about technology and requirements and constraints is what we hear about our customers that Anthos is good for the engineering teams, and what we hear our customers say, that because they are choosing this technology, their talent is appreciating that they can use the best and latest technology and their skills are portable to other areas as well and they can attract the best talent. That to me is a very big value for us that are looking to do digital transformation. >> I'll take a crack at it as well, so Anthos is Google's opinionated solution for hybrid and multi cloud and it is like Chen said, something that mitigates risk and gives users choice so that they're not locked in to a particular cloud and instead, they can build once and deploy anywhere. From a technical standpoint, it's three things. There's a multi cluster, multi cloud, management plane, that's hosted in Google Cloud. Number two, there's a service management layer which actually bridges your monolithic, migrated services with your green field services that are containerized and treats them all as services that you can secure, manage, and control, and then number three, we have an awesome marketplace from which you can deploy Google Services, you can also deploy partner services, and you can deploy them into anywhere that Anthos is registered and can run. >> So Anthos embraces the cloud, all clouds, all services. >> Anthos embraces the user and it puts the user first. >> Does this benefits, good choice, lock in options, negotiating contracts, developers love it, ... Guys congratulations, thanks for the insight, love the explanation of Anthos, thanks for sharing, appreciate it. (mumbles) Thanks for coming on, cube coverage here live in San Fransisco, we're breaking it down, Google Next 19, day one of three days, there'll be live cube coverage. We have all the leaders, google executives, all the engineers, coming on to explain to us what's happening, thanks for watching, stay with us for more after this short break. (funky music)

live from San Francisco it's the cube covering Google cloud next 19 taught to you by Google cloud and its ecosystem partners hello everyone welcome back to the cubes live coverage here in San Francisco the Moscone Center for the Google clouds conference is called Google next 2019 I'm Chevrolet my costume in omim de Ville ante is also here doing interviews our next guest is probably Bob who's the VP of product and design for server lists at Google probably great to see you thanks for coming on thank you for having me so you'd be a you're the VP of Product you got the keys to the kingdom on the roadmap you're seeing all the announcements obviously server lists cloud run was announced cloud code was mentioned on stage that's going to come out tomorrow so code build run this is DevOps this is actually happening yeah you know what super exciting is that we've we're finally solving the problem for customers and taking a customer centric view of this I'll start off with a little bit of the journey we took to get here right as we were talking to customers they kept coming back to three things that they wanted from us the first thing they wanted was agility they understand that you know cloud could give them great cost savings but they also wanted to be able to move faster and innovate right the second bit they wanted was having the flexibility to be hybrid and multi-cloud super important especially to our largest customers and then the third piece was they've really struggled with his journey to cloud and they wanted our partnership to make it a much more seamless and non-deceptive journey so as we talk to them about these three things right we came back to the drawing board and said hey what are the products that we can build to make their journey to be more cloud native and more agile much more seamless and future-proofed that much better right so we came back to the drawing board and came up with three products that you talked about this now the first was we looked at developers and their journeys and we said look they're building in traditional ideas like IntelliJ or vs code optimized for local development right and they're not writing a lick of Yama they're right for kubernetes and we said okay how can we take those environments and help those development teams build cloud native apps really really easily so really just turbocharging their cloud native development so bill cloud code which extends their local ids and lets them deploy to remote clusters so they can get full debugging full deployment building its integrated in the cloud build and they get the full kubernetes a development environment right in place so cloud build was released earlier you got enhancements of that so news the hard news here is enhancements to cloud build cloud code as new announce here yeah cloud run announced today that's right so this is the new this is the new hard news that's right so bottom line what does it mean for a developer so like I didn't enterprise so I'm a cio I'm a site C so I'm gonna be putting all my eggs in the cloud basket I've still gonna run the on Prem day is gonna be critical to my strategy it's this early day set up time or are you guys thinking it's more about the setup or more the life cycle of CI CD pipelining all the way to application deployment a great question John so I think where we are in this journey is that enterprises have started off with something that's the most basic cloud ready workloads that have been lifted and shifted we now see the next wave of workloads this is the 80% of workloads that are still on premise we see them start to get cloud ready and cloud native and the way that their enterprises are gonna do that is by building on top of the standards we've created like kubernetes and sto and key native and what cloud cold and build and run and of course Anthes that we talked off this morning as well these are great managed solutions from Google fully managed solutions from Google that let you get cloud native fast all right Polly wonder if you can help us you know spin through I see a disconnect in the market so you know Google showed great leadership in the container space and of course kubernetes we came out of Google and when I look at like cloud run okay it's helping to connect that and Kay native to kubernetes in service when I talk to a lot of the developers and service it's not the infrastructure moving up the stack it's they didn't want to even think about it it's right built in the cloud that's right I focus on the application I don't even think about that so I've got this big gap as to you know on premises forget it I don't never want to touch it or think about it and you know the one of the reasons you know there's the term server list would put it to the side but now if I need one is this environment I don't want to think about it and we know hybrid is a reality but there's this big disconnect as to what kind of developer are you or you a DevOps person that came from an infrastructure background or are you just building apps today yeah yeah yeah we're definitely seeing that from our customers right so one thing that we hear all the time is developers don't want to just not think about infrastructure they actually want the managed service and the platform they're building on to think about the infrastructure and optimize it for them so it's not this program will infrastructure it it's cloud run programming the infrastructure for you so you don't have to do it and I think increasingly you're gonna see products like cloud run and anthos and cloud code let developers focus just on code because that's what they want to do right I don't ever seen a developer say I really want to write a Yama file or I want to set up more configuration parameters right so I think we're gonna get to the place where you have developers being able to focus on cold and all of the rest of this being taken care of by platforms like code and run and anthos automation becomes key I mean Jennifer Lynn's demo I thought was very game-changing because she made the comment developers can focus on their code and agility not access permissions and all the configuration management that goes on under the you guys gonna provide that in an automatic programmable way we're gonna believe he is and she kind of teased out service missions so service missions kind of point in the future which is app developers are gonna still need to be aware of maybe not aware of what cloud run how to manage those sirs as they come stand up and get pulled down dynamically yeah how do you view that because this has become a gonna become complex is that gonna be automated is that where cloud run comes in you expand on this whole impact of service meshes because that's the next level that's right that's right so if you think about key native it's built on kubernetes and it forms the kind of triad with sto as well right and what a product like cloud run does is it lets you not have to think about that because at the end of the day we don't want developers to have to think about K native what cloud run is it takes care of the K native portability and compatibility for you and all you do is focus on the code itself right so ultimately we want developers to focus on their applications but I will say this right we do care about another important constituent which is all of those folks who've already got an apps built out there can those workloads be serviced as well and that's part of the problem we're trying to solve it that's an operational thing all right so let's take a step back here so server list actually fanfare has been great we're seeing a lot of traction people are enamored by it because functions as a service has been very compelling whether it's retail managing you know that spiked loads and becomes we see some some use cases where it's like you know really an amazing thing where is it limiting what is the next level growth for server list where do you see you mention workloads and we see people deploying functions and being happy with it are there limitations with serverless how does it go to the next level can you take a minute to describe the current state of server lists and what's coming around the corner now so great question the first thing I'll say is that there's a ton of developers who come up to us every day and tell us cloud functions is awesome right and they really like functions as a service they like the event-driven approach to it they like the service full approach but several is provides love the programming model that's great but there's an another large contingent of developers who tell us look this is super constraining for what I want to do I don't get to choose the libraries I want you're forcing me into a particular programming model can you give me more flexibility and what they see every day is the flexibility that containers provide especially on kubernetes right and what we've tried to do with cloud run is try to bridge those worlds where you get all of the flexibility that you want right that you get with containers but then combine it with what what you really want with the operational model which is service right so you pay only for what you use and of course you get the agility of service as well now one thing that we've noticed heard some great stories about this is a customer of ours Veolia which is one of the early adopters of cloud run and they've been partnering with us we thank them for it they are running a complex workload you talked about retail what Veolia does is they're large French multinational they do energy water and environmental services these are things that need to be highly reliable very complex and these are workloads that have existed for ages right and what viola is doing is using cloud run to run that complex workload but in a service in a service full way running in a service fashion all right take a minute explain what's a complex workload for your definition what is a simple workload because guys again we love functions Stu and I always talk about how great it is but what's that what's the D mark line when when does something become complex by your standards where you guys are addressing they could think describe the characteristics of a complex workload so the first thing is does the workload require flexibility right meaning are their custom workloads sometimes even legacies C++ or C applications do they need to pull that functionality in as well right do they need to pull random artifacts from across the enterprise to combine it and sometimes these are things that have been built over 20 years ago they're really critical mission critical pieces of software that need to be able to trigger and run right and can we actually take that flexibility but also combine in with a highly reliable environment right so were close like New Orleans there is no downtime right they need to be up 24 by 7 for 365 days of the year right so that flexibility plus that level of reliability is what we look at when we look at complexes so you're getting into complex systems where you got some code may be written in a mainframe COBOL in C++ we mentioned that was my jamm what kind of old dating myself but that was state-of-the-art back in the 90s so I'm running an agile job maybe of standing up cloud native but I need a use software and data from a system that's where is that where the container piece comes that ku burning it on either kubernetes but cloud run also supports docker so let's say you're running it in a docker container all you need is a docker container image and we can host that workload on program yeah Polly help us understand where where Google kind of what what's the same one what's different compared to the other service offerings out there just what I've heard feedback the last year or two is you know the great thing about server list is it's really easy to get started I've talked to marketing people that have no coding background that you know can get off and running it but doing complex mission-critical stuff yeah like we understand you know there is no magic wand NIT no silver bullet to make it easy but you know what do you see as Google's role in in this broader marketplace and you know where does open-source fit into that too yeah yeah so first I'll start off by saying there's a whole host of functions that are running on cloud functions which are relatively lightweight simple targeted event-driven functions those work great where we see us really making a difference for our customers is in two ways the first is get these more complex workloads that are currently running in a container whether it's a docker container our and or on gke for that matter and bring the agility of service to those workloads so it's the first thing it's something that we think is very unique because combining containers with serverless the second bit really is the open approach we've taken right built on top of K native key native as you know has a number of partners so one of the cool demos that you'll see during during Google Cloud next is you'll see a workload being shifted from cloud run on gke to the IBM cloud IBM is one of our partners 4k native without a single line of code and that flexibility is something that I think customers really decided talk about the business pen and some of the benefits at the business level in a developer level at the operations level can you hit those three points yeah of serverless silikal server less on those three sectors what's the benefits yep so we talked about the benefits for developers for developers it's simply about agility focus on your own code don't worry about Gamal don't worry about ki native you don't have to worry about any of that we'll take care of it for you the second benefit that I'll talk about is again this is just a benefit for the CIO which is hey we're gonna give you the flexibility and the openness so you can have portability of your workloads across whatever and why are you environment you want whether it's on tram or in a cloud whether it's Google or another cloud that's the second benefit the third bit is all of the operational benefits of service one of the things you'll see us do and continue to commit to do is we'll bill you to the hundredth of a millisecond right and so you'll continue to get that with all of the resiliency you expect of Google infrastructure security also pretty much baked in as well security is big then there's a fully managed offering from Google and so you'll get security compliance policies all Big Data of course we watched the keynote and we watch every word from Koreans giving Diane green a little tip of the hat which was nice signal a lot of class a great respect for that but jennifer lynn said something i want to get your reaction to she was kind of talking about her thing doing a great demo he changing and when she said this would allow you to negotiate better contracts okay that might have been a slip of the tongue your reaction that that implied to me I took that and say whoa that means leverage shifts to the customer your thoughts and that kind of maybe a slip of the tongue but if you're saying that I couldn't have options and choice yes Janice pardon this is what customers want and at Google what we're focused on is giving customers what they want and one of the things that customers are worried about today is lock-in and especially in the server this area because the current offerings are so proprietary customers are worried about it because they want server lists for all the benefits offers that we talked about here but they do want that flexibility and that's what we negotiate actually we know Oracle is very strict on their cloud this is going to give customers the choice is the saying that's whoa you want a license renewal yeah that's what you're getting out here so Polly you talked about choice and flexibility you know kubernetes gives some of that concern with serverless is if I look at a sure if I look at AWS if I look at Kay native you know those three aren't the same I talked there there's a small start-up called trigger mesh that's getting Kay native to work with AWS lambda but do you see a future is there you know I've talked to the CMC F I've looked at some of the various pieces that you know serverless isn't just something that I'm baked into a cloud yeah look I think we've seen extraordinary momentum around Kay native it's very similar to what we had seen when in the early days of kubernetes this huge amount of ecosystem interest and so we'll see continued innovation where you'll see work load portability come to service and I'm confident in that because of all of the momentum we were seeing around Canada so we're committed at Google to K native and its success so you'll see us continue to innovate yeah talk about open source open source becomes a very strategic part you can Shin kubernetes which you guys were the that have the DNA the founding fathers of kubernetes now teams on the team went to vmware someone have Microsoft some stay within Google containers certainly we see what you guys have done when four against four J but open source still this fear of open source I mean I don't mean it in a way that it's going to be inhibited and primitive but support making sure s LA's work latency microservice is going to be involved you mentioned k- yeah so as open source accelerates the time then value for the code that also triggers this op side of the serviceability and reliability and support what's your thoughts on that how are you guys how do you see the industry supporting that that critical piece of the puzzle yeah could not be more critical right for customers to be able to adopt this because the number one thing that we need to do for customers is give them a managed offering that lets them not have to worry about security lets them not have to worry about compliance lets them not have to worry about policies or identity etc right bake all of that into the managed service and then the second operational bit is which is as important this goes to what Thomas talked about at the very end of his keynote which is the open source announcement is we want to make it simple for customers to adopt it will be supported by Google and the partner you'll get unified billing unified support and one person to call when you have a problem yeah Polly we're at an interesting point in open source today because they're they want to get your opinion as a product person and your relationship with open source because you know there's a certain cloud out there it's they're gonna give you open source as a managed service but you have some of the companies that are making like open source databases changing their policies to try to fight against just being you know taken over by somehow the big players how does Google react to that yeah for us the approach is all about partnership because we think together we can better serve customers needs and best serve them and so our approach has always been about partnership so whether it's kubernetes or key native or the larger manage store manager open source offerings that we talked about earlier in the keynote we want to bring all of these together so we can serve customers so you're gonna see us continue to like support the open source equals because we believe that innovation is absolutely critical to helping our customers really start innovated in be agile final question I know we're tight on time I want to get this in because you know I see a lot of positive I've come out of the show there's been some critical analysis around you've got to build up salespeople and all the field stuff which is you guys are well aware of but one of the things that was kind of teased out in the open source announcement was the role of Google having their own ecosystem Asli the C & C has been a big tailwind for Google you guys been a big part of that ecosystem as a cloud commercial provider and with these kinds of server list you're going to have an ecosystem starting to develop kind of a thousand flowers blooming pun intended so how do you see that in your area because this is going to be super important partnering ecosystem support yeah which is you know developer traction distribution of software integration opportunities that's why in monetization all kind of come together your thoughts huge hugely critical for us and that's something that we've been focused on we have a rich ecosystem of partners for service we're gonna continue to build it out across all of the different pieces you need one of the things we didn't talk much about was our entire operational stack monitoring logging all of those pieces right we need to bring all of those together along with all of our partners we have a big partnership with the likes of data dog right number of others so we're gonna continue to partner with the entire ecosystem so we can go solve the problems that they have are you guys gonna show them the white space where they can play is gonna be part of the strategy yeah so it's gonna be across the board you'll see us continue to support the key native ecosystem tremendously and like lean into that and we're already excited to see all the different offerings that are exist on key native same thing with kubernetes we're gonna continue to like press hard we've got on the operational side we've got an offering called open census it's got lots of traction again just open monitoring of applications so we're gonna continue to do that across the board yeah probably great to have you on vice president of product and design got the keys to the kingdom right here he's the who's running the show for the server list really the key part of how kubernetes really intersects old and new to create the next generation applications thanks for joining us and sharing the insight I'm Jeff forest do many men here live coverage Google next more coverage after this short break

>> From Seattle, Washington, it's theCUBE. Covering KubeCon and CloudNativeCon North America 2018. Brought to you by Red Hat. The Cloud Native Computing Foundation and it's ecosystem partners. [techno Music] >> Okay, welcome back everyone. It's theCUBE's live coverage in Seattle for KubeCon and CloudNativeCon 2018. I'm John Furrier with theCUBE. Stu Miniman. Breaking down all the action. Talking to all the thought leaders, all the experts, all the people making it happen. We're here with Aparna Sinha who's the group product manager, Kubernetes, Google Cloud. Also one of the power women of the Cloud at Google, according the Forbes. I wrote the story. Great to see you again. >> Thank you, great to be here with you. >> Thanks for coming on. >> CUBE alumni. Great to have you on. I want to get your prospective. One when you've seen a lot of action, certainly overseeing the group engineering team at Google and all the Kubernetes action. A lot of contribution, a lot of activity, that you guys are leading. >> Yes. >> And quite frankly enabling and contributing to the community. So, congratulations and thanks for that work. Kubernetes certainly looking good. People are pumped up. >> Very much. >> 8,000 people. A lot of activity. A lot of new things around that you guys are always kind of bringing into, the Geo, knative, a lot things. You gave a key note. What's your focus here this year? What's the message from Google? >> Yeah, well as you pointed out, this is the largest KubeCon ever. 8,000 people, 2,000 on the wait list. And people are telling me here that this is the... This is here to stay, right? It's in the early majority going to the mainstream very much like you kind of think about virtualization was 10 years ago. So that's the momentum that I'm seeing here, that I'm hearing here. My keynote was about the community. Thanking the community first of all. So I talked about how open-source really, success in contingent on contribution. And so, I started by showing the contribution over the last one year, the companies that are contributing. And 80% of contributions are by at least 10 entities. One of them is individual contributors. 40% percent I think was Google, which is still staggeringly high. And then the next highest was Red Hat. And so I think in many of the keynotes, we've been calling out the contributors because it's really important. 1.13, the 13th release of Kubernetes shipped last week. A lot of stability, a lot of GA features, and the uptake in the enterprise. The other thing I called out was just the amount of job opportunity in Kubernetes >> Yeah >> 230% growth in the last year. You see here so many customers that are here to talk about their experience. But also they're here to hire. >> Yeah. And there recruiters on the floor, so it's been I think a huge economic value add. And we feel very proud of that. >> Yeah, Aparna, great point. We've been talking about the end users. I always loved... There's a job board right outside the hall here and it's just covered. Big giant white board there. Bring us inside a little bit. I mean Google's always fascinating people. What's the hiring situation there? What's your team lookin' like? Is anybody smart enough to actually go work there? >> Google, I think we've been very, very fortunate in that we've had the original board team that started the Kubernetes project. And so we have a really, really deep bench because we've been running containers since the beginning. So now 15 years of experience with that, which many people tell me, I think that the reason that Kubernetes is so successful is because it's not new actually, right? >> Yeah >> It's been tried and true at scale. So, we have quite a bit of that, but we've been building this community and a lot of folks have been hired in through the community-- >> Yeah >> into Google. And really amazing, amazing people. So yeah. >> The thing about we had Brian Grant on yesterday and Tim Hockin -- Yes. >> Who was talking about some of those early board days. >> Yes. I want to ask you your point of about the hiring because I think this is a interesting dynamic. Open-source is key to your strategy. We've talked many times about how you guys are committed to open source, but what's interesting is not just net new jobs are available, we're seeing a revitalization around traditional roles like the network engineer under Kubernetes. Looking at the policy knobs that your folks pointed out that's... They think it's underutilized. And then on top of Kubernetes, new things are going on that's getting the app kind of server guy-- >> Yeah. >> Kind of energized. >> Yeah. >> It's kind of enabling a lot of thing, actions that's transforming existing jobs. >> That's right. >> And bringing new ones. >> Talk about that dynamic because you see it from both sides. >> Yes >> You've got SREs, site reliable engineers. >> Yes >> You've got developers. But, Now enterprises are now trying to adopt... >> That's right >> You guys are hitting that note. Talk about that dynamic. >> That's right, so I've been talking to a lot of customers here, it's been non-stop. I've not been able to attend any talks or keynotes. And I'm seeing two things. One there's the kind of operations now called platform teams. And they're under tremendous pressure. They're doing incredible work. Incredible. And they're energized. They're really... So one of the customers I was talking to was moving from VMs on EC2 to containers on GCE on Kubernetes. Google Cloud. And in the last one year, they looked... Honestly, they looked miserable because they have worked so hard in doing that transfomation. Turning their application from a VM-based application into containers. But you could also see that they were so happy and so successful because of the impact that it's had. And so and then I asked them so like, "What is driving that?" This is different customer. What is driving that? And it's really... As soon they get that environment up and running, and this is a large enterprise bank that I was talking to, this other one, their developers are just all over it. And they have, they have hundreds of services running within six months. And they're like, "Well we just got this platform up. "We still have to figure how we're going to upgrade it." But it's... So those are the two constituents. The developers are happy. >> The integration and delivery changes the makeup of how teams work. So that's one thing we're seeing here. And the other one is just scale. >> Yeah. >> So that seems to be the area. Now I got to ask you, as you guys look at... As you guys are doing the work on the enterprise side, you guys, I know you're working hard, I talk to Jennifer a lot, Jennifer Lynn, as well and we've talked before, are used to doing the work. But there's still a lot more work done. Where do you guys see the work that this community value opportunities for participants in the eco-system to fill white spaces? Where are the value lines starting to be drawn? Can you comment? >> Yeah, so I see two or three different areas. One of the areas is of course hardening. And that's why Janet Quill gave the keynote about "Kubernetes is boring and that's a good thing". And that's been something we've been working on for the last year at least. Adding a lot more security capabilities. Adding a lot more just moving everything to GA, right? Adding a lot more hooks in the enterprise storage and into enterprise networking. Building up the training and building up the partners that'll do the implementations. All of those things I think are very, very healthy. >> Yeah. >> Cause I see them. You probably talked to the CNCF. They're helping a lot with the certification and the training. So that's one piece of enterprise adoption. I think the other piece is the developer experience. And that's where a lot of the talks here, my key note as well, I demoed Istio and Knative on top of GKE. The developer experience is ultimately this whole thing. My perspective, this whole thing is about making your developers more productive. And developers have been driving this transition. Again going back to those customer examples. So that's getting a lot easier. >> Yeah, Aparna, I'd love you to talk a little about Knative. So, I know the excitement is there. Products only been around for five months. I remember at your show last summer it was announce and roll. Trying to understand exactly what it is. It's like, wait, wait is serverless going to kill Kubernetes? And how does this fit? How does this work with all the various services in the Cloud? Maybe just understand where we are. >> Right. >> What it is, what it isn't. >> Right. >> Again, so the heritage of serverless, I'm going to go back to Google, right? We have the first serverless offering in the world like 10 years ago. And so that's based on containers. Underneath it's based on containers. That's why we knew that with Kubernetes that's the right foundation for building serverless. And it actually, I think, we sort of held back for the longest time. And a couple of years ago there were one, two, and then 15, and then 17 serverless frameworks that just kind of all popped up around Kubernetes, on top of Kubernetes. I remember the first demo in the community. Here's this serverless piece. And at some point, a little bit over a year ago we decided that actually serverless is really important to our customers, to our users. The majority of Kubernetes tends to be on-prem, actually. And so it's important to them to have serverless capabilities on-prem. So then we need to make sure it's stable and it's something that's standard. >> I think it's a really important point... I talked to some people that are in the serverless ecosystem that is living on a AWS and they say, "You can't build serverless on-prem "because then you're racking "and stacking and dealing with it." And it's not... We know there's servers underneath of it and it's just system calls and how we consume that. But maybe explain the nuances to how this is important and we understand it. >> Yeah. >> There's not like a solution out there. >> Yeah. >> Server meshes, there's a lot of options out there right now. >> Yeah. >> So. >> A lot of things, because this is an open-source community, a lot of things come from the users. So when the user says, "You know what, actually need "the serverless capability on-prem. "Why? "Because I've got this developer group and I don't want "them to have to muck with the infrastructure. "I don't want them to have access to the infrastructure. "I want to just give them a simple interface "where they're going to write their applications "and the rest is taken care of for them." Right? And then I want to be able to bill them on a per-use basis. So, it's... Yeah there's someone managing the server. Someone building actually the severless capability and that's the platform team. That's the guys that I talked about that are working very hard these days happily. But, working very hard. >> And these are the new personas, by the way-- >> Yeah. >> In the enterprise. This is new kind of new re-architecting of how enterprises are creating value. These new platform teams. >> Right. >> This is the opportunity. Well I got to ask you, you know everyone that watches theCUBE knows I'm a big fan of scale. Love Amazon scale. I love Google scale. I love the enterprise market. And I want to get your thoughts... I want you to take a minute to explain the culture at Google Cloud. Because it's a separate building. Give you an opportunity to share. But you guys are working hard to go after the enterprise. It's not like a new thing. But the enterprise is interesting. It's not so much the best technology that wins. It's grit. It's almost like a street fight. You got to go out. You got to win those battles. Get all the work done. Hit those features. You can't just roll into town and say we've got great technology. We're Google. You guys recognize this. And I want you to share the culture you guys are building and how you guys are attacking the enterprise. What's the guiding principles? What are some of the core tenants? >> Yeah, yeah. So you know my entire life has been spent in enterprise software. >> Yeah. >> I do think that enterprises respect Google Cloud. I work very closely with them. And they respect certainly the engineering prowess. Like, "Wow. I need that." >> Yeah. Right? Especially you see all these enterprises that are being transformed by technology. Their industry is being transformed by technology. Whether that's in transportation, or it's in retail, or it's in media. And they want the best. They want the latest. Right? And they also don't necessarily have the skills, like you said, right? So they're looking for a partner that'll both help them scale up but also provide them all of that guidance. And the one thing you asked about culture at Google. I think we are a revolutionary company. We are willing to do lots of things. Lots of things that you wouldn't expect. And that's why you saw GK on-prem from my team, right? The first, kind of, Kubernetes on-prem offering from a cloud provider. Managed by a cloud provider. And that's really... I mean we've seen tremendous, tremendous interest in that. Tremendous feedback from our users and new customers. People that hadn't thought about it. Hadn't thought about Google, necessarily before that have said, "Wow. If you are going to come and help me on-prem "with this, I'm ready. "Give it to me now. "Because I trust you and I know I want to go to the Cloud. "So it's the right step for me. "You have the right incentives." Right? "And you're the open cloud, which is important to me "because I may want to be multi cloud." So that's the piece that is... >> You got the enterprise chops. You've spent your whole career there. I know Jennifer as well. >> Yes. >> A lot of people you guys have hired. >> Right. >> The good news is you've got a market that's changing. So you don't have to come in and replicate the old IT. So that's an opportunity at Google. How are you guys attacking that, that beachhead? Because you have the check. What's the vibe? What's the grit? What's it like... How you guys attacking the enterprise? What do you see as opportunities knowing the enterprise of old-- >> Yeah >> As it shifts to new kind of method? >> Yeah. >> What's the core? >> I think about the problems the users are having. I think about what is the problem the customer is facing. And so... And then breaking that down and solving that for them. I mean that's what's important, right? And so some of the problems I see is one they need a developer platform. And the developer platform sometimes cannot be in the Cloud. When I talk to large financial institutions, there's so much compliance and regulation and things that have to be on-prem. That it has to be on-prem. And they try to move to the Cloud and some things will do it. But the majority, like 90% is on-prem. And so they need an agile development environment and there's no holding it back. Because, like I said, there's all this transformation. Their developers need that environment today. So you have to provide that. That's one use case. We provide an on-prem development and agile development environment. Best in class. Your developers are super happy. Your business is going to do well. The other thing I see, and I see this a lot in retail, but also in hospitality at some of these very kind of brick and mortar enterprises is the edge. They need a solution at their edge location. Thousands, these are thousands of branch locations. We've even got this use case with Chick-fil-A, right? And a lot of times this is... A lot of different use cases, but a lot of time the common thing is that they're collecting data. They're doing some processing at that site and then they're doing further processing in the Cloud. And so it's a connected, but an intimately, it's not always connected.... Intimately connected environment. So that's the second big use case. Edge retail or just edge. There's so many... For me, it's one of the most exciting. There's so many examples of that. >> Awesome. >> Aparna, first of all, just so many goodness I want to say thank you to Google because everything from I heard at the show Google wasn't giving out swag because it actually went to charitable givings instead of spending that money. One of the things we always look is open-source is, how much more value is being created for the eco-system not just the vendor that started it. And it is a really tough balance. We've seen it fail many times. Do you step too far back? And how much do you engage? How do you strike that bound? For the last five to 10 years, we've been saying, "Where is the independent place where we can have that "conversation about cloud?" We think found it at this show. I mean we've been here for three years now. Google Cloud, phenomenal event. Our teams loves to be there, but this feels like overnight has turned into oh wait, here's the show we were looking at to have that conversation. To have that commons where we can come together and there's so many diversity of people, diversity of projects in here. Many which have very disconnected from original Kubernetes and everything, so. It's been fascinating to watch and have to imagine your team is... When you watch that first piece go and everything that's built around it. It's got to be amazing. >> My team loves this event. We have literally I think 300 people here. And a lot of them are core maintainers. Everybody is a contributor, but they are core maintainers of the Kubernetes project. The Istio project. The Knative project. And I think the best thing here is just interacting with our users. Because this is a developer, this is a developer conference, primarily. There's a lot of businesses here. >> Yeah >> With their kind of director level executives. But primarily it's an action-oriented hands-on audience. And you just... These customer meetings that I have, we review their architecture and we're like... It's an engineer to engineer conversation. >> Yep. >> And so how can we make that better? And sometimes they're contributing back and it makes the whole project better. >> Yeah. The thing, too, is it's an engineering, it's a developer conference, true. But what's interesting about that evolution as it modernizes, those end users are developers. >> That's right. >> And so the end user aspect of this show. >> That's right. >> Is the developer piece. >> That's right. >> It never used to be like that. Used to be COMDEX or some big event. >> Yeah. >> And then people just selling their stuff. >> Yeah. >> Doing business. The end user participation... >> Yes. >> Is not a consumption conversation, it's a contribution. >> Right. And end users are all over the spectrum of sort of really, really hands-on. Very, very smart to just give me something that works and I respect all of that, right? And we were actually very far here in terms of GKE. Giving you something that you really don't need to get in, that's fully managed, right? But then on the other hand we had Uber on stage earlier today in their keynote talking about how they've built all of this advanced capability on GKE. And that's a power user. That's using all their capabilities. Like custom additions and an operator. And it's just really gratifying I think for us to work with them and for us to see the user base as well as the community. So the ecosystem. Google. I thinks it's very important for us to have and create economic opportunity for our partners. And you'll see that with GKE on-prem. We're partnering heavily on that one. And you'll see that also in our marketplace. Our Kubernetes marketplace. So many of the companies that have come out of this ecosystem are now part of selling through Google Cloud. >> Aparna, thank you for your time. I know you've had to move some things around to come here. Great to have you on. I love your leadership at Google, it's phenominal. You've got the enterprise chops building out heavily over there. Congratulations. And for more CUBE interviews check out theCUBE dot net. You can check out Aparna's other good news. Of course search her name on Forbes. I wrote a story about her featuring her. Talking about her background and her passion. Always great to have her on theCUBE and get some commentary from Google. Of course, theCUBE is breaking down live coverage. Been there from the beginning of KubeCon and now CloudNativeCon, the Linux Foundation. Bringing you all the analysis and insight. Be back with more coverage after this short break. [Techno Music]

(upbeat electronic music) >> Narrator: Live from San Francisco, it's The Cube, covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hey, welcome back, everyone. We are here live, The Cube in San Francisco, Moscone West for the Red Hat Summit 2018 exclusive coverage. I'm John Furrier, the cohost of The Cube. I'm here with my cohost, John Troyer, who is the co-founder of Tech Reckoning, an advisory and community development firm. Our next guest is Jonathan Donaldson, Technical Director, Office of the CTO, Google Cloud. Former Cube Alumni. Formerly was Intel, been on before, now at Google Cloud for almost two years. Welcome back, good to see you. >> Good to see you too, it's great to be back. >> So, had a great time last week with the Google Cloud folks at KubeCon in Denmark. Kubernetes, rocking the world. Really, when I hear the word de facto standard and abstraction layers, I start to get, my bells go off, let me look at that. Some interesting stuff. You guys have been part of that from the beginning, with the CNCF, Google, Intel, among others. Really created a movement, congratulations. >> Yeah, thank you. It really comes down to the fact that we've been running containers for almost a dozen years. Four billion a week, we launch and collapse. And we know that at some point, as Docker and containers really started to take over the new way of developing things, that everyone is going to run into that scalability wall that we had run into years and years and years ago. And so Craig and the team at Google, again, I wasn't at Google at this time, but they had a really, let's take what we know from internally here and let's take those patterns and let's put them out there for the world to use, and that became Kubernetes. And so I think that's really the massive growth there, is that people are like, "Wow, you've solved a problem, "but not from a science project. "It's actually from something "that's been running for a decade." >> Internally, that's called bore. That's tools that Google used, that their SRE cyber lab engineers used to massively provision manage. And they're all software engineers, so it's not like they're operators. They're all Google engineers. But I want to take a minute, if you can, to explain. 'Cause you're new to Google Cloud. You're in the industry, you've been around, you helped form the CNCF, which is the Cloud Native Foundation. You know cloud, you know tech. Google's changed a lot, and Google Cloud specifically has a narrative of, they're one big cloud and they have an application called Google stuff and enterprises are different. You've been there now for almost a year or more. >> Jonathan: Little over a year, yeah. >> What's Google Cloud like right now? Break the myths down around Google Cloud. What's the current status? I know personally, a lot of cloud DNA is coming in from the industry. They've been hiring, making some great progress. Take a minute to explain the Google Cloud. >> Yeah, so it's really interesting. So again, it comes back from where you started from. So Google itself started from a scale consumer SAS type of business. And so that, they understood really well. And we still understand, obviously, uptime and scalability really, really well. And I would say if you backtrack several years ago, as the enterprise really started to look at public clouds and Google Cloud itself started to spin up, that was probably not, they probably didn't understand exactly all of the things that an enterprise would need. Really, at that point in time, no one cloud understood any of the enterprise specifically. And so what they did is they started hiring in people like myself and others that are in the group that I'm in. They're former CIOs of large enterprise companies or former VPs of engineering, and really our job in the Office of the CTO for Google Cloud is to help with the product teams, to help them build the products that enterprises need to be able to use the public cloud. And then also work with some of those top enterprise customers to help them adopt those technologies. And so I think now that if you look at Google Cloud, they understand enterprise really, really well, certainly from the product and the technology perspective. And I think it's just going to get better. >> I interviewed Jennifer Lynn, I had a one-on-one with her. I didn't publish it, it was more of a briefing. She runs Product Management, all on security side. >> Jonathan: Yeah, she's fantastic. >> So she's checking the boxes. So the table stakes are set for Google. I know you got to do some basic things to catch up to get in the cloud. But also you have partnerships. Google Next is coming up, The Cube will be there. Red Hat's a partner. Talk about that relationship with Red Hat and partners. So you're very partner-centric with Google Cloud. >> Jonathan: We are. >> And that's important in the enterprise, but so what-- >> Well, there tends to be two main ares that we focus on, from what we consider the right way to do cloud. One of them is open source. So having, which again, aligns perfectly with Red Hat, is putting the technologies that we want customers to use and that we think customers should use in open source. Kubernetes is an example, there's Istio and others that we've put out that are examples of those. A lot of the open source projects that we all take for granted today were started from white papers that we had put out at one point in time, explaining how we did those things. Red Hat, from a partner perspective, I think that that follows along. We think that the way that customers are going to consume these technologies, certainly enterprise customers are, through those partners that they know and trust. And so having a good, flourishing ecosystem of partners that surround Google Cloud is absolutely key to what we do. >> And they love multicloud too. >> They love multicloud. >> Can't go wrong with it. >> And we do too. The idea is that we want customers to come to Google Cloud and stay there because they want to stay there, because they like us for who we are and for what we offer them, not because they're locked into a specific service or technology. And things like Kubernetes, things like containers, being open sourced allows them to take their tool chains all the way from their laptop to their own cloud inside their own data center to any cloud provider they want. And we think hopefully they'll naturally gravitate towards us over time. >> One of the things I like about the cloud is that there's a flywheel, if you will, of expertise. Like I look at Amazon, for instance. They're getting a lot of metadata of the kinds of workloads that are on their cloud, so they can learn from that and turn that into an advantage for them, or not, or for their customers, and how they could do that. That's their business decision. Google has a lot of flywheel action going on. A lot of Android devices connected in the Google system. You have a lot of services that you can bring to bear in the cloud. How are you guys looking at, say, from a security standpoint alone, that would be a very valuable service to have. I can tap into all the security goodness of Google around what spear phishing is out there, things of that nature. So are you guys thinking like that, in terms of services for customers? How does that play out? >> So where we, we're very consistent on what we consider is, privacy is number one for our customers, whether they're consumer customers or whether they're enterprise customers. Where we would use data, you had mentioned a lot of things, but where we would use some data across customer bases are typically for security things, so where we would see some sort of security impact or an attack or something like that that started to impact many customers. And we would then aggregate that information. It's not really customer information. It's just like you said, metadata, themes, or trends. >> John Furrier: You're not monetizing it. >> Yeah, we're not monetizing it, but we're actually using it to protect customers. But when a customer actually uses Google Cloud, that instance is their hermetically sealed environment. In fact, I think we just came out recently with even the transparency aspects of it, where it's almost like the two key type of access, for if our engineers have to help the customer with a troubleshooting ticket, that ticket actually has to be opened. That kind of unlocks one door. The customer has to say, "Yes," that unlocks the other door. And then they can go in there and help the customer do things to solve whatever the problem is. And each one of those is transparently and permanently logged. And then the customer can, at any point in time, go in and see those things. So we are taking customer privacy from an enterprise perspective-- >> And you guys are also a whole building from Google proper, like it's a completely different campus. So that's important to note. >> It is. And a lot of it just chains on from Google proper itself. If you understood just how crazy and fanatical they are about keeping things inside and secret and proprietary. Not proprietary, but not allowing that customer data out, even on the consumer side, it would give a whole-- >> Well, you got to amplify that, I understand. But what I also see, a good side of that, which is there's a lot of resources you're bringing to bear or learnings. >> Yeah, absolutely. >> The SRE concept, for instance, is to me, really powerful, because Google had to build that out themselves. This is now a paradigm, we're seeing a cloud scale here, with the Cloud Native market bringing in all-new capabilities at scale. Horizontally scalable, fully synchronous, microservices architecture. This future is a complete game-changer on functionality at the different scale points. So there's no longer the operator's room, provisioning storage here. >> And this is what we've been doing for years and years and years. That's how all of Google itself, that's how search and ads and Gmail and everything runs, in containers all orchestrated by Borg, which is our version of Kubernetes. And so we're really just bringing those leanings into the Google Cloud, or learnings into Google Cloud and to our customers. >> Jonathan, machine learning and AI have been the big topic this week on OpenShift. Obviously that's a big strength of Google Cloud as well. Can you drill down on that story, and talk about what Google Cloud is bringing on, and machine learning on OpenShift in general? Give us a little picture of what's running. >> Yeah, so I think they showed some of the service broker stuff. And I think, did they show some of the Kubeflow stuff, which is taking some machine learning and Kubernetes underneath OpenShift. I think those are very, very interesting for people that want to start getting into using AutoML, which is kind of roll-your-own machine learning, or even the voice or vision APIs to enhance their products. And I think that those are going to be keys. Easing the adoption of those, making them really, really easy to consume, is what's going to drive the significant ramp on using those types of technologies. >> One of the key touchpoints here has been the fact that this stuff is real-world and production-ready. The fact that the enterprise architecture now rolling out apps within days or weeks. One of those things that's now real is ML. And even in the opening keynote, they talked about using a little bit of it to optimize the scheduling and what sessions were in which rooms. As you talk to enterprises, it does seem like this stuff is being baked into real enterprise apps today. Can you talk a little bit about that? >> Sure, so I certainly can't give any specific examples, because what I think what you're saying is that a lot of enterprises or a lot of companies are looking at that like, "Oh, this is our new secret sauce." It always used to be like they had some interesting feature before, that a competitor would have to keep up with or catch up with. But I think they're looking at machine learning as a way to enhance that customer experience, so that it's a much more intimate experience. It feels much more tailored to whomever is using their product. And I think that you're seeing a lot of those types of things that people are starting to bake into their products. We've, again, this is one of these things where we've been using machine learning for almost 10 years inside Google. Things like for Gmail, even in the early days, like spam filtering, something just mundane like that. Or we even used it, turned it on in our data centers, 'cause it does a really good job of lowering the PUE, which is the power efficiency in data centers. And those are very mundane things. But we have a lot of experience with that. And we're exposing that through these products. And we're starting to see people, customers gravitate to grab onto those. Instead of having to hard code something that is a one to many kind of thing, I may get it right or I may have to tweak it over time, but I'm still kind of generalizing what the use cases are that my customers want to see, once they turn on machine learning inside their applications, it feels much more tailored to the customer's use cases. >> Machine learning as a service seems to be a big hot button that's coming out. How are you guys looking at the technical direction from the cloud within the enterprise? 'Cause you have three classes of enterprise. You have the early adopters, the power, front, cutting-edge. Then you have the fast followers, then you have everybody else. The everybody else and fast followers, they know about Kubernetes, some might not even, "What is Kubernetes?" So you have kind of-- >> Jonathan: "What containers?" >> A level of progress where people are. How are you guys looking at addressing those three areas, because you could blow them away with TensorFlow as a service. "Whoa, wowee, I'm just trying to get my storage LUNs "moving to a cloud operation system." There's different parts of this journey. Is there a technical direction that addresses these? What are you guys doing? >> So typically we'll work with those customers to help them chart the path through all those things, and making it easy for them to use and consume. Machine learning is still, unless you are a stats major or you're a math major, a lot of the algorithms and understanding linear algebra and things like that are still very complex topics. But then again, so is networking and BGP and things like OSPF back a few years ago. So technology always evolves, and the thing that you can do is you can just help pull people along the continuum there, by making it easy for them to use and to provide a lot of education. And so we work with customers on all ends of the spectrum. Even if it's just like, "How do I modernize my applications, "or how do I even just put them into the cloud?" We have teams that can help do that or can educate on that. If there are customers that are like, "I really want to go do something special "with maybe refactoring my applications. "I really want to get the Cloud Native experience." We help with that. And those customers that say, "I really want to find out this machine learning thing. "How can I actually make that an impactful portion of my company's portfolio?" We can certainly help with that. And there's no one, and typically you'll find in any large enterprise, because there'll be some people on each one of those camps. >> Yeah, and they'll also want to put their toe in the water here and there. The question I have for you guys is you got a lot of goodness going on. You're not trying to match Amazon speed for speed, feature for feature, you guys are picking your shots. That is core to Google, that's clear. Is there a use case or a set of building blocks that are highly adopted with you guys now, in that as Google gets out there and gets some penetration in the enterprise, what's the use, what are the key things you see with successes for you guys, out of the gate? Is there a basic building? Amazon's got EC2 and S3. What are you guys seeing as the core building blocks of Google Cloud, from a product standpoint, that's getting the most traction today? >> So I think we're seeing the same types of building blocks that the other cloud providers are, I think. Some of the differences is we look at security differently, because of, again, where we grew up. We do things like live migration of virtual machines, if you're using virtual machines, because we've had to do that internally. So I think there are some differences on just even some of the basic block and tackling type of things. But I do think that if you look at just moving to the cloud, in and of itself is not enough. That's a stepping stone. We truly believe that artificial intelligence and machine learning, Cloud Native style of applications, containers, things like service meshes, those things that reduce the operational burdens and improve the rate of new feature introduction, as well as the machine learning things, I think that that's what people tend to come to Google for. And we think that that's a lot of what people are going to stay with us for. >> I overheard a quote I want to get your reaction to. I wrote it down, it says, "I need to get away from VPNs and firewalls. "I need user and application layer security "with un-phishable access, otherwise I'm never safe." So this is kind of a user perspective or customer perspective. Also with cloud there's no perimeters, so you got phishing problems. Spear phishing's one big problem. Security, you mentioned that. And then another quote I had was, "Kubernetes is about running frameworks, "and it's about changing the way "applications are going to be built over time." That's where, I think, SRE and Istio is very interesting, and Kubeflow. This is a modern architecture for-- >> There's even KubeVirt out there, where you can run a VM inside a container, which is actually what we do internally too. So there's a lot of different ways to slice and dice. >> Yeah, how relevant is that, those concepts? Because are you hearing that as well on the customers? 'Cause that's pain point, but also the new modern software development's future way to do things. So there's pain point, I need some aspirin for that. And then I need some growth with the new applications being built and hiring talent. Is that consistent with how you guys see it? >> So which one should I tackle? So you're talking about. >> John Furrier: VPN, do the VPNs first. >> The VPNs first, okay. >> John Furrier: That's my favorite one. >> So one of the most, kind of to give you the backstory, so one of the most interesting things when I came to Google, having come from other large enterprise vendors before this, was there's no VPNs. We don't even have it on our laptop. They have this thing called BeyondCorp, which is essentially now productized as the Identity-Aware Proxy. Which is, it actually takes, we trust no one or nothing with anything. It's not the walled garden style of approach of firewall-type VPN security. What we do is, based upon the resource you're going to request access for, and are you on a trusted machine? So on one that corporate has given you? And do you have two-factor authentication that corporate, not only your, so what you have and what you know. And so they take all of those things into awareness. Is this the laptop that's registered to you? Do you have your two-factor authentication? Have you authenticated to it and it's a trusted platform? Boom, then I can gain access to the resources. But they will also look for things like if all of a sudden you were sitting here and I'm in San Francisco, but something from some country in Asia pops up with my credentials on it, they're going to slam the door shut, going, "There's no way that you can be in two places at one time." And so that's what the Identity-Aware Proxy or BeyondCorp does, kind of in a nutshell. And so we use that everywhere, internally, externally. And so that's one of the ways that we do security differently is without VPNs. And that's actually in front of a lot of the GCP technologies today, that you can actually leverage that. So I would say we take-- >> Just rethinking security. >> It's rethinking security, again, based upon a long history. And not only that, but what we use internally, from our corporate perspective. And now to get to the second question, yeah. >> Istio, Kubeflow, is more of the way software gets run. One quote from one of the ex-Googlers who left Google then went out to another company, she goes, she was blown away, "This is the way you people ship software?" Like she was a fish out of water. She was like, "Oh my god, where's Borg?" "We do Waterfall." So there's a new approach that opens doors between these, and people expect. That's this notion of Kubeflow and orchestration. So that's kind of a modern, it requires training and commitment. That's the upside. Fix the aspirin, so Identity Proxy, cool. Future of software development architecture. >> I think one of the strong things that you're going to see in software development is I think the days of people running it differently in development, and then sandbox and testing, QA, and then in prod, are over. They want to basically have that same experience, no matter where they are. They want to not have to do the crossing your fingers if it, remember, now it gets reddited or you got slash-dotted way back in the past and things would collapse. Those days of people being able to put up with those types of issues are over. And so I think that you're going to continue to see the development and the style of microservices, containers, orchestrated by something that can do auto scaling and healing, like Kubernetes. You're going to see them then start to use that base layer to add new capabilities on top, which is where we see Kubeflow, which is like, hey, how can I go put scalable machine learning on top of containers and on top of Kubernetes? And you even see, like I said, you see people saying, "Well, I don't really want to run "two different data planes and do the inception model. "If I can lay down a base layer "of Kubernetes and containers, then I can run "bare metal workloads against the bare metal. "If I need to launch a virtual machine, "I'll just launch that inside the container." And that's what KubeVirt's doing. So we're seeing a lot of this very interesting stuff pop. >> John Furrier: Yeah, creativity. >> Creativity. >> Great, talk about your role in the Office of the CTO. I know we got a couple of minutes left. I want to get out there, what is the role of the CTO? Bryan Stevens, formerly a Red Hat executive. >> Yeah, Bryan's our CTO. He used to run a big chunk of the engineering for Google Cloud, absolutely. >> And so what is the office's charter? You mentioned some CIOs, former CIOs are in there. Is it the think tank? Is it the command and control ivory tower? What's the role of the office? >> So I think a couple of years ago, Diane Greene and Bryan Stevens and other executives decided if we want to really understand what the enterprise needs from us, from a cloud perspective, we really need to have some people that have walked in those shoes, and they can't just be Diane or can't just be Bryan, who also had a big breadth of experience there. But two people can't do that for every customer for every product. And so they instituted the Office of the CTO. They tapped Will Grannis, again, had been in Boeing before, been in the military, and so tapped him to build this thing. And they went and they looked for people that had experience. Former VPs of Engineering, former CIOs. We have people from GE Oil and Gas, we have people from Boeing, we have people from Pixar. You name it, across each of the different verticals. Healthcare, we have those in the Office of the CTO. And about, probably, I think 25 to 30 of us now. I can't remember the exact numbers. And really, what our day to day life is like is working significantly with the product managers and the engineering teams to help facilitate more and more enterprise-focused engineering into the products. And then working with enterprise customers, kind of the big enterprise customers that we want to see successful, and helping drive their success as they consume Google Cloud. So being the conduit, directly into engineering. >> So in market with customers, big, known customers, getting requirements, helping facilitate product management function as well. >> Yeah, and from an engineering perspective. So we actually sit in the engineering organization. >> John Furrier: Making sure you're making the good bets. >> Jonathan: Yes, exactly. >> Great, well thanks for coming on The Cube. Thanks for sharing the insight. >> Jonathan: Thanks for having me again. >> Great to have you on, great insight, again. Google, always great technology, great enterprise mojo going on right now. Of course, The Cube will be at Google Next this July, so we'll be having live coverage from Google Next here in San Francisco at that time. Thanks for coming on, Jonathan. Really appreciate it, looking forward to more coverage. Stay with us for more of day three, as we start to wrap up our live coverage of Red Hat Summit 2018. We'll be back after this short break. (upbeat electronic music)