>> Live from San Francisco, its the CUBE. Covering Google Cloud Next 2018. Brought to you by Google Cloud and its ecosystem partners. >> Welcome back everyone this is the CUBE's live coverage in San Francisco Google Cloud's big conference, Google Next 2018, #googlenext18, I'm John Furrier with Jeff Frick bringing you live coverage. Melody Meckfessel, Vice President of cloud engineering at Google is here in the CUBE. She leads a lot of the managing 40,000 plus engineers making them happy and creating great code, friendly environment, doing great work. Just featured her in a story we did about the power of women in Google Cloud. Melody great to see you, thanks for coming on. >> Thank you so much for having me, it's great to be here. >> Today is a lot of developer announcements, we saw a lot of community discussions, new code. You guys talked cloud build. What is some of the news, let's get that out of the way, what's going on here at Google Cloud Next? >> Great. Very excited to announce and demo today, and it was a live demo, I don't know if you saw that, so we had some dramatic excitement waiting for the actual build. Yeah we're very excited to announce Cloud Build, which is a fully managed continuous integration and delivery platform. It lets developers build and test their applications in the cloud at any scale, and it's based on a lot of the lessons learned that we had within Google, iterating over the last two decades with developer and operator tools. Google does some crazy scale internally, and we're really excited to bring that automation and scale out to our customers. >> We had the chance to meet a couple weeks ago, we went deep dive on developers. You have a job focus that's really to kind of keep the developers productive, happy, there's a lot of them at Google and they are tough customers, they want to be coding. They don't want any distractions. They don't want any toil, a word we've been using a lot and hearing a lot here. And so there's techniques that you guys have done within Google, this seems to be the theme of Google Next, taking the best of Google and trying to make it consumable for customers. In this case developers. What is the state of the art to keeping developers happy, making them productive, more cohesive in their work, what are some of the things that you guys are doing, I know there's a lot going on, Google Cloud Build is one. What are some of the things you guys do to keep developers productive and happy? >> Yeah, that's a really good question. What we've found is that there's a tremendous amount of value of automating away, you said toil, the things that developers want to do. So some of the research, industry research that we've done, developers want to write code, they want to do design, they want to work on requirements. They don't want to take care of the plumbing and the pipeline of how their build test and release happens. So we showed some pretty amazing features today around automated canary analysis. So it's almost in a way, we want these tools and the automation to have the developer and the operator's backs. Because we know, we've learned at Google, that when we do that, they take more risks. They move quickly. Because they know that the DevOps tools are going to catch the breakages for them, and we showed a couple of things today around running tasks, identify if they're vulnerability scans, trying to find vulnerability scans before they get pushed out to production. We're trying to move as much as we can into the front part of the pipeline. So what makes developers happy? Well one thing is, give them automation so that they can focus on code. The second thing is, the culture to support and empower them. We've found that 65% of developers believe that they have the ability to choose their own tools. So at GC we want to make that easier for them. >> Wow you mentioned something earlier I want to get into. What's a canary? Explain what that is. Because a lot people, they know what it is, but some people might not know this canary concept. >> So essentially what you're trying to do is take the release that you build and test, make sure it's secure, now you want to start routing traffic to it. So you take that you release it to a small set of production instances, you start routing traffic to it, you look at air rates, you look at traces you sort of see what's going on, if it's good, then you slowly deploy it out to all your production instances. So it's a really safe way, it reduces your risk. Right, you want to catch the errors before they get out. >> Canary in a coal mine. >> Yeah, there you go. >> So it's a great agile way to push code and test it. Well not push code, push users to code. >> That's right. >> And get a feel for does it break. >> Yes. >> And if it breaks you pull back. >> Yes, and we want to find things ahead of time. I know you're talking to Dave Resin, you know the alignment of having shared goals between developers and operators is really important culturally because when you're incented towards minimizing, we call it the MTTR right, the minimum time to respond. So when you do things like canary analysis, you're finding the issues before they roll out and impact your user community. >> It's super valuable. But it sounds so easy. Why don't we just roll it out to like, our top users or the ones who won't leave the platform, and then pull it back? And this is a DevOps principle. If done right, works great. But it's hard to do. How hard is it to do it if you didn't have all these tools? I mean think about, you got to push code, pull the servers back, re push the new code. >> Yeah, you don't want to do that, right? Human error. >> Without automation, without all these tools, how hard is it? >> It's very difficult and time consuming. And we know, as humans, we're prone to error. Right? So it was really fun to show a live demo today of a spinnaker pipeline, showing the canary, pushing it out to production, and then going back to the website and seeing the impact of the code fixes that we put in place. >> Right, so just on the culture side, you've been at Google for a while. And you know we still think of Google, I still think of it as a supersized startup. But you guys have been at it for a while. You've been there for 13 years on LinkedIn, they company's 20 years old. How do you maintain kind of that cool, the colored bikes, the great food, you know go play volleyball outside in the middle of the day, kind of culture as the company just grows and you have so many new people. How do you maintain that baseline culture that's been there and made Google what it is today? >> You know we have a very strong culture within Google. A very strong engineering community. And that engineering community really comes from, and I think this has been consistent for the almost 14 years I've been there, using data to guide our decisions. Right? We've also put things in place to help enable the trust between the humans, which when I talk to customers, this is a challenge. Throw it over the wall to the operators, you know they don't trust each other. We've had blameless post-mortems within the engineering culture for decades. We've abstracted away, it's about learning. It's about continuous improvement. We're a software a company, and everyone's a software company now. How do you accept and learn from failure? But when you create this shared goals, use the data not someone's opinion or someone's title, and then ground. And we're learning, we're always learning. We're always making it better. That inspires people, right? To have that impact together. Now, the culture, the benefits, you know I'm working on writing code, products, I don't know the last time I played volleyball. >> Beautiful court, though. >> It looks great when you come in the building. >> You're the second, Dave also mentioned this blameless post-morten, I'd love to dig a little bit more in, because obviously that must be an institutionalized thing that you guys do. How do you do it without hurting feelings? Because it's still people, and even when it's data-based, you still kind of risk hurting people. So how do you institutionalize it's the data, it's not you, and we're actually trying to use this to learn and grow, not necessarily get on that particular person or that team for something that didn't work. >> Well you know I love this quote, it comes from SRE, if your SLO target is perfection, it's the wrong target. So we know, in software development and systems, that things break. And as humans, we're writing the code. We are writing the services. So we're going to make mistakes. And I think that tolerance and that understanding, we have some structure, right, we track to-dos that came out of the outage, we make sure that they get closed so we don't have the outage again, but when you obstruct that away, and know that maybe I made the mistake this week and maybe someone else on my team's going to make the mistake the next week. But how we learn from it and how we come together as a team is what's important. >> Blameless post-mortem is a great concept. Most people think post-mortem, something bad happened. Someone needs to be charged with a crime. Oh my god, bad things. You're learning, blameless post-mortem is an iteration of learning. >> Mm hmm, continuous improvement. >> So this is a culture, now let's take that to open source, because one of the things that's happening here that's front and center, I mean it's just natural for you guys, the importance of open source. Software development is getting more power. And you mentioned the stats and some of the cycle graphics. They can choose any tool that they want. That's a challenge for companies. Retaining them, keeping them employed, because they can get a job anywhere, they get more power, open source seems to be this balance in the force if you will. It's kind of like open source is now operationalized for that's where recruiting happens, that's where social activity happens, conferences. How important is open source, and how are you guys organizing around it as you build the cloud out, what's the vision? >> I have been so inspired by Google's increased contributions and collaborations to open source. I think we had over, I hope I get these stats right, we were contributing over 30,000 repos last year, 1% of the total contributions in 2017 on GitHub came from Googlers. We're committed to it. And we really believe that Google Cloud platform is living the open cloud. And we do that through open APIs, we do that through collaboration around open source tooling, and by creating this abundance and community ecosystem around it. And if you think about, I'll throw out another stat, 70% of developers feel a connection with each other. That's how they get inspired, that's how they learn. Think about Stack Overflow, you think about GitHub. You think about contributing to a product that you're going to make better, it's incredibly inspiring. >> Co-creation creates a bond. >> Yeah it does, it's connection. So if you look in the DevOps base, we've made some commitments with Bazil, which is we've open-sourced our build system, if you look at the contributions in the Go community in terms of Go working really well on Cloud. And then I showed Spinnaker which is actually a project that Netflix started, with their workloads, and we stocked up an engineering team to contribute to that to make it work for multi-cloud. Right, it's the right thing to do for developers, to have these tools that they can use in different, irrespective of where they're deploying. Now Google Cloud platform is the best platform to deploy to, but choice is really important. >> But it's another piece to the puzzle that you contribute to keeping them happy, right? Their participation in open source is why they still have their day job, and the accolades and kind of the peer feedback that comes from that is an important piece. So to be able to do that while still having the day job has got to be a big piece of what keeps them at Google, keeps them happy. >> It is, and you look at the community aspect around Kubernetes and TensorFlow, and the ecosystem is having such a huge effect on the innovation that's happening. And we all get to be a part of that, that's what's inspiring around Cloud. >> Opens the new competitive advantage, certainly from a retention standpoint, recruiting, and productivity. >> Yeah and productivity, absolutely. >> We believe in open, we're open conduct, we're co-creating content here at Google Next with the best minds at Google. Melody thanks for coming on, we really appreciate your time. >> Thank you so much, great to see you again. >> It's the CUBE out in the open here on the floor at Google Next, we're got more coverage. Stay with us after this short break.

