>> Lisa: I'm Lisa Martin with theCUBE. We're on the ground at Google for the 6th Annual CloudNOW Top Women in Cloud Awards. Very excited to be joined by award winner and CUBE alumni Erica Windisch, founder and CTO of Iopipe. Welcome back to theCUBE, Erica. >> Erica: Thank you. Great to have you here, and congratulations on being one of the top women in Cloud. >> Yeah, of course. >> Tell me, when you heard about that you were being recognized, what did that mean to you and where you are in your career? >> Well, oh gosh, I mean it really meant, it was really big for me. I actually wasn't really expecting it. I think I was nominated and I totally forgot. I think somebody had mentioned to me that they were nominating me and I had no idea about it. I totally forgot about it. But I mean, for me it's just so validating because as much as I've, well one, because I've done a lot of interesting things in Cloud and in tech, but I've never really gotten a lot of recognition for that. And also, just recognition, I mean to be quite honest, I'm transgender. So the fact that I was recognized as a woman, Top Ten Women in Cloud Computing, was extra important and special for me. >> Oh, that's awesome. So tell me about your path to being where you are now. Were you always interested in computers and technology, or is that something that you kind of zigzagged your way to? >> Yeah, well, it was one of these things I guess I had some interest. When I was a child, we had BASIC exercises printed in our math books but our teachers never went over it. So I got kind of interested and I would read through those like those little appendums in my math books, and I would start teaching myself BASIC. And I picked up a Commodore 64 and it didn't work and I taught myself BASIC, more BASIC with those manuals. And I just had these little tiny introductions to technology and just self-taught myself everything. Eventually using a high school job to buy myself books and just teaching myself from those books. Managed to grab Linux on some floppy disks, installed it and tried to figure out how to use it. But I didn't really have lot of mentors or anything that I could really follow. At best there were other kids at school who were into computers and I just wanted to try and do what they were doing or do better than they were doing. >> I love that, self-taught, you knew you liked this and you were not afraid to try, "Hey, let me teach myself." That's really inspiring, Erica. >> Yeah. >> So, speaking of inspiring, tell me about the Iopipes story. So you're a TechSource company, tell us a little bit about TechSource, what that investment in IOpipe means. >> Yeah, so, I started, I guess I first started IOpipe two years ago. And I found the co-founder Adam Johnson, who joined me. And we applied for Techstars, got in, and that was like the first validation that we had from outside of ourselves and maybe one angel investor at that time. And that was a really big deal because it really helped accelerate us, give us validation, allow us to make the first hire, and they also taught us a lot about how to refine our elevator pitch, and how to raise money effectively. And then we ended up raising money, of course. So with the end of Techstars we had a lot of visibility, and that helped us raise two and a half million dollars seed round. >> Wow, so a really good launching pad for you. >> Yes, yeah. >> That's fantastic. So tell us a little bit more about the technology, I know that there's AWS Lambda, we just got back from re:Invent last week, so tell us a little bit more about exactly what you guys do. >> Oh yeah, so what we do is we provide a service that allows developers to get better insights into their application, they get observability into the application running a Lambda, as well as debugging and profiling tools. So you can actually get profiling data out of your Lambda and load that into Google DevTools and get Flame Graphs and dig in deep into which function called which function inside of each function call, so every Lambda invocation you can really dig down and see what's happening. We have things like custom metrics and alerts for that. So you can, for instance, we built this bot. I built it in two days. It's a Slack bot that, if you put an image in a Slack, it will run it through Amazon Rekognition and tell you, describe the objects in it, and describe it. So, for instance, if you have visually impaired members of your team, they can find out what was in the images that people pasted. I built it in only two days, and I could use our tool, let's say to extract how many objects were found in that image, whether or not a specific object was found in that image, and then we can create alerts around those, and do searches based on those, and get statistics out of our product on the data that was extracted from those images. So that was really cool, and we actually announced that feature, the profiling feature, at Midnight Madness at re:Invent so it was like the opening ceremony for re:Invent. It was just us, Andy Jassy and Shaquille O'Neal. >> Lisa: What? >> Yeah, and we launched our product, and we did the demo of this Slack bot, and it was a lot of fun. >> Wow! So you were there last week, then? >> I was there, we were there last week, and we were actually the first, myself, my co-founder and one of our engineers were up there and we were the first non-AWS speakers at the entire arena, it was really amazing. >> Wow, amazing. Congratulations. >> Thank you. >> So with all the cool announcements that came out last week on Lambda, Serverless, even new features that were announced for recognition, how does that either change the game or maybe kind of ignite the fire under you guys even a little bit more? >> Well I think one of the biggest announcements relative to us was Cloud9. And we knew that this was going to happen, Amazon acquired them a year ago, a year and a half ago, but they finally launched it. And they really doubled down on providing a much better experience for developers of Lambda to make it easier for developers to really build and ship and run that code on Lambda, which provides a much tighter experience for them so that they can on-board into things like IOpipe more easily. So that was really exciting, because I think that's really going to help with the adoption of Lambda. And some of the other features like Alexa for work is really interesting. It will probably just again, a lot of Alexa apps are built on top of Lambda, so all of these are going to provide value to my own company because we can tell you things like, "Well, how are your users interacting "with those Alexa skills?" But I think it's just generally exciting because there's just so many really cool, I mean, I don't know how many things they announced at this re:Invent that were just really amazing. Another one I really loved was Fargate, because I mean I came from Docker, I used to be a maintainer of the Docker engine and something that I was pushing for at that time in OpenStack and other projects, was the idea of just containers completely as a service without the VM management side of things, because with like ECS, you had to manage virtual machines, and I was like, "Well that is a little, like, "I don't want to manage virtual machines, "I just want Amazon to give me containers." So I was really excited that they finally launched Fargate to offer that. >> So the last question in our last couple of minutes here, tell me about the culture and your team that you lead at IOpipe. You were saying before, you know, when you were a kid you were really self-taught and very inspired by your own desire to learn, but tell me a little bit about the people that work for you and how you help inspire them. >> Oh gosh, well I think first of all, we are, right now we're nine people. I would say about four or five of us are under-represented minorities in tech in one way or another. It's really been fantastic that we've been able to have that level of diversity and inclusion. I think part of that is that we started very diverse. You know, a lot of companies will say, well, one of their problems with not having enough diversity is that they hire within their networks, well we hire within our networks, but we started very diverse in the first place. So that organic growth was very natural and very diverse for us, whereas that organic pairing growth can be problematic if you don't start in a very diverse place. So I think that's been really great, and I think that the fact that we have that level of diversity and inclusion with our employees is kind of inspiring, because a lot of workplaces just aren't like that in tech. It's really hard to find, and granted we're only nine right now. I would really hope that we can keep that up and I would like to actually make our workforce even more diverse than it is today. But yeah, I don't know, I just think it's fantastic and I want what we're doing to be a role model and an inspiration to other companies and say, "Yes, you can do this." And also the work people in the workforce, yes, you can be a woman in tech, yes, you can be trans in tech, yes, you can be non-binary in tech. I am binary, but we have non-binary people in staff. And, I don't know, I hope that's inspiring to people and also myself being a transgender founder, I maybe know one or two other people who are transgender founders, it's very uncommon. And I hope that also is an inspiration for people. >> Well I think so, speaking for myself I find you very inspiring. You seem to be someone that's really known for thinking, "I'm not afraid of anything. "I'm just going to try it. "Starting a company, I'm going to try it." And it sounds like you guys are very purposefully building a culture that's very inclusive, and so I think that, as well as your recognition as one of the Top Women in Cloud, be proud of that, Erica. That's awesome. >> Thank you. >> And you got to meet Shaquille O'Neal? >> I got to meet Shaquille O'Neal, yeah. >> I've got to see the photo. (laughs) >> Yeah. >> Well thank you so much Erica for joining us back on theCUBE. Congratulations on the award, and we look forward to seeing exciting things that you do in the future. >> Okay great, thank you. >> I'm Lisa Martin on the ground with theCUBE at Google for the CloudNOW Top Women in Cloud Awards. Thanks for watching, bye for now.

