>> Host: From around the globe, it's theCUBE, with coverage of KubeCon and CloudNativeCon North America 2020 virtual brought to you by Red Hat, the cloud native computing foundation and ecosystem partners. >> Hi everyone, I'm John Furrier with theCUBE. We are here covering KubeCon and CloudNativeCon North America 2020, November 17th to the 20th, a virtual event. Normally we're there in person, but again, 2020 has been a crazy year, we're not going to be able to be there in person, but we're here remotely. We have two great guests, the co-chairs of KubeCon and CloudNativeCon Stephen Augustus senior, open source engineer VMware KubeCon CloudNativeCon chair and Constance Caramanolis principal software here at Splunk and you guys are co-chairs of KubeCon. Big responsibility, thank you for coming on. >> Thank you. Thank you for having us. >> Thank you for having us. >> Okay so we, the number one question every year is before it gets started is, how did you make the selections for the talks, what's the hottest thing going on, what's the focus for this KubeCon? >> Well, so actually we use a Ouija board to choose the talks. (laughing) No, I'm joking it doesn't happen that way. >> Yeah, yeah, it's pretty much all out of a hat, but seriously, we spent a lot of time with talks that showed, I guess diversity and integration in the community. So, what projects are starting to pick up steam? What projects are starting to integrate more deeply with other ones? So you'll see lots of commentary around, multi cluster items within cloud native technologies, as well as, lots of content on security, which I'm excited about. >> Yeah, and also things are like, there's a little bit like, kind of to your point about like things layered on, like we're starting to get to the point where people are talking about like hey, I deployed Kubernetes and Envoy and something else. And like, these are starting to be a lot more of these kind of joint talks there that actually even make it harder for us to place. Like, does it belong in networking? Does it belong in application development? Like there've been some really good challenges trying to figure out where things are slotted and what's right- >> You know one of the things I love about KubeCon besides being fun to go to while it's face to face is even with the virtual, it's still a great community. The talks are awesome, people are submitting talks. But you got the sixth year, I think it's a six year or fifth year. We've been there for all years. I think this is the sixth year for us, the maturation, the growth and of Kubernetes now it's pretty clear. This glue layer, is gluing things together the API is extending to service and more services. Can you guys comment on what you guys are seeing in terms of some of the practical projects and how they're playing out for developers? Because you're starting to see you know, more clusters you've got cloud you've got multi-cloud around the horizon. So you've got more of these conversations where you have more capabilities but the focus on the modern application building is the number one business focus. So, you know, the developers are trying to build out under the covers and say, how do I scale this? So, this seems to be the kind of a growth year and inflection point for that next level. It seems like next level. Steven, what's your thoughts and reactions to that? >> Yeah absolutely. So, as a former, I've been out a few cloud native companies at this point so more or less from Red Hat before heading over to VMware. And as a former field engineer and solutions architects at some of these places, we spent a lot of time thinking through what is the days, zero day one story, right? And it's very clear that as a community, we've gotten to the point where like that is officially the boring stuff, right? Seeing a lot of the features within projects like (indistinct) and Cluster API come to maturation. We start to focus a lot more on that developer story, right? And ultimately that's what we care about, right? Businesses are not necessarily looking for a new tool to play around with, right? There are business goals that are tied to the new technologies, right? So the velocity in which you deploy your applications, the feedback loop in terms of understanding, you know, what ties into your application, where things are going wrong and, you know, Constance can definitely speak to the, the observability layer for all of these cloud native applications that are out there. >> Constance, observability I hear is really hot right now, what's your take on it, I mean is observability everywhere? New startup comes out and you work at Splunk, they're the King King of observability, they started out with very small observation space now it's a full platform. You have to look at the observation space to get the data that's the internet. >> You do. >> That's semi application. What's hot in observability? Take us through your thoughts. >> I think what's also starting to like, so you're still like, there's some, I can think of like one talk right now, it's a little bit talking about like, you know, observability at scale in a sense of just like now we have these massive applications and saying we globally and to observe and monitor observe right now, I'm not going to use a tourism changeable. I know that's a total different debate the available topic, but for now, just keep it at that. But it's also now, I think one thing as observability space and maturing is we're not talking only about like, hey, I instrument my like application with metrics, logs, traces, or some other thing there. It's now being a little bit more critical about how, if I'm using all three of these are all different telemetries, like how to be smart about it. Like, okay, I'll need to use traces for some things and let me use logs for something else. And like kind of getting to reach a part of like, now that we have that data let's actually think about better ways to use that data. So we don't, you know, collect everything cause you can't collect everything as much as we want to. >> Well, I mean this is something that I want to get your both thoughts on because one of the conversations we're hearing from developers and we hear it from them on the business size everything is a service, that's like the ivory tower you know, the CXOs, everything is as a service and then it down into the developers in the engineering community and they're like, well, it's not that easy 'cause you got tools for every platform, right? And that's a problem because these siloed tools are tools that were built for a certain products. And then you've got the systems thinking you guys talk about this integration is a key area. So making everything is as a service, just isn't that easy, right? So the goal is to make it easy, right? So this is the systems conversation. How do you guys look at that from a KubeCon, CloudNativeCon because cloud native does enable a lot of, good things. It's horizontally scalable cloud from a resource standpoint, you've got programmability. You can look at it as a system but people are stuck with these tools for the platform. I mean, you have tools for this, tools for that and five different tools, how do you make observability work? How do you make security work? These are tough questions. What's your reaction to that? >> I think that a lot of it comes down to, from a building perspective and, you know, taking the builder perspective and then also taking the consumer perspective. For builders, and I actually spent some time with, at some developer heads in New York, we sat down for a dinner and kind of talked, talked through some of the problems in the space. And I think what it really comes down to is when we build tools we need to think about who we're building the tools for, right? There are multiple personas that you might look at in the cloud native space. And, you know, one might be the persona of that systems integrator, of the classic Opsy, DevOps SRE role, right? Then you've got someone who may be building tools on top of one of those Ops platforms, right? And then you've got the consumers that may be in your company maybe they're external, right? That's for their experience, they're really only interested in how do I ship my app, right? So whether we're talking about building out Kubernetes or whether we're talking about a server less platform, right? So sort of Alyssa and the cloud, right? You often hear the, it runs on, it's running on someone else's machine, right? You know, it's not really, so I think in that space you have to consider a developer experience, right? So I think one of the overarching themes that you'll see throughout this KubeCon is, how do we talk about the developer experience? Who are we building these tools for? How can we actually get outcomes that end users are looking for? Right, cause it's not, again, it's not about the tools it's about the outcomes for the respective businesses. >> Constance what's your reaction to this trend of tools. >> I think. >> Edge computing, 'cause you you don't want to have to build security for everything, single thing. I've got an edge device, I want to have that'd be software operated, right? It makes total sense. But making that happen is hard. >> Yeah, I think this is something that as a community like we're really, I guess like kind of how I use example like end user docs versus restaurants documentation. I think that we've been, done a really good job at creating these really powerful tools but like in terms of, we still need to simplify them for anyone who doesn't want to learn, like say Kubernetes or Envoy or open telemetry, like the back of their hand. And I think that's where we're starting to finally start to close that gap. And as I think also why KubeCon is getting a lot more popular is like now things are a little bit more accessible to those who don't have, you know, either don't have the bandwidth or it just it isn't in their interest to learn all these things in details. And so we're slowly going from those who want to be deep, deep experts into, yeah I kind of want to play around with it and make it more manageable. And, I do think we still have quite a bit of ways to go. Like I think, you know, what's been helpful like at least like our end user stories that we get and like the application development track, especially that one, like the case studies that there's no longer track but it is highlighted as like these talks and case studies. I think that shows it's kind of giving people more like, hey, these are stories of how I can take these tools and start making them more digestible in my own way. 'Cause going from like, oh, this feature does XYZ to, this is a whole story that you can do around it. It's been a little very gap, we're closing. >> Yeah, and I think one of the things about you kind of being shy there, I'll say, KubeCon, CloudNativeCon, CNCF in general has been very successful because of the end user focus I will say that. But also the ecosystem of the vendors that are there. So you have kind of the best of both worlds and they'll want to get better, right? So, but they al have to make money at the same time. So you have this balance, is open source, is what it is, it's out in the open. Can you guys comment on how the community is thriving and surviving? We're in a tough time with the pandemic. It's been a big challenge honestly, we're not in person we're remote. How is everything going with the community? Because it's such a great end user vendor community working together out in the open shipping code, trying to make things better. What's the state of the community? >> Yeah, so I would say that honestly, what it comes down to is that word community, we're all friends, right? There are people who, you know, as the, as we moved towards is kind of like cloud native consolidation of companies. A lot of us have worked together before, right? A lot of us are active in multiple communities and what comes out of that is really open and honest collaboration as a result. You know, even today there's a Twitter thread going, you know, I started talking about the Kubernetes release cadence, right? And if, and how it should change. Given 2020, we had an extended release cycle for 119, right? And questions became, what do we do? Like, do we continue with three releases a year? Do we try for, to do the switch back to four? Like, what does that look like? Right. And reaching out across the Kubernetes community across the CNCFC, the contributor strategy saying in CNCF and getting feedback from all of these people who depend on the products that we build day to day is huge. So I think what it comes down to really is, is open and honest collaboration. I think, you know, when you were strained I know that everyone has a lot going on in life right now. What's great about it is being forthcoming with that, right? We have all of these teams that are, that are built to support the people that are around them. So, if anything, I, you know, I'd love to see all of the collaboration and feedback coming from everyone who works on these projects day to day. >> Yeah. >> Constance what's your reaction? I mean when, I've talked of some developer friends of mine, they're like, hey, this is great, I can work virtually, I've been doing it for years anyway. So no big deal. It's not like the people who have to go to the office every day. So they're used to virtual format. The other comment was, I get more time to do some gaming too. Trying to make light out of the bad situation, but you know, it is serious. What's your reaction to the survival and the thriving continue thriving of the community? >> Yeah, I also want to eventually go back to cause you're making a comment about vendors and now this is my first time as vendor. I have interesting, I like, it's a really interesting perspective to come from, but let's talk about the community. I think like, you know, it's like one of the things that like I think actually has been one of the highlights of this year for me, for 2020, it like to be co-chair but it's also just to like be able to work with Stephen and Nancy and the rest of the CNCF community. And also like any attendees, like has actually even though this is a big year of change and it's, you know, it was a change that no one was planning. It has definitely been like really nice to just get like Kube, I guess would say as an example, the story like for KubeCon you, like I was surprised at how many people were engaged in the Slack channel and asking questions and like Priyanka has set up these happy hours and people are just joining and we're starting to talk and so it wasn't quite hallway track but we still had that connection. And there was definitely, there are people who are attending from all parts of the world. And I thought that was really nice. Like, we think CNCF has made it, like they have made the statement before that there will always be a virtual component to it to address the fact that, you know, our community we're so used to being in person, but that does, you know it does reduce accessibility to those who can't travel or for whatever reason they can't be there in person. So now it is becoming more open. And, I know, I mean kind of turning back a little bit a little bit derail, I'm a little bit derailing but to your point about like also like the vendors. And so this is my first time being a part of a vendor. And I think what's really interesting is like, there's this natural like, you know, tension between like, oh, some were like, oh, I don't want to do it from the vendors, or like, I only want things from end users. But I think the thing that I've kind of forget is that both of them are like active, you know, they're active in the community, both in either contributing or enabling others to be successful using CNCF projects. And so we all have, you know, valid points and perspectives on it really. You can maybe sometimes argue that sometimes being a vendor is almost a bonus because you get to talk to maybe more people who are trying to adopt the technology and you get to see trends. And then after as an end user, you could say like, hey, I have this really unique problem here and this is how I try to solve it and share that story with other people, so. >> Yeah, I mean, I think you're right. I mean, there's checks and balance I've observed over my years in open source you've seen certain things thrive certain ways. And I think that balance and, but having the mission and kind of a rules of engagement if always seen well, good, worked well for CNCF they embraced the vendors really well, but they're, I mean I will say paranoid cause that's my word. But like they're paranoid of the vendors I would be too, like, you know, only to get their fingers in the pie, but they're also contributing. So there's always been that checks and balance and that's, what's been magical I think about it is that they fostered the community, they fostered the engagement and they fostered that balance. And I think that's where the give and get comes in. And I think that's a healthy community and I just love to see and love to be involved with. So, it's super, super good approach. Now, putting back the vendor hat on, if I'm a vendor, I want a competitive advantage. So yeah, this brings us to the next gen conversation open source goes and going next gen, you're seeing a big focus on AI, you're seeing a big focus on, you know, edge computing which is going to be software operated, software defined, which cloud native will lead. I got to get your perspective on something. Steven said at the top was security. Every conversation for the past five months with Dave has been shift left. So, okay. Where are we going left? We're shifting left. This is about security. How do you build security in? This has been a big conversation. It's not easy problem. I know it's a top focus. I want to get your reactions Steve and we'll start with you then Constance I would like you to weigh in too. >> Yeah sure, so, security, security is already strict, right? And I think that people start to put the focus on security when it's a little too late, right? The move is always preventative as opposed to reactive, right? And security is an onion, right? So it's not enough to just think about security on one axis, right? It's, you know, how is this affecting, you know, how is this affecting my application, the systems that I build, the physical, you know, the physical restraints of the, you know, of the area, right? Infrastructure, the cloud providers that I'm running on, right? Are they a certain level of compliant, right? Especially when that comes up for federal customers, right? On the application side, right? You know, if you think of, you know, if you think of all the, the different ways that you can break an application that hurts security now with the cloud native space container security, right? Am I building a safe Docker files or build packs or what have you, however you package your application. And ultimately you have to, you know and then there's also the supply chain, right? Am I getting, how am I moving that stuff from some physical infrastructure or some cloud infrastructure into the hands of the developers, into the hands of the customers? How do I react to changes once those applications have actually been deployed? Right? So like all of these things to consider and when you look at that space, these are multiple teams, right? These are dozens and dozens of teams across, you know, multiple companies, right? You may not have, you may not have full control of your security story, right? So I think that, what, you know what you need to do is start the conversation internally about how we can build security at multiple layers, right? So some of the things that are kind of interesting to see pop up during this KubeCon and some of, you know, and some of the last ones, the continued work that's happening on OPA and Gatekeeper spiffy and Spire, right? And, you know, all of these, all these frameworks for authentication and authorization that are kind of cropping up, right? I think, you know, Spiffy and Spire really interesting story because, you know, the first thing that you think is I have these cloud native applications that I'm building and I also have these legacy applications, right? How can I build a bridge between the two? Right? And then you've also got things like, you know, service mesh, right? And you start to talk about service mesh and, you know, the security within applications that live inside a cluster or across cluster, right? And how you negotiate that. So tons of things to think about, and, you know, it's honestly going to it's honestly going to depend on where you are in your journey but I think that, you know, good security is only built by having the conversation and having the conversation across all teams and doing it before you get into trouble. >> Do it before you get in trouble have it baked in from the beginning, brush your teeth make sure you're all healthy. Constance your reaction, (laughing) your reaction. >> So I will say like, I am unfortunately one of those people that like security, well security is just not something that I guess going to say I find super exciting. And it mostly just because I, I really love observability and like service mesh and so I usually defer to the experts on that, but I do want to like, I guess plus when some of what Steven said, obviously using git hub, you know, terminology for plus and what you know, enhancing things like definitely started early and it, but I think, you know, start early, start a conversation. But I think we also need just be cognizant of like for any of the technologies, like if it's security say networking whatever, all of these things are behavior changes and just bucket more time than you think you're going to need. There's going to be so many roadblocks and especially when it comes like, especially when it comes to behavior changes. Like, if you're and behavior, but not like necessarily like a personal, but like, you know, technology behavior like you're used to sending things without MTLS, right? Or, you know, with our backs, things are going to fail and, you know, there's going to be that initial friction and so definitely trying to make this smooth as possible. >> Yeah, I mean, I think that's the focus I like to see more of which is having it be built in. So if you're really not into it, but you don't want to screw it up either so you want to be on top of it without doing it, right? That's the end game, right? That's what DevOps is about. So if you don't have programming infrastructure write code. So all these things, this is the trend this is the trend that we're seeing in cloud native. Can you guys share your thoughts this year on, on the most important stories that you think people should think about or lean into or at least look at for KubeCon? What are some of the things that attendees or people watching remotely or participating virtually or in the Slack channels, what should they pay attention to? >> So starting with, I think even with the last KubeCon and some of the products that have recently come out from certain vendors, we're starting to look a lot more at the, what is that conversion story for someone who is a classic CIS admin, right? Who may be learning all about cloud native technology for the first time, or how do we, you know, how do we welcome a new KubeCon attendee to the community? So I think one of the best things that we did was instantiate that's a one-on-one track, right? So with the one-on-one track, I think we got a bunch of great feedback. So we work to make sure that they were actually, we eliminated I believe we fully eliminated the lightning talks and work to include more one-on-one content as well as tutorials within this program. >> Constance, your reaction, Constance your reaction to thoughts on the most important story to pay attention to? >> I think it's more, right, cause, okay, I know this is like a common line that we say at KubeCon and like, you know, depends what group your on. But since so many more of our talks we're now talking about intersections between like, you know, using X and Y try to build Z, Zed. Oh my goodness I'm trying, I'm losing my Zeds. I think trying to like, you know looking for those talks that at least somewhat resonated like, hey, I've already talked to communities, let me see how I add Envoy. Like, trying to find those there because there's a lot more of that content now, right? Cause maybe you know, about like to even last KubeCon or like last KubeCon North America, a lot of the things were more focused on like one project, maybe a hint or you're just going to see more of these combinations. And so there are a lot more, there's a lot more of that content available for you to find. I'm doing two, three, maybe four, It's a lot of projects at once, adoptions and seeing how that works too. Oh yeah, one-on-one track has definitely been definitely like a great hit. I'm going to say, right? The first time it was launched and we got so many CFPs for one-on-one it was just amazing to see all these ways that people wanted to make KubeCon more accessible to everyone else who hasn't been a part of, you know. >> It's every year, it's every year the onboarding of new members of the community would be impressive. And having that tracker laddering or different ways to work as a community to help people along has been another thing I noticed you guys do really well on. There's a real camaraderie amongst the community. So a hat tip for you guys on that. Final question for you guys is more about the format. Obviously it's virtual this year the game is still the same. There's talks, there's people, there's hallways, but they're virtual, I guess you're virtually walking through Slack and discord or Twitter, whatever. What's the learnings from last event, as we're going into virtual, how does an attendee maximize their time, their engagement there's times to lean in and be present, attending a talk, you mentioned Slack Constance. What's some of the learnings that you guys have learned from virtual? And what can people think about and prepare for, for KubeCon virtual this year? >> Yeah, I think one way you start it. So, there's actually a resource, this came from our debrief for me, it was like there's a resource like, hey, let me help get the day off. And like, we even provided template to like provide to your, you know, direct to your managers. Say like can I please get this day off so I could focus on it? And I think that's one thing that and I think we'd all probably seen on Twitter and blogs is that even though it is virtual it is still a brain drain, well it's still, you know, you have to engage with a topic so set aside time. I would probably even say attend fewer talks, than you would normally do in person there is zoom fatigue, I guess it's been from on screen fatigue. So just give yourself a lot more space to consume the information and just debrief and also join the activities, right? Like ask questions in Slack. There's a lot of the virtual events like there's bingo there's even an escape room, which sounds like a lot of fun, all these different activities too that you can do with everyone. So like definitely enjoy that part, right? 'Cause you still get a little bit off until you just say like hey, you mentioned this project, let's chat offline. And then, you know, a few weeks later you may be on a four hour long Zoom meeting talking about some project. And so, yeah >> Yeah, I noticed the hang space kind of mindset of virtual was pretty cool. Be mindful to introduce yourself and either do a sidebar or jump on some back channel. I mean, there's plenty of tools, developers know what they are, so pretty good point I want to call that out. Good, good point Constance. Steven, your thoughts on learnings from the virtual format and then things this year people should pay attention to and jump in and use the site for. >> Yeah, so I would say if anything the previous attendees gave lots of thoughtful feedback about how to improve the overall program. One of my favorite parts of any conference and it's the part that I prioritize more than anything else in the conference even the talks, right? Is the hallway track, right? It's one of the few times, you know, especially with KubeCon and the various contributors across the cloud native space that's the, you know, the one time every quarter or so that I get an opportunity to see these people face to face, right? So, you know, we wanted to do our best to bring in experience that felt, you know, it's not the, you know, it's not the same as the physical hug, right? Or the, you know, or going out for, you know, going out for dinner after a long day. But we tried and we laughed through lots of crazy ideas that the event team, to see what they would come up with for me as a New York resident and having a conference that is any virtual but would have been in Boston, I thought it was important thinking about screen fatigue, as well as just the physicality of where people would have been at the time, is the start time of the conference, right? So as Constance was mentioning screen fatigue it's, I think with all of the virtual conferences going on, it's very hard to have that time during the day, right? So this KubeCon for folks on the East coast it starts basically at your lunchtime. So the idea is, hopefully you get some, you get some of your meetings in for the day, grab a bite to eat and then you sit down for lunch and you, and you dig into some KubeCon, so. >> Yeah, and you can have any lunch you want and then later of you will be able to eat lunch from the conference. That's awesome. The other thing I love about the, what you guys said is the hallway tracks. And I think one of the things I've noticed going to a lot of virtual events and doing them is, Constance you're right, it's mentally draining to lean into a talk because you're present, even though you're virtual. So taking time to get involved in the fun activities or just, you know, wandering Slack or doing a sidebar with the hallways is kind of a have some time off like the time to regroup and not be so, you know, leaned into a session, I find that to help on the fatigue side for sure. The other one is viewing parties. We popped into some, you know, Zooms together and we watched each other watch the session, right? So viewing parties has been one trick I've seen work well, other ones I've seen people toast beer at a certain time. The Germans obviously do at first, cause they're on the time zone, but you start to see these playful things. You know, people can share their kind of position where they are. So it's fun. We'll look forward to seeing that. Okay, final comments, Steven, Constance. What's the bumper sticker this year for KubeCon? >> Ooh, have we decided yet Constance? (laughing) >> Velvet jackets are required for entry. (laughing) I'll make word sense after you see a special message from us. (laughing) >> It's a lot of fashion on stage, on stage, right? >> All right we stumped the co-chairs. (laughing) We stumped the, well, I want to say thank you very much for coming on and sharing little color commentary on KubeCon around the program, some of the things when the virtual event too some of the talks, really appreciate it and we really appreciate what you do, the community does. It's been a hard year. We're not going to be there in person. We'll continue to ride the wave in to back to the normal. So thanks for doing what you doing and thank you for coming on. >> Thank you so much for having us. >> Yeah, thank you. >> Okay. This is theCUBE, virtual coverage of KubeCon CloudNativeCon virtual November 17th to the 20th. I'm John Furrier, your host for theCUBE. Thanks for watching. (upbeat music)

