(bright music) (crowd talking indistinctly in the background) >> Hey guys, welcome back to Detroit, Michigan. theCUBE is live at KubeCon + CloudNativeCon 2022. You might notice something really unique here. Lisa Martin with our newest co-host of theCUBE, Savannah Peterson! Savannah, it's great to see you. >> It's so good to be here with you (laughs). >> I know, I know. We have a great segment coming up. I always love talking couple things, cars, one, two, with companies that have been around for a hundred plus years and how they've actually transformed. >> Oh yeah. >> Ford is here. You have a great story about how you, about Ford. >> Ford brought me to Detroit the first time. I was here at the North American International Auto Show. Some of you may be familiar, and the fine folks from Ford brought me out to commentate just like this, as they were announcing the Ford Bronco. >> Satish: Oh wow. >> Which I am still lusting after. >> You don't have one yet? >> For the record. No, I don't. My next car's got to be an EV. Although, ironically, there's a Ford EV right behind us here on set today. >> I know, I know. >> Which we were both just contemplating before we went live. >> It's really shiny. >> We're going to have to go check it out. >> I have to check it out. Yep, we'll do that. Yeah. Well, please welcome our two guests from Ford, Satish Puranam, is here, The Technical Leader at Cloud and Rebecca Risk, Principal Architect, developer relations. We are so excited to have you guys on the program. >> Clearly. >> Thanks for joining us. (all laugh) >> Thank you for having us. >> I love you're Ford enthusiasts! Yeah, that's awesome. >> I drive a Ford. >> Oh, awesome! Thank you. >> I can only say that's one car company here. >> That's great. >> Yes, yes. >> Great! Thank you a lot. >> Thank you for your business! >> Absolutely. (all laugh) >> So, Satish, talk to us a little bit about- I mean I think of Cloud as a car company but it seems like it's a technology company that makes cars. >> Yes. Talk to us about Ford as a Cloud first, technology driven company, and then we're going to talk about what you're doing with Red Hat and Boston University. >> Yeah, I'm like everything that all these cars that you're seeing, beautiful right behind us it's all built on, around, and with technology, right? So there's so much code goes into these cars these days, it's probably, it's mind boggling to think that probably your iPhones might be having less code as opposed to these cars. Everything from control systems, everything is code. We don't do any more clay models. Everything is done digital, 3D, virtual reality and all that stuff. So all that takes code, all of that takes technology. And we have been in that journey for the last- since 2016 when we started our first mobile app and all that stuff. And of late we have been like, heavily invested in Google. Moving a lot of these experiences, data acquisition systems AI/ML modeling for like all the autonomous cars. It's all technology and like from the day it is conceived, to the day it is marketed, to the day when you show up for a servicing, and hopefully soon how you can buy and you know, provide feedback to us, is all technology that drives all of this stuff. So it's amazing for us to see everything that we go and immerse ourselves in the technology. There is a real life thing that we can see what we all do for it, right? So- >> Yes, we're only sorry that our audience can't actually see the car, >> Yep. >> but we'll get some B-roll for you later on. Rebecca, talk a little bit about your role. Here we are at KubeCon, Savannah and I and John were talking when we went live this morning, that this is huge. That the show floor is massive, a lot bigger than last year. The collaboration and the spirit of the community is not only alive and well, as we heard in the keynote this morning, it's thriving. >> Yeah. >> Talk about developer relations at Ford and what you are helping to drive in your role. >> Yeah, so my team is all about helping developers work faster with different platforms that my team curates and produces, so that our developers don't have to deal with all of the details of setting up their environments to actually code. And we have really great people, kind of the top software developers in the company, are part of my team to produce those products that other people can use, and accelerate their development. And we have a great relationship with the developers in the company and outside with the different vendor relationships that we have, to make sure that we're always producing the next platform with the next tech stack that our developers will want to continue to use to produce the really great products that we are all about making at Ford. >> Let's dig in there a little bit because I'm curious and I suspect you both had something to do with it. How did you approach your Cloud Native transformation and how do you evaluate new technologies for the team? >> It's sometimes- many a times I would say it's like dogfooding and like experimentation. >> Yeah. Isn't anything in innovation a lot of- >> Yeah, a lot of experimentation. We started our, as I said, the Cloud Native journey back in 2016 with Cloud Foundry and things, technologies around that. Soon realized, that there was like a lot of buzz around that time. Twelve-Factor was a thing, Stateless was a thing. And then all those Stateful needs to drive the Stateless. So where do we do that thing? And the next logical iteration was Kubernetes was bursting upon the scene at that time. So we started doing a lot of experimentation. >> Like the Kool-Aid man, burst on the Kubernetes scene- >> Exactly right. >> Through the wall. >> So, the question is like, why can't we do? I think we were like crazy enough to say that Kubernetes people are talking about our serverless or Twelve-Factor on Kubernetes. We are crazy enough to do Stateful on Kubernetes and we've been doing it successfully for five years. So it's a lot about experimentation. I think good chunk of experiments that we do do not yield the results that we get, but many a times, some of them are like Gangbusters. Like, other aspects that we've been doing of late is like partnering with Becky and rest of the organization, right? Because they are the people who are like closest to the developers. We are somewhat behind the scenes doing some things but it is Becky and the rest of the architecture teams who are actually front and center with the customers, right? So it is the collaborative effort that we've been working through past few years that has been really really been useful and coming around and helping us to make some of these products really beautiful. >> Yeah, well you make a lot of beautiful products. I think we've all, I think we've all seen them. Something that I think is really interesting and part of why I was so excited for this interview, and kind of nudged John out, was because you've been- Ford has been investing in technology in a committed way for decades and I don't think most people are aware of that. When I originally came out to Dearborn, I learned that you've had a head of VR who happens to be a female. For what it's worth, Elizabeth, who's been running VR for you for two and a half decades, for 25 years. >> Satish: Yep. >> That is an impressive commitment. What is that like from a culture perspective inside of Ford? What is the attitude around innovation and technology? >> So I've been a long time Ford employee. I just celebrated my 29th year. >> Oh, wow! >> Congratulations! >> Wow, congrats! That's a huge deal. >> Yeah, it's a huge deal. I'm so proud of my career and all that Ford has brought to me and it's just a testament. I have many colleagues like me who've been there for their whole career or have done other things and come to Ford and then spent another 20 years with us because we foster the culture that makes you want to stay. We have development programs to allow you to upscale and change your role and learn new things and play with the new technologies that people are interested in doing and really make an impact to our community of developers at Ford or the company itself and the results that we're delivering. So to have that, you know, culture for so many years that people really love to work. They love to work with the people that they're working with. They love to stay engaged and they love the fact that you can have many different careers within the same umbrella, which we call the "blue oval". And that's really why I've been there for so long. I think I probably had 13 very unique and different jobs along the way. It's as if I left, and you know shopped around my skills elsewhere. But I didn't ever have to leave the company. It's been fabulous. >> The cultural change and adoption of- embracing modern technology- Cloud Native automotive software is impressive because a lot of historied companies, you guys have been there a long time, have challenges with that because it's really hard to get an entire moving, you'll call it the blue oval, to change and adapt- >> Savannah: I love that. >> and be willing to experiment. So that that is impressive. Talk about, you go by Becky, so I'll call you Becky, >> Rebecca/Becky: Yeah. >> The developer culture in terms of the developers really being the center of the nucleus of influencing the direction in which the company's going. I imagine that they probably are fairly influential. >> Yeah, so I had a very- one of the unique positions I held was a culture change for our department, Information Technology in 2016. >> Satish: Yeah. >> As the teacher was involved with moving us to the cloud, I was responsible- >> You are the transformation team! This is beautiful. I love this. We've got the right people on the show. >> Yeah, we do. >> I was responsible for changing the culture to orient our employees to pay attention to what do we want to create for tomorrow? What are the kind of skills we need to trust each other to move quickly. And that was completely unique. >> Satish: Yeah. >> Like I had men in the trenches delivering software before that, and then plucked out because they wanted someone, you know who had authentic experience with our development team to be that voice. And it was such a great investment that Ford continues to do is invest in our culture transformation. Because with each step forward that we do, we have to refine what our priorities are. And you do that through culture transformation and culture management. And that's been, I think really, the key to our successful pivots that we've made over the last six years that we've been able to continue to refine and hone where we really want to go through that culture movement. >> Absolutely. I think if I could add another- >> Please. >> spotlight to it is like the biggest thing about Ford has been among various startup-like culture, right? So the idea is that we encourage people to think outside the box, right? >> Savannah: Or outside the oval? >> Right! (laughs) >> Lisa: Outside the oval, yes! >> Absolutely! Right. >> So the question is like, you can experiment with various things, new technologies and you will get all the leadership support to go along with it. I think that is very important too and like we can be in the trenches and talk about all of these nice little things but who the heck would've thought that, you know Kubernetes was announced in 2015, in late 2016, we have early dev Kubernetes clusters already running. 2017, we are live with workloads on Kubernetes! >> Savannah: Early adopters over here. >> Yeah. >> Yeah. >> I'm like all of this thing doesn't happen without lot of foresight and support from the leadership, but it's also the grassroot efforts that is encouraged all along to be on the front end of all of these things and try different things. Some of them may not work >> Savannah: Right. >> But that's okay. But how do we know we are doing something, if you're not failing? We have to fail in order to do something, right? >> Lisa: I always say- >> So I think that's been a great thing that is encouraged very often and otherwise I would not be doing, I've done a whole bunch of stuff at Ford. Without that kind of ability to support and have an appetite for, some of those things would not have been here at all. >> I always say failure is not a bad F-word. >> Satish: Yep. >> Savannah: I love that. >> But what you're talking about there is kind of like driving this hot wheel of experimentation. You have to have the right culture and the mindset- >> Satish: Absolutely. >> to do that. Try fail, move on, learn, iterate, go. >> Satish: Correct. >> You guys have a great partnership with Red Hat and Boston University. You're speaking about that later today. >> Satish: Yes. >> Unpack that for us. What, from a technical perspective, what are you doing and what's it resulting in? >> Yeah, I think the biggest thing is Becky was talking about as during this transformation journey, is lot has changed in very small amount of time. So we traditionally been like, "Hey, here's a spreadsheet of things I need you to deliver for me" to "Here is a catalog of things, you can get it today and be successful with it". That is frightening to several of our developers. The goal, one of the things that we've been working with Q By Example, Red Hat and all the thing, is that how can we lower the bar for the developers, right? Kubernetes is great. It's also a wall of YAML. >> It's extremely complex, number one complaint. >> The question is how can I zero on? I'm like, if we go back think like when we talk about in cars with human-machine interfaces, which parts do I need to know? Here's the steering wheel, here's the gas pedal, or here's the brake. As long as you know these two, three different things you should be fairly be okay to drive those things, right? So the idea of some of the things with enablementing we are trying to do is like reduce that barrier, right? Reduce- lower the bar so that more people can participate in it. >> One of the ways that you did that was Q By Example, right, QBE? >> Satish: Yes, Yes. >> Can you tell us a little bit more about that as you finish this answer? >> Yeah, I think the biggest thing with Q By Example is like Q By Example gives you the small bite-sized things about Kubernetes, right? >> Savannah: Great place to start. >> But what we wanted to do is that we wanted to reinforce that learning by turning into a real world living example app. We took part info, we said, Hey, what does it look like? How do I make sure that it is highly available? How do I make sure that it is secure? Here is an example YAML of it that you can literally verbatim copy and paste into your editor and click run and then you will get an instant gratification feedback loop >> I was going to say, yeah, they feel like you're learning too! >> Yes. Right. So the idea would be is like, and then instead of giving you just a boring prose text to read, we actually drop links to relevant blog posts saying that, hey you can just go there. And that has been inspirational in terms of like and reinforcing the learning. So that has been where we started working with the Boston University, Red Hat and the community around all of that stuff. >> Talk a little bit about, Becky, about some of the business outcomes. You mentioned things like upskilling the workforce which is really nice to hear that there's such a big focus on it. But I imagine too, there's more participation in the community, but also from an end customer perspective. Obviously, everything Ford's doing is to serve the end customers >> Becky: Right. How does this help the end customer have that experience that they really, these days, demand with patience being something that, I think, is gone because of the pandemic? >> Right? Right. So one of the things that my team does is we create the platforms that help Accelerate developers be successful and it helps educate them more quickly on appropriate use of the platforms and helps them by adopting the platforms to be more secure which inherently lead to the better results for our end customers because their data is secure because the products that they have are well created and they're tested thoroughly. So we catch all those things earlier in the cycle by using these platforms that we help curate and produce. And that's really important because, like you had mentioned, this steep learning curve associated with Kubernetes, right? >> Savannah: Yeah. >> So my team is able to kind of help with that abstraction so that we solve kind of the higher complex problems for them so that developers can move faster and then we focus our education on what's important for them. We use things like Q By Example, as a source instead of creating that content ourselves, right? We are able to point them to that. So it's great that there's that community and we're definitely involved with that. But that's so important to help our developers be successful in moving as quickly as they want and not having 20,000 people solve the same problems. >> Satish: (chuckles) Yeah. >> Each individually- >> Savannah: you don't need to! >> and sometimes differently. >> Savannah: We're stronger together, you know? >> Exactly. >> The water level rises together and Ford is definitely a company that illustrates that by example. >> Yeah, I'm like, we can't make a better round wheel right? >> Yeah! So, we have to build upon what we have already been built ahead of us. And I think a lot of it is also about how can we give back and participate in the community, right? So I think that is paramount for us as like, here we are in Detroit so we're trying to recruit and show people that you know, everything that we do is not just old car and sheet metal >> Savannah: Combustion. >> and everything and right? There's a lot of tech goes and sometimes it is really, really cool to do that. And biggest thing for us is like how can we involve our community of developers sooner, earlier, faster without actually encumbering them and saying that, hey here is a book, go master it. We'll talk two months later. So I think that has been another journey. I think that has been a biggest uphill challenge for us is that how can we actually democratize all of these things for everybody. >> Yeah. Well no one better to try than you I would suspect. >> We can only try and hope everything turns out well, right? >> You know, as long as there's room for the bumpers on the lane for if you fail. >> Exactly. >> It sounds like you're driving the program in the right direction. Closing question for you, what's next? Is electric the future? Is Kubernetes the future? What's Ford all in on right now, looking forward? (crowd murmuring in the background) >> Data is the king, right? >> Savannah: Oh, okay, yes! >> Data is a new currency. We use that for several things to improve the cars improve the quality of autonomous driving Is Level 5 driving here? Maybe will be here soon, we'll see. But we are all working towards it, right? So machine learning, AI feedback. How do you actually post sale experience for example? So all of these are all areas that we are working to. We are, may not be getting like Kubernetes in a car but we are putting Kubernetes in plants. Like you order a Marquis or you order a Bronco, you see that here. Here's where in the assembly line your car is. It's taking pictures. It's actually taking pictures on Kubernetes platform. >> That's pretty cool. >> And it is tweeting for you on the Twitter and the social media platform. So there's a lot of that. So it is real and we are doing it. We need more help. A lot of the community efforts that we are seeing and a lot of the innovation that is happening on the floor here, it's phenomenal. The question is how we can incorporate those things into our workflows. >> Yeah, well you have the right audience for that here. You also have the right attitude, >> Exactly. >> the right appetite, and the right foundation. Becky, last question for you. Top three takeaways from your talk today. If you're talking to the developer community you want to inspire: Come work for us! What would you say? >> If you're ready to invest in yourself and upskill and be part of something that is pretty remarkable, come work for us! We have many, many different technical career paths that you can follow. We invest in our employees. When you master something, it's time for you to move on. We have career growth for you. It's been a wonderful gift to me and my family and I encourage everyone to check us out careers.ford.com or stop by our booth if you're happen to be here in person. >> Satish: Absolutely! >> We have our curated job openings that are specific for this community, available. >> Satish: Absolutely. >> Love it. Perfect close. Nailed pitch there. I'm sure you're all going to check out their job page. (all laugh) >> Exactly! And what you talked about, the developer experience, the customer experience are inextricably linked and you guys are really focused on that. Congratulations on all the work that you've done. We got to go get a selfie with that car girl. >> Yes, we do. >> Absolutely. >> We got to show them, we got to show the audience what it looks like on the inside too. We'll do a little IG video. (Lisa laughs) >> Absolutely. >> We will show you that for our guests and my cohost, Savannah Peterson. Lisa Martin here live in Detroit with theCUBE at KubeCon and CloudNativeCon 2022. The one and only John Furrier, who you know gets FOMO, is going to be back with me next. So stick around. (all laugh) (bright music)

