>> Live from San Francisco, it's theCUBE. Covering Google Cloud Next 2018. Brought to you by Google Cloud and its ecosystem partners. >> Hello everyone and welcome back it's theCUBE coverage live in San Francisco at Moscone South for Google Cloud Next 18, I'm John Furrier with Dave Vellante, next guest is Jennifer Lin, Director of Product Management, Google Cloud featured in Forbes as one of the power women at Google Cloud. Congratulations on your Forbes distinction. >> Thanks so much John. >> Great to see you. So we had a chat before the event, couple weeks ago leading up to it around Istio, Kubernetes. You're in charge of a lot of the cool, I would say the modern middleware. >> Yes. >> That's going on. I want to say middleware kind of in quotes, it's not really middleware, it's cloud, it's horizontally scalable. Take a minute to explain some of the areas you're working on and then the importance of Istio's announcement today that 1.0 generally available, huge news, it's kind of nuanced it's not as big as the cloud sources platform and some of the Cisco relationships, but huge progress. >> Yes. >> In this services, microservices, this is the key part. Take a minute to explain. >> Yeah, we're really excited to get to this week and I think the announcement of the cloud services platform of which, obviously, the evolution of Kubernetes and Istio are a key part. Now we've kind of changed the way people manage container environments, and now people are really writing really innovative services and microservices and the ability to manage that easily is really what Istio's all about. And do that in a secure way. >> So we had the CEO Sundar Pichai on the stage, of Google proper, as Diane Greene was also on stage. Sundar made the comment, this is the only event I could make a containers and Kubernetes joke. >> Yes, with the big containers. >> Translate, he's smart, he knows tech. Very strong tech culture here. Jennifer, explain to the people why Google Cloud is differentiating around APIs and services and open source. Why is that so important? >> At heart I think we really are a software innovation company, and Google is a company of developers that want to do creative things with software. As Diane said this morning, I think the, sort of, ability to do that in a way that hides the complexity, but also excites emerging developers with all the things that they can do, I think that's what we're seeing in cloud. Originally we started very much with the cloud natives who were doing very new types of consumer applications. As Sundar said, when we moved into doing business applications and more and more people were developing enterprise applications with a cloud native model, we started to see a big uptake and adoption of our cloud platform. And I think with a lot of the things we're doing in security and the ability to enable administrators to kind of, manage that in a more automated way, that's a lot of what I think we're differentiating around. >> So one of the headlines that I can see happening on these on SiliconANGLE or TechCrunch or some of the blogs and publications out there is Google Doubles Down on Kubernetes. >> Yes. >> And the announcement of Istio's general availability of 1.0 certainly is good news, what does that mean? What should people know about the importance of Kubernetes doubling down as a momentum point for Google and the importance of Istio? What is the real benefit to the customer? >> We've had a managed Kubernetes environment on GCP for four years now, but before that, Urs talked about a decade worth of understanding how to scale Kubernetes in an operational environment. So we've learned a lot of domain knowledge there that we're kind of baking into the software platform itself. Istio really models the way we do microservice management, as we launch billions of containers a week. So how do we essentially secure the service environment? How do we give really good visibility? We showed the service graph where we can see the latency between two services, and really hide a lot of the back end complexity that really, from an operational perspective, is causing a lot of toil for application developers as well as operators. >> I notice toil is a word that's being kicked around the Google community a lot, toil being headaches, pains, but I wanted you to take a minute to explain for the folks that are learning about Kubernetes for the first time. Kubernetes was donated, or donated by an open source but by Google, but prior to Kubernetes, you guys have been running Borg, which is the internal system. >> That's right. >> That's been the foundation of the scale of the service management for all of Google. >> That's right. >> Explain that important history there, and how you're making Kubernetes easy to consume because most companies aren't Google. >> Yes. >> Explain the little history and then how it translates to consumption. >> I think Borg was really built and designed to keep developer agility up and make sure that developers could be very productive, but we could run essentially at global scale the container orchestration environment. When Kubernetes was donated to the open source community, there were some things that needed to be defined, such that the abstractions could be very clean outside of a Google environment. But that framework, obviously, held up very well and hence the growth with Kubernetes. Istio, I think similarly, models a lot of the way that we've done service management with the service mesh within Google. Obviously the names are slightly different, but there's a lot of operational domain knowledge on best practices and how to essentially enable automation at a much more granular level of applications. Where it's not a bunch of proprietary applications, but you have a lot of loosely coupled systems coming together. >> So, Jennifer, the maturity curve of the developer community, obviously is in some bell shape. >> Yes. >> How does Google approach engaging with those developers? Are you trying to get leading edge guys that want to develop software the way Google develops software? Obviously you're trying to reach a bigger market, so how do you balance those two? >> I think that's where open source is the most exciting, 'cause whether it's kids in school or very experienced developers, number one the transparency, things move so fast, a lot of that is about developer reach. But also about the participation of developers to give back to the community and help evolve the system. For something like Kubernetes, obviously, and Istio, Google sort of bootstrapped that and donated it to the community, but since then, we've seen just incredible participation at things like Kubecon, and developer hackathons, et cetera. So that's both a model for growing the community, but also just to educate and share, essentially, a lot of the best practices in a different type of way than most software companies, I think. >> Well, and you've worked at a lot of very successful enterprise companies, some very profitable enterprise companies. I get the sense that profit is an outcome of doing good work at Google. >> Yeah. >> You don't wake up in the morning and say okay, how am I going to make money? >> Yeah. >> You say, how am I going to do work and you don't seem to be stressing. I guess it helps that you have $100 billion in the balance sheet. But is that the right way to think about how you guys think about the marketplace? >> Yeah, I think the goal is very clear for us and I know Sundar talked about it a lot, the alignment between our original mission at Google and the opportunity we see in Cloud. Data is exploding, new applications are being written in a way that really brings together worlds that didn't come together before. Healthcare applications where you need to share a lot of data, people need to do research, and you need to make it very easy to share, but at the same time it needs to be highly secure. We're under the same pressures as any other enterprise in terms of regulatory environments, et cetera, so making all of that easy, I think is the reason why open source and open ecosystems make a lot of sense to us. It's just the only way to move fast, and actually make sure that we're bringing the whole community with us. >> But not everybody takes that philosophy, obviously. It's one that you're attuned to. But when you think about Google's posture in this community, I mean you started kind of late to the enterprise game, don't seem to be too stressed about it, you're developing the ecosystem. We've seen in this world, some of the companies you work with, it's winner take all. >> Yeah. >> Is Cloud just so big that there's plenty of room for everybody? Or is it winner take all in different segments? How do you think about that? >> Our leadership, to Diane, basically really sees this as we're playing the long game. And it is about driving adoption more so than essentially quarter to quarter revenue. When we're reinventing how software is designed and delivered, and published, et cetera, and shared? I think it is not going to be the monetization per quarter, which, many of the companies, I think, have to be under the pressure for. Within Google, I think we really do see this as the future of software, and that's going to take some time, but yeah. Urs talked a lot about spend has gone up in many enterprise environments despite the fact that they are changing their environment. Automation is a way to bring down a lot of the cost, so we believe there's a lot of value to be captured there, but we're not in a race to essentially monetize every piece of every product we put out there. >> So how do you measure your success? Is it just a feeling that, yeah we're doing good work? Or adoption, or? >> Adoption and the happiness of our customers and the lead partners that we work with. Our leadership is very focused on that. We want to prove it out with some trusted partners and customers, and I think some of those were on stage today. Make sure that it's replicable, and make sure that we leave our options open. 'Cause you never know what's going to happen in the next year. >> I got to ask you about the on-prem solution that was demoed today >> Yup. >> Actually they put a little easter egg in the demo and then came back and said, oh by the way, that node was on-premise. >> Yep. >> And Cloud. One of the things we talked about, and you've been harping on this, about Kubernetes orchestrating an abstraction at higher levels of services. >> Yes. >> Both in the cloud and on-premise. >> Yes. >> It's happening now, that was really elegant. Is that a demo? Is that actually shipping code? How far along are you? >> Yeah. >> Where's the head room in this? Explain this important phenomenon, because this is multi-cloud, and I've been really negative on multi-cloud, until we see things like this. This is easy to understand. >> Yeah. >> Your thoughts? >> Now that you really have workload portability and a common abstraction layer, and a single point of administrative control, there's a lot you can do there. And that was really hard to do, I think, with the proprietary systems. That wasn't just a demo, a lot of customers are starting to see that they have to think about hybrid and multi-cloud in a different way. And using some of these innovative technologies with containerization, you don't have to worry about the kernel version and the OS and a lot of the toil that was in the system before. So yeah, I think we're coming at hybrid cloud and multi-cloud in a way that no other cloud provider is, and that was, I think, the start of what a lot of customers have waited for. >> Yeah, and certainly this is the benefit of a Kubernetes and Istio now has got some capabilities into it, policy and that's still going to evolve. The question I want to put to you, and I'll play the devil's advocate role. Shouldn't the multi-cloud be an independent group? Or if I'm going to say, "Okay Google, I'm nervous, you're going to do all this stuff." There's a trust there, how do you guys answer the naysayers who might say it should be an independent organization handling multi-cloud. What's the answer to that? >> I think that's why a lot of the partners that we worked on initially with something like Istio, IBM and Lyft, they also didn't want to be locked into any one cloud provider. And we've done some things in the marketplace where we believe that the future is hybrid and multi-cloud. I think from a technology perspective, just making sure that essentially we can define those interfaces in a way that's not tied to a vendor implementation, be transparent. We have in Istio things like partner mixer adapters, that ecosystem is growing very quickly, so that pluggable adapter model allows the whole ecosystem to participate. >> And the role of open source in all this, obviously STO, we were at the Linux Foundation's CNCF covering this pretty heavily in Denmark just recently, we've spoken about it. How does all the action happening here at Google Next impact open source? What's going upstream, what are some of the updates, can you share what's going on in open source with Google? >> Istio 1.0 is essentially an announcement about the open source effort. I think we also saw that many of our enterprise customers want a managed environment. So just like Kubernetes, we have the open source Kubernetes which is rockin' and rollin' along, we have our managed Kubernetes commercial offer. Now that there's a level of maturity in the managed Kubernetes environment, and people are excited that Istio 1.0 is getting more mature, they want that to be a part of the evolution of their managed Kubernetes environment. Which is why we're starting to see just the whole stack evolve. First we abstracted the infrastructure, now we can manage services, and then we can bring in a whole new type of ecosystem. So, it's very exciting. >> So here's a philosophical question for you, Dave and I always like to talk about old new way. So old IT is like horse and carriage, and buggy, and cloud is like the first car, now you got sports car. How do you explain all the under the hood examples of the engine? >> Yeah. >> The car just drives. You don't have to feed the horses the hay, what's the new benefits that the old world won't see with clarity? Can you tease out, from your perspective, what are some of those things that go away and say, wow, we used to do that? What are some of the things? >> I think, even within how we build our products, we're very focused on user experience. And sometimes the user is a developer, sometimes the user is an administrator, and sometimes the user is the end user, in our case, maybe the customer's customer. So we do a lot of UX research, but like you said, there's a lot of complexity in a car, but when I drive a car, I just want to drive the car. So the user experience for the driver is very different from the mechanic who's fixing the engine. There's no doubt that there is a lot of complexity in these large-scale, global distributed systems, but many of our enterprise customers don't want to know every little bit of how it's built. What they want to know is some declarative end-state of what they want to get to. The functions that they want or application that they're trying to drive. That is the maturity level that we're at, where Istio hides a lot of that complexity, provides a common service abstraction, but still gives essentially the administrators the things that they need out of the system. >> Well and it speaks to as well, and you guys talked about this in your interview, how software's being developed and how that's changing. When I deal with Spotify, if I have a problem, I don't call up. >> No. >> Their billing department, or their customer service department, I just do it. >> Yes. >> And that's the way software is going to be developed in the future. >> Yes. >> Versus the way most enterprise. >> And you talk about a great customer of GCP, Spotify, I use them everyday as well, but yeah, that is a lot about user experience. But what they've done with machine learning, to basically serve up the song that I want to hear that day, based on the playlists I had before, it really is changing how software is done. >> So if you look at some of these old metaphors like horses versus cars, you mentioned that. Jobs get automated away with that old model, but yet there's new jobs are created. >> Yes. >> So I want you to talk about what's going away and what's evolving. 'Cause the value is shifting up the stack with higher level sets of services and new abstractions. >> Yup. >> Which you don't need to know all the details, just magic happens for the customer. There's new value being created. >> Yup. >> You could almost look at the market and say, IT operations, decimated. Manual configuration, decimated. >> Yes, well. I mean that's the history. >> That's my words. >> Of technology. The history of technology is moving forward and automating things. For Google, obviously, we don't think of the software layer as just the infrastructure layer. A lot of what we're trying to get to is essentially with things like machine learning and analytics, and that's real business value that people really had too much toil to essentially stitch the systems together. >> Yes. >> Now as the platform evolves, I think it just becomes one stack. And we can put those tools into-- >> Is there an API administrator? 'Cause you start to see people starting wiring services together. >> Yep. >> Between building blocks. >> Yes. >> So almost the cloud model. Right? >> Yep. >> So is that a API administrator? Is it code? >> You know-- >> There's still a human component. We agree. >> Yes, yes. >> But what is that new role? >> I think we've always had the notion of API management, with cloud endpoints and our apogee acquisition. APIs are evolving with microservices, and a lot of the partners that essentially have been in that space are all re-basing on something like Istio where they can do service management at a higher level. The API is part of it. Within Google, we use things like protobufs, where you have structured data and message protocols that essentially are not just an API. We think about API and service management hand in hand. Both of those things I think are changing. >> So my final question for you, I want to get your advice to any of the practitioners out there or customers that really want to take cloud native because with the containers, Kubernetes and Istio, you can actually manage lifecycle of old stuff and still bring in the new. >> Yup. >> You guys do API service management, you got cloud endpoints, billing, commerce, marketplace, Kubernetes serverless, and Istio is kind of a focus group. What's your advice and what's coming next that people should be aware of? For the folks who want to go cloud native, want to put the more gas, less brake, put the pedal to the metal with cloud native and not foreclose or have to do a rip and replace. Manage their existing lifecycle applications and to bring in the new with cloud native. What's your advice? >> I think build for the future, make sure you don't get stuck in a silo. We often see that different pace of customers and the way they're moving to cloud native. Our tagline for this conference was also, we're bringing the cloud to our enterprise customers, they can move at their own pace. We recognize that sometimes the migration challenges are pretty tough with their legacy systems. But they have a much clearer view now, in terms of where software is going, so depending on the steps they want to take, we want to enable that either natively, with what we're doing with CSP, or enabling partners to take phased approach to that end state. >> Awesome, and ultimately the developers for the applications >> Absolutely. >> Will win on this. Jennifer Lin, Director of Product Management at Google Cloud here inside theCUBE, breaking down all the action around APIs, service management, and why it's important as the modern middleware within the cloud, enabling developers. I'm John Furrier with Dave Vellante. Back with more live coverage here in San Francisco after this short break. Stay with us. (electronic music)

