live from Las Vegas it's the cube covering AWS reinvent 2018 brought to you by Amazon Web Services Intel and their ecosystem partners welcome back to Las Vegas everybody I'm Dave Villeneuve my co-host David Flair you want to the cube the leader in live tech coverage this is our third day of coverage at AWS reinvent 2018 our sixth year covering this event that keeps getting bigger and bigger Dave at 53,000 people amazing place is still jam we still barely have our voices 18 Cockroft is here he's a vice president of cloud architecture and strategy very well known in the industry q Balam thanks so much for coming back on thank you yeah it's the I've been to all of the reinvents we've been far as the customer and then we've been off of one but we watched remotely and hung on every word you know back when there wasn't a lot of information about a DMS now it's like too much information to process it's gonna take us months to sort through it all but at any rate it's it's a phenomenal opportunity for us to to learn to share to inspire folks and you do with some great work talk a little bit about you know some of the fun stuff you're working on and in your current role yeah I have a few different things I do one is one part of my role as I go around the world giving keynotes AWS summits but mostly I call it doing one of Ogle's impressions his deck and I get to presented around the world so we have to digest all of this stuff into a 90-minute deck that we can take to around the world that's a you know what do you leave out there's some it's it's harder and harder every year so that's a lot of fun but the team that I run for AWS I mean recruiting and running is around open-source right and we do we sponsor various events we members of various foundations we make contributions to projects and have been helping that by hiring people from the open-source communities into AWS to help help some of the edge over service teams with their launches of open-source related projects so what I've got what's been happening this year is had like a hundred blog posts related to open source lots of tweets lots of activity lots of events like ask on all things open in coupe car so be there in a couple of weeks exciting to you guys probably again but this week there are a few of the launches where we got quite deeply involved we did a blog posts on the open source blog most at the same time as Jeff fires okay here's the service and here's the open source part of it this is how you contribute and this is what's going on so we've had some fun with that so but it was it two years ago when we first met you've just been on the job for about a month about that particular time and you laid out what you wanted to do in terms of from your previous experience about how you wanted to turn AWS into a an open-source contributor how would you rate yourself in two years I think we've made some good progress really made me a AWS was making contributions to open source but had nobody talking about it and nobody know it was nobody's job to go out and explain what we were doing so that what part of the problem two years ago it was actually more happening so most people knew about but we were just not telling the story and it said it wasn't coming across well and the culture and the culture I mean it was spotty like some parts of AWS were doing a lot of open source other parts we're kind of not really seeing it as a priority so by talking a lot more about it we kind of get a more uniform acceptance across AWC huge organized just there but Amazon as a whole we are actually telling that story the story a much broader story than just AWS and be able to bring that and get everyone go oh this i see everyone doing it so i should be doing that so it helps create the the the leadership for more teams to follow and what we've seen in with you know really the first year building the team the last year kind of getting the content flowing and getting the processes kind of working to get all the all of the different events and blog posts and out the outbound part grips getting increasing number of contributions and launches so now Corrado was a few weeks ago so it you need us launch but that was that was an example that was it's a lot a lot happened from my team from Aaron Gupta my team his a Java champion he used to be at Sun he was a worked at Red Hat on J bar so he's like he knows everybody in Java has great credibility across the Java community and he said we should launch this product in Belgium at like midnight or so you know West Coast time and let's fly in James Gosling and like to a secret like get him on stage without anyone knowing he's gonna do it and do the introduction so it's like this totally crazy idea and it came off beautifully and we even had the the you know the Oracle Java people saying nice things about it the contributions to open JDK just just a really nice example of figuring it out all that get everybody on board get everything done right and then say here's something that matters to the community that we can contribute it'll show up on the rooftop complete thanks the star power thing but mincing James to do it was a right around a lot of credit for that that particular launch but you know this is the kind of people I have on my team and we're like we're pulling them in and pointing them at okay can you help this team figure out how to take this open-source project to market now I mean that was a major contribution to the open-source community and it was just in time wasn't it but another slight view would might be that you and Oracle should have been working this out until not leaving it until the last minute but I mean we were doing this work anyway right okay we're effectively self-supporting our own version of Java or internally we were getting better performance and better sooner bug fixes on open JDK so it made a decision to just move to the open JDK dream and we were just unhooking our internal use of the of the other the other options we have home mix you know a very large organization along for you acquire lots of different versions and flavors of Java you notice this one language so we like clean it up let's get JDK 8 and 10 we're self supporting it and then we announce to our cave will support our Amazon Linux version right and the final step was like the customers were saying please just like supportive on my laptop and anywhere else I need it and the thing we didn't announce then we didn't make a big thing out and arm support we didn't we kind of it was in there by default we didn't talk about it because the ARM chips came out this week so hey and part of it was also have exactly the same version of Java now on all of the Amazon Linux is even the the Intel AMD and arm so that helps the compatibility for people kind of going well it's a different processor architectures ties together so it was all part of the thinking if you didn't want to tip your hand on the announcement this young is right ok so I think sometimes a AWS is misunderstood partly from its own doing I mean you just mentioned you contribute a lot to open-source but you never talked about it generally when AWS doesn't have something to say they don't say a lot about it so others are left to you know make the narrative you come on you've now got an open-source agenda can you just sort of summarize what that motivation is and what the objectives are well we have you know lots of different pieces of this but you have service teams saying I'm gonna launch this product and there's an open source component to it can you help and sometimes that means I hire someone in my team to specialize in that area sometimes it's just our consulting with the team we may know connecting them to the open-source community so that's one piece of it is having that if you think about CN CF in particular cloud native computing foundation that's got lots of projects if you think about the AWS service teams no one team really owns the scope of CN CF but my team has that ownership for CN CF as a whole we have the board seat position and we say ok we have the serval as people over here we've got some entertaining things over here there's some Linux kernel virtualization bits here we can reach out to lots of different teams across AWS but act as a central point where you have something about open-source you want to talk about with with AWS or Amazon even as a whole you can come to us and we'll find the right people and we'll help you make those connections so part of it is acting as an on-ramp for the sort of buffer between the internal the external concerns of the communities there's somewhere to go and partly just getting contributions out there and what we could gain criticized for not making enough contributions well we've been making more and we're making more and we'll just keep making more contributions until people give credit for it and that's that's the if you're like what's the strategy contribute more and then tell people point at it and hope the people like what we did and take the input no it's the customer driven thing right we're gonna do what our customers ask us to do and their customer community focus on the things we want to do and we've been contributing to spinnaker the the Netflix OSS project we made some serious contributions to that in the this year firecracker myths which talk about that a bit and the Robo maker that those are all areas where we've been working with firecracker is particularly interesting isn't it I mean that's a major contribution of improving the performance and capability of those micro VMs yeah can you talk about that a little bit yeah it's the baby it's interesting because it's a piece of software pretty much no one will ever see your use it's the thing you run on the bare metal but lets you run your container Dee that lets you run your container on top right well it's deep down in the guts of the system there's this piece of code but we we kind of there's a few reasons we're using it particularly in production now with its supporting some of our production use of Fargate and lambda there in the middle it's not a hundred centraal out but there's a good chunk of the capacity running on it and that's where it turns out to be useful and just to cook how long we have to get into this but if you think about a customer running a lambda function we would put create a VM with that lambda function in it if they wanted a second lambda function we put it alongside that one no the customer comes and we start a new VM for them and we start a lambda function in that VMs take a while to start up so you have cancer pre-made some sitting there waiting but these are big VMs and we're putting lots of little functions in them what what firecracker lets you do is start a separate micro VM for every function and safely put all of the customers on one machine so you start packing them in it's a much more efficient way to run your capacity our utilization of those machines supporting lambda is vastly higher than having a machine with a bunch of empty space in it that we're trying to weight running for running for the customer so it's that efficiency is the thing and then the speed of starting a VM it's a very it's a very cut-down VM so it's 125 milliseconds with just to start the VM which is incredibly fast when you think hey give me a VM on ec2 it's you know they're in kinda like 30 seconds to a few minutes like I get 12 terabyte VM takes a little while to boot up but you don't have to pay for it till it finished including my good things about these huge machines right how about Robo maker can you talk a little bit about that and it's important so a rubber makers interesting on the open source blog which we posted on Slate on Sunday night early on Monday morning I did an interview with Brian Goerke who's the founder of the open robotics foundation and what we've done there is it's kind of an extension of sage maker if you think about that being AI if you've got these eight where I can deploy an AI model what is the AI model I want to do it wants to read something from the real world and modified the real word so it's a read from a camera or at some of the sensor and then control motors and servos and that's what Robo maker does it wraps the intelligence you can build with sage maker with the robotic operating system that has actually a library of actuators and a library of algorithms control algorithms you've got little brain in the middle and you've got a new robot that does something and we had the the Robo racer low racing car to which where all of these things come together to make an old toy race car that we can drive around tracks which is a whole other topic we get into but what interviewed Brian on what is the history of Rose the robotic operating system where did it come from you know what is the hard thing about running in it turns out the hard thing with Rose wasn't building the robots it was simulating the robots and the simulators quite a CPU intensive job it's graphics intensive you got this virtual world you're running and VR worlds are quite intensive and getting that installed and running was the hard part so what what what robot maker is is that as the service it's this simulator is called gazebo just a funny name so gazebo as a service is the actual service that effectively were charging for with a free tier so you can play with it and then we charge you for the sort of simulation units like how much computing time you're using when the rest of it is all you know cloud9 for the front end and deployment of fleets of data to fleets the robots and updating them and managing them but they're interesting thing is this is getting into like the people that the field of the first robotic thing is high schools high school robotic competitions they're interested yeah universities are interested in a university solar so we kind of it's not just for commercial production robots it's the whole training thing we're getting into STEM education if kids like playing with robots it's like Center and we're pulling all this in so now you can go home and take these like the latest most advanced AI algorithms that used to have to be doing a PhD at Stanford to be playing with and play with your kid you know over Christmas and see what you can come up with really simplifying the whole software development side of that when you look at the Dean came in competitions we're just awesome yeah all the kids they could have gravitate to the hardware cuz they can touch the software was really hard and and and this is gonna I think take a new level is particularly enough and it's all open source yeah you can go yes oh you've got this robot there no no I pointed them somebody who's complaining that we'd done it and no it was some proprietary robot thingy with the toy cars and I pointed them at the github URL it's that you can go build this thing it's all open source you can put anything else you want on it but the robot cars robot has rolls on it the robotic operating system H maker Robo maker all combined together and they're off running races and having all having fun now you guys are both Formula one fans yeah and you guys have been having some you know profile of Formula One folks here you got the little the mini vehicle riff on that really open source but I have another like thing I'm doing on the site it turns out the over the last year or so we started looking for opportunities to do sports sponsorship with a particular focus on Europe and the rest of the world we had a few US sports where they I don't know something with balls I like I like sports with wheels so about the middle of last year like this June we announced the deal with Formula One which is a multi-part deal part of the deal was just take them to the cloud that they have some data centers stuff they were running at a space and their data center is like no they wanted to do a technology refresh so for all the reasons that everyone else is moving to cloud we moved the sports core infrastructure to cloud over some number of years right so that's a process for starting and part of that is the archive of all Formula One races it's a treasure trove like 67 years of archive of everything they've got all the videos were digitizing it we're gonna figure out what to do what you know we've got to process it to label everything anyway so that's one thing and then we went turned up it we all turned up at Silverstone in the UK at that race it was the week after the announcement and that race we have a do as logos turning up on the screen because another piece was sponsorship so we start sponsoring the core video feed that Formula One uses to the world and that's 500 million fans watch Formula One so now 500 million fans for the next few years they're going to see a dope race logos on screen around the analytical insights of what is going on in the sport the odd rear tires are overheating you went round a corner this fast here's the pit stop strategy so we brand advertising associate with a high-technology sport and analytical insights and that's why we did that deal and they get all of our technology AI a lot of help helping them migrate and then the third thing we did that I got involved with was I'd already done a few CIO summits at Formula One races along the way so I was kind of like trying to poke my way into this thing that was happening I'm not involved in sponsorship set up right so hang on if you've done that thing yet and then them so we decided to do some executive events around Formula one so we'll pick a few races we'll have some you know corporate hospitality like things but when you put a bunch of senior executives together for a few days they share they solve each other's problems and you just get out of the way and they know the people that have solved one problem will share it with the other so it's a really it's like a tiny reinvent right here everyone is sharing if you sit next to someone what problem have you sold you can find stuff out so this is a concentrated version of that and we retired it in Monza earlier this year went great amazing I mean it's fun and it you know next to the business so it finally was like can we get someone on the car on Reba okay who's in Abu Dhabi on Saturday can we get them on Sunday night for the launch for the robot slut no this is like top guy in Formula One got here from Abu Dhabi if by Wednesday morning I'm just happy that they got here yeah that was that was a huge tire cube team we've watched your career you've been somebody who you know shares his knowledge and done some great work so thank you so much for coming back in the cube like that congratulations on all your great work Andy Jesse's coming up next we're excited about that keeper right to everybody we'll be back with our next guest Andy Jesse CEO of AWS right - this short break [Music]