>>mhm. Joining me now is Drew Schlussel, who is the senior director of product marketing at Wasabi. Hey, Drew. Good to see you again. Thanks for coming back in the Cube. >>They great to be here. Great to see you. >>All right, let's get into it. You know, Drew prior to the pandemic zero trust. Just like, kind of like a digital transformation. It was sort of a buzzword. And now it's become a real thing. Almost a mandate. What's what's Arby's take on zero trust? >>Uh, so absolutely right it was. It's been around a while, and now people are paying attention. Uh, sabes take is zero. Trust is is a good thing. Uh, you know, there are There are too many places right where the bad guys are getting in. And, you know, I think of zero. Trust is as kind of smashing laziness, right? It takes a little work, takes some planning, but, you know, done properly and using the right technology is using the right vendors. The rewards are of course, tremendous. Right? You you you can put to rest the fears of of ransomware and having your systems compromised. >>Well, and we're going to talk about this. But there's a lot of process and thinking involved and, you know, design in your zero trust. And you don't want to be wasting time messing with infrastructure. So we're gonna talk about that. There's a lot of discussion in the industry drew about a mutability and air gaps. I'd like you to share wasabi point of view on these topics. How do you approach it? And what makes wasabi different? >>Uh, so in terms of air gap and mutability, right, the beautiful thing about object storage, which is what we do all the time, is that it makes it that much easier. Right? To have a secure, immutable copy of your data someplace that's easy to access and, uh, doesn't cost you an arm and a leg to get your data back. Um, we're working with some of the best partners in the industry. Um, you know, we're working with folks like VM con vault Arc Marquis MSP 3. 60. Um, all folks who understand that you need to have multiple copies of your data. You need to have a copy stored offsite, and that copy needs to be immutable. And we can We can talk a little bit about what a mutability is and what it really means. >>You know, I want I wonder if you could talk a little bit more about with subi solution, because sometimes people don't understand. You actually are a cloud you're not building on other people's public clouds. And storage is the one use case where it actually makes sense to do that. Tell us a little bit more about those ABS approach and your solution. >>Yeah, I appreciate that. So there's there's definitely some misconception. We are our own cloud storage service. We don't run on top of anybody else, right? It's It's our systems. It's our software deployed globally, and we interoperate because we adhere to the S three standard. We interoperate with practically hundreds of applications, primarily in this case, right? We're talking about backup and recovery applications, and it's such a simple process, right? I mean, uh, just about everybody who's anybody in this business, protecting data has the ability now to, uh, access cloud storage. And so we've made it really simple. Uh, in many cases, you'll see wasabi, as you know, listed in the primary set of available vendors and, uh, you know, put in your private keys. Make sure that your account is locked down properly using, uh, let's say multi factor authentication, and you've got a great place to store copies of your data securely. >>I mean, we just heard from David friend. I did my math, right? He was talking about, you know, 1/6 the cost per terabyte per month, Maybe even a little better than that. How are you able to achieve such attractive economics? >>Yeah, So, you know, I can't remember how to translate my fractions into percentages, but I think we talk a lot about being 80% right, less expensive than the hyper scholars. And, you know, we talked about this at demon, right? There's there's some secret sauce there. Um, and, you know, we take a different approach to how we utilise the raw capacity to the effective capacity. And the fact is, we're also not having to run a few 100 other services, right? We do storage plain and simple all day, all the time, so we don't have to worry about overhead to support, you know, up and coming other services that are perhaps, uh, you know, going to be a loss leader right. Um, customers love it, right? They see the fact that their data is growing 40 80% year over year. They know they need to have some place to keep it secure. And, uh, you know, folks are flocking to us in droves. In fact, we're We're seeing a tremendous amount of migration, actually, right now, multiple petabytes being brought to Assad because folks have figured out that they can't afford to keep going with their current hyper scale or vendor. >>And the mutability is a feature of your product, right? What's the feature called? Can you dig? Double click on that a little bit? >>Yeah, Absolutely. Um So the determined s three is object lock. And what that means is your application will write an object to cloud storage, and it will define a retention period. Let's say a week. And for that period, that object is immutable. Untouchable cannot be altered in any way, shape or form. The application can't change it. The system administration can't change it with subi Can't change it. Okay, it is truly carved in stone, and this is something that it's been around for a while. But you're seeing a huge uptick in adoption and support for that feature by all the major vendors. And I named off a few earlier. Um, and the best part is that with the mutability comes some some sense of Well, it comes with not just a sense of security. It is security, right when you have data that cannot be altered by anybody. Um, even if the bad guys compromise your account, they steal your credentials, right? They can't take away the data. And that's a beautiful thing. A beautiful, beautiful thing. >>And you look like an s three bucket. Is that right? >>Yeah. Yeah. I mean, we're fully compatible with the S three a p I. So if you're using S three a p I based applications today, um, it's a very simple matter of just kind of redirecting where you want to store your data. Beautiful thing about backup and recovery, right? That's probably the simplest application. Simple being a relative term as far as lift and shift right, because that just means for your next full right point that it was subi retain your other falls for whatever 30 60 90 days. And then once you've kind of made that transition from vine divine. You know you're off and running with wasabi. >>I talked to my open about the allure of object storage. Historically, you know the simplicity of the get put syntax. But what about performance? Are you able to deliver performance? That's that's comparable to other storage formats. >>Oh, yeah, Absolutely. And we've got the We've got the performance numbers on the site to back that up. But I forgot to answer something earlier, Right? You said that the mutability is a feature, and I want to make it very clear that it is a feature, but it's an API request. Okay, So when you're talking about gets and puts and so forth, you know the comment you made earlier about being 80% more cost effectively, percent less expensive. Um, you know that API call, right? It's typically something that the other folks charge for, right? And I think we use the metaphor earlier about the refrigerator. Uh, but I'll use a different metaphor today, right? Uh, you can think of cloud storage as as a magical coffee cup, right? It gets as big as you want to store as much copy as you want. And the coffee is always warm right, And when you want to take a sip, there's no charge. You want to pop the lid and see how much coffee is in there. No charge. And that's an important thing. Because when you're talking about millions or billions of objects and you want to get a list of those objects or you want to get the status of the immutable settings for those objects anywhere else, it's going to cost you money to look at your data. We'll also be no additional charge, and that's part of the thing that sets us apart. >>Excellent. Thank you for that. So you mentioned some partners before. How do partners fit into the wasabi story? Where do you stop? Where do they pick up what you know, What do they bring? Can you give us maybe a paint a picture for us? Example or two? >>Sure. So again, we just do storage, right? That is our Our sole purpose in life is to, you know, to safely and securely store our customers' data. And so they're working with, uh, their application vendors. Whether it's, you know, active archive backup in recovery, uh, Iot surveillance, uh, media and entertainment workflows, right? Those systems already know how to manage the day to manage the metadata. They just need someplace to keep the data that is being worked on being stored and so forth. All right, so just like, uh, you know, plugging in a flash drive on your laptop, right? You literally can plug in wasabi as long as your applications support the AP getting started. Incredibly easy, right. We offer a 30 day trial, one terabyte, and most folks find that within, you know, probably a few hours of their P O. C. Right. Um, it's giving them everything they need in terms of performance, in terms of accessibility, in terms of sovereignty. I'm guessing you talked to, uh, you know, Dave friend earlier about data sovereignty, right. We're global company. All right, so there's got to be probably, you know, wherever you are in the world, someplace that will satisfy your sovereignty requirements, um, as well as your compliance requirements. >>We did talk about sovereignty, Drew. This is really what's interesting to me. A bit of an industry historian. When I look back to the early days of cloud, I remember the large storage companies, you know, they CEOs would say, We're going to have an answer for the cloud and they would go out. And for instance, I No. One bought competitor of carbonite and then couldn't figure out what to do with it. They couldn't figure out how to compete with the cloud, in part because they were afraid it was going to cannibalise their existing business. I think another part is because they just didn't have that imagination to develop an architecture that in a business model that could scale to see that you guys have done that is I love it because it brings competition. It brings innovation, and it helps lower clients cost and solve really nagging problems like, you know, uh, Ransomware, mutability and recovery. I'll give you the last word, Drew. >>Yeah, you're absolutely right. You know, the the on prem vendors. They're not going to go away anytime soon, right? There's always going to be a need for, you know, incredibly low latency high band with, you know, But, uh, you know, not all data is taught all the time. And by hot, I mean, you know, extremely hot. Uh, you know, uh, you know, let's take, uh, you know real time, Uh, analytics for maybe facial recognition, right, That requires sub millisecond type of processing. But once you've done that work right, you want to store that data for a long, long time, and, uh, you're gonna want to also tap back into it later. So, you know, other folks are telling you that, you know, you can go to these like cold, glacial type of tiered storage. Don't believe the hype. You're still going to pay way more for that than you would with just a wasabi like hot cloud storage system. And, you know, we don't compete with our partners, right? We complement you know what they're bringing to market in terms of the software vendors in terms of the hardware vendors were beautiful component for that hybrid cloud architecture. And I think folks are gravitating towards that. I think the cloud is kind of hitting a new gear, if you will, in terms of adoption and recognition for the security that they can achieve with it. >>All right, Drew, Thank you for that. We definitely We see the momentum in a moment. Drew and I will be back to get the customer perspective with Kevin Referenda, who's the director of information technology services at the Hodgkiss School. Keep it right there. >>Mhm

