>> Live from San Francisco, it's the Cube. Covering Google Cloud Next 2018. Brought to you by Google Cloud and it's ecosystem partners. >> Hello, welcome everyone back to the Cube's live coverage. This is day three of Google Cloud Cube coverage here. Google Next 2018 #GoogleNext18. I'm John Furrier, my co-host Jeff Frick. Our next two guests kicking off day three, is Ed Anuff, the director of product management at Google Cloud, part of the Apigee acquisition, really part of the APIs and really a big part of the story here at Google Next, and Chuck Knostman, vice-president of IT at T-mobile customer. Ed, thanks for coming on. Chuck, thanks for coming on. So Apigee, a big part of the story at Google Next is, you know, the role of APIs and services. Huge, and I won't say nuanced. I mean, certainly Istio is new to a lot of people. Kubernetes, superly a very important piece of this new cloud service platform, as well as just running work loads, multicloud, etc. What's the focus, what's going on for you guys at the event. Take a minute to explain the announcements and what you guys did here at the show. >> Sure, so, APIs are how software talks to software. And what we announced this week at the show with Kubernetes and Istio are new ways for people to build software and deploy it, in new distributive fashions. And so that's creating new ways for tying your software together. Microservices, a lot of people are talking about now, are a key part of this. And so, from an Apigee perspective, you know, we're looking at facilitating how to make that communications happen, how to make it secure, how to make it efficient, how to monitor it. So what we announced was that Apigee is making it now possible for you to have all the tools that we've given you for managing your APIs, for, you know, getting your mobile apps to talk to your cloud services and all that, now is also going to apply to these new microservices that you're building. And so we think it's a pretty exciting thing. Lot of our customers have been asking for this, and obviously, uh, Chuck being one of them, and so, you know, that's what it's been all about for us this week. >> Chuck, obviously, APIs, key part of dev ops. You know, it first started with slinging some APIs around, stitching them together. Developers voted with their code, clearly APIs is the way that software's working. Microservices takes us to a whole nother level. Now, operationalizing APIs seems easy, but it's, you've got to start managing things differently. How are you guys taking that API and this new service management piece of it and kind of operationalizing APIs into T-Mobile? >> Yeah, we've been using Apigee for about four years now, and so over the time I think we were have 200 plus internal APIs, so we've over that time we've kind of learned how to operationalize that piece of it. Over the last couple of years we've really been focused on the microservice layers. Writing cloud-native applications, essentially. And that layer, and now with the Apigee hook into Istio, we're going to have a much better way to manage it. And it's really nice to see the platform starting to grow and mature along with us, so that's really great. >> I can only imagine how complicated it is to run real-time, cloud-native and have also legacy, and I think one of the things I'd like to get your thoughts on is, containers have become a nice piece of, not ripping and replacing to bring in the new. You don't have to kill the old to bring in the new. And now with containers, Kubernetes, and microservices and Istio, you have an ability to kind of do both. Talk about how you guys do it, cause this is like a perfect storm, in a good way, for enterprises. >> Well yeah, and it's really good timing for us as well. We're just now starting our Kubernetes journey on premise, if you will. So we're a big cloud-foundry shop. We're starting to put our legacy applications into docker containers and moving them, we'll be moving them onto Kubernetes. And so you can see the whole, the containerization shift as we go, as we go through time. And it's really, for us, like you said, it's fortuitous that at this timing because now with Istio coming in and being able to control all that, that's a great thing for us. >> Ed, talk about, you give a lot of history. To use, as normal APIs, it's lingua franca, it's been around for a while, you've had a lot of experience in that. But a lot of the enterprises that we talk to are like, there's a lot of pressure in IT to do more now with cloud-native. And now with the new services that are out there, it kind of takes the pressure off IT because the pressure of, oh, I got to sunset that app or I don't know when to kill that workload. I know I want to maybe transform it, but I don't want to have to disrupt all this stuff. So talk about the importance of nondisruption, because this seems to be a conversation that's talked a lot in the hallways. >> That's exactly right. So, you know, what you see within enterprises is that there's a need to deliver a whole set of new applications, and a lot of these are connected to digital experiences. Basically everything that you experience on your mobile apps, every new form of engaging with your customer. That's where a lot of the business growth is that's bringing, you know, a lot of the funding for these new initiatives. But, a lot of the core data of the enterprise is locked up within systems that have been operating very efficiently, but siloed for many years. And so that's the part that we see the most, which is, you know, folks within IT come to us and say, "Look, you know, I've been building these legacy systems "for many years now, and I know that if I can just take "the data that's locked up in these and bring these "into these new ways of doing business, "that it's going to have a huge impact on my business." And that's, you know, that's where the question sits. And then the follow up on that is, "Hey, you know, we want to, "we want to make our businesses more like the way, you know, "you guys are doing it in Silicon Valley. "And we, we see what you're doing with containers, "and we see things like Kubernetes, and cloud-native, "and we know that's the right way to build things, "but there has to be a way for us to bring "all of these other assets that we've been building "for the last 30 years along for the ride." And in fact for most of these businesses, our response is, "Hey, it's not just a question "of building along for the ride. "That, that's your core, that's your, that is been "what you built your business on. "So don't even just think about it "as this thing that you somehow have to drag along. "Think about how you actually can amplify it "because it's been the source of your business for so long." >> Yeah, the other I would add to that is that it gives us scale and operation, a much better operational platform to work with. For us, we've grown tremendously, or our growth has been tremendous over the last five years. We've gone from I think 30 million customers to 73 million customers, and frankly, to scale those systems up, containerization is probably the only way we can go with it. And with, from an operational standpoint, having one platform like Kubernetes to have, to operate for all of this stuff just helps us out tremendously. >> We hear that all the time. I think that's the biggest story around containers outside of geeking out on the benefits of it is that it really allows a nice bridge to the future. You don't have to burn the boats, as they say, in Silicon Valley, you know. >> And you can pick your, you can pick on the applications you want to keep around, right. Then you refactor 'em to be cloud-native on the ones you don't. You don't have to go all the way, right, and so you can make it much better that way. >> Chuck, I'm curious to get your take on the changing competitive environment. Cause before, you know, you had these big complex systems and you wanted to keep them running. Now the pressure for more innovation, more applications, quicker applications, to leverage not only your inside stuff but outside stuff, and how some of these technologies are helping you deliver that to your customers or your internal development team. >> Yeah, like I said, scale is one aspect of it. Performance is another, and the ability to move those workloads close to the customer just like Google's trying to do with moving closer to the customer, we do the same thing. Right, and so the hybrid cloud is real for us. We run in almost all the clouds right now, and on premise we treat that as a cloud as well. But being able to do that can only happen when we containerize stuff and utilize similar platforms on all these places. >> Right, and then you'll have this huge transformational shift over the next several years with 5G right, that's coming-- >> Yeah, yeah, and we've been at it for a couple years now. >> For a couple years, so this is going to be another huge wave of change inside your infrastructure. >> Yeah, sounds fantastic. >> What attracted you to Google Cloud? Share, take a minute to explain. What was the interest in Google Cloud. Why Google Cloud for your guys? >> Well we're just getting started with it, but it's really, it's the partnership we've had with Apigee that's helped us kind of understand what's going on with Google Cloud, but then the open-source nature of it as well as the focus on AI and ML. That's why we're really taking a hard look at what's going on with Google Cloud, and the attitude towards enterprises is great as well. >> Culture's a good fit there. >> Yeah, yeah, absolutely. >> Yeah, it's interesting, a lot of people are attracted by some of the speed. I mean, we've been hearing here at the show, you know, Google obviously has built their business on being fast. >> Yeah, well and having your own network is massive as well, right. >> And now you got the API. And what's the future look like for APIs and Apigee inside Google? Give us a little taste of what you guys are working on, some of the projects you guys are passionate about, and some of the successes you've had or any anecdotal use case studies. >> So definitely, so, you know, APIs carry our customers' most important data. And data's the basis for machine learning and AI, and so you're going to see a lot of product innovation for us about bringing, you know, AI to the point of these data conduits that are what APIs are all about. It's the natural place to couple it with every business process. So that's a big deal for us. I think that, you know, the security aspect, you heard a lot about security in the key notes. Again, you know, APIs are the conduit in many cases for, again, the enterprises most important data. To get outside of the perimeter of the enterprise, it has to be done in a secure way. You know, and then finally, being able to go and leverage the sort of collaborative nature, the stuff you see within open-source, the community around all of this, again, you know, most APIs are about bringing a lot more developers to, you know, build more applications in less time around these APIs and that is, that collaboration component is something that we see a ton of opportunities in terms of leveraging, you know, Google's unique know-how in terms of advancing and pushing this data that are in an API management. So I think you're going to see a lot of that from us. >> Chuck, I'd love to get your thoughts on how you in IT, obviously and IT's transforming, we talk about it all the time, how you keep track of what's good, right. It used to be in the old days the stack was pretty not that complex. And you go to Gartner or magic quadrant, oh they're a leader, I'll kick the tires, they come in, a vendor will come in, but some of the best cloud providers don't even show up on a magic quadrant because it's horizontally scalable. APIs changes the stack a little bit. A new modern middleware is emerging with Istio and new sets of business models and services are emerging. So a lot of people are like trying to be, how do you determine who's good. You know, in IT, because ou want to move the needle, you want to transform, you got a lot a build up. How do you kind of evaluate, is there any new ways, or is it gut instinct or specific things that you look at? >> Really good question. We look, we try to adopt the open-source stuff first. But we, from the company standpoint we also look at the company themselves and who's really vested in what's going on with it. Like, Apigee four years ago was really the only ones that were really only doing APIs, right. And their knowledge and the depth and their road map, that's what we really kind of look for. But to your point, things are changing so rapidly that you kind of have to go with the, watch the open-source community. Where are all the pull requests coming from, or what platforms are they going after? And then track that, and that's where, that's what we try to do. And so when we see Kubernetes and the explosion that's happening on that, the tooling that's coming around that, we know that's going to be good for enterprises going forward. So, we're going to be heavily investing in that platform. >> It's interesting, we always talk about developers, but what's interesting that's coming out of the show that we're observing is, it's always about developers do building apps. But the role of an operator inside IT, used to be an operator would, you know, maybe provision some storage and some servers. Now the role of what an operator, I mean, network op guys, now it's kind of like a more of a holistic view. Your thoughts on this. I know it's super early, but the emergence of these two personas in IT is super critical. >> Yeah, we look at it like it's automation, right. That's where it all comes to play. So if you've got a platform like a Kubernetes where you can have all this automation built around it, and you let the developers just do their thing and focus on the business logic, it's huge. So there is kind of two personalities, and the caring and feeding of that platform is just as important as the guys writing the applications across the top. >> Yeah, it's really a great environment. Final question for you guys. Observations on the show, Google Next. What's your observation, obviously you've got an API perspective, just globally looking down. If you kind of look, zoom out and look at, look down at the show, thoughts and commentary on what's happening here. >> You know, I think the scale of it has been amazing, you know, we became part of Google two years ago. We were here at the show last year, looking at it this year. And, the level of growth, the activity, attendees, the number of announcements, it's just been amazing. It's been very exciting for us to be a part of. >> Cool, Chuck your thoughts? >> Super impressed. This is our first one, really, that we've come to. We were even participating on the stage on the Knative, we wrote some applications to work with Knative. But, it's a, it's a very diverse crowd which is awesome. I think you really need that. Some of the others, I don't see as much. So I think what Google is doing, and again their approaches to enterprise, looking more at solutions, vertical solutions, very impressed with what's going on here. >> It's a really great time. Congratulations on all your success with the APIs. You guys have done the work, and open-source, it's where the, your employees want to work. They want to meet other people, and this is where the co-creation, that's where the assessments of the vendors happen. >> Opensource.T-Mobile.com, that's where we want to be. >> Alright, great. Well, Chuck, Ed, thanks so much. Really appreciate the time. It's the Cube live coverage here in San Francisco covering Google Cloud's conference, Next '18. We'll be right back with more day three coverage. Stay with us, we'll be right back. (light jazzy music plays)