>> Announcer: Live from Manhattan, it's the CUBE. Covering AWS Summit, New York City, 2017. Brought to you by Amazon web services. >> And we are live here at AWS Summit here at the Javits Center, New York City, we're midtown, Manhattan, a lot of activity going on outside, you can imagine all the buzz inside as well. Somewhere between 6, 7, 8,000 attendees, kind of tough to tell right now, but everybody's jammed inside here on the show floor and they've been here all day and they're going to stay for a while I think too. As I said, a lot of buzz going on, and good buzz too. Along with Stu Miniman, I'm John Walls and we're now joined by Erica Windisch who is the Co-founder and the CTO of IOpipe. Erica, thanks for being with us here on the CUBE. >> Thank you, thank you for having me. >> You have had a big day. >> Yes we have, yeah. >> It's always fun to talk about money but you did have a fairly significant announcement this morning to make. Tell us about that. >> Yeah, so this morning we announced funding, $2.5 million from several investors including NEA, Madrona, and Underscore. >> So, yeah, you don't often get to high-five everybody for a day like that. I mean that kind of validation, obviously is something that not you just take to the bank, you take it to the marketplace too. >> Yeah, absolutely. And we actually started, our first check was from Techstars so we joined Techstars here in New York City and did that last year for their summer program and it was really great and that was the first foundation that we really had, and then having that further validation from major VCs like NEA and Madrona, Underscore, you know that really was really validating for us as well as just the fact that we're building, we're hiring and we're building and having what I think is an increasingly awesome product. >> Sure, well tell us about IOpipe, for folks at home who are watching might not be familiar with your space, what you do and how you do it. >> Yeah, so we provide tools for software developers to build and manage their applications on Amazon Lambda. So, basically, it's all serverless, we're actually built on serverless as well, we monitor with IOpipe, we dogfood everything. And we are providing deeper insights into those application workloads as well as correlating that information in more useful ways. Deeper knowledge of what exactly is happening in the run times, so we're able to see the data we ingest tells us information on the processes and the containers and the virtual machines that are running your Lambda workload, so we can see things like memory leaks and we can see file descriptor leaks and displaced utilization leaks, things like that that Amazon doesn't collect or at least doesn't give you that information. So, we're looking at ways we can provide more value to users of Lambda and also extending it with plugins so we have a plugin for tracing where you can time aspects of your application as well as profiler, so you can enable a profiling plugin and you get a full flame graph. So you can see, these are all the functions and this one ran and this one ran and the stack looks like this and so you can see the full flame graph of what happened and when and full timing information. This kind of insight that nothing else really gives you. >> Yeah, Erica, every time we have a new technology we go through this kind of diffusion of innovation that goes through. Remember back, I go back thinking about when virtualization came, people, what is it, how do I use it? We saw that in containers and each wave seems to be going faster and faster so there's still plenty of people I talked to that were like, "serverless what?" You know, some new as a service, I mean I thought I knew it with SAS and everything else like that. You're digging into these environments further. Can you give us, what are some of the kind of key use cases you're seeing, what are the challenges that customers are having? What works, what doesn't work, help us unpack that some? >> So, I think there's a number of challenges that users run into today. One is the fact that it is new so some of the tools are still evolving. Operations tools, development tools are still evolving. Just this week, Amazon announced SAM local so you can do editing and debugging locally on your machine or your laptop. That wasn't available before, right? So these tools, we're very much still in a learning phase for some of the tools, but some of the things like what we're doing with IOpipe, in some ways is more traditional because we're bringing in some of the basic monitoring tools and capabilities that you would expect from other platforms. But the other side, also innovating because we're bridging that development and operations into a single tool so it's not development and operations, it's, not even just different tools for those two things, but single tools for those. So I think that's part of the solution, part of the problem, in terms of workloads, I think there's a lot of ETLs, streaming applications, very infrequent things like chron jobs, web applications, you can take flask applications or express applications and just port them directly over to Lambda with almost a lift and shift for those, right? So there's a lot of power for bringing on the web 'cause you pay per the request. You don't scale your application and build your application for the number of servers that you need to handle the requests, it scales it per request and you pay per request and that's what's powerful in both scale of operations and team and like financially, but also, yeah, I lost train of thought there, but it all scales that way, right? Like just according to the request. >> Yeah, bring us into a typical customer, I know there are no typical customers, everyone's a little bit different, but you've got the developers, you've got the operators, finance has always had, you know, there's challenges with cloud in general but serverless at least promises that it's going to be less expensive. What are those dynamics from an organizational standpoint that you see inside? >> In terms of cost? >> Not just cost, but do the developers make something and the operators are like, wait, you know, there's challenges there? Or who drives this initiative in general? Does finance come and say, has finance heard about this and said hey, I heard I could save 60-70% on my cloud if you just re-architect this on Lambda. Or is it the developers coming through and saying, oh, wow, this is great, and can do it, or are operators, who's driving the initiatives and what are some of those dynamics? >> So I see a combination of these things. Some organizations, and I don't want to say names 'cause I don't want to like, you know, they did this and that's how it is. But I get the impression that certain organizations they have a top-down approach where they're going like, everything is going to be serverless and the cost really matters. So you're going to build serverless unless you can't, right? Serverless by default, anything else as an exception. Then there's organizations where developers are really pushing for it because it simplifies their requirements, right? It's a self-service aspect, right, even if they can spit out VMs, even if they have self-service VMs, they won't have to spit out VMs, they don't have to build docker images, they don't have to look at how the operating system is configured. They write code and they deploy code. There's no other steps, right? They're not like, oh, what version of Python is on here and how do I install all the libraries and how do I, right, like with serverless you just write the code and you ship the code. Which is really, really nice. So, in a way it's like having a golden image that you can't change, and you just know you're always going to build for in every application and every organization is going to the same golden image. Which simplifies a lot of things. >> Stu and I were talking about serverless, the whole concept, because it's really not truly serverless it's just different server, or it's a different flavor of it basically. So, first off, what gave birth to that and then where do you think, with serverless computering, serverless application, so on and so forth, where's that going? >> Yeah. >> What's going to be the real value at the end of the day of that? >> So, first of all the term "serverless," I look at it as, yes there are servers, serverless is servers are not my concern as a developer, right, I am not worrying about what the server looks like or operating the servers necessarily. I care about building my application which is why we're looking at building tools that are bridging development and operations so that operations is part of your development. But I see, the direction of serverless, really interesting in a few ways. One is that it's going to be available for more use cases. So right now there's certain use cases that make sense and one of the challenges is figuring out which use cases it doesn't work for. Eventually, you're not going to have that question, potentially, right? So maybe we get to a point where you don't have to ask, the challenge isn't, is serverless good for this use case? Maybe it's good for all use cases eventually down the road, maybe. Another thing is... >> If I could just follow up on that. Some of the announcements today like AWS Glue has serverless in the background there. Seems very promising, things like machine learning, artificial intelligence, serverless, IOT where you know, I need to balance the surface area of attack there but with serverless it won't be active as much and there will be links that are a little bit more dynamic. So, lots of those new use cases seem to be built really well for serverless. What are some of the cases today that you just say, hey, don't even go serverless there. >> Oh don't go serverless, where to do that? Well, so, Lambda has an execution time window which can be limiting for some things that you might want to do. So, like, Lambda in particular may not be the best case for all video encoding tasks. Some video encoding tasks if you can time limit it can be fine. But it's not good for all video encoded tasks because it's a batch process, potentially. Serverless processes that can let's say paralyze that and say, we're going to run Lambda but we're going to say split this up into segments, for instance, you can do that, or if you do it as a stream, right? Like you pipe a video and blocks into Kinesis, right, you can make that work. But it becomes a challenge to those kinds of use cases. >> Yeah, there was the example I think in the keynote was, this high process that would have taken five years, we can do 155 seconds. >> Right, but you have to paralyze it, right? >> Stu: Exactly. >> And if you can't paralyze a task and you can't do it within five or ten minutes, you can't use Lambda for it today. But it also depends on how you define serverless, right, because if serverless is Lambda, that's one thing. But if serverless is these other SAS products as well potentially, like AWS Transcode service, well is that serverless? If it is, then there you go. There's a solution potentially for you. So there's very blurry lines sometimes around what is serverless, and we're looking at IOpipe around serverless functions. I feel the same way around cloud in general was that there's cloud compute and it kind of evolved over time and the cloud is everything like all these things are in a cloud. But originally when we're talking cloud, five years ago, ten years ago, it was all compute. That's what we were talking about. So these terms change over time, so it's hard to say what serverless will be in five years or ten years because it'll mean something different. >> Or next week, for that matter. >> Yeah. >> Erica, last question I have. $2.5 million, what's that going to drive, what should we expect to see from your company and give us any final thoughts on what you'd like to see for the maturation of the serverless technology field? >> Yeah, so we've been hiring and building out a team, we're working on improving the user experience of the product, we are adding additional plugins and enhancements to the service. We feel that we have a really good base with our 1.0 announcement, 'cause we're not just the 2.5 million, we also announced our 1.0. And the 1.0 has a really good base of functionality and we're looking at adding additional plugins and additional features that can extend the service. So we're looking at doing that with that money. And with serverless in general, I think this is really compelling, what we're going to see in the next year, because we're going to see more large enterprises and more enterprise adoption, I think. I mean I was involved early in cloud. I was involved early in docker. And this point of serverless is very much at the early days of these technologies, and I definitely see a rocket ship taking off, and I think in the next year it's going to be really interesting to kind of see it starting to orbit a little bit. >> Well, new product, new funding, and a new day for IOpipe. >> Yes. >> So congratulations on a good day and thank you for being with us here on the CUBE. >> Thank you very much. >> You bet, we'll continue here at the Javits Center we're in midtown Manhattan continuing our coverage of the AWS Summit, here on the CUBE. (futuristic music)