>>from the Cube Studios in Palo Alto and Boston connecting with thought leaders all around the world. This is a cube conversation. Hi, I'm stupid, man. And welcome to a cube conversation. I'm coming to you from our Boston area studio, and we're gonna be talking about the networking giant. So, uh, joining me is the first time on the program some of the members been on and the cover launch of Pensando so vivid Jane, his CTO and co founder of Pensando Bipin thanks so much for joining us. >>Thank you. It was very nice talking to you. >>All right, so in a big theme we've been talking about for a number of years now is multi cloud. And, you know, I go back and think about you know, that the concept of cloud and even, you know, I've been around long enough You think about the and one of the challenges you look at is well, security is always a challenge. The other things network bandwidth is not infinite. The speed of light has not been solved, though you know, help us understand is you know the first I guess give our audience a little bit of your background. As I said, anybody in the networking world knows less team, though. Tell us, you know, have you been on the journey with them for all of that? Or And you know what brought you and Sandy? >>Yes. Yes. Um, I mean, I've been in the journey with the team since 2000 and six, so it's pretty long, I would say 14 years now, and it's been tremendous. Um uh, at heart, I'm an engineer who takes, you know, Brian brilliant things and taking upon challenges. And I've got multiple startups before this been in a new era, The more startups before that. And of course, you know, they were not experience more independent startups. And, you know, all through the course, I have gained appreciation for, like, you know, starting all the way from silicon to build a distributed systems and a u io all the way up to the fully consumable, you know, system. So I I totally understand the the angle I need to look at this time in a holistic manner. Having contributed to Cisco, UCS of and Nexus products on. Before joining pensando, I was, um I was contributing with my own open source container networking project, which is quite exciting to see How do you evangelize, You know, my own my own core, and that was fun. And that's where I come from, But, uh, but I I'm I'm a software engineer. To start off it started contributing to a six, then started going into the application world with containers trying to pull a container networking with, Ah, we did a server product with Cisco UCS and on and pretty much all over the stack with respect, participation. So that's my background. Um, but it's being exciting to consider what's next for me. And I was largely trying to see >>so, so definitive, actually, if I If I could jump in there, right, you know, I think back the UCS it was, You know, some of those ways I gather virtualization had been around for quite a number of years at that point. But, you know, how do you optimize it you're in. How do you transform infrastructure toe live for those environments, though? You know, UCS, You know, remember, people get back saying, you know, Cisco getting into services like Well, they are. They are because they're changing that compute model really caught that. You know, Cisco led that way. If the urge instructor, so many things you talked about that we'll get to later in the interview open for station. When I look out today, you know infrastructure's paint a lot and cloud obviously, is a huge impact, but also the application. So help us understand kind of the the waves that were writing together And, you know, what was it that you know in Santo decided to build in order to meet what you know, the customers of a require >>Um So I think, you know, going back to the UCS common that you had We started off thinking, for example, what are what were the challenges with respect is scaling out the deployment of servers and we quickly realized that manageability is number one challenge on. And of course, you know when we speak about manageability, it comes down to the underpinnings of what you're building. Are you Are you able to see the entire infrastructure together, or are you still seeing those big pieces? And that's when I think UCS was born to say that Look, we need to bring everything together that could be consumed in a holistic manner. And for that you have to have all those components there are There are somewhat independent to be consumed as a unified thing. And which is why I think it was a unified computing system. UCS. Um and then I think, you know, and Sanders a journey that takes it to probably not just that concept, but in general, the the challenges and the disruptions that we're seeing to the next level. So, I mean, just to summarize, I would say we started off looking at all the disruptions that are happening in the industry. And there are many of those I'm happy to talk about, which means we looked at, uh and then we looked at What are the consumption models that people are largely, you know, finding it very appealing these days because the days in which you're going to write a spirit to do something is still pretty old you want to be able to consume and most this after consumable way, How can we build, you know, how can you build systems that are programmable in the field? Those kind of things? The consumption model reliability software is the friendly factor there, and highly appealing to you guys and all their last one. You know, at least we also we also wanted to be really heard in the game, competitiveness wise. So those were like the the overarching set of things there that we started to think about, like, what descriptions are we going to solve, um, and how the consumption model needs to be for or ah, for the future of infrastructure. And how can we get that key, which is which is far ahead and better than anything that exists out there? So that's where we started to look at. Let's bring something which is bigger B sphere and and something. Even if we have the possibility of feeling it. Let's go ahead and they're doing their anything. >>Yeah, and absolutely. There's been so much discussion over the last decade or so about about software's eating the world and what's going on there yet you know, your your team mates. It's a lot of times it's been the chip set. There have been some huge ripples in the industry, you know, major acquisitions by some of the big, disruptive companies out there. Apple made a silicon acquisition, you know, everybody paid and that will have. You can't talk about disruption today without talking about Amazon. And, of course, when Amazon bought Annapurna Labs, you know, those of us looking at the Enterprise and the clouds base was like, Keep an eye on this. And absolutely, it's been something over the last year or so now, where we've seen Amazon roll things out and, of course, a critical component of what Amazon's doing from outposts. So with that as the stage there, you talked about wanting to be interesting leading, you know Amazon, you know, is really sick, and it's setting the bar that everyone is measured against. And when I look at the solution pensando, the kind of best comparable analogy that we've seen is, you know, look at what Nitro chip can do. This is an alternative for all of the other 1000 for customers that might not want to get them from Amazon. Is that a fair comparison? And how would you line up what founder is doing compared to what Amazon has done there? >>Um, so you know, what you've seen in the Amazon announcement really is possible. Amazon is a great benchmark to beat eso No make mistakes. We are very happy to say that, you know, we are We are doing by comfortably so But then, you know, Amazon is more than more than just the just the chips that are that they are building. I mean, what you consume is what they're building and underneath the engines are really part up by by the nicety off all these things that they're very, um, having said that, you know, And Sandra was consisting off both the you know, it's recognized us as a team which has been in traditionally building chips. But yet I think you know, the the Iot or the the previous venture from Mpls Team was somewhat of an eye opening as to how bringing things together is much more value in op, ex and and simplifying things is a huge, huge value compared to just putting performance and those things. So why this is important? That is another aspect which is important in trying to simplify things and make it consumable like software. And Sandra itself has probably, you know, I would say, Ah, good chunk, like about 60% of people in software team and not the, you know, basic harbor t This is not to say that, you know, we, you know, we are under emphasizing one versus the other. Software is a bigger beast when you start trying to build all those programs on a programmable and doing that here and start to roll out those applications on. So that's why I think the emphasis on software is there. Having said that, you know, it's the software that runs the data path pipeline. There's also a layer of software that we're building that can help manage all you know, all the product in a more cohesive manner and unified. >>Okay, that's Ah, thank you for laying that out. You mentioned you've got some background and open for definitely an area where, for a number of years, you know, Amazon has not exactly, uh, open source. Not exactly been a strength for AWS. They have put a lot of effort. They've done some president IRS over the last couple of years. >>And >>how do you see open source fitting into the space? What is I kind of the philosophy of pensando when it comes to open source. And where do you see it playing in the You know, this network piece of the multi cloud. >>Yeah, no, I think it's It's ah, it's a squared, relevant in a way that you know of the cloud native movement on how applications with very Onda normalization of AP eyes across multiple clouds. Israel, We are all seeing the benefits offered. And I think that that trend will continue and which is all driven through open source Ah, you know, community that exist in, you know, in the heart of the word. So personally for me, I think I learned a whole lot of things in the open source community. You know, the importance off evangelizing whatever you're working on, the reason to have convinced other people about contributing into what you're working on on. Frankly, I also learned how difficult it is to make revenues in an open source based part of that strategy. So I think you know that those were the things that I got away from it when I was doing my own open source project of container networking. Um, but at the same time, pensando, uh, you know, we have to make sure that we are 100% aligned with anything that's happening in open source. Never replicated, Um, anything that might be that might be happening in open source instead tried to make people use those things in the best possible way and in the most efficient way and the easiest possible way to use those. So our strategy largely is that, you know, embrace open source which exists are there from an infrastructure point of view, we are collaborating and communicating with less of the users are Hello. I think we're going to standardize most of things we're looking in before community. So our stands largely is that, you know, if we are building a programmable platform than the community is what is gonna driver and we are very much working towards a step by step, of course, trying to get through, you know, a stable state where we could we could not just empower people who are who are taking up the open source efforts which are going on. But at the same time, we can also contribute our program are programs into the open source community and defining the right abstractions into into the community. Um, because we came out of stealth pretty recently, you'll start seeing that and helping those activity as Well, >>excellent. Well, you know the launch of Pensando you had a phenomenal lineup. Not only you know, John Chambers obviously has the relationship with your theme, but you know, oh, am partners of Hewlett Packard, Enterprise and IBM, as well as the Marquis of Goldman Sachs. Things look a little bit different in the first half of 2020 and then they didn't end of 29 teams. So, you know, curious, You know that the global pandemic, the rippling financial implications, you know, what does that mean? The pensando. How has that impacted conversations that you're having with your >>Well, one thing I know at a broader level, let me cover, um, where things are heading. And in that sense, you know, I see that network and the infrastructure in general cloud infrastructure networking it's going to become. And we have realized it's this during during during recent early 20 twenties that that is going to be very important to have the have a new underpinning infrastructure that is not just working efficiently, securely, but is, you know, highly cost effective and very high performance, you know, ranging from people who are trying to connect from home to people who are trying to use videoconferencing and people who are going to be more and more use cloud based services even to order simple of the data being, you know, going to source for so network will become essential, you know, essential element for four things as we go forward. And we do see that being embraced by our customers and and things where we were trying to communicate that, you know, look, you will need performance and cost benefits are becoming more and more real Now. It's like, oh, things that we were having things in the pipeline for us. We need to work on that now. And the reason is because the things that we anticipated the demand increase, which is gonna happen over the fear of years, is happening literally in a few months. And so that is what we see. We are definitely, you know, very well poised to take advantage of their of their demand for sure. But also the fact that you know it needs to be done super efficiently. And so I think we are. You know, we are right. Well, I would say, you know, situated to be able to take advantage of start. >>Yeah, absolutely. You know, one thing you can't control as a company is you know what the global situation is when you come out of stealth and, you know, move through some of those early phases, you know, you've been part of You said a number of startups you've been part of been in give us a little bit of the inside baseball of, you know, being part of Rondo. You know, any stories on a little some of the ups and downs on the multi year journey to get where you are today? >>Definitely. I think. You know, um, minutes aren't good. They are largely an execution play. Relatively independent startup is is going to be about you know, how we cracked the overall market market fit and, ah, on execution, Of course, on deal with maybe in a competition in a different way, of course, like maybe big companies are our great partners. At the same time, you have to navigate that. So the overall the overall landscape in Spain and forces forces not is it's quite different. We can be much more border than we are independent company In trying to disrupt almost anything because we don't have any point of view to define per se. We do exactly, You know, what could be the most disruptive way, too, to potentially benefit the users on day? That's a big, you know, big change. I would say, um, we are being but paranoid as well at the same time, impractical to look at. You know how how we could navigate this situation in a very practical may. And the journey off, often independent startup is, you know, personally, for me, this is this is my fourth in different and start and best off. Off off, all independent. Once, I would stay largely because the kind of tradition that we're getting being an independent company is so huge. I'm just concerned about those things. But what We're really trying to trying to ensure that, you know, we can't get our stuff, but I want you and we started. >>Excellent. Guess what? One of the other things about being a startup is You know what you know adjustments You need to make along the way. So I'm curious. As you know, you've gone to some of your early customers. Any feedback or adjustments in some of the use cases or, you know, things that you've learned along the way that you can share. >>Um, fundamentally, at a base level, we haven't shifted from what we started off. We look at disruptions on on how consumption models are going to be changing, how speeds and feeds are gonna become important because, you know, because most law is going to be almost operating, how we how we deliver things into and containers are going to be a primary, you know, vehicle to deliver and build applications. So we recognize those disruptions, and we haven't changed, But normally from those disruptions that we wanted people after her. Uh, but at the same time, I think, you know, as we went and socialize our ideas and on architecture and designs with customers, we realized that that they are giving us lots more feedback on work all we could do and ah, and starting to become like we could take on different segments of market and not just one. So why stick ourselves to the data center power? Why not work on something on edge, blur wine or wine are real solutions for five G where latency and and performance is super crucial. Why don't take up on, you know, branch that use cases. So there are many things that are opening up. Um, and largely the you know, the shift. Or I would say the the inclination of what we should change versus not is happening with respect to where our customers are driving us. And and it is very important to make sure that you know the users of our lives Articulating all of the shift happens as opposed to, uh, you know, as opposed to anything else. We listen to them like super, super carefully, uh, and at the same time trying to make sure that we not only meet their means for you there their demands. So, um, definitely, you know, from the from the overall landscape of things, we are starting to get a lot more than what we are capture, which is good news For the same time, we're trying to also, uh, take on one part. I'm you know, >>all right, Vivienne, I can't let you off the hook as the cto without talking a little bit about that. You know, I think earlier in my career there was the old discussion and said you know, we should have started it, you know, a year or two ago. But, you know, we didn't. So we should start it today with changing pace of technology. You know, I've always said, you know, if I could I'd rather wait a year because I could take the next generation. I can take advantage of all these other things, but I can't wait, because then I'd never ship any things that I need to start now, Give us a little bit, you know, Look out in the future. How is your architecture designed to be able to take advantage of all the wonders coming with five G and everything there, Um, and anything that we should be looking at, You know, through the next kind of 12 18 months on the roadmap that you could share >>your Ah, yes. So, um, I would first of all say that we didn't build a part of, actually, what we build was a platform on which we can build multiple products. And we started we started off going there because we thought that, you know, the the platform that we're building is capable of capable of doing a lot more things than than one use case that we start off with. And so, to that point, I would say that yes. I mean, he started focusing on one product initially on the possibilities off. Trying to take it to multiple segments is is normally very much there. But we are already, you know, having those conversations to see what is the core set of use cases that we could we could get into for different segments. Besides the data center, you know, public Private Data center, you're looking at edge. We're looking by the looking at, Yeah, you mentioned this is as well as the, you know, storage and conversion infrastructure. So I would say that the food of all those things that we're starting to engage is going to start showing up in next 18 months. I could actually I think we are very well boys to take advantage of what we have. The hardware that we're shipping is going to be 100% compatible with four programs, but I don't those. So that is that is lot more possibilities are interesting. More use cases as people. The software's architecture that we have built is very extensible as well. Eh so we believe that. You know, uh, we believe that we can normally satisfy those use cases, but we're starting to you get into those things now, which will start to show up in and actually useful products of unusable for us with customer testimonials and then maybe 12 to 18 months from now. All >>right, well, thank you so much. It's great to catch up with. You really appreciate you coming on. >>Thank you to Because they're talking to you. And, you know, I appreciate your time. >>All right, I'm stew minimum. And be sure to check out the cube dot net for all the coverage. Go see the launch that we did. So in the second half of 2019. Thank you for watching you. Yeah, Yeah, yeah, yeah.