>> Live from San Francisco, it's theCUBE, covering Google Cloud Next 2018, brought to you by Google Cloud and its ecosystem partners. (electronic music) >> Hello, everyone, welcome to theCUBE, here, live in San Francisco at Masconi South. We're here with Google Cloud Next Conference. It's Google Next 2018. It's theCUBE's exclusive three days of wall-to-wall coverage. I'm John Furrier, and I'm joined with my co-host Dave Vallente. Jeff Rick's here, the whole team is here. This is a big break out moment for Google Cloud and we're going to break it down for you. Going to have interviews with Diane Green coming in today, Google Executives, Google's top women in the Cloud, top customers, and top people within the ecosystem. Google Cloud is really going to the next level. This show is really about coming out party for two years of work that Diane Green and her team have been doing, transforming Google from the largest Cloud for their own business, to making Google Cloud consumable and easy to use with the technology for large enterprise customers as well as developers around the world, global platform. Dave, we had the keynote here. I'd say Google we're seeing, introduce their Google Cloud service platform GCP certifying partners, Cisco announced on stage they are re-selling Google Cloud, which takes a big objection off the table around not having a quote, "Enterprise ready sales force". Google is in every large enterprise, Google's Cloud is morphing into a large scale technology driven Cloud. The number one advantage they have is their technology, their OpenSource, and now a partnership with Cisco, and all the machine learning and all the infrastructure that they have are bringing out a new look. This is Google's coming out party. This is really two years of hard work, that Diane Green and the team have accomplished. Working, bringing on new people, bringing on a whole new set of capabilities. Checking the boxes for the table stakes, trying to get it to pull position, for the Cloud game, obviously Amazon is significantly ahead of everybody. Microsoft making great progress, their stock is up. Microsoft, although leveraging their core confidency, the enterprise and the office, and all the existing business that they do. Again a B to B, Google bringing in end-user centric view with all the automation. Big announcements. Google Cloud services platform, Histeo is now shipping in production, doubling down on Kubernetes, this is Google looking at new abstraction layers for developers and businesses. Diane Green, not the most elegant in her keynotes, but really hitting all her marks that she needed to hit. Big customer references, and really showcasing their competitive advantage, what they want to do, the posture of Google Cloud is clear, next is the execution. >> So here at Google Next 25,000 registered people, so big crowd. Diane Green said on stage 3000 engineers here, we want to talk to you. The Cisco announcements, classic case of a company without a Cloud, wanting to partner up with somebody that has a Cloud, Google, and Google, without a big enterprise sales presence. Obviously Cisco brings that. So kind of match made in heaven. Obviously, Cisco's got relationships with other Cloud providers, particularly Microsoft but, to me this makes a lot of sense. It's going GA in August, you also saw underneath that, GKE, Google Kubernetes Engine, now it's on prem, so you're seeing recognition of hybrid. We heard Diane Green talk about two years ago when she started John, she got a lot of heat from the analysts. You're not really an enterprise company, you got a long way to go, it's going to take you a decade. She basically laid down the gun and said, we are there. We'll talk about that. We'll talk about what leadership means. You just made a comment that Amazon is obviously in the lead. What is leadership? How does Google define leadership? Clearly they're leading in aspects of the Cloud. Scale, automation, OpenSource, contributing a lot, it makes me wonder, does this hundred plus billion dollar company with a hundred billion dollars in the bank, do they really care about how much money they make in the enterprise? Or are they trying to sort of change the way in which people do development, do programming, that's maybe a form of leadership that we really haven't often seen in the industry. I mean I go back, I harken back, not that it's an exact comparison, but you think about Xerox park and all the contributions they made to the industry, think about the contributions that Google's making with TensorFlow, with Kubernetes, with Istio, a lot of OpenSource chops giving to the community. And taking their time about monetizing it, not that a couple billion dollars or billion dollars a quarter is not monetization, but compared to 25 billion of Amazon, and what Microsoft's doing it's much smaller market share. >> I mean that's a great point about the monet, all the analysts and all the Wall Street guys are going to go to try to figure out, squint through the numbers try to figure out how you make money on this. We've been talking to a lot of the Google Executives and a lot of the engineers leading up to Google Next, we've had great relationship, some of their inside people. The common theme Dave that I'm hearing is absolutely they're playing the long game, but if Google's smart, they will leverage their retail business, ads and other things, and not focus on the short-term monetization, and that's pretty clear, some of the posture. That they're looking at this as an engineering culture, engineering DNA, OpenSource DNA, and they're about speed. When I press Google people and say, "What is the DNA of Google Cloud?". It all comes back down to the same thing, inclusive, open, speed. They're going to focus on how to make things faster, that has always been the culture at Google, make page loads faster, make things go faster. Amazon has the notion of, ship things as fast as possible at lower prices. Amazon is make stuff go faster and make it easy to use from a consumer standpoint so, easy of use has always been a consumer DNA of Google, and now with Cloud, if they don't focus on the short-term, they continue to march the cadence of open, speed, ease of use, and take that user-centric view, to make things easier that's key. I'm really impressed with the announcement, one little kind of technical kind of nuance is this Istio. Istio is an extension of Kubernetes, and this is where you're starting to see some signals from Google on where they're going to be scanning through with (mumbles). And that is as Kubernetes builds on top of containers, and as Kubernetes starts to be more of an orchestration layer, the services that are deployed in the Cloud are going to have more and more functionality. This is classic moving up the stack. This is an only an opportunity to build abstraction layers, that make things really easy to consume, and make things faster. If they can get that position, that beach head, they will enable developer greatness, and that'll maybe hopefully change the game a little bit, and sling shot them into a position that's different than what Amazon, I mean, what Microsoft's doing. Microsoft's just brute force, throwing everything at Cloud. The numbers look good on paper, but will that truly translate to ease of use, large scale, global deployment, managing data at scale. I mean Google's great some technology, and that is their number one thing that they have a their disposal. >> Well Istio, the classic case of dog fooding, right John? I mean there's Google, using tons and tons of micro services for its own purposes, enter gate, how do we simplify this? How do we automate this? And how do we pay it forward? And that's what they do, that's their culture. This is a company that's, again, talk about leadership, they spent well over $10 billion a year on Capex, you can argue easily they got the biggest Cloud in the world, certainly they got more underwater cable, the biggest network in the world, so these are forms of leadership. Diane Green talked about information technology powering every aspect of the business. I mean we've heard that since Nick Carr said IT doesn't matter, but now it seems like more than ever, it's more important. She also said CIO's realized they're not in the data center business, but yet they only have a small fraction of their workloads in the Cloud. This is why she said Google is seeing, and others I'm sure, seeing such big growth in the Cloud. But then she underscored, but we're modern Cloud. We're not lift and shift Cloud. We're not doing what Oracle's doing and sticking the existing apps in the Cloud. We're doing things differently. You talk about this a lot John, you talked to a couple of really high level women in Google, about the new development model, the new programming model, they're really changing the way in which people think about software development. >> Yeah I mean I think one of the things that's clear is that, the modern era can hear around software development. Software development life cycle, certainly we hear, Agile have been going on for the DevOps movement and that's kind of been out there, but what's changing now is that software engineering, or software development, isn't just computer science. You don't need three computer science degrees to do Cloud and do development. The aperture is widening on what computer science is, that's opening up more women in tech, and as Diane Green pointed out on her keynote, there's a re-engineering of business going on, there's new discoveries happening, and half the population is women, and so women should be part of making the products consumed by women and other people. So there's a huge opportunity to fill the gender diversity gap, but more importantly I think what's interesting about Google Cloud in particular is that they kind of figured out something, and it might have been a pop to their arrogance balloon but it used to be, "Oh, everyone wants to be like Google, 'cause we're so huge and we're great". 'Cause they are. Their technology is phenomenal, you look at what Google's built and Urs has been on stage, they have built probably the best most complex system to power their business, and all of a sudden that's come out from map produced paper, Kubernetes, which they're now doubling down on, Google has done amazing. They're about 10 to 15 years ahead of the market in terms of technology by my estimate. The problem that they've had when they first started doing Cloud was, oh just, you want to be like Google. No people don't want to be like Google, people can't be like Google, what they now understand is that people want what Google has, and that's ease of use, DevOps, fully com instead of libraries, com instead of interfaces, really ease of rolling out at scale applications. That's different. People want the benefits of what Google has for their business, not, they don't want to be like Google. I think that was the, I think that Diane Green two years ago, came in and reset. They've hired great enterprise people, and the question is can they catch up? How fast can they catch up? They're checking the boxes, they're doing the table stakes, and can they harvest the best that they're making? Auto ML is a great example. IT operations is going to be decimated as an industry sector. All the industry analysts and the financial analysts have not yet observed this but, anyone who's in the business of IT operations is going to get decimated. Automation's going to take that away and make it a service, it's going to be a human component, but the value is going to shift up the stack. This is something that we're seeing as to look at value of start ups, IT operations, AI operations, this is a new category of the industry, and Google is betting on that. That to me is a big tell sign. >> And we've been talking about the economics of that for years, but I want to come back to something you said. Google clearly was late to the enterprise party, and I think part of the reason you were touching on this is I think they underestimated the degree to which organizations, enterprise in particular, have all this technical debt built up. You can't just rip out and replace, these companies are making money with their existing Oracle databases, with their existing outdated processes, but they're making money, they're meeting Wall Street expectations, they're making their big bonuses so they can't just stop doing that. It'd be like Google to your point, but Google is playing the long game, they are doing something differently, and they're trying to help people get to this new era of software development, so I think that's a very very important point. >> Melody Meckfessel, one of the VP of Engineering, she is going to announce a survey that she did. It's interesting, they pulled the human aspect of development, and they asked the question, "What do you care about?". And developers care about generally the enterprise and kind of Cloud native developers, really two things. Technical debt, and time to push code. If technical debt accumulates, that's a huge problem, makes them unhappy, makes them kind of, not happy with how things are going, and then also speed. If you're shipping code it takes more than a few minutes to get back the commits that it hit. That's a problem. This is a huge issue. You said technical debt. Enterprise IT has been accumulating decades of technical debt, that's now running the company. So as re-engineering the business theme that Diane Green points out, really is spot on, people are going to stop buying IT and be deploying services more in the future, and using those services to drive business value. This to me is a big shift, this is what's going to hurt in (mumbles) and enterprises that, no one's buying IT. They're building platforms, the product is the platform, and the sense of services will enable applications to sit on top of them. This is an absolute mindset shift, and that impacts every vertical that we cover. You've covered IOT and everything else. The way CIOs think about this is they think about a portfolio, and it's just to simplify it. It's like run the business, grow the business, transform the business. And by far, the biggest investments are in run the business, and they can't stop running the business, they can't stop investing in running that business. What they can do is say, okay we can grow the business with these new projects and these new initiatives, and we can transform the business with new models of software development, as we transform into a digital company as a software company. So that it increasingly going to be pouring investments there, and it's slowly sunset, the run the business apps. It happens over decades. It doesn't happen over night. >> Well that's actually the number one point I think that didn't come out in the keynote but Earl's talked about it, where he said the old model is lift and shift. When we covered at the Linux foundation, and the CNC app, and the other shows that we go to is that what containers and Kubernetes are bringing to the market, the real value of that, is that existing IT CIOs don't have to rip and replace old apps, and that's a lot of pressure, the engineering requirements, there's personnel requirements, there's migration, so with Kubernetes and containers, containers and Kubernetes, you can essentially keep them around for as long as they need to be around. So you can sunset the applications and let the apps take its natural life cycle course, while bringing in new functionality. So if you want to be Cloud native right out of the gate, with Google Cloud, and some of these great services, like AI and machine learning that's going on, you can actually bring it in natively, containerize and with Kubernetes and now Istio, build a set of services to connect existing applications, and not feel the pressure and the heat, the budget for it, the engineer for it, to actually hire against it, to manage the existing life cycle. This is a huge accelerant for Cloud native. The rip and replace doesn't have to happen. You can certainly sunset applications at will, but you need to kill the old, to bring in the new. This is a very very important point. >> Yeah so a couple things that Diane Green hit on that I just want to go quickly through her keynote. She talked about, like you say, a small fraction of workloads are actually in the Cloud, but she asked the question, why Google? She said "Look, we're an enterprise company, but we're a modern enterprise company. We take all the information from that Cloud, we organize it, we allow you to put it back intelligently. We've got a global Cloud and it's unbelievably complex. We've got 20 years of scaling and optimizing, with that elite team. We've the most advanced Cloud in the world". She said, she didn't give the number, but many many football size, football stadium size data centers around the world that are carbon neutral with tons of fiber under the ocean, specialized processors, talked about Spanner, which is this amazing distributed, globally distributed consistent transactional database, big query, and she also talked about a consistency with a common core set of primitives. Now I want to ask her about that, 'cause I think she was taking a shot at Amazon, but I'm not sure, if they have a, to make a similar statement, so we're going to ask her about that when she comes on. She also said, the last thing I'll share with you is, "AI and security are basically hand in hand". She said security is what everybody's worried about, AI is the big opportunity, those are the two areas where Google is putting some of its greatest resources. >> That was my favorite sound bite by the way, she said, "Security's the number one worry, and AI is the number one opportunity". Really kind of points to it. On the primitive things, I don't think that's so much a shot at Amazon, as in it's more of multi Cloud. We've been kind of seeing multi Cloud vapor ware for months, past year, 'cause it kind of is. What we were seeing with Cloud native community and OpenSource is multi Cloud can only happen if you can run the same map across multiple Clouds with common interfaces, and that ultimately is I think what they're trying to solve. My favorite sound bites from her keynote is, she said, quote, "We've got 20 years scaling Google Cloud", it's obviously very large, number one Cloud, if you want to put Clouds in benchmarks and without (mumbles) of the enterprise number one, in terms of tech and scale. But she says, "My main job at Google two years ago was surfacing the great technologies and services, and make it easy to use. We have a technical infrastructure, TI, that has big query, Spanner, and then consistencies across all primitives", and she said on top of the technical infrastructure they got Gmail, Gsuite, maps, et cetera et cetera, powering at large scale, dealing with all the threat intelligence, and a ton of body of technology around II. And then to cap it all off, leader in OpenSource. To me this is where Google's betting big, with security as the number one worry, which is a major check box with AI kind of the catnip for developers. And they got security features. If you compare Amazon to Google Cloud, Amazon wins on sense of services in terms of number of features, but the question is, does Google have the right features? These are the questions we're going to have. And the dig at Amazon was Reed Hastings, Netflix CEO, friend of Diane Green, I've seen them both speak at Stanford, so she bumped into, what she said, "Reed Hastings is a power user of Google Chrome and Gsuite", and kind of said how great it is, but that's not Netflix. Now Netflix is an Amazon customer, so interesting jab there was about Reed Hastings personally but not about Netflix being a customer of Google Cloud. The question is, can Diane Green convince Reed Hastings to move Netflix from Amazon to Google Cloud? That's the question I'm going to ask her. >> The other piece of the keynote that I thought was quite interesting was Urs Holzle, who's the Senior Vice President of Technology Infrastructure who was doing Cloud before anybody talked about Cloud, he said, "Cloud's a fundamental shift in computing. GCP gives you access to unlimited computing on the world's largest network". Talked about Spanner, the globally consistent distributed database, ML APIs for doing speech and natural language recognition. Big query, the big data warehouse, basically a silo buster, but he said what's still missing, is essentially that hybrid (mumbles) all the Cloud's are different. I interpreted that meaning closed. So he said, "Things like setting up a network, provisioning a virtual machine, are all different". And basically to your point John, that stuff is going to get automated away. So Istio, they talked about Apogee, visibility, orchestration, serverless, they talked about GKE on prem, which is Google Kubernetes Engine on prem, and then Cisco came out on stage. The big partnership, the big news from the keynote. >> Lets talk about what we're going to look for this week in Google Cloud, and also within the industry. Dave I'll start. I'm looking for Google's technology architecture map, which I love, I think they've got a great solution, does that translate to the enterprise? In other words, can they take what Google has and make it usable and consumable for enterprises without having the be like Google strategy, use what Google has benefited from, in a way that enterprises can consume. I'm going to look for that, see how the technology can fit in there. And then I think the most important thing that I'm going to swing through all the hype here and the comment and the news and Kool Aid that they're spreading around, is how are they making the ecosystem money? Because if Google Cloud wants to take the long game, they got to secure the beach head of the viable, large scale Cloud which I think they're doing extremely well. Can they translate that into a ecosystem flourishing market? Does that make money for developers? They talk about going into verticals as a core strategy and healthcare being one. Can they go in there, in financial services, manufacturing, transportation, gaming and media, and attract the kind of partners and business customers that allow them to do better business? Does it translate the distribution for developers? Do businesses make more money with Google? That to me is the ultimate tell sign with how Google Cloud translates to the market place. Ecosystem, benchmark, and value to customers in terms of money making, utility of the users, and their customers' customers. >> So two things for me John. One is the same as yours is ecosystem. I learned from the SiliconANGLE editorial team, by the way, go to siliconangle.com, there's some great editorial to drop this week in support of just what's going on in Cloud and Google Next, but I learned from reading that stuff, Google late to the party. Only 13,000 partners. Amazon's got 100,000 Cloud partners. (mumbles) has 70,000 Cloud partners. Where, what's the ecosystem strategy, how are they going to grow? How are they going to help make money? The second thing is, basic question, I want to understand what Google wants in the Cloud. What's their objective? I know Amazon wants to dominate infrastructures of services, and be the leader there. I know that Microsoft wants to take its existing software state, bring it to the Cloud. I'm not really clear on what exactly Google's objectives are. So I want to get clarity on that. >> I think it's going to be developers, and one of the things we're going to dig into as the OpenSource. theCUBE coverage here in San Francisco, live coverage of three days wall-to-wall, (mumbles) Dave Vallante, stay with us. thecube.net is where you can find the live feed if you're watching this on SiliconANGLE or around the web, or with Syndicate. Go to thecube.net to get all the content, and siliconangle.com has a Cloud special this week. The team is putting out a ton of content. Covering the news, critical analysis, and what it means and the impact of Google Cloud into the industry and to their customers. So I'm John Furrier, Dave Vallante, stay with us, live coverage here, be right back. (electronic music)