>> 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.

>> Narrator: Live from Las Vegas, it's theCUBE. Covering AWS re:Invent 2017. Presented by AWS, Intel, and our ecosystem of partners. >> Welcome back and we're live here in Las Vegas. This is 45,000 people here for Amazon Web Services re:Invent. This is theCUBE's exclusive coverage. I'm John Furrier with my co-host Stu Miniman. And our next guests are Barry Russell, general manager and business development of AWS Marketplace, and John Rooney, Vice President of product management for Splunk, partner of AWS. Also we cover Cube.com, Cube alumnis. Welcome back, good to see you. >> Thank you, it's wonderful to be back. >> So what's it like partnering with AWS? Because you guys got a big mention from Andy Jassy on my interview with him last week, really highlighting Splunk as a partner that's done so well on the platform, in the ecosystem. You guys were called out as just a real success story. Congratulations, what's the secret magic formula? Just can't be making great products? >> No, really, I think the secret formula is really about helping customers, and sort of what do customers need, and getting it to them. And there is this sort of virtuous cycle of the more AWS continues to innovate in how customers can build, deploy, manage services and applications, really build a whole business in the cloud, the more varied visibility needs there are. And that's what we provide. So it's a really good symbiotic relationship. It's a partnership that goes back years and years. I think I was here in 2012 on theCUBE re:Invent that year. And every year, it seems like there is no shortage of services. >> You and Jerry Chen have been on every year of AWS. >> I'm trying to dress better. That first year I wore a black Splunk t-shirt. And my Aunt Merry Jo was really upset. Like, "Can you please dress up?" So I'm wearing a sport jacket and shirt. So doing my best. >> Whatever you do, don't wear a tie. I'm boycotting the tie. >> I'll try not to. Yeah. >> Barry, we've been talking about the engagement and integrations that you've been doing. Talk about Splunk, the category that they're in, and why that's important in the marketplace. >> Yeah, well they've been great at innovating with us. In particular, they offer customers the ability to really deeply analyze what's happening in their environment. And as customers are migrating over, that's been super important for us. As a customer makes a decision to shut down data centers and migrate those application workloads over, they want to understand what's happening in their environment. They want security within that environment. And Splunk has been innovating around that. And for us, they've been a great partner because not only have they offered a traditional machine image-based software. But now they offer Splunk Cloud, which is a SAS based offering. Which we know many enterprise customers are moving to that model. >> What's the Splunk formula for the product? Because I hear there's a lot. And it's been debunked, but I'll bring it up because it's out there in people's minds. Whoa if we partner with Amazon I don't know they might take over our company. So I won't say there's a general fear, but I've heard that before. >> No, no, I think our relationship, again, with Amazon, it is around delivering the best possible service. the best possible products to our customers and we feel like the Amazon platform is, it's obviously best in industry, and best in class. Look around at the people that are here. And our customers are going there in droves. And they're looking at moving workloads. They're looking at starting. I mean, that's the other thing that's great. And the interesting thing, That we heard so much about serverless in the last couple of days and so much about sort of the next paradigm in building applications. That's all because the groundwork's been set in the cloud by Amazon for when the cloud in 2008, 2009, 2010 was all forklift a VM into the cloud and that sort of cloud. Well now we're completely re-architecting. We're really thinking about re-thinking the way applications and services are built. And again, that brings in new changes and challenges in visibility. I think the early, the sort of last decade or so at the early stage of, what were the concerns around the cloud? It's like, well, what about security and what about visibility? Obviously Verner talked today in the keynote about security is job one. Every developer needs to think about security. That's no longer a concern. That's not a blocker for cloud migration. Then obviously you have things like the Kinesis Firehose. All these other sources of information and sources of data so that customers who are moving their workloads to the cloud still have the same and probably better and more manageable visibility then they would have if they were pulling log files off disks in their data center. >> John you mentioned customers going through that transformation. I remember when we first started covering the Splunk conference with theCUBE. It was heavily virtualization environment. I mean, I first came across Splunk from the VMware community and the like. Customers are being pulled and going through those transformations. You mentioned Kinesis, you talk about, I think you've got an announcement for the Alexa for business also. You have a pretty broad spectrum. I mean, Splunk, how do you manage that portfolio internally and with customers? How do you manage the, I wouldn't say old guard for Splunk but you know manage the modernization and all these changes that are happening? >> Well, sort of the mental model for Splunk has always been, we'll go and get your data wherever it is and we'll pull it into Splunk so then you can correlate, visualize, search, and get value out of that data. And in some cases, that data is going to live, again, in the traditional distributed data center environment. Is going to be a log written to disk. There are still some industries where there are still mainframes. I know it seems crazy, but that is still a big piece and that's not necessarily going to go away tomorrow or the next day. But more importantly, I think increasingly, you're going to see, not just a, again, take an existing VM and forklift that into an IS environment. Lets re-architect an entire service. Lets rethink the way that we're delivering value to our customers. Those are the interesting opportunities for us It's a very close partnership with AWS. We're very closely aligned with the teams. So as they think about services, Cloud Trails, and the Kinesis Firehose, and Guard Duty. These things that they realize are valuable to their customers because they are here and their customers ask for it. We have just a good partnership that says, how can we plug in? How can we contribute to that initiative? >> Hey Barry, there's a word that John used that I want to ask you about. It's data. So you know when we interviewed Andy last year I put forth the premise, I think data is going to be the next flywheel for AWS. How does the marketplace look at that? You work with your partners, obviously integrations, the APIs but data is at the center of it. And how do you make sure that you are securing the data? Make sure that only the people have it but that partners can also help customers get more value out of it? >> Well you know all the applications we list in the catalog are put through security tests and we scan the applications themselves, the code, 24 hours a day seven days a week. It's part of the value we add. But working with ISVs like Splunk we also build API integration to services like Kinesis Firehose, like S3, like Aurora, so that customers have the opportunity to move their data over into AWS, which is where it's secure, and then leverage secure software to access and analyze that data. So I think he's exactly right in working in partnership with AWS. There's that connective tissue between a third party software and the native AWS service. >> Where's it go next for you guys? I mean, obviously, I think you're right about this whole partnership thing. Even though I brought that other question up. The growth is so massive. You can innovate with AWS. It's not like you're just partnering with them and putting it in a marketplace and hope someone buys it. There's growth. I think that's the nuance that people don't understand, is that you can do more with AWS. >> Well yeah I mean absolutely. I think the ability to be part of, the same way, again, in the keynote today, we talked about building in security from the get go. You start with security and with functionality. I think the notion of visibility and observability from a data standpoint. If you are building something, how do you know it's working? How can you provide the folks in operational roles and business roles the data and information that they need? So if you bake that in from the beginning, we now have an opportunity for Splunk to rethink our integration points. To rethink how we deliver value to customers. Again if you think about the Splunk origin story, we started with monitoring and troubleshooting in production environments. Right? Obviously, we built the company on that. We drink a lot of free soda in San Francisco based on those use cases. But if you think about now with DevOps and sort of the shift left movement that >> Your chair has grown significantly, big time because more services are available. >> More services are available but also people are rethinking the whole notion of product development and life cycle. And again I think DevOps, in many cases, the accelerant for DevOps has been cloud and obviously the accelerant for cloud has been AWS. >> Alright question for both of you guys because we've been talking about this on theCUBE and I've got Andy coming on in a few hours. We believe there is going to be a renaissance in software development. You mentioned software lifecycle. You can see it here. Verner's keynote about re-imagining architecture. He put the basic architecture slide up from a video streaming company, boxes and lines, normal architecture. Then S3 buckets, it looked completely different. So the question is with all the simplicity now, all this simplification in APIs. This is going to be a real boom for developers. We believe this is going to be a renaissance in software development, because it's not going to be you grandfather's software development lifecycle. Do you believe that, and how do you see software developers evolving? More craft? More artisanship? What do you see? >> I think that the confines of the scope of what a developer did five, ten, fifteen years ago is different. Developers didn't think about security. They didn't care about security. They didn't think about scalability. They didn't think about. What does elasticity of scale look like in my application? I don't know it worked in my dev environment. That now feels archaic. That's like leeches. Nobody does business like that anymore, right? And I think that's where the notion of >> Cloud9 was an impressive demo too. >> Absolutely. >> Things like that are coming down >> Yeah the idea that you have a fully powered IDE that includes interactivity in the cloud. Folks have sort of dreamt of that. If you think about how heavyweight the client based IDE has got to a certain point kind of in the late odds. Everyone went away from that and said nope we're just going to VI everything. I don't want to see, I don't want to plug in. I don't want to download anything. I just want to VI anything. Now it's sort of, we're back to. I have this full set of functionality. I have code completion, and I have all the things I need as a developer to help me. But its completely light weight. It's a service. It's a utility. It's like the faucet. So-- >> Here's what I would say. I would say that for the first time developers are going to have a rich set of options where they can choose how the customer deploys the software. Containers or serverless. API based or SAS. With the consumption model that matches that use case. Hourly, and metered, annual, or multi-year or consumed via an API service. >> It's going top be awesome and creative too. A lot of creativity. Final question because I know both of your companies very well. Both have really strong communities. The role of communities, certainly open source is growing exponentially. We're seeing that with the Linux Foundation and a variety of other places. With the cloud flywheel, with the open source flywheel, we believe communities are going to be very important. You guys both have strong communities, Splunk and AWS. What would you say to folks that aren't thinking about nurturing and building community into their products? >> I would say that our company was built by our early advocates. I mean again, our mission at the end of the day and from the very beginning was our core practitioners, our users. It's a little slightly different now AWS is sort of the classic developer but for us it was the sysadmin, the tier one and tier two SOC analysts and security. How do we help their lives? How do we make their job better? So we have to have an intimate understanding of what problems are they trying to solve? How do we solve that? How do we abstract away, essentially, the high-effort low-value parts of their job? Have the software do that, so they get to the point where their focus is on the. Essentially they get to apply their intellect, their expertise. Then they evangelize for us. So community is one hundred percent essential. It doesn't matter how great the mouse trap is if you are not connecting with people, if you are not making people part of that and allowing people to share ideas. >> So you had a strategy for community out of the gate. >> Yeah I think it's community first. >> Without community you don't get the feedback on how to improve your product. It's that simple. >> That simple, all right. Man, a great conversation. Marketplace is booming. General Manager of the Marketplace, Barry Russell. We got also John Rooney vice president of product marketing at Splunk. Very successful company. Gone from very small niche product, great community, to public company and now taking over the data world. Great to see you, John. Thanks for coming on. Barry, thanks for the commentary. >> Thank you. >> It' theCUBE 45,000 people here live in Vegas for re:Invent. I'm John Furrier and Stu. We'll be back with more coverage after this short break. (upbeat music)