>> from Boston, Massachusetts. It's the queue covering active eo 2019. Data driven you by activity. >> Welcome back to Boston, Everybody. Money >> belong here with my co host, a student of John >> Kerry's. Also here today You watching the Cuban leader and on the ground tech coverage. This is day one of active fio 19 data driven content Conference hashtag data driven 19 red cara minuses. Here is the senior vice president of fantasy Sports A draftkings Greg. Thanks for coming on. What a cool title. >> Yeah, it's It's, you know, I was joking with my wife. Anytime you could be working fantasy sports, it's a great place to be. Everybody's a little bit jealous. >> So the formula is easy, right? Offer big giant prizes and everybody comes And that's all there is suing. Anybody can come >> in. I just have the dream job right now. >> So hugely competitive market. You guys, you become the >> leader. We were in the radio. Check out your websites. I mean, take us through the draft kings and your ascendancy. How you got here? >> So, you know, company started in 2012 initially around sort of the major big American sports on DH. Then really a CZ. We started scale that we saw there was a huge consumer interest in the product players that would come on. We're very, very, very sticky. Um, and we've just been kind of, you know, pushing, pushing on growing that using these. So the initial founders are three former analyst. So come on. It's always been sort of a very analytically driven company. So they looked at what we were dealing with, and it was we had L TVs that were way higher than our cracks. So let's keep marketing and growing and growing and growing and finding out ways to offer a better product. So, over 2015 we did a major marketing blitz, blew up the company Absolutely huge. Um, and since then we've been just constantly innovating, adding new sports, adding new features on DH, adding ways toe on the product. And then even more recently, just about a year ago, we expanded also into online sports betting over New Jersey has that's become a legal product across the U. S. So it's been a great time to be at the company a lot of fun. >> What what was your first sport was like Amazon started in books and then, you know, scaled out what was your first sport. So it's actually the first sport was >> baseball because of the time that they actually launched. So is the middle of April. Sporting calendar is a little bit thin. Right then, so is it was baseball to start, and then once football season started, that's really when things take on >> 2015 is when you started the marketing blitz and I remember just here in the ads and it was just intense, like a while. This company's going for it. So you sort of took >> all the chips I went >> all in and it worked. Yeah, I mean, it's part of the, you know, the lifeblood of the company. It's We're a company that ends up being taking risks, but we take calculated risks. So at any given point, you sort of say, like, Hey, what is the what is the range of outcomes over here? We're not playing for second place. We want to be a market leader, so you have to take risks in order, be a market leader. So let's take calculated risks. Let's make sure we're not being insane, but you know we did the math. We figured out what? This is A This is a worthwhile shot. We pushed him for it. Andi really took off from their love to bet on >> sure things. Yeah, well, Greg, we know the people that play the fantasy for it feel that data is what differentiates whether they're going to live in, you know, winner lose. Talk to us a little bit about the data journey inside your business And how that helped differentiate draftkings in the market. Yes. So we think Death draftkings >> is one of the most analytically based companies in the, you know, definitely in the market, but also into sort of like General Cos right now we use our analytics platform to inform pretty much everything we dio on. Go to your point. You're joking. You know, it seems like fantasy sports is easy throughout some giant prizes there, and everything will take care of itself. You know, running a fantasy sports car company. If you throw out a contest that's too big, you lose a ton of money. There's a lot of asymmetric risk in the business where if we're right, we make a little bit more. But if we're wrong. We lose a ton very, very, very fast. So our ability to be very, very sound analytically is what allows us to sort of pushed the envelope and grow, grow, grow but not, you know, lose our heads along the way. You know, some of the fun of that is really, you know, when we first ran, I think one of the most game changing contest we ran was actually back in October of 2014. It was the very first millionaire maker contest I could still remember. It was Week five of the 2020 14 NFL season where we said, Hey, this it's crazy. We need crazy things that happen in order for it to work. But if we're on a $20 contest to enter with $1,000,000 top prize and 2,000,000 of total prizes, it could go viral, go absolutely crazy. And if it loses, here's how it'll losing. Here's how much will hurt us. It's a worthwhile risk. Let's go for it. So that sort of energy of, you know, doing discipline analysis and constantly sort of them. Taking the risk on the back of it is what allowed us to build >> up the brand value that you would have got out of that was sort of worth that risk in part anyway. And you wouldn't have to hurt presumably. >> Exactly. We knew our downside. As long as you know your downside, you're normally in a pretty good spot to take those risks. >> So where do you >> see this All going mean? So the company has grown. You're at this kind of critical mass now, Like we said, highly competitive, you know, knock down. You know, if you take your eye off the ball. So how do you guys keep this going? >> So we have a huge challenge ahead of us over the next couple of years, as sports betting becomes legal across the US, we need to make sure that we are one of the top competitors in that market. Sports betting in the US, we expect to be an absolutely enormous market. It will probably be significantly larger than the fantasy sports market in terms of absolute revenue and even, you know, on order of magnitude more competitive. So we need to be executing each step along the way a CZ markets open up. We need to be able to get into getting two market very, very fast. And that means our tech team needs to be working feverishly to make sure that we can hit the requirements that each legislator and each regulator puts on market entry in their state. We didn't mean making sure we're constantly figuring out what are the product elements that are absolutely critical for our for our users. Is it Maura around the live betting experiences that around the different markets that you offer? It's around pricing. And how do we find these things, these different lovers and told them to make sure that we're putting out a great product for users. And if we do that and throw a great product after users were pretty sure we can make you want >> to be one stop shopping presumably, right? I mean, all sports, right? But But then you've got these niche sports betting. I mean eggs, invest. Example. I could think of this horse racing. You know where it is alive. It's gonna video. It's got commentators on the ground that you know the business really well. Is >> that Is that the strategy to go sort of horizontal and so be a one stop shop or you >> gonna sort of pick your spots? What is the day to tell you? >> You know, I think we're constantly talking about it. One of the things that allowed our fantasy sports business to grow so fast was going a little bit more horizontal. So we offered Gulf in Mass at a time period when the primary competitors and the space vandal did not. On DH, we built that product into one of our largest sports. It's, you know, right up there with MLB in terms of the actual size that that comes in a Z have gone also horizontal, we pulled in other places, like NASCAR. Mm, a great sports that people are interested in. It gets more users into our platform. And honestly, if uses are interested in a product, we don't want them to have to go elsewhere. We want to be able to have the offerings that any sort of, you know, critical mass type environment is going toe is gonna have >> Well, it's that experience, right? Well, I like to shop in Amazon. You do, too, because I >> trusted. And it's the same user experience. So, Greg, one of things >> I'm hearing from you is something that everybody tries for, but it's really challenging that speed. How do you react that fast and move the company into new markets and new offerings and keep innovating? You know, culturally technology wise, you know, How does Draftkings do that? You know, I think a za company, you know, from really every single person that we recruit in higher We've been actually execution Aly disciplined throughout the company's history. It's It's something that our founders did a great job of instilling in the culture right at the gates. I mean, we've tried to foster all the way along the way, which is all the best strategies of the world. They're going to fail if you can't execute well and every single person down the company knows that. And we try to, you know, enable each person to be as autonomous as possible in their ability to execute their their portion of the business that allows us to move really, really, really fast. You know, we disseminate that responsibility quickly, and each leader and sort of each person knows what they have to do to execute. There's a high degree of accountability behind that, you know, I'd like to say there's some. There's some magic recipe that's, um, secret sauce, but it's a lot of just great people doing great work everyday. Well, Greg, you know it's any your competitors that they look at, You know, Boston's been been doing pretty well in Draftkings era, you know, for the last few years. ES o Boston's been a great market for us. We've expanded Conover here on DH. The sports teams have been fantastic, although the Bruins it was a little bit sad about Game seven over there, but it happens. >> So his m o be the flagship news that no, I wouldn't say >> that MLB was first, primarily just of the time of the year when we launched. NFL is always going to go, are not always going to be, but for the for the foreseeable future is the dominant US sport on will remain the dominant US for >> no reason. I mean, kids there watch MLB anymore. Maybe the maybe the playoffs and the games. It was a game. I think I'm some Father's day was like almost five hours long, you know, gets called. You can come in and out. But you know what some of the trends. You see soccer. Is that growing NFL? Obviously huge. Do you see so niche sports like lax coming on. >> So, uh, you know, starting point NFL has been huge. We actually launched a new product Ah, little over a year ago called Showdown, which allowed you start to do fantasy for a single game as opposed to the combination of games that's taken off fantastically because that's tapping into more of the I'm going to sit down and watch this game, and I would love to have a fantasy team on that on this game. That's really expanded the audience like that. That >> was genius because, look, if you're >> out of the running, it doesn't matter because I'm weak. On top of that N b A and NHL on fire. The embassy put out a great product is an actual sport league. You know, the Finals were great. You hate to see the injuries, but it was a great final. Siri's very competitive. The NHL Finals has been very, very competitive. Golf is growing phenomenally as a sport, way farm or interesting golf than I ever anticipated when I first started with the company and it's one of the most exciting things. When the Masters comes each year, every screen has turned to it and we see a huge player. Player number is kind of coming into that one. Beyond that, you know NASCAR. What's been interesting? NASCAR's been having a tough couple years, but the Truck series for us? We launched it this year and the trucks have been great. I don't know if you've watched NASCAR Trucks. They're wildly entertaining. Uh, you know, Emma, you got the big fighter. So every sport sort of has its moments. It's a matter of like picking those moments and figuring out how to make >> the most of them. Do you see boxing at all making a comeback? >> So we have thought about how to get boxing into a into a fantasy. We don't have it at the moment. We're putting a lot of thought into it, so we are actually seeing through. We've seen, you know, we've been in the M M A space and we've seen the growth out from there where that sports doing great and you look at places like Bela Tor. The Professional Fighters league is other leagues, and then boxing is the next step. There's a lot of interest there. I don't think they have the right products yet to be able to kind of engage with that extra way. So that's one of things we're working on. Also, you need a marquee fighter. You always need a marquee fighter. Kind of helped bring in the interest over on that side. So, um, be interesting to see with Taki on sort of the downside of his career. At this point on DH, Mayweather hasn't been fighting much. Will be interesting to see. Who's that next meeting with Adam. But >> I grew up in an era >> of Marquis fighters. What? They would fight, you know, they literally fight 6 70 times a year, you know, and you had used huge names on DSO, and then mm comes along and he's really hurt, >> but it feels like it's tryingto so to resuscitate. Yeah. I mean, I think these things could >> be a little bit cyclical. Like you get one Marquis fighter out there like so my wife, this Filipino. So I'm a huge backing out fan now way watch every fight. Even when we were living in remote locations that forces watching at weird hours. He's a type of athlete that could bring popularity of the sport. So if there was a major U. S. Fighter that gains that degree of sort of, you know that that degree of fame people will be into it, I think >> Do do do your analytics sort of have a probe into the activity at the at the fan level at the sports level, not just the fantasy level or the betting level? Is that a sort of ah ah predictor for you? Yet we >> see a lot of correlations between how many people play our sport are fantasy game, and how many people actually follow the underlying sport. Way can also see trends in terms of If I'm from Boston, I probably pick more patriots in my fantasy lineups than, uh, normal on DH. You can actually see that as people play different sports that you know, the number one Q. Be drafted in in Boston is almost always gonna be Tom Brady. And once you leave that you start seeing Aaron Rodgers pop up. Let's really, really fast. So you see these little micro trends where it's like you are still a sports fan of your local team in your local environment, but it manifest itself in the fantasy. >> So what you think that is? Do you think it's fan affinity >> or do you think it's just the sort of lack of knowledge out inside? You're sort of a circle of trust. >> I think it's probably a combination. I mean, I could say is, you know, following the Celtics in the mid to thousands, I knew the depth of the Celtics pension, how they would use their rotation better than anybody else, Probably better than anybody else in the coaches would probably disagree. But it's like I knew that James Posey was a huge value play on Saturday nights. I knew. I kind of with I feel the Eddie House nights. Uh, so, you know, on your local team, you probably know those players at the not the top top echelon All Stars, but the guy's right beneath. You know them a little bit better and probably more comfortable using >> what's your favorite sport. >> So my favorite sport, from a fantasy perspective, is I play all the basket. I play all football, played basketball just during play offs, and I played baseball. But baseball I'm strictly a fantasy player. I don't really follow the sport to play. I'm just playing fantasy. Okay, >> That's great. So, what do you think? The conference. Here. >> You have you Have you had any timeto interact? I know you were swamped after coming off the stage. >> You know, it looks like a great turnout over here. There's a lot of enthusiasm amongst them from people. I was a little bit late to the late to show up this morning, so I got a bit Swanson eager to go and be able to catch up a bit more. >> Okay, Well, Greg, thanks so much for coming on. The Cuba's great to have your every pleasure meeting you. >> All right, people. Right there. Still, when I >> was back with our next guest, John for it is also in the house. You wanted The Cube from active field data driven 19. Right back