>> Announcer: Live, from Boston, Massachusetts, it's the Cube. Covering Red Hat Summit 2017. Brought to you by Red Hat. (futuristic tone) >> Welcome back to the Cube's coverage of the Red Hat Summit here in Boston, Massachusetts. I'm your host, Rebecca Knight, along with my co-host Stu Miniman. We are welcoming right now Sam Ramji. He is the Vice President of Product Management Google Cloud Platforms. Thanks so much for joining us. >> Thank you, Rebecca, really appreciate it. And Stu good to see you again. >> So in your keynote, you talked about how this is the age of the developer. You said this is the best time in history to be a developer. We have more veneration, more cred in the industry. People get us, people respect us. And yet you also talked about how it is also the most challenging time to be a developer. Can you unpack that a little bit for our viewers? >> Yeah, absolutely. So I think there's two parts that make it really difficult. One is just the velocity of all the different pieces, how fast they're moving, right? How do you stay on top of all the different latest technology, right? How do you unpack all of the new buzzwords? How do you say this is a cloud, that's not a cloud? So you're constantly racing to keep up, but you're also maintaining all of your old systems, which is the other part that makes it so complex. Many old systems weren't built for modernization. They were just kind of like hey, this is a really cool thing, and they were built without any sense of the history, or the future that they'd be used in. So imagine the modern enterprise developer who's got a ship software at high rates of speed, support new business initiatives, they've got to deliver innovation, and they have to bridge the very new with the very old. Because if your mobile app doesn't talk to your mainframe, you are not going to move money. It's that simple. There's layers of technology architecture. In fact, you could think of it as technology archeology, as I mentioned in the keynote, right, this we don't want to create a new genre of people called programmer archeologists, who have to go-- >> I'm picturing them just chipping away. >> Sam: I don't think it'll be as exciting as Indiana Jones. >> No. >> Digging through layers of the stack is not really what people want to be doing with their time. >> Sam: Temple of the lost kernel. >> I love it. >> So Sam, it's interesting to kind of see, I was at the Google Cloud event a couple months ago, and here you bring up the term open cloud, which part of me wants to poke a hole in that and be like, come on, everybody has their cloud. Come on, you want to lock everybody in, you've got the best technology, therefore why isn't it just being open because it's great to say open and maybe people will trust you. Help explain that. >> Puppies, freedom, apple pie, motherhood, right. >> Stu: Yeah, yeah. (laughs) >> So there's a couple sides to that. One, we think the cloud is just a spectacular opportunity. We think about 1.2 trillion dollars in current spend will end up in cloud. And the cloud market depending on how you measure it is in the mid 20 billions today. So there's just unbounded upside. So we don't have to be a aspirational monopolist in order to be a successful business. And in fact, if you wind the clock forward, you will see that every market ends up breaking down into a closed system and a closed company, and an open platform. And the open platforms tend to grow more slowly, sort of exponential versus logarithmic, is how we think about it. So it's a pragmatic business strategy. Think about Linux in '97. Think about Linux in 2002. Think about Linux in 2007. Think about Linux in 2012. Think about Linux today. Look at that rate. It's the only thing that you're going to use. So open is very pragmatic that way. It's pragmatic in another direction which is customer choice. Customers are going to come for things that give them more options. Because your job is to future proof your business, to create what in the financial community call optionality. So how do you get that? In 2011, about eight other people and I created a nonprofit called the Open Cloud Initiative. And the Initiative is long since dead, we didn't fund it right, we kind of got these ideas baked, and then moved on. >> Stu: There's another OCI now. >> That's right, it's the Open Container Initiative. But we had three really crisp concepts there. We said number one, an open cloud will be based on open source. There won't be stuff that you can't get, can't replicate, can't build yourself. Second, we said, it'll have open access. There'll be no barriers to entry or exit. There won't be any discrimination on which users can or can't come in, and there won't be any blockers to being able to take your stuff out. 'Cause we felt that without open access, the cloud would be unsafe at any speed, to borrow a quote from Ralph Nader. And then third, built on an open ecosystem. So if you are assuming that you have to be able to be open to tens of thousands of different ideas, tens of thousands of different software applications, which are maybe database infrastructure, things that as a cloud provider, you might want to be a first party provider of. Well those things have to compete, or trade off or enrich each other in a consistent way, in a way that's fair, which is kind of what we mean when we say open ecosystem, but being able to be pulled through is going to give you that rate of change that you need to be exponential rather than logarithmic. So it's based on some fairly durable concepts, but I welcome you to poke holes in it. >> So we did an event with MIT a little while back. We had Marshall Van Alstyne, professor at BU who I know you know. He's an advisor at Cloud Foundry, and he talked about those platforms and it was interesting, you know, with the phone system you had Apple who got lots of the money, smaller market share as opposed to Android, which of course comes out of Google, has all of the adoption but less revenue. So, not sure it's this, yeah. >> Interestingly, we've run those curves, and you kind of see that same logarithmic versus exponential shift happening in Android. So we've seen, I don't have the latest numbers on the top of my head, but that is generating billions of dollars of third party revenue now. So share does shift over time in favor of openness and faster innovation. >> So let's bring it back to Red Hat here, because if I talk to all the big public cloud guys, Microsoft has embraced open source. >> And they're not just guys, actually, there's lots of women. >> Rebecca: Yes, thank you. >> Stu: I apologize. >> Sorry, I'm in a little bit of a jam here, where I'm trying to tell people the collective noun for technologists is not guys. >> Stu: Okay. >> It could be people, it could be folks, internally we use squirrels from time to time, just to invite people in. >> So, when I talk to the cloud squirrels, Microsoft has embraced open source. Amazon has an interesting relationship. >> I was there when that happened. >> You and I both know the people that they've brought in who have very good credibility in the open source community that are helping out Amazon there. Is it Kubernetes that makes you open because I look at what Red Hat's doing, we say okay, if I want to be able to live across many clouds or in my own data centers, Kubernetes is a layer to do that. It comes back to some of the things like Cloud Foundry. Is that what makes it open because I have choice, or is there more to it that you want to cover from an open cloud standpoint, from a Google standpoint? >> Open and choice effectively is a spectrum of effort. If it's incredibly difficult, it's the same as not having a choice. If it's incredibly easy, then you're saying actually, you really are free to come and go. So Kubernetes is kind of the brightest star in the solar system of open cloud. There's a lot of other technologies, new things that are coming out, like istio and pluri. I don't want to lose you in word soup. Linker D, container D, a lot of other things, because this is a whole new field, a whole fabric that has to come to bear, that just like the internet, can layer on top of your existing data centers or your existing clouds, that you can have other applications or other capabilities layered on top of it. So this permission-less innovation idea is getting reborn in the cloud era, not on top of TCP/IP, we take that for granted, but on top of Kubernetes and all of the linked projects. So yeah, that's a big part of it. >> I want to continue on with that idea of permission-less innovation and talk about the culture of open source, particularly because of what you were saying in the keynote about how it's not about the code, it's about the community. And you were using words like empathy and trust, and things that we don't necessarily think of as synonymous with engineers. >> Sam: Isn't it? >> So, can you just talk a little bit about how you've seen the culture change, particularly since your days at Microsoft, and now being at Google, in terms of how people are working together? >> Absolutely, so the first thing is why did it change? It became an economic imperative. Let's look at software industry competition back in the 90s. In general, the biggest got the mostest. If you could assemble the largest number of very intelligent engineers, and put them all on the same project, you would overwhelm your competition. So we saw that play out again and again. Then this new form of collaboration came around, not just birthed by Linux, but also Apache and a number of other things, where it's like oh, we don't have to work for the same company in order to collaborate. And all of a sudden we started seeing those masses grow as big as the number of engineers who went a single company. Ten thousand people, ten thousand engineers, share the copyright to the Linux kernel. At no point have they worked at the same company. At no point could a company have afforded to get all of them together. So this economic imperative that marks what I think of as the first half of the thirty years of open source that we've been in. The second half has been more us all waking up, and realizing open source has got to be inclusive. A diverse world needs diverse solutions built by diverse people. How do we increase our empathy? How do we increase our understanding so that we can collaborate? Because if we think each other is a jerk, if we get turned off of building our great ideas into software because some community member has said something that's just fundamentally not cool, or deeply hurtful, we are human beings and we do take our toys away, and say I'm not going to be there. >> That's the crux of it too. >> It's absolutely a cutthroat industry, but I think one of the things I'm seeing, I've been in Silicon Valley for 22 years, less three years for a stint at Microsoft, I've actually started to see the community become more self-reflective and like, if we can have cutthroat competition in corporations, we don't have to make that personal. 'Cause every likelihood of open source projects is you're employed as a professional engineer at a company, and that employment agreement might change. Especially in containers, right? Great container developers you'll see they move from one company to another, whether it's a giant company like Google, or whether it's a big startup like Docker, or any range of companies. Or Red Hat. So, this sort of general sense that there is a community is starting to help us make better open source, and you can't be effective in a community if you don't have empathy and you don't start focusing on understanding code of conduct community norms. >> Sam, I'm curious how you look at this spectrum of with this complexity out there, how much will your average customer, and you can segment it anywhere you want, but they say, okay I'm going to engage with this, do open source, get involved, and what spectrum of customers are going to be like, well, let me just run it on Google because you've got a great platform, I'm not going to have Google engineers and you guys have lots of smart people that can do that in any of the platform. How do you see that spectrum of customer, is it by what their business IT needs are, is it the size of the customer, is there a decision tree that you guys have worked out yet to try to help end users with what do they own, what do they outsource? It's in clouds more than outsourcing these days. The deal of outsourcing was your mess for less, and this should be somewhat more transformational and hopefully more business value, right? >> Yeah, Urs Hölzle, who's our SVP of Technical Infrastructure, says, the cloud is not a co-location facility. It is different, it is not your server that you shipped up and you know, ran. It's an integrated set of services that should make it incredibly easy to do computing. And we have tons of very intelligent women and men operating our cloud. We think about things like how do you balance velocity and reliability? We have a discipline called site reliability engineering. We've published a book on it, a community is growing up around that, it's sort of the mainstream version of dev ops. So there are a bunch of components that any company at any size can adopt, as long as you need both velocity and reliability. This has always been the tyranny of the or. If I can move fast I can break things, but even Mark Zuckerberg recently said you know, move fast and break fewer things. Kind of a shift, 'cause you don't want to break a lot of people's experience. How do you do that, while making sure that you have high reliability? It really defies simple classification. We have seen companies from startups to mom and pop shops, all the way to giant enterprises adopting cloud, adopting Google cloud platform. One of the big draws is of course, data analytics. Google is a deeply data intensive business, and we've taken that to eleven basically with machine learning, which is why it was so important to explain tense or flow, offer that as open source, and be able to move AI forward. Any company, at any size that wants to do high speed, high scale data analytics, is coming to GCP. We've seen it basically break down into, what's the business value, how close is it to the decision maker, and how motivated is an engineer to learn something different and give cloud a try. >> Because the engineer has to get better at working with the data, understanding the data, and deriving the right insights from the data. >> You're exactly right. Engineers are people, and people need to learn, and they need to be motivated to change. >> Sam, last question I have for you is, you've been involved in many different projects. We look at from the outside and say, okay, how much should be company driven, how much does a foundation get involved? We've seen certain foundations that have done very well, and others that have struggled. It's very interesting to watch Google. We'd give you good as we've talked on the Cube so far. Kubernetes seems to be going well. Great adoption. Google participates, but not too much, and Red Hat I think would agree with that. So congratulations on that piece. >> Sam: Thank you. >> What's your learnings that you've had as you've been involved in some of these various initiatives, couple foundations. We interviewed you when you were back at the Cloud Foundry, and things like that, so, what have you learned that you might want to say, hey, here's some guidelines. >> Yeah, so I think the first guideline is the core of a foundation is, the core purpose of a foundation is bootstrapping trust. So where trust is missing, then you will need that in order to create better contribution and higher velocity in the project. If there's trust there, if there's a benevolent dictator and everyone says that person's fine or that company's fine, then you won't necessarily need a foundation. You've seen a lot of changes in open source startups, dot coms that are also a dot org, shifting to models where you say well, this thing is actually so big it needs to not be owned by any one company. And therefore, to get the next level of contribution, we need to be able to bring in giant companies, then we create trust at that next level. So foundations are really there for trust. It's really important to be strong enough to get something off the ground, and this is the challenge we had at Cloud Foundry, it was a VMware project and then a Pivotal project, and many people believe this is great open source, but it's not an open community, but the technology had to keep working really well. So we how do we have a majority contributor, and start opening up, in a thoughtful process and bringing people in, until you can say what our target is to have the main contributor be less than 50% of the code commits. 'Cause then the majority is really coming from the community. Other projects that have been around for longer, maybe they started out with no majority. Those organizations, those projects tend to be self-organizing, and what they need is just a foundation to build a place that people can contribute money to, so the community can have events. So there's two very different types of organizations. One's almost like a charity, to say I really care about this popular open source project, and I want to be able to give something back, and others are more like a trade association, which is like, we need to enable very complex coordination between big companies that have a lot at stake, in which case you'll create a different class of foundation. >> Great, well Sam Ramji, thank you so much for being with us here on the Cube. I'm Rebecca Knight, and for your host Stu Miniman, please join us back in a bit. (futuristic tone)