(upbeat music) >> Welcome back everyone to Supercloud22, I'm John Furrier, host of theCUBE here in Palo Alto. For this next ecosystem's segment we have Muddu Sudhakar, who is the co-founder and CEO of Aisera, a friend of theCUBE, Cube alumni, serial entrepreneur, multiple exits, been on multiple times with great commentary. Muddu, thank you for coming on, and supporting our- >> Also thank you for having me, John. >> Yeah, thank you. Great handshake there, I love to do it. One, I wanted you here because, two reasons, one is, congratulations on your new funding. >> Thank you. >> For $90 million, Series D funding. >> Series D funding. >> So, huge validation in this market. >> It is. >> You have been experienced software so, it's a real testament to your team. But also, you're kind of in the Supercloud vortex. This new wave that Supercloud is part of is, I call it the pretext to what's coming with multi-clouds. It is the next level. >> I see. >> Structural change and we have been reporting on it, Dave and I, and we are being challenged. So, we decided to open it up. >> Very good, I would love it. >> And have a conversation rather than waiting eight months to prove that we are right. Which, we are right, but that is a long story. >> You're always right. (both laughs) >> What do you think of Supercloud, that's going on? What is the big trend? Because its public cloud is great, so there is no conflict there. >> Right. >> It's got great business, it's integrated, IaaS, to SaaS, PaaS, all in the beginning, or the middle. All that is called good. Now you have on-premise high rate cloud. >> Right. >> Edge is right around the corner. Exploding in new capabilities. So, complexity is still here. >> That's right, I think, you nailed it. We talk about hybrid cloud, and multi cloud. Supercloud is kind of elevates the message even better. Because you still have to leave for some of our clouds, public clouds. There will be some of our clouds, still running on the Edge. That's where, the Edge cloud comes in. Some will still be on-prem. So, the Supercloud as a concept is beyond hybrid and multi cloud. To me, I will run some of our cloud on Amazon. Some could be on Aisera, some could be running only on Edge, right? >> Mm hm >> And we still have, what we call remote executors. Some leaders of service now. You have, what we call the mid-server, is what I think it was called. Where you put in a small code and run it. >> Yeah. >> So, I think all those things will be running on-prem environment and VMware cloud, et cetera. >> And if you look back at, I think it has been five years now, maybe four or five years since Andy Jassy at reInvent announced Outposts. Think that was the moment in time that Dave and I took this pause back and said "Okay, that's Amazon." who listens to their customers. Acknowledging Hybrid. >> Right. >> Then we saw the rise of Snowflakes, the Databricks, specialty clouds. You start to see people who are building on top of AWS. But at MongoDB, it is a database, now they are a full blown, large scale data platform. These companies took advantage of the public cloud to build, as Jerry Chen calls it, "Castles in the cloud." >> Right. >> That seems to be happening in all areas. What do you think about that? >> Right, so what is driving the cloud? To me, we talk about machine learning in AI, right? Versus clouded options. We used to call it lift and shift. The outposts and lift and shift. Initially this was to get the data into the cloud. I think if you see, the vendor that I like the most, is, I'm not picking any favorite but, Microsoft Azure, they're thinking like your Supercloud, right? Amazon is other things, but Azure is a lot more because they run on-prem. They are also on Azure CloudFront, Amazon CloudFront. So I think, Azure and Amazon are doing a lot more in the area of Supercloud. What is really helping is the machine learning environment, needs Superclouds. Because I will be running some on the Edge, some compute, some will be running on the public cloud, some could be running on my data center. So, I think the Supercloud is really suited for AI and automation really well. >> Yeah, it is a good point about Microsoft, too. And I think Microsoft's existing install base saved Azure. >> Okay. >> They brought Office 365, Sequel Server, cause their customers weren't leaving Microsoft. They had the productivity thing nailed down as well as the ability to catch up >> That's right. >> To AWS. So, natural extension to on-premise with Microsoft. >> I think... >> Tell us- >> Your Supercloud is what Microsoft did. Right? Azure. If you think of, like, they had an Office 365, their SharePoint, their Dynamics, taking all of those properties, running on the Azure. And still giving the migration path into a data center. Is Supercloud. So, the early days Supercloud came from Azure. >> Well, that's a good point, we will certainly debate that. I will also say that Snowflake built on AWS. >> That's right. >> Okay, and became a super powerhouse with the data business. As did Databricks. >> That's right. >> Then went to Azure >> That's right. >> So, you're seeing kind of the Playbook. >> Right. >> Go fast on Cloud Native, the native cloud. Get that fly wheel going, then get going, somewhere else. >> It is, and to that point I think you and me are talking, right? If you are to start at one cloud and go to another cloud, the amount of work as a vendor for us to use for implement. Today, like we use all three clouds, including the Gov Cloud. It's a lot of work. So, what will happen, the next toolkit we use? Even services like Elastic. People will not, the word commoditize, is not the word, but people will create an abstraction layer, even for S3. >> Explain that, explain that in detail. So, elastic? What do you mean by that? >> Yeah, so what that means is today, Elasticsearch, if you do an Elasticsearch on Amazon, if I go to Azure, I don't want enter another Elasticsearch layer. Ideally I want us to write an abstracted search layer. So, that when I move my services into a different cloud I don't want to re-compute and re-calculate everything. That's a lot of work. Particularly once you have a production customer, if I were to shift the workloads, even to the point of infrastructure, take S3, if I read infrastructure to S3 and tomorrow I go to Azure. Azure will have its own objects store. I don't want to re-validate that. So what will happen is digital component, Kubernetes is already there, we want storage, we want network layer, we want VPM services, elastic as well as all fundamental stuff, including MongoDB, should be abstracted to run. On the Superclouds. >> Okay, well that is a little bit of a unicorn fantasy. But let's break that down. >> Sure. >> Do you think that's possible? >> It is. Because I think, if I am on MongoDB, I should be able to give a horizontal layer to MongoDB that is optimized for all three of them. I don't want MongoDB. >> First of all, everyone will buy that. >> Sure. >> I'm skeptical that that's possible. Given where we are at right now. So, you're saying that a vendor will provide an abstraction layer. >> No, I'm saying that either MongoDB, itself will do it, or a third party layer will come as a service which will abstract all this layer so that we will write to an AP layer. >> So what do you guys doing? How do you handle multiple clouds? You guys are taking that burden on, because it makes sense, you should build the abstraction layer. Not rely on a third party vendor right? >> We are doing it because there is no third party available offer it. But if you offer a third party tomorrow, I will use that as a Supercloud service. >> If they're 100% reliable? >> That's right. That's exactly it. >> They have to do the work. >> They have to do the work because if today I am doing it because no one else is offering it- >> Okay so what people might not know is that you are an angel investor as well as an entrepreneur been very successful, so you're rich, you have a lot of money. If I were a startup and I said, Muddu, I want to build this abstraction layer. What would be funding advice that you would give me as an entrepreneur? As a company to do that? >> I would do it like an Apigee that Google acquired, you should create an Apigee-like layer, for infrastructure upfront services, I think that is a very good option. >> And you think that is viable? >> It is very much viable. >> Would that be part of Supercloud architecture, in your opinion? >> It is. Right? And that will abstract all the clouds to some level. Like it is like Kubernetes abstract, so that if I am running on Kubernetes I can transfer to any cloud. >> Yeah >> But that should go from computer into other infrastructures. >> It's seems to me, Muddu, and I want to get your thoughts about this whole Supercloud defacto standard opportunity. It feels like we are waiting for a moment where there is some sort of defacto unification, whether it is in the distraction layer, or a standards body. There is no W3C here going on. I mean, W3C was for web consortium, for world wide web. The Supercloud seems to be having the same impact the web had. Transformative, disruptive, re-factoring business operations. Is there a standardized body or an opportunity for a defacto? Like Kubernetes was a great example of a unification around something for orchestration. Is there a better version in the Supercloud model where we need a standard? >> Yes and no. The reason is because by the time you come to standard, take time to look what happened. First, we started with VMs, then became Docker and Containers then we came to Kubernetes. So it goes through a journey. I think the next few years will be stood on SuperCloud let's make customers happy, let's make enough services going, and then the standards will come. Standards will be almost 2-3 years later. So I don't think standards should happen right now. Right now, all we need is, we need enough start ups to create the super layer abstraction, with the goal in mind of AI automation. The reason, AI is because AI needs to be able to run that. Automated because running a work flow is, I can either run a workflow in the cloud services, I can run it on on-prem, I can run it on database, so you have two good applications, take AI and automation with Supercloud and make enough enough noise on that make enough applications, then the standards will come. >> On this project we have been with SuperCloud these past day we have heard a lot of people talking. The themes that developers are okay, they are doing great. Open source is booming. >> Yes >> Cloud Native's got major traction. Developers are going fast and they love it, shifting left, all these great things. They're putting a lot of data, DevOps and the security teams, they're the ones who are leveling up. We are hearing a lot of conversations around how they can be faster. What is your view on this as relative to that Supercloud nirvana getting there? How are DevOps and security teams leveling up to devs? >> A couple of things. I think that in the world of DevSecOps and security ops. The reason security is important, right? Given what is going on, but you don't need to do security the manual way. I think that whole new operation that you and me talked about, AI ops should happen. Where the AI ops is for service operation, for performance, for incident or for security. Nobody thinks of AI security. So, the DevOps people should think more world of AI ops, so that I can predict, prevent things before they happen. Then the security will be much better. So AI ops with Supercloud will probably be that nirvana. But that is what should happen. >> In the AI side of things, what you guys are doing, what are you learning, on scale, relative to data? Is there, you said machine learning needs data, it needs scale operation. What's your view on the automation piece of all this? >> I think to me, the data is the single, underrated, unsung kind of hero in the whole machine learning. Everyone talks about AI and machine learning algorithms. Algorithms are as important, but even more important is data. Lack of data I can't do algorithms. So my advice to customers is don't lose your data. That is why I see, Frank, my old boss, setting everything up into the data cloud, in Snowflake. Data is so important, store the data, analyze the data. Data is the new AI. You and me talk so many times- >> Yeah >> It's underrated, people are not anticipating how important it is. But the data is coming from logs, events, whether there is knowledge documents, any data in any form. I think keep the data, analyze the data, data patterns, and then things like SuperCloud can really take advantage of that. >> So, in the Supercloud equation one of the things that has come up is that the native clouds do great. Their IaaS to SaaS is interactions that solve a lot of problems. There is integration that is good. >> Right. >> Now when you go off cloud, you get regions, get latency issues- >> Right >> You have more complexity. So what's the trade off in the Supercloud journey, if you had to guess? And just thinking out loud here, what would be some of the architectural trade offs of how you do it, what's the sequence? What's the order of operations to get Superclouding going? >> Yeah, very good questions here. I think once you start going from the public cloud, the clouds there scale to lets say, even a regional data center onto an Edge, latency will kick in. The lack of computer function will kick in. So there I think everything should become asynchronous, right? You will run the application in a limited environment. You should anticipate for small memories, small compute, long latencies, but still following should happen. So some operations should become the old-school following, like, it's like the email. I send an email, it's an asynchronous thing, I made a sponsor, I think most of message passing should go back to the old-school architectures They should become asynchronous where thing can rely. I think, as long as algorithms can take that into Edge, I think that Superclouds can really bridge between the public cloud to the edge. >> Muddu, thanks for coming, we really appreciate your insights here. You've always been a great friend, great commentator. If you weren't the CEO and a famous angel investor, we would certainly love to have you as a theCUBE analyst, here on theCUBE. >> I am always available for you. (John laughs) >> When you retire, you can come back. Final point, we've got time left. We'll give you a chance to talk about the company. I'm really intrigued by the success of your ninety million dollar financing realm because we are in a climate where people aren't getting those kinds of investments. It's usually down-rounds. >> Okay >> 409 adjustments, people are struggling. You got an up-round and you got a big number. Why the success? What is going on with the company? Why are you guys getting such great validation? Goldman Sachs, Thoma Bravo, Zoom, these are big names, these are the next gen winners. >> It is. >> Why are they picking you? Why are they investing in you? >> I think it is not one thing, it is many things. First all, I think it is a four-year journey for us where we are right now. So, the company started late 2017. It is getting the right customers, partners, employees, team members. So it is a lot hard work went in. So a lot of thanks to the Aisera community for where we are. Why customers and where we are? Look, fundamentally there is a problem to solve. Like, what Aisera is trying to solve is can we automate customer service? Whether internal employees, external customer support. Do it for IT, HR, sales, marketing, all the way to ops. Like you talk about DevSecOps, I don't want thousands of tune ups for ops. If I can make that job better, >> Yeah >> I want to, any job I want to automate. I call it, elevate the human, right? >> Yeah. >> And that's the reason- >> 'Cause you're saying people have to learn specialty tools, and there are consequences to that. >> Right, and to me, people should focus on more important tasks and use AI as a tool to automate those things right? It's like thinking of offering Apple City as Alexa as a service, that is how we are trying to offer customer service, like, right? And if it can do that consistently, and reduce costs, cost is a big reason why customers like us a lot, we have eliminated the cost in this down economy, I will amplify our message even more, right? I am going to take a bite out of their expense. Whether it is tool expense, it's on resources. Second, is user productivity And finally, experience. People want experience. >> Final question, folks out there, first of all, what do you think about Supercloud? And if someone asks you what is this Supercloud thing? How would you answer? >> Supercloud, is, to me, beyond multi cloud and hybrid cloud. It is to bridge applications that are build in Supercloud can run on all clouds seamlessly. You don't need to compile them, re-clear them. Supercloud is one place to build, develop, and deploy. >> Great, Muddu. Thank you for coming on. Supercloud22 here breaking it down with the ecosystem commentary, we have a lot of people coming to the small group of experts in our network, bringing you in open conversation around the future of cloud computing and applications globally. And again, it is all about the next generation cloud. This is theCUBE, thanks for watching. (upbeat music)