>> ANNOUNCER: Live from Las Vegas, it's theCUBE. Covering VM World 2017. Brought to you by Vmware and its ecosystem partner. >> Hi, I'm Stu Miniman here with John Troyer and excited to welcome back to the program Chris Wahl, who's the Chief Technologist at Rubrik. Chris, thanks for joining us. >> Oh, my pleasure. It's my first VMworld CUBE appearance so I'm super stoked. >> Yeah, we're pretty excited that you hang out with, you know, just a couple of geeks as opposed to, what's it Kevin Durant and Ice Cube. Is this a technology conference or Did you and Bipple work for some Hollywood big time company? >> It's funny you say that, they'll be more tomorrow. So I'll allude to that. But ideally, why not hang out with some cool folks. I mean I live in Oakland. Hip Hop needs to be represented and the Golden State Warriors. >> It's pretty cool. I'm looking forward to the party. I know there will be huge lines. When Katie comes to throw down with a bunch of people. So looking forward to those videos. So we've been looking at Rubrik since, you know, came out of stealth. I got to interview Bipple, you know, really early on, so we've been watching. What you're on like the 4.0 release now right? How long has that taken and you know why don't you bring us up to speed with what's going on with Rubrik. >> Yeah, it's our ninth, our ninth major release over basically eight quarters. And along with that, we've announced we've hit like a 150 million dollar run rate that we've included when we started it was all about VMWare, doing back-ups providing those back-ups a place to land, meaning object store or AWS S3. And now it's, we protect Hyper-V, Acropolis from Nutanix, obviously the VMWare Suite, we can do archive to Azure, we can do, there's like 30 some-odd integration points. With various storage vendors, archive vendors, public cloud, etcetera. And the ulta release which is 4.0, just really extends that because now, not only can we provide backups and recovery and archive, which is kind of our bread and butter. But you can archive that to public cloud and now you can start running those workloads. Right, so what we call a cloud on, I can take either on demand or archive data that's been sent to S3, and I can start building virtual machines, like I said on demand. I can take the AMI, put it in EC2 and start running it right now. And I start taking advantage of the services and it's a backup product. Like, that's what always kind of blows my mind. This isn't, that's not the use case, it's one thing that we unlock from backup to archive data >> One of the challenges I usually see out there, is that people are like, oh Rubrik, you know they do backups for VMWare, how do you, you know, you're very much involved in educating and getting out there and telling people about it, how do you get over the, oh wait you heard what we were doing six months ago or six weeks ago, and now we're doing so much more. So how do you stay up with that? >> It's tough to keep up obviously, because every quarter we basically have either some kind of major or a dot release that comes out. I mean realistically, I set the table a little bit differently, I say, what are you looking to do? What are the outcomes that you're trying to drive? Simplicity's a huge one because everyone's dealing with I have a backup storage vendor and I have a storage vendor, and I have tape vendor, and all this other hodge podge things that they're dealing with. They're looking to save money, but ultimately they're trying to automate, start leveraging the cloud. Start really like, taking the headache out of providing something that's very necessary. And when I start talking about the services they can add, beyond that, because it's not just about taking a backup, leaving it in some rotting archive for 10 years, or whatever, it's really what can I do with the data once I have this duplicated and compressed, kind of pool, that I can start drawing from. And that's where people start to, their mind gets blown a little bit. Now that the individual features and check boxes sets, it is what it is, you know, like if you happen to need Hyper-V or Acropolis or whatever, it's really just where you are on that journey to start taking advantage of this data. And I think that's where people start to get really excited and we start white boarding and nerding out a little bit. >> Well Chris, so don't keep us in suspense, what kinds of things can you do once you have a copy of this data? It's still, it's all live, it's either on solid state or spinning disk or in the cloud somewhere. That's very different than just putting it on tape, so what do I do now, that I have all this data pool? >> So probably the most common use case is, I have VBC and a security group in Amazon. That exists today. I'm archiving to S3 in some way, shape, or form. Either IA or whatever flavor vessel you want. And then you're thinking, well I have these applications, what else can I do with them? What if I put it to a query service or a relational data base service, or what if I sped up 10 different copies because I need to for lode testing or some type of testing. I mean it all falls under the funnel of dev test, but I hate just capping it that way, because I think it's unimaginative. Realistically, we're saying here you have this giant pile of compute, that you're already leveraging the storage part of it, you the object store that is S3. What if you could unlock all the other services with no heavy lift? And the workload is actually built as an AMI. Right, so an ami, it's actually running an EC2, so there's no, you don't necessarily have to extend the Hyper Visor layer or anything like that. And it's essentially S3 questions, from the product perspective. It's you know, what security group, BCP, and shape of the format you want it to be. Like large, small, Xlarge, et cetera. That's it. So think about unlocking cloud potentials for less technical people or people that are dipping their toe in a public cloud. It really unlocks that ability and we control the data plane across it. >> Just one thing on that, because it's interesting, dev tests a lot of times, used to get shoved to the back. And it was like, oh you can run on that old gear, you know you don't have any money for it. We've actually found that it can increase, kind of the companies agility and development is a big part of creating big cool things out of a company, so you don't under sell what improving dev tests can do. So did you have some customer stories or great things that customers have done with what this capability has. >> Yeah, but to be fair, at first when I saw that we were going to start, basically taking VMWare backups and pushing that in archive and then turning those into EC2 instances of any shape or quantity. I was like, that's kind of crazy, who has really wanted that Then I started talking to customers and it was a huge request. And a lot of times, my architectural background would think, lift and shift, oh no, don't necessarily do that. I'm not a huge fan of that process. But while that is certainly something you can do, what they're really looking to do is, well, I have this binary package or application suite that's running on Elk Stack or some Linux distro, or whatever, and I can't do anything with that because it's in production and it's making me money, but I'd really like to see what could be done with that? Or potentially can I just eliminate it completely and turn it into a service. And so I've got some customers that completely what they're doing, they're archiving already and what they have the product doing is every time a new snapshot is taken and is sent to the cloud, it builds automatically that EC2 instance, and it starts running it. So they have a collection of various state points that they can start playing with. The actual backup is immutable, but then they're saying, alright, what if exactly what I kind of alluded to a little, what if I start using a native service in the cloud. Or potentially just discard that workload completely. And start turning it into a service, or refactor it, re platform it et cetera. And they're not having to provision, usually you have to buy infrastructure to do that. Like you're talking about the waterfall of Chinese stuff, that turns into dev stuff three years later. They don't have to do that, they can literally start taking advantage of this cloud resource. Run it for an hour or so, because devs are great at CDIC pipelines, let's just automate the whole stack, let's answer our question by running queries through jenkins or something like that. And then throw it away and it cost a couple of bucks. I think that's pretty huge. >> Well Chris, can you also use this capability for DR, for disaster recovery? Can you re hydrate your AMI's up there if everything goes South in your data center? >> Absolutely. I mean it's a journey and this is for dot zero. So I'm not going to wave my hands and say that it's an amazing DR solution. But the third kind of use case that we highlight with our product is that absolutely. You can take the work loads either as a planned event, and say I'm actually putting it here and this is a permanent thing. Or an unplanned event, which is what we all are trying to avoid. Where you're running the work loads in the cloud, for some deterministic period of time, and either the application layer or the file system layer, or even, like a data base layer, you're then protecting it, using our cloud cluster technology, which is Rubrik running in the cloud. Right there, it has access to S3 and EC2, you know, adjacently, there is not net fee and then you start protecting that and sending the data the other way. Because Rubriks software can talk to any other Rubrik's software. We don't care what format or package it's in. In the future we'd like to add more to that. I don't want to over sell it, but certainly that's the journey. >> Chris tell us about how your customers are feeling about the cloud in general. You know you've lived with the VM community for a lot of years, like many of us, and that journey to cloud and you know, what is Hybrid and multi-cloud mean to them, and you know, what you've been seeing at Rubrik over the last year. >> Yeah it's ahh, everybody has a different definition between hybrid, public, private-- >> Stu: Every customer I ever talked to will have a different answer to that. >> I just say multi cloud, because it feels the most safe And the technically correct version of that definition. It's certainly something that, everyone's looking to do. I think kind of the I want to build a private cloud phase of the journey is somewhat expired in some cases. >> Stu: Did you see Pat's keynote this morning? >> Yeah, the I want to build a private cloud using open stack and you know, build all my widgets. I feel that era of marketing or whatnot, that was kind of like 2008 or 2010. So that kind of era of marketing message has died a little bit. It's really just more I have on prem stuff, I'm trying to modernize it, using hyper-converge, or using software to find X, you know, networking et cetera But ultimately I have to start leveraging the places where my paths, my iya's and my sas are going to start running. How do I then cobble all that together. I mean at the sea level, I need visibility, I need control, I need to make executable decisions. That are financially impactful. And so having something they can look across to those different ecosystems, and give you actionable data, like here's where it's running, here's where it could run, you know, it's all still just a business decision, based on SLA. It's powerful. But then as you go kind of down message for maybe a director or someone's who's managing IT, that's really, someone's breathing down their neck, saying, we've got to have a strategy. But they're technically savvy, they don't want to just put stuff in the cloud and get that huge bill. Then they have to like explain that as well. So it kind of sits in a nice place where we can protect the modern apps, or kind of, I guess you can call them, modern slash legacy in the data center. But also start providing protection at a landing pad for the cloud native to use as an over watch term The stuff that's built for cloud that runs there, that's distributed and very sensitive to the fact that it charges per iota of use at the same time. >> Well Chris, originally Rubrik was deploying to customers as an appliance, right? So can you talk a little bit about that, right, you have many different options now, the customer, right? You can get open source, you can get commercial software, or you can get appliances, you can get SAS, and now it sounds like you're, there's also a piece that can run in the cloud, right? That it's not just a box that sits in a did center somewhere So can you talk about, again, what do customers want? What's the advantage of some of those different deployment mechanisms, what do you see? >> I'm not saying this as a stalling tactic, but I love that question. Because yes, when we started it made sense, build a turnkey appliance, make sure that it's simple. Like in deployment, we used to say it can deploy in an hour and that includes the time to take it out of the box and that only goes so far because that's one use case. So certainly, for the first year or so, the product that was where we were driving it, as a scale out node based solution then we added Rubrik edge as a virtual appliance. And really it was meant to, I have a data center and I'm covering those remote offices, type use cases. And we required that folks kind of tether the two, because it's a single node that's really just a suggesting data and bringing it back using policy. Then we introduced cloud cluster in 3.2 which is a couple of releases ago. And that allows you to literally build a four plus node cluster as your AWS, basically you give us your account info and we share the EMI with you or the VM in case of Azure and then you can just build it, right? And that's totally independent, like you can just be a customer. We have a couple of customers that are public, that's all they do, they deploy cloud cluster they backup things in that environment. And then they replicate or archive to various clouds or various regions within clouds. And there's no requirement to buy the appliance because that would be kind of no bueno to do that. >> Sure. >> So right, there's various packages or we have the idea now where you can bring your own hardware to the table. And we'll sell you the software, so like Lenovo and Cisco and things like that. It can be your choice based on the relationships you have. >> Wow Chris your teams are gone a lot, not just your personal team but the Rubrik team I walked by the booth and wait, I saw five more people that I know from various companies. Talk about the growth of like, you know Rubrik. You joined a year ago and it felt like a small company then. Now you guys are there, I get the report from this financial analyst firms and like, have you seen the latest unicorn, Rubrik and I'm like, Rubrik, I know those guys. And gals. So yeah absolutely, talk about the growth of the company. What's the company hiring for? Tell us a little bit about the culture inside. >> Sure, I mean, it's actually been a little over two years now that I've been there, it's kind of flying. I was in the first 50 hires for the company. So at the time I felt like the FNG, but I guess now, I'm kind like the old, old man. I think we're approaching or have crossed the 500 employee threshold and we're talking eight quarters essentially. A lot of investment, across the world, right, so we decided very early on to invest in Europe as a market. We had offices in Utruck in the Netherlands. And in London, the UK, we've got a bunch of engineering folks in India. So we've got two different engineering teams. As well as, we have an excellent, center of excellence, I think in Kansas City. So there's a whole bunch of different roots that we're planting as a company. As well as a global kind of effort to make sales, support, product, engineering, marketing obviously, something that scales everywhere. It's not like all the engineers are in Palo Alto and Silicone Valley and everyone else is just in sales. But we're kind of driving across everywhere. My team went from one to six. Over the last eight or nine months. So everything is growing. Which I guess is good. >> As part of that you also moved to Silicone Valley and so how does it compare to the TV show. >> Chris: It's in Oakland. >> Well it's close enough to Silicone Valley. >> It's Silicone Valley adjacent. I will say I used to visit all the time, you know. For various events and things like that. Or for VM World or whatnot. I always got the impression that I liked being there for about a week and then I wanted to leave before I really started drinking the kool aid a little heavily so it's nice being just slightly on the east bay area. At the same time, I go to events and things now. More as a local and it's kind of awesome to hear oh I invented whatever technology, I invented bootstrap or MPM or something like that. And they're just available to chat with. I tried it at that the, the sunscreen song, where he says, you know, move to california, but leave before you turn soft. So at some point I might have to go back to Texas or something to just to keep the scaley rigidity to my persona intact. >> Yeah, so you missed the barbecue? >> Well I don't know if you saw Franklin's barbecue actually burned down during the hurricane, so. >> No >> Yeah, if you're a, a huge barbecue fan in Austin, weep a tear, it might be a bad mojo for a little bit. >> Wow. Alright, we were alluding at the very beginning of the interview, you've got some VIP guests, we don't talk too much about, like, oh we're doing this tomorrow and everything, but you got some cool activities, the all stars, you know some of the things. Give us a little viewpoint, what's the goal coming into VM World this year and what are some of the cool things that you're team and the extended team are doing. >> Yeah, so kind of more on the nerdy fun side, we've actually built up, one of my team, Rebecca Fitzhughes build out this V all stars card deck so we picked a bunch of infuencers, and people that, you know friends and family kind of thing built them some trading cards and based on what you turn in you can win prizes and things like that. It was just a lot of other vendors have done things that I really respect. Like Solid Fire has the socks and the cards against humanity as an example. I wanted to do something similar and Rebecca had a great idea. She executed on that. Beyond that though, we obviously have Ice Cube coming in. He's going to be partying at the Marquis on Tuesday evening so he'll be, he'll be hanging around, you know the king of hip hop there. And on a more like fun, charitable note, we actually have Kevin Durant coming in tomorrow. We are shooting hoops for his charity fund. So everybody that sinks a goal, or ahh, I'm obviously not a basket ball person, but whoever sinks the ball into the hoop gets two dollars donated to his charity fund and you build it to win a jersey and things like that. So kind of spreading it across sports, music, and various digital transformation type things. To make sure that everyone who comes in, has a good time. VMWare's our roots, right? 1.0, the product was focused on that environment. It's been my roots for a long time. And we want to pay that back to the community. You can't forget where you came from, right? >> Alright, Chris Wahl, great to catch up with you. Thanks for joining us sporting your Alta t-shirt your Rubrik... >> I'm very branded. >> John Troyer and I will be back with lots more coverage here at VM World 2017, you're watching theCUBE.

