>> Live, from Barcelona Spain, it's theCube! Covering, KubeCon CloudNativeCon Europe 2019: Brought to you by RedHat, the Cloud Native Computing Foundation and the Ecosystem Partners. >> Hi, and welcome back. this is theCube's coverage of KubeCon CloudNativeCon 2019 here in Barcelona, Spain. We're at the end of day one of two days of live, wall-to-wall coverage. I'm Stu Miniman, and at the end of the day, what we try to do always is do our independent analysis and say what we really think. And joining me is someone that usually has no problem telling you exactly what he thinks online. So, I've challenged Mr. Corey Quinn. Cloud economist, of the Duckbill Group. and the curator, author, Last Week in AWS. To tell us what he actually thinks. >> Well, Stu, you know what your problem is. All the best feedback starts off that way. Now, this has been a fascinating experience for me. This is the first time I've ever been to KubeCon. I didn't quite know what to expect- >> It's KubeCon, not Koob-Con. Come on. It is in GitHub, how you have to make the pronunciation correct. >> We are on theCube. We would think that we would be subject matter experts on this. >> CNCF will be cracking down on you if I don't correct you on this. >> I still maintain we're in Barcelona, Italy. But that's a whole separate argument to have with other people. >> Yes, well, most Americans are geographically challenged. And we understand you have some challenges too. >> Exactly, most Americans need to learn geography, we go to war. (chuckling) >> All right, so, Corey, I guess the first question for you is, you usually go to mostly AWS shows. Most of the customers we've talked to have been AWS customers. So is this feeling much different from the usual show you go to? >> The focus of the conversations is different, and to be clear, I'm not much of a cloud partisan myself. I deal with AWS primarily because, not for nothing, that's where my customers are. That tends to be exactly where the expensive problems tend to live. For better or worse. If that changes, so will I. >> So, you're saying yet that the other cloud providers don't have their customers big enough bills, or they just haven't figured out how you might be able to help them in the future? >> To be very honest with you. Yes, is the short answer. Right now on aggregate, my customers spend about a billion dollars a year on AWS. I don't see the same order of magnitude on other providers, but it's coming. It is very clearly coming. None of these providers are shrinking as far as size goes. It's largely a matter of time. >> Alright. But Corey, I hope at least you've understood that Kubernetes at the center for all things. And that multi-cloud is the way that we are today and will always be in the future. And we should all hold hands and sing along, that we all get along. Is that what you've learned so far? >> I think that's absolutely what I've learned so far. It comes down to religion and it's perfectly name for it. I mean, Kubernetes was the Greek God of spending money on cloud services. >> All right. But seriously. Corey, I think one of the things that I really liked is. We talk to customers and there were some interesting things at least I heard when you talked about they see huge value in what they're doing with Kubernetes. Many of them only have one cloud provider today. Yet they are choosing to lay on Kubernetes either with AWS or with another solution there. What's been your take of what you've heard about. Kind of the why and what they're doing? >> There've been a few different reasons on it. One that resonated with me did validate what I talked about at the beginning of the day. Which was, that by trying to position yourself to be strategically amenable to any potential provider you might want to use in the future. You are sacrificing velocity. And you're gaining agility, losing velocity to do that. Is that trade off worth it? I don't think I'm qualified to judge. I think that's a decision every business has to make on its own. My argument has always been that if that's the decision you make, do it knowingly. And I don't think we've talked to anyone who's made that unknowingly today. >> Yeah. I think that's a really good point. What is it, you know, surprised you or interest you that we've heard so far? >> I have to be honest. I have a long and storied history in open source. I was staff at the Freenode IRC network for about a decade. Which was an interesting time. And I've seen a lot of stuff, but I don't think I've ever seen two open source projects merge before. The fact that we saw that today is still swirling around in my head for better or worse. >> Yeah. And it was OpenCensus and OpenTracing coming together. Open Telemetry. So, definitely check out Ben Siegelman. and it was Morgan McLean from a Google cloud. You know, really interested in discussion. I don't think we're sharing too much when we say off camera. There were like, look, it's like, yes, they got us in a room and we worked, but we'll try not to throw punches here on the set and everything like that. We understand that look, there are people that put these things together and you have smart people that build things the way that it should be done. And these were not like two very similar projects going in the same direction, they were built with different design principles and therefore there'll be somethings that they all need to reconcile to be able to go forward. But yeah, very interesting. >> And everyone we spoke to today was very focused on what the needs of their customers, whoever they happen to be and how to meet those customers and their business requirements. There's no one that we spoke to that was sitting here saying, oh, this is the right answer because it is technically correct. The answer is we're always of the form. This is what we need to do in order to serve customers. And it's very hard to argue against that strategy. >> All right, but none of this really matters because Serverless, right Corey? >> Oh, absolutely. Serverless is the way and the light of the future and to some extent I believe that. >> But they're not doing Serverless. I'm pretty sure they're half a step behind you. Yes, it tends to be, it's easy to make go ahead and die and say, Oh, if you're not running the absolute latest bleeding edge thing, you're behind, you're backwards, etc. And I don't get that all the sense that that is reality. I think that there's, if you're building something greenfield today, you are fundamentally going to make different choices, than if you have something you're trying to carry forward. And I don't just mean carrying forward a technical sense. I mean carrying it forward in terms of process, in terms of culture, in terms of existing business units that need to modernize. People are moving in the same general direction. The question that I think is still on answered is, today, there's a perception rightly or wrongly, that Containers are slightly behind Serverless. I don't know that that necessarily holds true. I think that they are aligned towards the same business value. I think, judge either one of them by today's constraints in the context of longer term strategy is a mistake. I'm curious to see what happens. >> Corey, I love. So we had Jeff Brewer from Intuit and they were like look, we're doing Serverless, we're doing a lot of Containerless stuffs and I'd love it for my developer not to have to worry about. And they've had been moved down that path. So, we know one of the truisms out there is everything in IT is always additive. When you talk to them and say, oh, well I'm going into cloud wait, I still have some stuff that, running on my main frame or my eyes series. And that we'll probably be running there when I've retired. We were talking offline. It's like, well, there's been a little resurgence in COBOL. Just because it did not die after Y2K and so did these things always come back and it's always additive and the longer you've been in business as a company, the more legacy you need to be able to maintain and extend and connect to where you want to go with the future. >> It's almost a sawtooth curve. As complexity continues to rise it becomes to a point where it's untenable. There's something that comes out that abstracts that away and you're back down to a level a human being might actually be able to understand. And you take it a step further and you start to see it again and again and again, and then it collapses down. Docker and a lot of the handbuilt orchestration systems were like that. And then Kubernetes came out. Initially it was fairly simple and then things have been added to it now. And I think we're climbing that sawtooth curve again. Whether or not that maintains? Whether or not that simplifies again? I find that history rhymes particularly in tech. >> Well yeah and I always worry sometimes when you talk about the abstraction layer you got to be really careful what you're abstracting. What we see here a lot, is a lot of times it's people, how can I just consume that? I want to buy it as a service and somebody take care of that not, it hides the complexity for me but some of the complexity is still there. >> Right. So our site is now intermittently slow what do you plan to do? Its update my resume immediately cause we're never untangling that Gordian knot of an infrastructure. That's not a great answer but it is an honest one in some shops. >> I've talked to, we know that there was, for a long time people outsourced what they were doing. And we need to make sure that when you're buying something as a service that you haven't outsourced, That you understand what's important to your business, what happens when things go wrong. We had some discussion today about, networking and observability that we need to be able to go down that rabbit hole, at least turn to somebody who can. Because just because I can't touch that gear doesn't mean my next not on the line, If something goes wrong. >> You can outsource a lot of work. You can't outsource responsibility. I put slightly more succinctly, the line I've always liked was you own your own availability. If you have a provider that you've thrown a lot of these things over to and they go down, well sure you're going to have loud angry phone calls and maybe a few bucks back from an SLA credit. We your customers we're down and we're suffering. So the choices you made impact your businesses perception in the market and your customer's happiness. So as much as fun as it is to be able to throw things over the wall for someone else to deal with, you're still responsible. And I think that people forget that at their own peril. >> One of the things I like. I've got a long history in open source to. If there are things that aren't perfect or things that are maturing. A lot of times we're talking about them in public. Because there is a roadmap and people are working on it and we can all go to the repositories and see where people are complaining. So at a show like this, I feel like we do have some level of transparency and we can actually have realism here. What's been your experience so far? >> I think that people have been remarkably transparent about the challenges that they're facing in a way that you don't often get at a vendor show. Where you have a single vendor, you're at their show, regardless of who that might be. You're not going to be invited back if you wind up with a litany of people coming on a video show or a podcast or screaming and sobbing in the bathroom, however you want to, whatever your media is. Just have a litany of complaints the entire time or make that provider look bad. I don't sense that there's any of that pressure. And for some reason, and this is my first coop gone, so maybe this is just the way this culture it works. Everyone, regardless of who they worked for or what they're working on or what their experience has been, seems happy. I can only assume there's something in the water. >> All right. Well, I've just been informed that the CNCF had asked me to remove Corey because he refuses to say KubeCon. But, Corey. Since this might be your last time on the program, any other final words that you have for it or I will let you do something very rare and if you have any questions for me. Love on my way. >> Absolutely. What did you find today that you didn't expect to find? >> The one that jumps out for me really is two things. One, we discussed it already is the, the observability piece coming together. The other one is. You talk about that maturation of where Amazon fits in this ecosystem. And we had lovely conversation, with Abby fuller. But not just that one. We talked to the users and how they think about it. Which is what really matters is, there's so much talk about, who contributes more code and who does the most here. But look, we're talking cloud. Most of these customers are using AWS as if not the cloud, one of the clouds. I've set it on theCube many times. When you live in a hybrid and multi-cloud world and the public cloud, AWS is the far leader. There's no debating that. So they are participating here. They are doing plenty for what their customers want and they give choice and they listen to the feedback. So that was interesting to me that maturation of where that sits because when I come into the show and many times it is, it is the open source in this whole ecosystem, trying to prevent Amazon from taking over the world. And look, we want a good robust ecosystem out there. >> We absolutely do. >> While I have many friends that work for Amazon. We probably don't want to all be working for a single company down the road. >> I certainly don't. >> We like a nice robust ecosystem where there is choice out there and that keeps its (mumbles). So that maturation of where they are on has been interesting to me so far, especially from the user stand point. >> Very much so. I don't think that anyone wants to look back and say, wow, I'm sure glad we have only one option in this entire space that does anything useful. And then a whole bunch of could have the didn't. And for better or worse, I don't think that the future is nearly as clear cut as the past of cloud. Historically, AWS has been the 800 pound gorilla. I think that we hearing fascinating things from GCP and from Azure. I don't necessarily think that the future is preordained. I do think right now it is AWS game to lose, but I'm starting to see a lot of other players in his face start to make a lot of very interesting and arguably very correct moves. >> All right. Well, we know you as our audience have lots of places where you can turn to find your information and we are always pleased that when you turn to us to watch theCube. if you have any feedback for ourselves, Corey Quinn and myself, Stu Miniman. Reach out on Twitter. We are easy to reach on that. And we have lots of posts. So if you're like, Hey, tired of looking at this mug here. Let us know. But hopefully we're asking the questions and digging into the areas that you want and we'll help your businesses going forward. So we are at the end of day one, Two days live coverage here at KubeCon CloudNativeCon. This is the cube. You're a leader in live tech coverage. Thanks for watching. (music)