>> Narrator: From San Mateo, California, it's theCUBE, covering SnapLogic Innovation Day 2018. Brought to you by SnapLogic. >> Hey, welcome back here, Jeff Frick here with theCUBE. We're at the crossroads, it's 101 and 92 in San Mateo, California. A lot of popular software companies actually started here, I can always think of the Siebel sign going up and we used to talk about the movement of Silicon Valley from the chips down in the South Bay and Sunnyvale, and intel, really to a lot of software here in the middle of the peninsula. We're excited to be here at SnapLogic's headquarters for Innovation Day, and our next guest is Craig Stewart, he's the VP of product management. Craig, great to see you. >> Thank you very much. Welcome. >> Absolutely So, we're talking about API's, and we go to a lot of tech shows and the API economy is something that's talked about all the time. But really that has evolved for a couple reasons. One, is the proliferation of Cloud services, and the proliferation of applications in the Cloud services. We all know if you go to Google Cloud Next or Amazon re:Invent, the logo slide of absent services available for these things is tremendous. Give us kind of an update, you've been involved in this space for a long time, how its evolving what you guys are are working on here at SnapLogic. >> What we've seen change of late, is that not only is there a requirement for our customers to build API's, but also to then allow those API's to be consumed by their partners and networks out there. As a part of that, they may need to have more management of those API's, then we provide. We're very good at creating API's with inbound and outbound payload, parameters, all of those things, so we can create those data services via our API's, but customers then need to have a requirement now to add some functionality around. What about when I have a thousand users of these, and I need to be able to throttle them and those kinds of things. What we've seen happening is there's been this space of the full lifecycle API management technologies, which have been available for some time, and amongst those we've had Google Apigee kind of being the benchmark of those with the Apigee Edge platform, and in fact what we've done in this latest release is we've provided engineered integration into that Apigee Edge platform so that the API's that we create, we can push those directly into the Apigee Edge platform for them to do the advanced authentication, the monetization, the developer platform around it to develop a portal, all of those kind of things. In addition to that, we've also added the functionality to generate the open API specification, Swagger, as it's known, and to be able to take that Swagger definition to having generated it, we can then actually drop it into the API gateways provided by all of the different Cloud vendors. Whether it's Amazon with their API gateway or the Aggre gateway, all you need to do is then take that generated Swagger definition, and this literally is a right-mouse button, "open" API, and it generates the file for you, from there just drop that into those platforms and now they can be actually managed in those services directly. >> I want to unpack API lifecycle management, cos just for a 101 for people that aren't familiar. We think of API's and we know applications or making calls, and it's, "I'm sending data from this app to that app, "and this is pulling information from that app to this app." That's all pretty straightforward, but what are some of the nuances in lifecycle management of API's that your typical person really hasn't fought through that are A, super important and only increasing in relevance as more and more of these systems are all tied together. >> The use of those API's, some of the things around them that those platforms provide is some advanced authentication. They may be using, wanting to use OWA two-factor authentication, those kind of things. They may want to do some protocol translation. Many customers may know how to consume a SOAP service... generally Legacy, these days-- >> So funny that SOAP is now Legacy (laughs) >> It just cracks me up. I remember, the hottest thing since sliced bread >> Oh yeah! Oh yeah! I still have the Microsoft Internet Explorer four T-shirt-- >> When it was 95 Box too, I'm sure. But that's another conversation for another day. (laughs) >> The management of those API's adding that functionality to do advanced authentication, to do throttling... If you have an API, you don't want all of your back end systems to suddenly be overwhelmed. >> Jeff: Right. Right. >> One of those things that those full lifecycle platforms can do is throttle so that you can say this user may have only 10 requests a minute or something like that, so that stops the back end system being overwhelmed in the event of a spike in usage. That helps with denial of service attacks and those kind of things where you're protecting the core systems. Other things that they can do is the monetization. If you want to atrially expose an API for partners to consume but you want to charge them on that basis, you want to have a way of actually tracking those things to then be able to monetize that and to provide the analytics and the billing on top of it. There's a number of those different aspects that the full lifecycle provides on top of what we provide which is the core API that we're actually creating. >> Right. Is it even feasible to plug an API into a Cloud-based service if your service isn't also Cloud-based cos as you're speaking and talking about spikes, clearly that's one of the huge benefits of Cloud, is that you have the ability to spike whether it's planned or unplanned to massive scale depending on what you're trying to do and to turn that back down. I would imagine (laughs) if your API is going through that platform and you're connecting to another application, and it's Pepsi running a promotion on Superbowl Sunday, hopefully your application is running in a very similar type of infrastructure. >> Absolutely. You do have to plan for that elastic scalability. And that's one of those things with the SnapLogic platform, is it has been built to be able to scale in that way. >> Right. Now there's a lot of conversation too around iPass and integration platforms as a service. How do you see that mapping back to more of a straightforward API integration. >> What we're talking about in terms of API integration here, and the things that we've just recently added, this is the consumption of our API's. The iPass platform that we actually provide consumes API's, all sorts of different API's, whether they're SOAP or REST and different native API's of different applications. That we do out of the box. That is what we are doing, is API integration. >> Right. >> The new functionality that we've introduced is this added capability to then manage those API's from external systems. That's particularly where those external systems go beyond the boundaries of a company's own domain. It's when they need to expose those API's to their partners, to other third parties that are going to want to consume those API's. That's where you need those additional layers of protection. Most customers actually use those API's internally within their organization, and they don't need that extra level of management. >> Right. Right. But I would imagine it's an increasingly important and increasingly common and increasingly prolific that the API integration and the API leverage is less and less inside the building and much much more outside the building. >> It is certainly going a lot more outside the building because customers are recognizing their data is an asset. >> Right. Right. Then having it be a Cloud broker, if you will, just adds a nice integration point that's standardized, has scale, has reliability, versus having all these point-to-point solutions. >> Yeah, absolutely. >> I was going to say, As you look forward, I can't believe we're May 16 of 2018 already (laughs), the years halfway over, but what are you looking forward to next? What's kind of on the roadmap as this API economy continues to evolve, which is then going to increase the demands on those API's integration, those API's in management, as you said the lifecycle of the way all this stuff works together, what's kind of on the roadmap if we talk a year from now, what are we going to be talking about? >> There's a lot of... settling down of what we've delivered that's going to take place, and on top of that, then the capabilities that we can add to add some additional capabilities that the customers want to use, even internally. Because even internally where they're not using a Cloud service, they have requirements to identify who in an organization is utilizing those things. So additional capabilities without having to go beyond the boundaries of the customers own domain. That's going to be some things like authentication, it's going to be some additional... Metrics of what's actually being used in those API's, the metrics on the API's themselves in terms of how are they performing, how frequently are they being called, and in addition to that, what's the response time on those things? So there's additional intelligence that we're going to be providing over and above the creation of the API's that we're looking to do for those customers, particularly inside the organization. >> It's very similar requirements but just different, right, because organizations, take a company like Boeing, or something, is actually not just one company, there's many, many organizations, you have all kinds of now with GDPR coming out, cut of data, privacy and management restrictions, so even if it's inside your four walls, all those measures, all those controls are still very very relevant. >> Very much so. Providing some additional capabilities around that is pretty important for us. >> Alright. Well Craig, you're sitting right on top of the API economy, so I think you'll keep busy for a little while. >> (laughs) That's for sure. >> Thanks for taking a few minutes to stop by. >> Thank you. >> He's Craig Stewart, I'm Jeff Frick, you're watching theCUBE from SnapLogic in San Mateo, California. Thanks for watching. (techno music)