>> Live from San Francisco. It's theCUBE covering Google Cloud Next 2018. Brought to you by Google Cloud and its ecosystem partners. (electronic music) >> Hey, welcome back everyone. Live here in San Francisco it's theCUBE's coverage of Google Cloud and their big conference Google Next #GoogleNext18. I'm John Furrier, Dave Vellante. Our next guest is Adam Seligman, Vice President of Developer Relations at Google. Man, making it all happen, keeping the trains on time, keeping everyone motivated, welcome to theCUBE. Thanks for joining us. >> Thanks, glad to be here. >> So, first of all, take a step back, what is your job at Developer Relations? Are you herding cats, are you feeding them great code, are you overseeing a big team? Google's been very big on open-source, you've been part of the code program going back many many years. Google's always been a steward of open-source and developers are just devouring open-source in a big way right now. What's your job? >> I look after Developer Relations. There's around 20, 22 million developers in the world and we want to make every single one of them successful and build cool things, learn new technology, be part of community. That's something that's super important. I try to rally all of Google to sort of stand for developers. >> One of the big trends we're seeing now at open-source is that it's becoming such a good norm. I remember the days when I was getting into the business back in the late '80s, early '90s. Open-source, we'd kind of steal some code here and it kind of was radical. It's so normal now, and you start to see the clean, upstream etiquette, upstream projects, everyone's contributing, co-creating for a common good, monetizing downstream has been really well defined. There's some examples of probably where that could be better but for the most part, I think people are generally seeing a positive contribution. That's a community dynamic. How do you go to the next level for developers? Because this has turned out to be quite an opportunity to one: learn, meet new people, learn new skills and take advantage of some new technologies. How do you foster that community? What are you guys doing? Because no-one wants vendors to put their fingers in these upstream projects (laughs) but they're super important, they're all participating. What's the formula? How is that evolving? How do you see that? >> Google's been an open-source for maybe 20 years. Some big contributions early days, things like GCC, foundational compiler technology. And we have whole businesses that build around open-source, Chrome on the Web, Android for mobile, and now we see kubernetes in cloud and TensorFlow and AI and new things like Knative and Istio, so I think there's a course there where open-source can really shape whole ecosystems and create a lot of opportunity and a lot of innovation. And I think the challenge in all that is to do it in a really healthy, positive, community-centric way. And I think that's some real learning we've had in the last couple of years, is great leaders like Sarah Novotny have really helped guide us and her interface with open-source communities and foster the right kind of community interactions, and that's a big focus. We're trying to bring that here also. >> So, you had a keynote coming up, I know you got a hard stop and we want to try and get as many questions as we can. But I want to ask you, what are you going to be talking about at your keynote, what's the topic? 'Cos this is a, I won't say coming-out party for Google Cloud in particular, but clearly setting a couple stakes in the ground on what's going on. Enterprise focus, checking the boxes, table stakes are being met. And real tech: high performance, large-scale, really a good developer environment. What are you going to talk about at the keynote? >> Well, I think customers like HSBC and Target and others are coming to us, not for table stakes, they're coming to us for what's next. They're coming to us for massive-scale kubernetes, they're coming to us for AI. So, I think that the introductions we've had so far, things like the Cloud Services Platform, Istio 1.0, Knative, it really shows a bright future of service and AI-driven applications. What we're going to talk in the developer keynote, tomorrow, in day three, is really three themes: innovation, openness and open-source, and then that community theme that we were just talking about. And one area of innovation that we're going to talk about is Melody Meckfessel, who I think you talked to earlier, is going to talk about our approach to Cloud Build and integrated toolchains. We have a lot of technology we're going to open up in the DevOps space. But it's really a mentality, and this is the thing that I think is really needed coming to Google, is it's not just about pushing code down the waterfall to production, it's about building services for users and building services that the developers consume. And really flowing from code right out to running services, and then when you're done, the service is a turn on for everybody, you start routing traffic to it, you run canaries. So, it's a big step-change in how we think about continuous delivery and DevOps, we really want to land that in the keynote tomorrow. >> So I got to give some props to my partner, John Furrier, in 2010, John, you said, "Data is the new development kit." It was a while ago, and it's turned out, in my view anyway, to be true, but, Adam, it's also changed the profile of the developer. Data hackers, statisticians, mathematicians, artists. And so it's changed the way in which we think about a developer. I wonder, if you could talk about that, in terms of, how that's changed Developer Relations? >> Yufeng Guo is going to do a section AI in the keynote and he does these videos on YouTube that literally millions of people watch about how to get started on machine learning. And he's got a great line in there, which I think is attributed to him, that says, "AI is programming with data." And so I think we're in a world where all this data of user interactions and event streams and interactive things and mobile applications, we now have a lot of data to program the world on. And I think it's an incredible opportunity for developers. But the flip side, if we just restrict it to a couple thousand data scientists, it doesn't open up the world to everyone. So I think beyond that 20 million, what are the next 20 million we could pull in with AutoML? The next 20 million that can do SQL queries and can use BigQuery and do ML in BigQuery? So that's the vision of opening it up to more people, more developers. >> And the democratization of software, I mean, it's interesting, that's my background in software engineering, computer science, in the '80s you were called software engineering. Then it became software developer, then it became a software hacker. Now we're hearing words like software artisan. I interviewed Aparna, she said, "You don't need three PhDs, three degrees "in computer science, to do development anymore." The aperture's widening, big-time, because now craft is coming back to development. Because a lot of these abstractions, both on the business and tech side, are enabling different personas to come in. >> It's not legacy development anymore, it's heritage development, right?. (John laughs) I love that developers have the freedom to define their own titles and define their own tools they want to work with, and do a mix of the old and the new, and mix it up. So I think it's really important that we're not too narrow in how we define people and you don't have to be this tall to ride the ride, we really welcome everybody in to be a part of the community and if your entrance to ML is AutoML, but then eventually you graduate to TPUs, that's just fantastic. >> And how about crypto developers? They've exploded with innovation, what do you see in there? >> I could just go back to security, I think every company is really wrestling with security right now. How do they get two-factor everywhere? How do they stop phishing? How do they keep their employees safe? How do they have shielded VMs at every level of security? And it's a challenge to get developers to think about security sometimes. It's the operators that have to live with it, and so understanding your dependencies, way back up with developers are like, "Oh, I'll just use this library, "and I'll just use this library." How do you ensure you're using trusted dependencies back there, you don't have vulnerabilities you're introducing by taking dependencies in other codes. So I think there's a lot of education and best practice to share with developers to get them to care about security. >> My final question, I know you got to go. I just want to get it out there, years ago, when David and I used to hear on theCUBE, people come on, "We want to win the developers," no, they're not winnable. You don't win developers, you earn trust and you earn relationships and they might work with you and enjoy the services that they might provide to them. So I always kind of used to poo-poo that. But now with the Cloud you're seeing again, more range with developers. So, how do you keep developers happy? That might be a better question, because in order to earn and have a relationship with people who are going to be contributing IP and building IP, how do you keep harmonious relations? How do you keep people happy if you have things, like technical debt bothers people and people are like, "Oh, technical debt," you know, shipping codes, times. How do you think about that because keeping people happy is a broad answer, but in general, what's your view on keeping developers happy, harmonious, loving, working together, doing the things they love to do? >> It's a little different at Google, it's an interesting place, because there's never an "us and them" with developers, this is a company with tens of thousands of engineers on staff, most of the senior leadership team have an engineering background. So it's more like we live in the community of developers, my engineers are all over the world, living in developer communities. And so I think it really does matter how we show up and how we interact. But we sort of live it every day. So I don't think we have a hill to climb, so much as get to developers, I think we just have to have a really clear narrative, and then a really keen ear to listen to what they need and that's what I'm trying to orient them around. >> Listening, I think that's a great answer, listening. "What do you want?" you know, "What's important to you?" And then you have that perspective yourselves. Yeah, I mean, we're sort of a developer-centric company and I think the important thing is we put them at the center of everything we do, I use the word with my team, it's empathy. We have empathy for developers, you know, they have great jobs, great opportunities, but also great challenges, and as humans, can't we have empathy for them. >> I was hosting a panel one time, a night event, it was all out of fun, bunch of nerds on there were talking tech, getting on the hood, talking developers, all this stuff, range of questions, and one guy introduced himself as the, "I'm the CTO, I'm the Chief Toy Officer." (Adam laughs) Because we play with technology then we turn it into product. And you guys brought a lot of toys out here with Google, all this open-source. >> And then if we can amplify that for all the amazing talent that's in the world, at Google I/O, we host the developers' student clubs from Indonesia, and these young Indonesian women are teaching other college kids how to do android development. So, if we could bring that kind of magic to all of our assets, to the Cloud assets, I think there's this amazing, receptive community out there that could give us a bunch of whole new ideas that we don't just get in South of Market, San Francisco. >> It's inspiring to see people build things with open-source, pay it forward, contribute upstream, be part of a community, this is what it's all about, Developer Relations. Congratulations, thanks for coming on theCUBE. >> Thank you, so glad to be here, thanks guys! >> This is theCUBE paying it forward with content here from Google Next, all out in the open, co-creating with Google, Google's team, Google's customers, the best engineers, the best talent here at Google Cloud, I'm with theCUBE. I'm John Furrier, Dave Vellante, thanks for watching. Stay with us, more coverage after this short break. (electronic music)