>> Hey welcome back everybody. Jeff Frick here with theCUBE, we are on the ground in downtown San Francisco at the Google Next 17 Conference. It's this crazy conference week, and arguably this is the center of all the action. Cloud is big, Google Cloud Platform is really coming out with a major enterprise shift and focus, which they've always had, but now they're really getting behind it. And I think this conference is over 14,000 people, has grown quite a bit from a few years back, and we're really excited to have one of the powerhouse partners with Google, who's driving to the enterprise, and that's Intel, and I'm really excited to be joined by Raejeanne Skillern, she's the VP and GM of the Cloud Platform Group, Raejeanne, great to see you. >> Thank you, thanks for having me. >> Yeah absolutely. So when we got this scheduled, I was thinking, wow, last time I saw you was at the Open Compute Project 2015, and we were just down there yesterday. >> Yesterday. And we missed each other yesterday, but here we are today. >> So it's interesting, there's kind of the guts of the cloud, because cloud is somebody else's computer that they're running, but there is actually a computer back there. Here, it's really kind of the front end and the business delivery to people to have the elastic capability of the cloud, the dynamic flexibility of cloud, and you guys are a big part of this. So first off, give us a quick update, I'm sure you had some good announcements here at the show, what's going on with Intel and Google Cloud Platform? >> We did, and we love it all, from the silicon ingredients up to the services and solutions, this is where we invest, so it's great to be a part of yesterday and today. I was on stage earlier today with Urs Holzle talking about the Google and Intel Strategic Alliance, we actually announced this alliance last November, between Diane Green and Diane Bryant of Intel. And we had a history, a decade plus long of collaborating on CPU level optimization and technology optimization for Google's infrastructure. We've actually expanded that collaboration to cover hybrid cloud orchestration, security, IOT edge to cloud, and of course, artificial intelligence, machine learning, and deep learning. So we still do a lot of custom work with Google, making sure our technologies run their infrastructure the best, and we're working beyond the infrastructure to the software and solutions with them to make sure that those software and solutions run best on our architecture. >> Right cause it's a very interesting play, with Google and Facebook and a lot of the big cloud providers, they custom built their solutions based on their application needs and so I would presume that the microprocessor needs are very specific versus say, a typical PC microprocessor, which has a more kind of generic across the board type of demand. So what are some of the special demands that cloud demands from the microprocessor specifically? >> So what we've seen, right now, about half the volume we ship in the public cloud segment is customized in some way. And really the driving force is always performance per dollar TCO improvement. How to get the best performance and the lowest cost to pay for that performance. And what we've found is that by working with the top, not just the Super Seven, we call them, but the Top 100, closely, understanding their infrastructure at scale, is that they benefit from more powerful servers, with performance efficiency, more capability, more richly configured platforms. So a lot of what we've done, these cloud service providers have actually in some cases pushed us off of our roadmap in terms of what we can provide in terms of performance and scalability and agility in their infrastructure. So we do a lot of tweaks around that. And then of course, as I mentioned, it's not just the CPU ingredients, we have to optimize in the software level, so we do a lot of co-engineering work to make sure that every ounce of performance and efficiency is seen in their infrastructure. And that's how they, their data center is their cost to sales, they can't afford to have anything inefficient. So we really try to partner to make sure that it is completely tailor-optimized for that environment. >> Right, and the hyperscale, like you said, the infrastructure there is so different than kind of classic enterprise infrastructure, and then you have other things like energy consumption, which, again, at scale, itty bitty little improvements >> It's expensive. >> Make a huge impact. And then application far beyond the cloud service providers, so many of the applications that we interact with now today on a day to day basis are cloud-based applications, whether it is the G Suite for documents or this or that, or whether it's Salesforce, or whether we just put in Asana for task tracking, and Slack, and so many of these things are now cloud-based applications, which is really the way we work more and more and more on our desktops. >> Absolutely. And one of the things we look at is, applications really have kind of a gravity. Some applications are going to have a high affinity to public cloud. You see Tustin Dove, you see email and office collaboration already moving into the public cloud. There are some legacy applications, complex, some of the heavier modeling and simulation type apps, or big huge super computers that might stay on premise, and then you have this middle ground of applications, that, for various reasons, performance, security, data governance, data gravity, business need or IP, could go between the public cloud or stay on premise. And that's why we think it's so important that the world recognizes that this really is about a hybrid cloud. And it's really nice to partner with Google because they see that hybrid cloud as the end state, or they call it the Multi Cloud. And their Kubernetes Orchestration Platform is really designed to help that, to seamlessly move those apps from on a customer's premise into the Google environment and have that flow. So it's a very dynamic environment, we expect to see a lot of workloads kind of continue to be invested and move into the public cloud, and people really optimizing end-to-end. >> So you've been in the data center space, we talked a little bit before we went live, you've been in the data center space for a long, long time. >> Long time. >> We won't tell you how long. (laughing) >> Both: Long time. >> So it must be really exciting for you to see this shift in computing. There's still a lot of computing power at the edge, and there's still a lot of computing power now in our mobile devices and our PCs, but so much more of the heavy lift in the application infrastructure itself is now contained in the data center, so much more than just your typical old-school corporate data centers that we used to see. Really fun evolution of the industry, for you. >> Absolutely, and the public cloud is now one of the fastest growing segments in the enterprise space, in the data center space, I should say. We still have a very strong enterprise business. But what I love is it's not just about the fact that the public cloud is growing, this hybrid really connects our two segments, so I'm really learning a lot. It's also, I've been at Intel 23 years, most of it in the data center, and last year, we reorganized our company, we completely restructured Intel to be a cloud and IoT company. And from a company that for multiple decades was a PC or consumer-based client device company, it is just amazing to have data center be so front and center and so core to the type of infrastructure and capability expansion that we're going to see across the industry. We were talking about, there isn't going to be an industry left untouched by technology. Whether it's agriculture, or industrial, or healthcare, or retail, or logistics. Technology is going to transform them, and it all comes back to a data center and a cloud-based infrastructure that can handle the data and the scale and the processing. >> So one of the new themes that's really coming on board, next week will it be a Big Data SV, which has grown out of Hadoop and the old big data conversation. But it's really now morphing into the next stage of that, which is machine learning, deep learning, artificial intelligence, augmented reality, virtual reality, so this whole 'nother round that's going to eat up a whole bunch of CPU capacity. But those are really good cloud-based applications that are now delivering a completely new level of value and application sophistication that's driven by power back at the data center. >> Right. We see, artificial intelligence has been a topic since the 50s. But the reality is, the technology is there today to both capture and create the data, and compute on the data. And that's really unlocking this capabilities. And from us as a company, we see it as really something that is going to not just transform us as a business but transform the many use cases and industries we talked about. Today, you or I generate about a gig and a half of data, through our devices and our PC and tablet. A smart factory or smart plane or smart car, autonomous car, is going to generate terabytes of data. Right, and that is going to need to be stored. Today it's estimated only about 5% of the data captured is used for business insight. The rest just sits. We need to capture the data, store the data efficiently, use the data for insights, and then drive that back into the continuous learning. And that's why these technologies are so amazing, what they're going to be able to do, because we have the technology and the opportunity in the business space, whether it's AI for play or for good or for business, AI is going to transform the industry. >> It's interesting, Moore's Law comes up all the time. People, is Moore's Law done, is Moore's Law done? And you know, Moore's Law is so much more than the physics of what he was describing when he first said that in the first place, about number of transistors on a chip. It's really about an attitude, about this unbelievable drive to continue to innovate and iterate and get these order of magnitude of increase. We talked to David Floyer at OCP yesterday, and he's talking about it's not only the microprocessors and the compute power, but it's the IO, it's the networking, it's storage, it's flash storage, it's the interconnect, it's the cabling, it's all these things. And he was really excited that we're getting to this massive tipping point, of course in five years we'll look back and think it's archaic, of these things really coming together to deliver low latency almost magical capabilities because of this combination of factors across all those different, kind of the three horseman of computing, if you will, to deliver these really magical, new applications, like autonomous vehicles. >> Absolutely. And we, you'll hear Intel talk about Jevons Paradox, which is really about, if you take something and make it cheaper and easier to consume, people will consume more of it. We saw that with virtualization. People predicted oh everything's going to slow down cause you're going to get higher utilization rates. Actually it just unlocked new capabilities and the market grew because of it. We see the same thing with data. Our CEO will talk about, data is the new oil. It is going to transform, it's going to unlock business opportunity, revenue growth, cost savings in environment, and that will cause people to create more services, build new businesses, reach more people in the industry, transform traditional brick and mortar businesses to the digital economy. So we think we're just on the cusp of this transformation, and the next five to 10 years is going to be amazing. >> So before we let you go, again, you've been doing this for 20 plus years, I wasn't going to say anything, she said it, I didn't say it, and I worked at Intel the same time, so that's good. As you look forward, what are some of your priorities for 2017, what are some of the things that you're working on, that if we get together, hopefully not in a couple years at OCP, but next year, that you'll be able to report back that this is what we worked on and these are some of the new accomplishments that are important to me? >> So I'm really, there's a number of things we're doing. You heard me mention artificial intelligence many, many times. In 2016, Intel made a number of significant acquisitions and investments to really ensure we have the right technology road map for artificial intelligence. Machine learning, deep learning, training and inference. And we've really shored up that product portfolio, and you're going to see these products come to market and you're going to see user adoption, not just in my segment, but transforming multiple segments. So I'm really excited about those capabilities. And a lot of what we'll do, too, will be very vertical-based. So you're going to see the power of the technology, solving the health care problem, solving the retail problem, solving manufacturing, logistics, industrial problems. So I like that, I like to see tangible results from our technology. The other thing is the cloud is just growing. Everybody predicted, can it continue to grow? It does. Companies like Google and our other partners, they keep growing and we grow with them, and I love to help figure out where they're going to be two or three years from now, and get our products ready for that challenge. >> Alright, well I look forward to our next visit. Raejeanne, thanks for taking a few minutes out of your time and speaking to us. >> It was nice to see you again. >> You too. Alright, she's Raejeanne Skillern and I'm Jeff Frick, you're watching theCUBE, we're at the Google Cloud Next Show 2017, thanks for watching. (electronic sounds)