>> Announcer: Live from Boston, Massachusetts, it's theCUBE, covering Spark Summit East 2017. Brought to you by Databricks. Now, here are your hosts Dave Vellante and George Gilbert. >> Welcome back to snowy Boston, everybody. This is theCUBE, the leader in live tech coverage. We're here at Spark Summit East, hashtag SparkSummit. Manish Gupta is here, he's the CMO at Redis Labs. Manish, welcome to theCUBE. >> Thank you, good to be here. >> So, you know, 10 years ago you say you're in the database business and everybody would yawn. Now you're the life of the party. >> Yeah, the world has changed. I think the party has lots and lots of players. We are happy to be on the top of that heap. >> It is a crowded space, so how does Redis Labs differentiate? >> Redis Labs is the company behind the massively popular open source Redis, and Redis became popular because of its performance primarily, and then simplicity. Developers could very easily run up an instance of Redis, solve some very hairy problems, and time to market was a big issue for them. Redis Enterprise took that forward and enabled it to be mission critical, ready for the largest workloads, ready for things that the enterprises need in a highly distributed clustered environment. So they have resilience and they benefit from the performance of Redis. >> And your claim to fame, as you say, is that top-gun performance, you guys will talk about some of the benchmarks later. We're talking about use cases like fraud detection, as example. Obviously ad serving would be another one. But add some color to that if you would. >> Redis is whatever you need to make real time real, Redis plays a very important role. It is able to deliver millions of operations per second with sub-millisecond latency, and that's the hallmark. With data structures that comprise Redis, you can solve the problems in a way, and the reason you can get that performance is because the data structures take some very complex issues and simplify the operation. Depending on the use case, you could use one of the data structures, you can mix and match the data structures, so that's the power of a Redis. We're used for ITO, for machine learning, for metering of billing and telecommunications environment, for personalization, for ad serving with companies like Groupon and others, and the list goes on and on. >> Yeah, you've got a big list on your website of all your customers, so you can check that out. Let's get the business model piece out of the way. Everybody's always fascinated. Okay, you got open source, how do you make money? How does Redis make money? >> Yeah, you know, we believe strategically fostering the growth of open source is foundational in our business model, and we invest heavily both R&D and marketing to do that. On top of that, to enable enterprise success and deployment of Redis, we have the mission critical, highly available Redis Enterprise offerings. Our monetization is entirely based on the Redis Enterprise platform, which takes advantage of the data structures and performance of core Redis, but layers on top management and the capabilities that make things like auto-recovery, auto-sorting, management much, much easier for the enterprise. We make that available in four deployment models. The enterprise can select us as Redis cloud, which runs on a public infrastructure on any of the four major platforms. We also allow for the enterprise to select a VPC environment in their own private clouds. They can also get software and self-manage that, or get our software and we can manage it for them. Four deployment options are the modalities in other ways where the enterprise customers help us monetize. >> When you said four major platforms, you meant cloud platforms? >> That's right. AWS, >> So, AWS, Azure >> Azure, Google, and IBM. >> Is IBM software, got there in the fourth, alright. >> That's right, all four. >> Go to the whip IBM. Go ahead, George. >> Along the lines of the business model, and we were sort of starting to talk about this earlier offline, you're just one component in building an application, and there's always this challenge of, well, I can manage my component better than anyone else, but it's got to fit with a bunch of other vendors' components. How do you make that seamless to the customer so that it's not defaulting over to a cloud vendor who has to build all the components themselves to make it work together? >> Certainly, you know, database is an integral part of your stack, of your application stack, but it is a stack, so there are other components. Redis and Redis Labs has a very, very large ecosystem within which we operate. We work closely with others for interfaces, for connectors, for interoperability, and that's a sustained environment that we invest in on a continuous basis. >> How do handle application consistency? A lot of in the no-SQL world, even in the AWS world, you hear about eventual consistency, but in the real-time world, there's a need for more rigorous, what's your philosophy there, how do you approach that? >> I think that's an issue that many no-SQL vendors have not been able to crack. Redis Labs has been at the forefront of that. We are taking an approach, and we are offering what we call tuneable consistency. Depending on the economics and the business model and the use case, the needs of consistency vary. In some cases, you do need immediate consistency. In other cases, you don't ever need consistency. And to give that flexibility to the customer is very important, so we've taken the approach where you can go from loose consistency to what we call strong eventual consistency. That approach is based on a fairly well trusted architecture and approach called CRDT, Conflict-free Replication Data Type. That approach allows us to, regardless of what the cluster magnitude or the distribution looks like geographically, we can deliver strong eventual consistency which meets the needs of majority of the customers. >> What are you seeing in terms of, you know, also in that a discussion about acid properties, and how many workloads really need acid properties. What are seeing now as you get more cloud native workloads and more no-SQL oriented workloads in terms of the requirement for those acid properties? >> First of all, we truly believe and agree that not all environments required acid support. Having said that, to be a truly credible database, you must support acid, and we do. Redis is acid-compli, supports acid, and Redis Labs certainly supports that. >> I remember on a stage once with Curt Monash, I'm sure you know Curt, right? Very famous database person. And he basically had a similar answer. But you would say that increasingly there are workloads that, the growth workloads don't necessarily require that, is that fair statement? >> That's a fair statement I would say. >> Dave: Great, good. >> There's a trade-off, though, when you talked about strong eventual consistency, potentially you have to wait for, presumably, a quorum of the partitions, I'm getting really technical here, but in other words, you've got a copy of the data here-- >> Dave: Good CMO question. (laughing) >> But your value proposition to the customers, we get this stuff done fast, but if you have to wait for a couple other servers to make sure that they've got the update, that can slow things way down. How does that trade-off work? >> I think that's part of the power of our architecture. We have a nothing shared, single proxy architecture where all of the replication, the disaster recovery, and the consistency management of the back end is handled by the proxy, and we ensure that the performance is not degraded when you are working through the consistency challenges, and that's where significant amount of IP is in the development of that proxy. >> I'll take that as a, let's go into it even more offline. >> Manish: Sounds good. >> And I have some other CMO questions, if I may. A lot of young companies like yours, especially in open source world, when they go to get the word out, they rely on their community, their open source community, and that's the core, and that makes a lot of sense, it's their peeps. As you become, grow more into enterprise grade apps and workloads, how do you extend beyond that? What is Redis Labs doing to sort of reach that C-Suite, are you even trying to reach that C-Suite up level to messaging? How do you as a CMO deal with those challenges? >> Maybe I'll begin by talking about our personas that matter to us in the ecosystem. The enterprise level, the architects, the developers, are the primary target, which we try to influence in early part of the decision cycle, it's at the architectural level. The ultimate teams that manage, run, and operate the infrastructure is certainly the DevOps, or the operations teams, and we spend time there. All along for some of the enterprise engagements, CIOs, chief data officers, and CTOs tend to play a very important role in the decisions and the selection process, and so, we do influence and interact with the C-Suite quite heavily. What the power of the open source gives us is that groundswell of love for Redis. Literally you can walk around a developer environment, such as the Spark Summit here, and you'll find people wearing Redis Geek shirts. And we get emails from Kazakhstan and strange, places from all over the world where we don't necessarily have salesforce, and requesting t-shirts, "send us stickers." Because people love Redis, and the word of mouth, that ground level love for the technology enables the decisions to be so much easier and smoother. We're not convincing, it's not a philosophical battle anymore. It's simply about the use case and the solution where Redis Enterprise fits or doesn't fit. >> Okay, so it really is that core developer community that are your advocates, and they're able to internally sell to the C-Suite. A lot of times the C-Suite, not the CTO so much, but certainly the CIO, CDO are like, "Yeah, yeah, they're geekin' out on some new hot thing. "What's the business impact?" Do you get that question a lot, and how do address it? >> I think then you get to some of the very basic tools, ROI calculators and the value proposition. For the C-level, the message is very simple. We are the least risky bet. We are the best long-term proposition, and we are the best cost answer for their implementation. Particularly as the needs are increasingly becoming more real-time in nature, they are not batch processed. Yes, there will always be some of that, but as the workloads are becoming, there is a need for faster processing, there is a need for quick insights, and real-time is not a moniker anymore, right. Real-time truly needs to be delivered today. And so, I think those three propositions for the C-Suite are resonating very well. >> Let's talk about ROI calculators for a second. I love talking about it because it underscores what a company feels as though its core value proposition is. I would think with Redis Labs part of the value proposition is you are enabling new types of workloads and new types of, whether it's sources of revenue or productivity. And these are generally telephone numbers as compared to some of the cost savings head to head to your competition, which of course you want to stress as well because the CFO cares about the cap-backs. What do you emphasize in that, and we don't have to get into the calculator itself, but in the conceptual model, what's the emphasis? Is it on those sort of business value attributes, is it on the sort of cost-savings? How do you translate performance into that business value? A lot of questions there, but if you could summarize, that'd be great. >> Well, I think you can think of it in three dimensions. The very first one is, does the performance support the use case or the solution that is required? That's the very first one. The second piece that fits in it, and that's in our books, that's operations per second and the latency. The second piece is the cost side, and that has two components to it. The first component is, what are the compute requirements? So, what is the infrastructure underneath that has to support it? And the efficiency that Redis and Redis Enterprise has is dramatically superior to the alternatives. And so, the economics show up. To run a million operations per second, we can do that on two nodes as opposed to alternative, which might need 50 nodes or 300 nodes. >> You can utilize your assets on the floor much better than maybe the competition can. >> This is where the data structures come into play quite a bit. That's one part of-- >> Dave: That's one part of the cost. >> Yeah. The other part of the cost is the human cost. >> Dave: People, yeah. >> And because, and this goes back to the open source, because the people available with the talent and the competency and appreciation for Redis, it's easy to procure those people, and your cost of acquisition and deploying goes down quite a bit. So, there's a human cost to it. The third dimension to this whole equation is time to market. And time to market is measured in many ways. Is it lost revenue if it takes you longer to get there? And Redis consistently from multiple analysts' reports gets top ranking for fastest way to get to market because of how simple it is. Beyond performance, simplicity is a second hallmark. >> That's a benefit acceleration, and you can quantify that. >> Absolutely, absolutely. And that's a revenue parameter, right. >> For years, people have been saying this Cambrian explosion of databases is unsustainable, and sort of in response we've gotten a squaring of the Cambrian explosion. The question is, with your sort of very flexible, I don't want to get too geeky, 'cause Dave'll cut me off, but the idea that you can accommodate time series and all these different ways of, all these different types of data, are we approaching a situation where customers can start consolidating their database choices and have fewer vendors, fewer products in their landscape? >> I think not only are we getting there, but we must get there. You've got over 300 databases in the marketplace, and imagine a CIO or an architect trying to have to sort through that to make a decision, it's difficult, and you certainly cannot support it from a trading standpoint or from an investment, cap-backs, and all that standpoint. What we have done with Redis is introduce something called Redis Modules. We released that at the last RedisConf in May in San Francisco. And the Redis Module is a very simple concept but a very powerful concept. It's an API which can be utilized to take an existing development effort, written as CC++, that can be ported onto the Redis data structures. This gives you the flexibility without having to reinvent the wheel every single time to take that investment, port it on top of Redis, and you get the performance, and you can make now Redis becomes a multi-model database. And I'm going to get to your answer of how do you address the multiple needs so you don't need multiple databases. To give you some examples, since the introduction of Redis Modules, we have now over 50 modules that have been published by a variety of places, not just Redis Labs. To indicate how simple and how powerful this model is. We took Lucene and developed the world's fastest full-text search engine as a module. We have very recently introduced Redis machine learning as a module that works with Spark ML and serves as a great serving layer in the machine learning domain. Just two very simple examples, but work that's being done ported over onto Redis data structures and now you have ability to do some very powerful things because of what Redis is. And this is the way future's going to be. I think every database is trying to offer multi-functionality to be multi-model in nature, but instead of doing it one step at a time, this approach gives us the ability to leverage the entire ecosystem. >> Your point being consolidation's inevitable in this business as well. >> Manish: Architectural consolidation. >> Yes, but also you would think, company consolidation, isn't that going to follow? What do you make of the market, and tell me, if you look back on the database market and what Oracle was able to achieve in the face of, maybe not as many players, but you had Sybase and Informix, and certainly DB2's still around, and SQL Server's still around, but Oracle won, and maybe it was SQL standards that. It's great to be lucky and good. Can we learn from that, or is this a whole different world? Are there similarities, and how do you, how do you see that consolidation potentially shaking out, if you agree that there will be consolidation? >> Yeah, there has to be, first and foremost, an architectural approach that solves the OPEX, CAPEX challenge for the enterprise. But beyond that, no industry can sustain the diversity and the fragmentation that exists in database world. I think there will always be new things coming out, of universities particularly. There's great innovation and research happening, and that is required to augment. But at the end of the day, the commercial enterprises cannot be of the fragmented volume that we have today in the database world, so there is going to be some consolidation, and it's not unnatural. I think it's natural, it's expected, time will tell what that looks like. We've seen some of our competitors acquire smaller companies to add graph functionality, to add search functionality. We just don't think that's the level of consolidation that really moves the needle for the industry. It's got to be at a higher level of consolidation. >> I don't want to, don't take this the wrong way, don't hate me for saying it, but is Oracle sort of the enemy, if I can say that. I mean, it's like, no, okay. >> Depends how you define enemy. >> I'm not going to go do many of the workloads that you're talking about on Oracle, despite what Larry tells me at Oracle OpenWorld. And I'm not going to make Oracle my choice for any of the workloads that you guys are working on. I guess in terms, I mean, everybody who's in the database business looks at that and say, "Hey, we can do it cheaper, better, "more productively," but, could you respond to that, and what do you make of Amazon's moves in the database world? Does that concern you? >> We think of Amazon and Oracle as two very different philosophies, if you can use that word. The approach we have taken is really a forward-looking approach and philosophy. We believe that the needs of the market need to be solved in new ways, and new ways should not be encumbered by old approaches. We're not trying to go and replicate what was done in the SQL world or in a relational database world. Our approach is how do you deliver a multi-model database that has the real-time attribute attached to it in a way that requires very limited computer force power and very few resources to manage? You take all of those things as kind of the core philosophy, which is a forward-looking philosophy. We are definitely not trying to replicate what an Oracle used to be. AWS I think is a very different animal. >> Dave: Interesting, though. >> They have defined the cloud, and I think play a very important role. We are a strong partner of theirs, much of our traffic runs on AWS infrastructure, certainly also on other clouds. I think AWS is one to watch in how they evolve. They have database offerings, including Redis offerings. However, we fully recognize, and the industry recognizes that that's not to the same capability as Redis Enterprise. It's open sourced Redis managed by AWS, and that's fine as a cache, but you cannot persist, and you really cannot have a multi-model capability that's a full database in that approach. >> And you're in the marketplace. >> Manish: We are in the marketplace. >> Obviously. >> And actually, we announced earlier, a few weeks ago, that you can buy and get Redis cloud access, which is Redis Enterprise cloud, on AWS through the integrated billing approach on their marketplace. You can have an AWS account and get our service, the true Redis Enterprise service. >> And as a software company, you'd figure, okay, the cloud infrastructures are service, we don't care what infrastructure it runs on. Whatever the customer wants, but you see AWS making these moves up-market, you got to obviously be paying attention to that. >> Manish: Certainly, certainly. >> Go ahead, last question. >> Interesting that you were saying that to solve this problem of proliferation of choice it has to be multi-model with speed and low resource requirement. If I were to interpret that from an old-style database perspective, it would be you're going to get, the multi-model is something you are addressing now, with the extensibility, but the speed means taking out that abstraction layer that was the query optimizer sort of and working almost at the storage layer, or having an option to do that. Would that be a fair way to say? >> No, I don't think that necessarily needs to be the case. For us, speed translates from the simplicity and the power of the data structures. Instead of having to serialize, deserialize before you process data in a Spark context, or instead of having to look for data that is perhaps not put in sorted sets for a use case that you might be doing, running a query on, if the data is already handled through one of the data structures, you now have a much faster query time, you now have the ability to reach the data in the right approach. And again, this is no-SQL, right, so it's a schema lesson write and it sets your scheme as you want it be on read. We marry that with the data structures, and that gives you the ultimate speed. >> We have to leave it there, but Manish, I'll give you the last word. Things we should be paying attention to for Redis Labs this year, events, announcements? >> I think the big thing I would leave the audience with is RedisConf 2017. It's May 31 to June 2 in San Francisco. We are expecting over 1,000 people. The brightest minds around Redis of the database world will be there, and anybody who is considering deploying the next generation database should attend. >> Dave: Where are you doing that? >> It's the Marriott Marquis in San Franciso. >> Great, is that on Howard Street, across from the--? >> It is right across from Moscone. >> Great, awesome location. People know it, easy to get to. Well, congratulations on the success. We'll be lookin' for outputs from that event, and hope to see you again on theCUBE. >> Thank you, enjoyed the conversation. >> Alright, good. Keep it right there, everybody, we'll be back with our next guest. This is theCUBE, we're live from Spark Summit East. Be right back. (upbeat electronic rock music)