 Live from San Francisco, it's theCUBE. Covering Google Cloud Next 2018. Brought to you by Google Cloud and it's ecosystem partners. Okay, welcome back everyone. It's theCUBE live here in San Francisco for Google Cloud coverage, exclusive coverage for three days, day two. This is Google Next, hashtag Google Next 18. I'm Javier DeValante. Orientation is the director of product management at Google. I've been in the cloud business since I could remember cloud being cloud, variety of great career positions here now at Google doing product management, giving a talk on stage today in the keynote around serverless, around all the cool things going on. Or in great to see you, thanks for coming on. Good to see you again as well. So I know you got a hard stop, you got another press briefing, but I want to get out on the table real quick. Break down the news, the hard news, what happened today, set of announcements around what you were talking about with serverless and some of the cool things that are going on at that level. Yeah, so serverless is foundational to what we're doing at Google. The reality is that we started on serverless before it even had that term. App Engine was the OG serverless, if you will, and it's been around for 10 years. So what we've really been doing is trying to modernize and bring this to market. So we had a huge suite of announcements that came out today. We announced that Google Cloud Functions is GA. We announced App Engine Standard, which is this original product, has a whole suite of new languages and capabilities. We announced, of course, this new add-on for GKE, because one of the questions that comes up all the time is, I love the idea of serverless, but how do I move it around? Am I stuck in one place? So with the GKE add-on, you can take your workloads and move it into GKE. And then finally, On-Prem 2. On-Prem 2. Okay. And then finally, we announced the K-Native open-source project. And what that is, is the underpinnings of what makes up serverless, and that's something we've been working on with IBM and SAP, a whole bunch of partners, to try and move the future of serverless together forward in a portable open way. Well, congratulations on the functions. That got a big applause. Actually, the K-Native also got a great applause. Explain K-Native. Let's double down on that for a second. I want you to get that out. That's super important. What's that open-source project about? Where did it originate from? What's the purpose? What's the plans? Yeah, so, you know, in some sense, if you're watching this, I almost, you shouldn't even care about K-Native, right? So K-Native is infrastructure. And sometimes I think we get caught up in infrastructure because it's exciting, but as a developer, as a user, it's almost irrelevant. What K-Native is, is it's the building blocks for serverless. So the key is there's lots and lots of companies today that are building serverless products. We're building them. Red Hat's building them. I've been, everyone's building serverless products. And what we want to make sure is that customers have the ability to seamlessly move between them, that they can take advantage of serverless without being feeling trapped. So they can download the source code and maybe modify it. It feels a little bit like OpenStack in a way. So OpenStack is using K-Native moving forward. So the whole idea is this is an underpinning to give you common control plan APIs as well as execution APIs, as long as well as a reference implementation that everyone can build off of the shared pieces together. We're serverless meets Kubernetes. We're serverless meets Kubernetes. And let's be clear. Kubernetes is the orchestration layer for people who care. And so for people who care, now you have a serverless layer on top. And for people who don't care, you come to a cloud vendor and we're going to hide all of that for you. But you can still have the exact same control APIs. So if you think about it, you're writing things, I have 20 functions and I write scripts to manage all of those. You can now have the same APIs to manage them everywhere. So for the folks that are out there going, okay, hey, you know, we saw Amazon with Lambda, all the serverless craze. How do I get involved? What does serverless mean for me vis-a-vis what Google's offering? How would you answer that question? I would say start out with App Engine Cloud Functions. Those are our GA shipping products. They're scalable. They serve 350 billion requests every single day. This is the reality of where you get started. They support a wide range of languages. They're battle tested. They're available in multiple regions. This isn't a science experiment. This is real. That's where everyone should start. And then you can step from there and say, oh, maybe I have my own Kubernetes cluster and I want to look at the add-on. Maybe I have my own, my GK cluster. Maybe I have my own Kubernetes cluster running on-prem. Maybe you're doing something really unique and that's when you start getting into more of the infrastructure pieces. I want to get your reaction to a comment I heard in the hallways at an event just recently. Talk about functions. Yeah. Functions as a service kind of area. And the comment was, man, that's awesome. Startups going to love that. And the person said to me, actually the adoption we're seeing is from enterprises, more than startups and the alpha developers. Do you see the same thing? And if so, why would enterprises be more interested in functions and serverless than start-ups? Because start-ups are always the early adopters. I get that. But the uptake on serverless and functions has been much higher on the enterprise side. Is there a reaction to that? What's your thoughts on it? What's your reaction? Well, I think there's a number of things going on, including in some places, this dichotomy between startups and enterprises is maybe not the right one, right? And the reality is that there are developers looking to take advantage of the latest technologies everywhere. And in some ways it's almost demeaning to talk about start-ups as these stayed incapable of innovating companies. Because the reality is we see amazing developers everywhere. And so that's one aspect. Another is that functions solves a real problem right now that customers are having. And that is you are already doing a lot of DevOps orchestration work quite often. And you're running that on a server somewhere and it's just a mess, right? You might have cron jobs, you might have scripts running, you might have something, even something, ironically, we've actually known people running servers under the desk to manage their stuff in the cloud. I mean, we've heard crazy stuff like that. And so giving these ops teams an instant place to run it without ever having to worry about it again, it's a no-brainer for them. They instantly pick it up. So, you know, I'm smiling because, you know, we go back, just go back to when we won the clock in 2008, really where the word infrastructure as code really started to get in the inner circle of the cloud. I saw it certainly before that, but from 08 to like 2011, that became the mantra for DevOps, infrastructure as code. We're here. I mean, we're seeing it now. And Cisco's here providing network support. I mean, where are we? I mean, in your view, obviously it's happening. Where's the reality? Where's the work to be done? And where's the fantasy of- So much work to be done. Yeah. Maybe this is just a product manager in me, but I have to say, when I look out, I feel like we're, you know, 5% of the way up this mountain right now. And that just means that in 2008, we didn't even know we were on the right path. You got to say that. I mean, more hiring racks up open. You got to get more people hired in. No, but I mean, it's more reality now than ever before you're starting to see that. I mean, it's obviously- That's right. Where's that reality line go to where experimentation and then ultimately the moonshot? You know, if we look at the crust in the CASA model, we're still in the early adopters. There's no doubt. Now again, I want to split out that early adopters don't mean startups. Early adopters can mean forward-thinking enterprises. And we're seeing this happen across the board or even within an enterprise company. I mean, I see this very aggressively where there's no, even a company itself isn't a monolith, right? And so there's a team that's picking it up and trying this out, and then they disseminate that out. I think what we're seeing is a combination of infrastructure as code, dev ops practices, concepts like SRE, which are part of the hand we're talking about, these all come together and you can take advantage of serverless as part of that. And so the more, you know, each piece is great. And when it's one plus one plus one equals 20. And so we're seeing that multiplicative factor coming out as well. So if I'm an enterprise CIO, I want to get in, where do you want to take it? You know, what's the vision? Where should I get started? So where you get started is I'd say is you have things running today that this is an instant fit for. You can look at small infrastructure changes, small orchestration pieces that you're doing as well. You know, there's always this, always this incredible split that's happened between you have your hardcore investment that's going on. You know, you have your ERP systems. Let's be honest, you're never touching them, right? That's never changing. But you're doing innovation around it, right? You're thinking about how do I integrate this? What's the next in the future? And every time you're thinking about that, you should be thinking about serverless. And in fact, that's how you can see partners like SAP doing. I don't know if you saw the Kima announcement from SAP, right? That's exactly what that story is about. So what we see all the time is, one, take a look at some of this infrastructure orchestration, take a look at the DevOps pieces. And two, look at how you're extending the investments you already made and do it incrementally. Because what you'll find is, you can do something quick and easy. You know, get started in a week. And then the next thing, you know, like that was just one thing. And then I have 10 things, then I have 100 things. You know, wait, I'm actually maybe putting the majority of my effort into serverless now. Great. What's the most important story for you here at the show? You have to boil it down to the most relevant, the biggest story that you're telling here. We care about our customers. You know, there's a meta point. I think that cloud in general is a story of enablement, right? This isn't, hey, look at our cool products. I don't care about our products. Oh, there's some cool products, though. There are some cool products. But it's in the service of, how do we make our customers successful? And we're not doing the perfect job. I think we could be doing 10 times better highlighting what our customers are doing. But it's a story about our customers. And that's what we're here for. And that's when you look around what we're doing. It's here for the customers. And then you can see the visibility in Google Cloud. Obviously, a lot's just stayed over two years. Diane's here. A lot of enterprise chops are coming in. You're here. We had a partner. She's enterprise. She's amazing, that's right. Total enterprise leader. Just great people coming in. It seems to be much different. And then you got the, I love the term, OG, App Engine. That's right. So App Engine's still kind of hanging around. It's not just hanging around. It's exploding. It's doing great. And customers love it. I mean, the applause and the excitement we get. The reality is it was a little bit getting tired for a while and we've reinvigorated it. And we're seeing this explosion of love come out for it now. Well, congratulations. Good to see Google Arena. The big guns, the focus of data, big advantage, large scale, horizontally scalable, low latency capabilities. Really, this is the cloud magic happening again early. That's right. Yeah, a lot more work to do. What's on the roadmap? Give us a quick peek into the roadmap. What's going on? What's your priorities? So my priorities are, I really think that 50 plus percent of workload should be serverless. There's a lot of work we need to get there, right? We need to be able to run more things. We need to be able to run it in more places. We need to be able to, as you have these serverless things, you're actually creating your own problems, right? Now we get it's more complicated. You have microservices. How do you have, are we actually turning what was single app development into a distributed systems problem? Which we know is like the worst kind of problems. How do we up level our development teams that our customers have so that they can make the simple choices in these relatively complicated systems? So that's what we're trying to do. Run anything, run it anywhere and not worry about the complexity. And the automation and the AI really plays a big role there. I got, yeah, big time. Lauren, thanks for coming on. Great, great to see you. Say a lot of Olivia for us. I will do. Great to see you guys in a while. Great to see you. It's great to see you. Thank you. The Cube here, coverage here of Google Cloud here in San Francisco, the Cube live coverage. Day two of three years of wall-to-wall coverage. Go to siliconangle.com. We have great stories. You've got a cloud series, journalist special over there. A lot of reporting, a lot of news and analysis. Of course, thecube.net for all videos on demand after the show. I'm John Furrier, Dave Vellante. Stay with us for more coverage after this short break.