>> Live from San Francisco, it's theCUBE covering Google Cloud Next 2018, brought to you by Google Cloud and its ecosystem partners. (techy music) >> Hello everyone, welcome back to theCUBE's live coverage here. We're in San Francisco for Google Cloud's major conference, Next 2018. I'm John Furrier, here for three days. Wall to wall coverage on day one. We've got two great guests from SignalFX, Karthik Rau, founder and CEO, and Rajesh Raman, who's the chief architect. Signal's a hot startup in the area. Way ahead of its time, but now as the world gets more advanced, the solution is front and center as the value proposition if cloud moves into the mainstream, devops going to a world at large scale. Not just networking, monitoring, applications, you've got service meshes booming, great topic. Karthik, great to see you, Rajesh, thanks for joining us. >> Thank you. >> John, great to be on. >> So, first of all let's just get it out of the way, you guys have some fresh funding in May, so just quickly give an update on the company. You guys raised-- >> Yeah >> A series... >> A series D. >> Series D, give us, but how much? >> Yeah, so we raised $45 million from General Catalyst leading the round back in May, been building a ton of momentum as a company, close to a couple hundred people today. We're using a lot of that to expand internationally. We've got a team in Europe now, just opened up a team in Australia. So, things have been going great. >> Congratulations, we've had chats before, always been impressed. You guys have a great stable of awesome engineers and talent in the company doing some great work, but it begs the question, I always like to get into the what ifs. What if I could have large scale application development environments with programmable infrastructure, how does that change things? So, Karthik, what's... How as that what if changes, now that is what's happening you're starting to see the cloud at scale for the common masses of enterprises, where old ways of doing things are kind of moving away. It's like horse and buggy versus having a car for the first time-- >> Yeah. >> Jobs are changing, but the value doesn't necessarily change. You still go from point A to point B, you still got an engine, people who care about fixing cars, so people just want to drive the cloud, some people want to get under the hood, whole new architecture. >> Yeah. >> What's the what if of if I could have all these resources, what's the challenges and what do you guys solve. >> Well, I think there are a couple of challenges in this new environment. One is the number of components are just orders of magnitude more than they used to be in a cloud environment, right? We went from having physical machines that live for three years in a data center, divide it up into VMs 10 years ago, now divided up into containers for every process. Not only that, but these containers get spun up and spun down every few minutes or every few hours, and so it's just the number of components in the churn is just massive. So, that in and of itself requires a far more analytics-based approach to understand patterns rather than what's happening on an individual component. The second thing that's changed is the operating model's fundamentally different, because now you're building and running web services, and when you're running web services the people who build the software are the ones who technically are responsible for operating it. And so, you know, you have more updates, you've got more people involved, you've got lots of different components that all need to interact with one another, and so having a communication framework across all of these disparate teams become really, really, really critical. So, those are the two fundamental changes as you move from, you know, for operating these modern, massively distributed-- >> Yes. >> Applications. >> And I'll just add just some observation data that we've seeing in theCUBE is those same folks building aren't necessarily operators, so they want to be in and out fast, right? (laughs) >> They don't want to be running and operating all the time, they want to push some code. Melody Meckfessel here at Google ran a survey with developers and said, you know, "What makes you happy," and it was two things that bothered developers: technical debt and speed for deployments, commits, and the commit number was around minutes. If you can't get something done in minutes then they're onto something else, so the mind share attention of developers and technicos. So, this is a challenge at scale when you have technical debt, which we've seen companies come out of the woodwork, "Oh, yeah, "I'm going to automate something, "I'm going to throw some compute at it with the cloud "with the best monitoring package on the planet "and look how great it is," but all they did was just code some instrumentation and that's it. >> Mm-hmm. >> They weren't dealing with a lot of moving parts. Now as more things come in this is a challenge that a lot of companies face. You guys kind of solved this problem... >> Yeah, absolutely, so maybe Rajesh was a part of the team at Facebook that built the Facebook monitoring system, and that's actually what gave us a lot of the vision to start SignalFX five-and-a-half years ago, so maybe-- >> Tell about the protection, the vision-- >> Yeah. >> And what you guys are doing. >> Yeah, so CICD, you know, it kind of, like, underlies a lot of this vision of, like, moving fast. You mentioned that people wanted, like, you know, push their code in a few minutes... The thing that makes that possible is for you to have observability into what's happening while that push happens, because it's one thing to push very fast, it's another thing to recognize that you might have pushed something bad and to be able to revert it very quickly, too. And so, you'd only need, like, you know, good observability into all the things that matter that characterize the health of your system to be able to quickly recognize patterns, to be able to quickly recognize anomalies, and to be able to maybe push forward or even roll back very quickly. So, I think, like, observability is like a very key aspect of this entire CICD story. >> That's great, and that's great to know that you were over at Facebook because obviously Facebook built, at scale from the ground up, a lot of opensource. Obviously they contributed a lot to opensource, but it's interesting, as they matured and you start to see their philosophy change. It used to be move fast, break stuff. >> Yeah. >> To move fast, be reliable. >> Yeah. >> This is now the norm that's the table stakes in cloud. You have to move fast, you got to push code, but you got to maintain an operational integrity. This is, like, not like an option. This is, like, standard. >> Absolutely. >> How do you guys help solve that problem? >> So, I think there are a few different aspects to it. So, the first is to, you know, people need to ensure that they have observability into their application, so this is ensuring that you have the right kind of instrumentation in place. Thankfully this is kind of becoming commoditized right now and getting metrics from your system. The second part, and the more key part, is then being able to process this data in a real time way. You know, have high resolution, very low latency, and then to be able to do real time streaming analytics on this data. In highly elastic environments when things come and go very quickly, the identity of any individual, like, component is less important than the aggregate system behavior, and so you really need the analytics capability to kind of, like, go across this data, do various kinds of aggregations, compare it against past data, do predictive analytics, that sort of thing. So, analytics becomes the very key concept of, you know, how you operate these environments. >> It sounds so easy. >> Yeah, well one thing I'll add to that, so you know, to your point a lot of big companies sometimes are scared by this. You know, "How do we," you know... "We can't move quickly and break things," and everything that they've designed is around having process and structure to check and make sure everything is clean before they push changes out, and now we're in this world where, you know, an intern or a developer can push directly on a production, how do you manage that? The key thing in this modern world when you're trying to release software quickly, Rajesh hit on this earlier, you need the magic undo button. >> Yeah. >> That is the key to this entire process. You need to design your software, you need to design your process, and you need to design your tools so that if you introduce something bad you catch it immediately and you can roll it back. So, lots of devops practices are oriented around this, right? The idea of a canary release, I'm going to roll out an update to one percent of my systems and users, test it out, observe all the metrics, make sure everything is clean before I roll it out to everyone else, and the ability to roll back quickly is also important. But in order to do all of this you need the visibility, you need the metrics, and you need to be able to do analytics on it quickly to identify the patterns as they emerge. >> That's a great point and I'd love to just double down on that and get your thoughts because some of the Google Cloud people who are operating at this scale, I put them on this whole service-centric architecture, because they're services. We're talking about services, managing sets of services, having analytics, observation space, the reverting back and the undo button, the magic button do-over, whatever you want to call it, but the interesting thing is clean. Having a clean service whether it's an API, message queue, or an event, this stuff's happening all over the place in the new services world. How do you guys help there, is that where you guys get involved? Do you see up in that layer, how far up are you guys looking at some of the instrumentation and the insights? >> Yeah, you want to take that? >> Yeah, sure, so you know, the one thing that we really like about SignalFX and we were very keen on when we built the platform is that we are very agnostic about metrics. We're happy to accept metrics from anywhere, we'll take instrumentation-- >> (chuckles) You don't discriminate against metrics. >> We'll take instrumentation from cloud environment, we'll take, you know, metrics from opensource systems and premier applications, so you know, some of these systems are already kind of built in to get metrics from. You know, we talk to the Kafkas and Cassandras of the world, for example. We can also talk to GCP and AWS and grab metrics from their system. I think the interesting question is like when people really are taking the devops philosophy of, like, so how do you instrument your own application, what questions do you want to ask from your environment that answer the critical questions that you kind of have, and so you know, that's the one, that's the next step in the hierarchy of needs is for people to ask the right kinds of questions, and you know, instrument their applications properly. But like having done that, we can go up and down the stack in terms of, like, insight into whether all the way from your cloud environment through opensource systems, all the way up-- >> So, you guys'll take data from anyone, just stream it in-- >> Yeah. >> Normal mechanisms there, what's the value added, where's the secret sauce on SignalFX? >> So, I think value, it's all about analytics. We are all about analytics, so we are able to look at patterns of the data, we can go up and down the stack and correlate across different layers of software, look at interactions across components in your microservice, for example. You know, one really interesting thing that's happening, as you might be aware, like the whole service mesh aspect of it, which lets us, gives us insight into interactions between components-- >> Yeah. >> In a microservices architecture, so you know, we are able to get all that data and give you insight into how your whole system is working. >> So, you guys, you can see in the microservices layer? >> Absolutely. >> Yeah. >> That's powerful. >> And the key point is monitoring really has become an analytics problem, that's what we keep saying, right, because what's happening on an individual component is no longer as interesting as what's happening across the entire service, so you have to aggregate the information and look at the trend across the entire service, but the second thing that's really important is you need to be able to do it quickly, and this is where our streaming real time system really mattes. And people might ask, "Why does it "matter to do something real time." Like, "Seconds versus minutes, can a human actually "process something in seconds versus minutes?" Perhaps not, but everyone's moving towards automation, right? >> Yeah. >> So, if you want to move to a system where you have a closed loop, you have automation, and guess what, all of these modern systems, all the stuff that Google's talking here is all about automation. >> Yeah. >> And in that world seconds versus minutes, it means a tremendous amount of difference, right, where if you can find signals that will tell you there's an emerging problem within seconds and then you can revert a bad code push or you can auto-scale a cluster or you can, you know, change your load balancing algorithms all within seconds, that is what enables you to deliver, you know, 4.9s, 5.9s type of availability. >> And the consequences of not having that is outages-- >> Yeah, outages. >> Performance. >> Performance degradations, unhappy customers. I mean the cost to a brand now of having any kind of a performance issue is enormous, right? People are on Twitter before your team knows about it. (chuckles) >> Actually, you guys have a lot of the things you're solving, what is the core problem that you solve, what's the value proposition if you narrow it down that's high order bit for SignalFX? What's the corporate problem you solve? >> Well, we're solving the monitoring and observation problem for people operating cloud applications, so what happens is when you use SignalFX you have the confidence to move quickly, right? It gives you the safety net to be able to deploy changes on a daily basis, to have the shared context across a distributed team, so if you've got hundreds of two pizza box teams working together we give you that framework, the communication framework and the proactive intelligence to find issues as they emerge and proactively address them. And bottom line what that means is you can move as quickly as a Google or a Facebook or a Netflix even if you're a traditional Fortune 500 company that's regulated, and you know, you think you may not be able to do it but you really can. >> You give them the turbo charge, basically, for the analytics. All right, here's a question for you, what are the core guiding principles for the company? You guys obviously have a lot going on so you've got a core tech team, I mentioned it earlier. >> Mm-hmm. >> What are some of the guiding principles as you guys hire, build product, talk to customers, what's the key DNA of SignalFX? >> Yeah, I would say we are a very impact-driven company, so I'm, you know, very, very proud of all the people that we have on the team. We've got a lot of entrepreneurs who are focused on solving big problems, solving problems that customers may not necessarily know they need at the time, but as the market evolves we're there to solve it for them. So, we're a very customer-centric company. We have fantastic, we invest aggressively in technology, so it's not just about wrapping a pretty UI around, you know, Bolton Tech. We have real differentiated technology that solves real problems for people, and you know, I think we've in general just tried to skate to where the puck is and understand where the market's headed as a company. >> What are some of the customer feedback that you're getting? For folks that don't know SignalFX, what are some of the things that you're hearing from customers, why are you winning, what are some of the examples, can you share some color commentary? >> Yeah, I'll give one example, a Fortune 500 company that has been very aggressively investing in cloud the past, you know, four or five years, built an entire digital team, and their entire initiative is, like a lot of people in the Fortune 500 now, is to have a direct-to-consumer type of a relationship, and one of the things that they struggled with early was how do they move quickly, support product launches that might have massive load, and have the visibility to know that they can do that and catch issues as they emerge, and they didn't have a solution that could give that visibility to them until they leveraged SignalFX. And so now, if you talk to people there they'll say that they've essentially gone from defense every time they did one of these product launches to being on offense and really understanding what it takes to successfully launch a product and they're doing way more of these, so-- >> Moving the needle on time to market. >> Moving their business forward, you know, and digital transformation just by-- >> Yeah. >> Having SignalFX as a core enabler. >> It's the cloud version of putting out fires, so to speak, when you do product launches, right? >> Yeah. >> I got to ask you guys a question. You guys are both industry veterans, obviously Facebook has a storied history. We know all the great things that happen on the infrastructure side. Karthik, you've been in VM where you've seen the movie before where VM, where it made the market, changed IT for the better, still talk about the VMwares now. Now as we see cloud taking that next transformational push, describe the wave we're on right now, because it's kind of an interesting time in tech history where the talent that's coming in is pretty amazing. The young guns coming in with opensource the way it's flourishing is pretty phenomenal. Some of the smartest computer science and/or engineering talent is really solving what was old school B2B problems that really no one really wanted to solve. I mean, it was people were buying IT. Now you're talking about building operating systems, so the computer science kind of mojo in the enterprise has upped a bit. >> Mm-hmm. >> What's this wave about, how would you describe the wave of this time in history of the tech industry? >> Do you want to... (laughs) I'll add my take but why don't you go first. >> I think the thing that I find striking is just like, you know, when people used to talk about big data, you know, a few years ago, and now that is like, that's just normal. >> Yeah. >> And like, the amount of compute and the amount of storage that people are able to, you know, bring to command at-- >> Yeah. >> On any problem, it's just incredible, and that's just going to, I think, like continue to grow, right? That's going to be an amazing thing to watch. I think, you know, what this means... It also has interesting implications for, you know, companies like SignalFX who are trying to be in the monitoring space because the mojo used to be you had to have all this complicated software to do the instrumentation. Well, the instrumentations part is easy, but now all the value that's going to come about monitoring is in what you do with all that data, how you analyze it and look for, like, you know, so the whole AI ops and all that is going to be the key of the whole monitoring problem going forward, you know, five, 10 years from now, but we already see that analytics is such a key aspect of the whole thing, so... >> Yeah, I'm very, I think we're at the beginning, still at the beginning of a massive 30 to 40 year cycle, and this hasn't happened since the PC revolution in the 1970s, right, so the smartphone comes out 2007, massively opens up the market for software-based services to several billion people who are connected all the time now, drives a massive refresh of the backend infrastructure, drives the adoption of opensource, and so we're at this magical point now where the market for software-based services is just exploding, and every enterprise, you know, is becoming a software company, and you know, I think the volume of data that we're accumulating is just growing exponentially and what you can do with AI at this point, it's just... We're just beginning to see the benefit of it, so I think this is a really, really exciting time and I think we're just at the beginning. Most of the enterprises, and even the tech companies, are just beginning to capitalize on what is in store for us in the industry. >> I find it to be intoxicating, fun, and just great people coming in. To your point about the beginning of a 40 year run, also the nature of software development is being modernized at an extremely accelerated pace, so as people in the enterprise start re-imagining how they do software, because if they're a software company they've never had product managers. I mean, so the notion of what is a product, how do you launch a product, is all kind of first generation problems and opportunities, so I think to me it's really the enablement... And this is really what I think people are looking for is who can take the burden off my shoulders, help me move faster, more gas, less brake. >> Mm-hmm. >> Go faster, drive value, and then ultimately compete, because competitive advantage with technology... What does that mean to you guys, because how do you react to that because what you essentially are doing is creating instrumentation for enabling companies to create new value faster with technology and software, in some cases at a level that they've never seen before. What do you, how do you react to that? >> Well, I think that's exactly what we do, right, I mean, every company, I think most companies realized that they had to invest in software and focus on all these new opportunities at the early part of this decade. First thing they had to do was figure out who's going to build all this software, so most of them had to go hire engineers or build digital teams. They had to decide where are they going to run, the cloud wars of, you know, the early part of this decade. Do we build a private cloud, do we use a public cloud, I think both of those things have happened and people are now comfortable with those decisions. The third leg, which is squarely in the space that we're in, which is how do you operationalize this new model, and I think people are working through that now. As they get through that in the next few years, the companies like SignalFX helping every company, operationalize it very quickly, I think that's when the true promise of this new digital era will be realized where you'll start to see all of these fantastic applications, mobile apps, web service apps, direct-to-consumer streamlined supply chains. We're just beginning to see the benefit of that, and we'll see when that happens then the volume of data that they're collecting will increase exponentially and then the promise of machine learning and AI will take an altogether nother step. >> You got to know how to automate it before you can automate it, basically. What's next, final question for you guys, what's going on with SignalFX, what are you guys going to conquer, what's the next major milestones for you guys, what are you looking to do? >> Yeah, well we're continuing to focus on driving value for our customers, so we're expanding our geographic presence, so we're doing a lot of international expansion at this point. We're hiring a lot of engineers, so if anyone is interested in a development job, reach out to us. >> What kind of engineers are you looking to hire? >> Rajesh, you want to take that, sorry. (chuckles) What kind of engineers... >> What kind of engineers you looking to hire? >> Everything. (chuckles) >> I mean, all kinds of engineers, especially distributed systems engineers, front end engineers, full stack engineers, like real tech, all the good engineers we can get. >> (chuckles) Awesome. >> A lot of product development, there's a lot of interesting things happening in this space, and so we're, you know, continuing to invest very aggressively. >> Large scale distributed systems. >> Yep. >> You've got decentralized right around the corner, so you've got a lot of stuff happening. >> Yeah. >> Yeah. >> Great job to have you coming on, thanks for coming on, Karthik. >> Great, great to be on. >> Rajesh, thank you so much. >> My pleasure. >> SignalFX here in the cloud of Google here at Next, it's theCUBE, theCUBE cloud, CUBE data, we're bringing it all to you. I'm John Furrier, thanks for watching. More coverage, stay with us, we'll be back after this short break. (techy 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)