>> Announcer: Live from Manhattan, it's theCUBE covering AWS Summit New York City 2017. Brought to you by Amazon Web Services. >> Welcome back live to Midtown Manhattan, along with Stu Miniman, I am John Walls. We're here on theCUBE and we're wrapping up our coverage here at AWS Summit. Again, kind of tough to get a feeling for just how many folks were here. But some were in that seven, eight, $9,000 range and most of them are still here I think, out on the show floor here behind us. Good keynotes this morning. Good programming throughout the day as well and then really good buzz here on the show floor. So, good day I think, for AWS Stu, and we've talked about it, it is kind of remarkable to see the number of people who turned out for a regional show. >> Yeah John, you know I've been to some shows in the Javits Center where people wander in, they get some swag, they look for a free beer and a t-shirt and then that's kind of their... These people are, you know, kind of diggin' in. I know there's a bunch of sessions been going on. The pavilion here has had all these little breakout sessions. There was one on, you know, VMware and VMware and AWS and it was, you know, not only the seats, which usually it was like oh come on in, you know, come get a prize and things like that. >> John: Right, right. >> There was five rows of people standing pressed in and asking questions like, "How do I set up "the networking on this, how does this work?" Things like this, so it's like a mini AWS re:Invent, so their big show, one we've done theCUBE at a number of years, I've been there a number of years. I commented on our intro that this is larger than the first Amazon re:Invent that I went to like four years ago. >> How about that, in that short of period of time? >> Yeah and that's one of the things about Amazon and public Cloud in general and all of these technologies, the growth and the speed of change is just amazing. It used to be we talked from a software standpoint, it was like okay, I'm tied to that Intel release of every 18 months that I'm going to click out, then it was like okay, we kind of go to a yearly cycle. Now it was more like well not only is a lot of software released, you know, continuous integration and continuous deployment CICD, which sometimes it's every six weeks, sometimes it's daily, but Amazon's releasing new features every day. We talked in the intro, oh there were three major releases and we had the guy I'm talking about, the machine learning stuff and he's like oh you mean the three announcements that we had in machine learning? And we're like oh, we only heard about one of those. Wait, you had a couple others underneath there? Oh, let's talk about the F1 compute instance and the FPGAs. There's always so much in Amazon and when you go into any environment in the little boxes that they put in there and you start peeling the onion, it's impressive. >> It is. >> And there's just depth and customers are interested in it and people are using it. You know, I was used to so much in my career where something gets announced and a year later it's like hello, is anybody using this? As opposed to at this show, a bunch of the announcements, I already talked to a bunch of people that have been in private beta, they've been testing this out, they're excited about it and because it's just so easy to get on all of these new features. >> Right, and I mean, we've seen it here, we've heard from many people here from a lot of different walks of life. You mentioned some of the past shows, AWS Public Sector. I was at that not too long ago in Washington, D.C. and you see a company that has its units very focused and very driven and doing very well and the right relationships. Buzzword, serverless, right? We heard it a lot today. Serverless applications, serverless computing. From more than one source, we heard it from several folks and so obviously this is not just a popular piece of nomenclature for the day, this is a trend, a theme that's going to be evolving and maturing over the next year or two. >> Yeah I mean everybody for the last couple years they've kind of been looking at it with their head sideways. I'm not sure that I understand it. We talked to two companies today, it was IOPipe and A Cloud Guru that their company, their IT infrastructure was all built on serverless, and they both got funding recently, so this isn't just oh yeah, some developer does some cool stuff on the side, microservices, buzz buzz, things like that. We talked to FICO is using serverless for their admin functions, certain areas they're not ready to roll it out across the board, governance compliance, things like that, I need to understand it. It is still very early, but that being said, there's a lot of usage in it. Last year it was oh, if you want to develop for the Alexa platform, the Amazon Echo type thing, that uses serverless, so we're seeing lots and lots of cases. That really is a new way of architecting the way to roll out really microservices driven applications and when we talk about the big challenge of our time, it's distributed architectures and how do I have new applications? We talked to a number of companies moving from the old way of doing my application to building new application, that's the long hole in the 10. This is not something that happens overnight, but I can start playing with it in a much smaller form factor and do it for pennies not years and millions of dollars so there is really serverless has really in many ways eclipsed kind of the container's discussion for the hot buzz in the industry. Kubernetes fits into that whole picture, but not just serverless in general, but AWS Lambda is the leader of the pack out there and you know, yet another reason why Amazon just going strong, their revenue still doing well, keeps adding to what they're doing and you don't hear many people griping when you walk around the show floor as to what they wish they had. It's a very positive experience. >> And you hear criticisms saying, "They only had 42% growth year to year." It's not what it used to be. But 42 as you know, most people would gladly be in that position. What about your thoughts about the maturation of the Cloud? You mentioned transformative and things are evolving and growing, where do you put it now? Is this second phase, next phase, late phase? Where are we in terms of what's happening and what AWS is making happen? >> So a couple years ago we know that Cloud is here to stay. There's still the joke a friend of friend of mine in the keynote. 20,000 people registered for this event and it was like well, I guess this Cloud thing might have legs, so we are still early in the overall wave of this. I've been in a number of conferences this year that we've done theCUBE on. You talk about the infrastructure companies and companies that have built on virtualization. They said, "We went through a decade "of tremendous growth with virtualization." Virtualization is still very important. Amazon builds their infrastructure not on VMWare, but they leverage virtualization technologies, but the next 10 years will be this huge wave of really that going up the uptake of the S curve so we're past really the classic crossing the chasm. We're in the early majority going to mid majority of people using it and there's just no shortage of new use cases that people can use it for. We've talked to lots of companies that start up and say, "I'm just leveraging Cloud because it's easy." THere's VCs that look at that as how to get involved and as I've just mentioned before, there's companies now that are building themselves on serverless so this is even kind of the next piece that follows these waves we are early in Cloud if you look at kind of overall ham of IT, public Cloud is still a very small piece. At Wikiban we've been talking for the last I think two years about what we really the multi Cloud environment. There's true private Cloud and there's public Cloud and how do I get that operational model that I can scale, I can build really a distributed architecture? I shift more to an operational expense rather than a capital expense, so it's flexibility, it's agility, it's speed, and it's very interesting, exciting times. There's no more exciting time to be in tech than today, maybe tomorrow, because we know the only thing constant is that the pace of change keeps increasing. >> It does increase and two big drivers of that, we heard again today, artificial intelligence, machine learning. How would you rate or how would you characterize the impotence that they're providing in terms of pushing the envelope? >> Absolutely there was some good announcements today, I don't know that there's any today that you'd say, "I'm going to look back five years from now and be like, 'Wow, I was in New York City when that was announced.'" >> John: Right, but just in general? >> But in general, let me say one of the things that I didn't hear today, I was was little bit disappointed, I mentioned it in the open, we talked to a couple of the partners here, you know the Kubernetes option. Adrian Kovrov got up on stage. He had written a blog post there was an announcement last week, no mention of where Kubernetes is going to fit in here. Definitely they're committed to it, they're making developments, but maybe something will come out in beta soon. I would expect by the time we get to the re:Invent show in November that we will have more clarity here. I was hoping to hear that more and that was something that didn't come out of Amazon, but they're embracing it. Customers are asking for it, developers, there's a ground swell on that, so they're involved with it. Lambda and serverless absolutely. Amazon is at the vanguard, they're pushing things forward. Machine learning and IoT, Amazon is at the table. It is still very early, they're driving a lot of things forward. Yeah, you know, you get enough, it's like come on, there's no BitCoin discussed today, why is that? So some of the other vendors there, but Amazon is in all the appropriate conversations. There's not any wide gaps that you'd say customers like hate these. Amazon's not in this base and I expect them to and therefore I'm going to choose another platform provider. That being said, it's not a winner-take-all, it is a multi Cloud world, most of these environments, we talked about even if I do serverless, if I architect them a certain way I can move them and make changes, Kubernetes the same way. So Amazon, one of the things that they pride themselves on is they need to keep proving to their customers every month that they are the ones that they fuse on because otherwise it is relatively easy to make a change, but they're the big dog, they got the leadership position, and it's always impressive to watch them. >> It is and you speak of impressive. re:Invent, is just what, two and a half months away, three months away, we'll be out there as well. Huge show, probably one of the largest shows by far that we attend and looking forward to that and seeing you down the road. Always a pleasure to be with you. >> Thanks so much. >> And great job as always. Stu Miniman does an outstanding job providing analysis for Wikiban, so on behalf of Stu and all the crew here at theCUBE, we thank you for joining us here at the AWS Summit in Midtown. We've been live at the Javits Center. Have a good week and we'll see you down the road here on theCUBE. (light electronic music)