>> Announcer: Live from San Jose, it's theCUBE, presenting Big Data, Silicon Valley, brought to you by SiliconANGLE Media and its ecosystem partners. >> Welcome back to theCUBE. Our continuing coverage of our event, Big Data SV, continues, this is our first day. We are down the street from the Strata Data Conference. Come by, we're at this really cool venue, the Forager Tasting Room. We've got a cocktail party tonight. You're going to hear some insights there as well as tomorrow morning. I am Lisa Martin, joined by my co-host, George Gilbert, and we welcome back to theCUBE, for I think the 900 millionth time, the president and CEO of DataTorrent, Guy Churchward. Hey Guy, welcome back! >> Thank you, Lisa, I appreciate it. >> So you're one of our regular VIP's. Give us the update on DataTorrent. What's new, what's going on? >> We actually talked to you a couple of weeks ago. We did a big announcement which was around 3.10, so it's a new release that we have. In all small companies, and we're a small startup, in the big data and analytic space, there is a plethora of features that I can reel through. But it actually makes something a little bit more fundamental. So in the last year... In fact, I think we chatted with you maybe six months ago. We've been looking very carefully at how customers purchase and what they want and how they execute against technology, and it's very very different to what I expected when I came into the company about a year ago off the EMC role that I had. And so, although the features are there, there's a huge amount of underpinning around the experience that a customer would have around big data applications. I'm reminded of, I think it's Gartner that quoted that something like 80% of big data applications fail. And this is one of the things that we really wanted to look at. We have very large customers in production, and we did the analysis of what are we doing well with them, and why can't we do that en masse, and what are people really looking for? So that was really what the release was about. >> Let's elaborate on this a little bit. I want to drill into something where you said many projects, as we've all heard, have not succeeded. There's a huge amount of complexity. The terminology we use is, without tarring and feathering any one particular product, the open source community is kind of like, you're sort of harnessing a couple dozen animals and a zookeeper that works in triplicate... How does DataTorrent tackle that problem? >> Yeah, I mean, in fact I was desperately interested in writing a blog recently about using the word community after open source, because in some respects, there isn't a huge community around the open source movement. What we find is it's the du jour way in which we want to deliver technology, so I have a huge amount of developers that work on a thing called Apache Apex, which is a component in a solution, or in an architecture and in an outcome. And we love what we do, and we do the best we do, and it's better than anybody else's thing. But that's not an application, that's not an outcome. And what happens is, we kind of don't think about what else a customer has to put together, so then they have to go out to the zoo and pick loads of bits and pieces and then try to figure out how to stitch them all together in the best they can. And that takes an inordinately long time. And, in general, people who love this love tinkering with technologies, and their projects never get to production. And large enterprises are used to sitting down and saying, "I need a bulletproof application. "It has to be industrialized. "I need a full SLA on the back of it. "This thing has to have lights out technology. "And I need it quick." Because that was the other thing, as an aspect, is this market is moving so fast, and you look at things like digital economy or any other buzz term, but it really means that if you realize you need to do something, you're probably already too late. And therefore, you need it speedy, expedited. So the idea of being able to wait for 12 months, or two years for an application, also makes no sense. So the arch of this is basically deliver an outcome, don't try and change the way in which open source is currently developed, because they're in components, but embrace them. And so what we did is we sort of looked at it and said, "Well what do people really want to do?" And it's big data analytics, and I want to ingest a lot of information, I want to enrich it, I want to analyze it, and I want to take actions, and then I want to go park it. And so, we looked at it and said, "Okay, so the majority "of stuff we need is what we call a cache stack, "which is KAFKA, Apache Apex, Spark and Hadoop, "and then put complex compute on top." So you would have heard of terms like machine learning, and dimensional compute, so we have their modules. So we actually created an opinionated stack... Because otherwise you have a thousand to choose from and people get confused with choice. I equate it to going into a menu at a restaurant, there's two types of restaurants, you walk into one and you can turn pages and pages and pages and pages of stuff, and you think that's great, I got loads of choice, but the choice kind of confuses you. And also, there's only one chef at the back, and he can't cook everything well. So you know if he chooses the components and puts them together, you're probably not going to get the best meal. And then you go to restaurants that you know are really good, they generally give you one piece of paper and they say, "Here's your three entrees." And you know every single one of them. It's not a lot of choice, but at the end of the day, it's going to be a really good meal. >> So when you go into a customer... You're leading us to ask you the question which is, you're selling the prix fixe tasting menu, and you're putting all the ingredients together. What are some of those solutions and then, sort of, what happens to the platform underneath? >> Yeah, so what you don't want to do is to take these flexible, microdata services, which are open source projects, and hard glue them together to create an application that then has no flexibility. Because, again, one of the myths that I used to assume is applications would last us seven to 10 years. But what we're finding in this space is this movement towards consumerization of enterprise applications. In other words, I need an app and I need it tomorrow because I'm competitively disadvantaged, but it might be wrong, so I then need to adjust it really quick. It's this idea of continual developed, continual adjustment. But that flies in the face of all of this gluing and enterprise-ilities. And I want to base it on open source, and open source, by default, doesn't glue well together. And so what we did is we said okay, not only do you have to create an opinionated stack, and you do that because you want them all to scale into all industries, and they don't need a huge amount of choice, just pick best of breed. But you need to then put a sleeve around them so they all act as though they are a single application. And so we actually announced a thing calls Epoxy. It's a bit of a riff on gluing, but it's called DataTorrent Epoxy. So we have, it's like a microdata service bus, and you can then interchange the components. For instance, right now, Apache Apex is this string-based processing engine in that component. But if there's a better unit, we're quite happy to pull it out, chuck it away, and then put another one in. This isn't a ubiquitous snap-on toolset, because, again, the premise is use open source, get the innovation from there. It has to be bulletproof and enterprise-ility and move really fast. So those are the components I was working on. >> Guy, as CEO, I'm sure you speak with a lot of customers often. What are some of the buying patterns that you're seeing across industries, and what are some of the major business value that DataTorrent can help deliver to your customers? >> The buying patterns when we get involved, and I'm kind of breaking this down into a slightly different way, because we normally get involved when a project's in flight, one of the 80% that's failing, and in general, it's driven by a strategic business partner that has an agenda. And what you see is proprietary application vendors will say, "We can solve everything for you." So they put the tool in and realize it doesn't have the flexibility, it does have enterprise-ility, but it can't adjust fast. And then you get the other type who say, "Well we'll go to a distro or we'll go "to a general purpose practitioner, "and they'll build an application for us." And they'll take open source components, but they'll glue it together with proprietary mush, and then that doesn't then grow past. And then you get the other ones, which is, "Well if I actually am not guided by anybody, "I'll buy a bunch of developers, stick them in my company, "and I've got control on that." But they fiddle around a lot. So we arrive in and, in general, they're in this middle process of saying, "I'm at a competitive disadvantage, "I want to move forward and I want to move forward fast, "and we're working on one of those three channels." The types of outcomes, we just, and back to the expediency of this, we had a telco come to us recently, and it was just before the iPhone X launched, and they wanted to do AB testing on the launch on their platform. We got them up and running within three months. Subsequent from that launch, they then repurposed the platform and some of the components with some augmentation, and they've come out with three further applications. They've all gone into production. So the idea is then these fast cycles of microdata services being stitched together with the Epoxy resin type approach-- >> So faster time to value, lower TCO-- >> Exactly. >> Being able to get to meet their customers' needs faster-- >> Exactly, so it's outcome-based and time to value, and it's time to proof. Because this is, again, the thing that Gartner picked up on, is Hadoop's difficult, this market's complex and people kick the tires a lot. And I sort of joke with customers, "Hey if you want to "obsess about components rather than the outcome, "then your successor will probably come see us "once you're out and your group's failed." And I don't mean that in an obnoxious way. It's not just DataTorrent that solves this same thing, but this it the movement, right? Deal with open source, get enterprise-ilities, get us up and running within a quarter or two, and then let us have some use and agile repurposing. >> Following on that, just to understand going in with a solution to an economic buyer, but then having the platform be reusable, is it opinionated and focused on continuous processing applications, or does it also address both the continuous processing and batch processing? >> Yeah, it's a good answer. In general, and again Gatekeeper, you've got batch and you've got realtime and string, and so we deal with data in motion, which is string-based processing. A string-based processing engine can deal with batch as well, but a batch cannot deal with string. >> George: So you do both-- >> Yeah >> And the idea being that you can have one programming model for both. >> Exactly. >> It's just a window, batch is just a window. >> And the other thing is, a myth bust, is for the last maybe eight plus years, companies assume that the first thing you do in big data analytics is collect all the data, create a data lake, and so they go in there, they ingest the information, they put it into a data lake, and then they poke the data lake posthumously. But the data in the data lake is, by default, already old. So the latency of sticking it into a data lake and then sorting it, and then basically poking it, means that if anybody deals with the data that's in motion, you lose. Because I'm analyzing as it's happening and then you would be analyzing it after at rest, right? So now the architecture of choice is ingest the information, use high performance storage and compute, and then, in essence, ingest, normalize, enrich, analyze, and act on data in motion, in memory. And then when I've used it, then throw it off into a data lake because then I can basically do posthumous analytics and use that for enrichment later. >> You said something also interesting where the DataTorrent customers, the initial successful ones sort of tended to be larger organizations. Those are typically the ones with skillsets to, if anyone's going to be able to put pieces together, it's those guys. Have you not... Well, we always expected big data applications, or sort of adaptive applications, to go mainstream when they were either packaged apps to take all the analysis and embed it, or when you had end to end integrated products to make it simple. Where do you think, what's going to drive this mainstream? >> Yeah, it depends on how mainstream you want mainstream. It's kind of like saying how fast is a fast car. If you want a contractor that comes into IT to create a dashboard, go buy Tableau, and that's mainstream analytics, but it's not. It's mainstream dashboarding of data. The applications that we deal with, by default, the more complex data, they're going to be larger organizations. Don't misunderstand when I say, "We deal with these organizations." We don't have a professional services arm. We work very closely with people like HCL, and we do have a jumpstart team that helps people get there. But our job is teach someone, it's like a kid with a bike and the training wheels, our job is to teach them how to ride the bike, and kick the wheels off, and step away. Because what we don't want to do is to put a professional services drip feed into them and just keep sucking the money out. Our job is to get them there. Now, we've got one company who actually are going to go live next month, and it's a kid tracker, you know like a GPS one that you put on bags and with your kids, and it'll be realtime tracking for the school and also for the individuals. And they had absolutely zero Hadoop experience when we got involved with them. And so we've brought them up, we've helped them with the application, we've kicked the wheels off and now they're going to be sailing. I would say, in a year's time, they're going to be comfortable to just ignore us completely, and in the first year, there's still going to be some handholding and covering up a bruise as they fall off the bike every so often. But that's our job, it's IP, technology, all about outcomes and all about time to value. >> And from a differentiation standpoint, that ability to enable that self service and kick off the training wheels, is that one of the biggest differentiators that you find DataTorret has, versus the Tableau's and the other competitors on the market? >> I don't want to say there's no one doing what we're doing, because that will sound like we're doing something odd. But there's no one doing what we're doing. And it's almost like Tesla. Are they an electric car or are they a platform? They've spurred an industry on, and Uber did the same thing, and Lyft's done something and AirBNB has. And what we've noticed is customer's buying patterns are very specific now. Use open source, get up their enterprise-ilities, and have that level of agility. Nobody else is really doing that. The only people that will do that is your contract with someone like Hortonworks or a Cloudera, and actually pay them a lot of money to build the application for you. And our job is really saying, "No, instead of you paying "them on professional services, we'll give you the sleeve, "we'll make it a little bit more opinionated, "and we'll get you there really quickly, "and then we'll let you and set you free." And so that's one. We have a thing called the Application Factory. That's the snap on toolset where they can literally go to a GUI and say, "I'm in the financial market, "I want a fraud prevention application." And we literally then just self assemble the stack, they can pick it up, and then put their input and output in. And then, as we move forward, we'll have partners who are building the spoke applications in verticals, and they will put them up on our website, so the customers can come in and download them. Everything is subscription software. >> Fantastic, I wish we had more time, but thanks so much for finding some time today to come by theCUBE, tell us what's new, and we look forward to seeing you on the show again very soon. >> I appreciate it, thank you very much. >> We want to thank you for watching theCUBE. Again, Lisa Martin with my co-host George Gilbert, we're live at our event, Big Data SV, in downtown San Jose, down the street from the Strata Data Conference. Stick around, George and I will be back after a short break with our next guest. (light electronic jingle)