 Live from London, England. Extracting the signal from the noise. It's theCUBE. Cover, Discover 2015. Brought to you by Hewlett Packard Enterprise. Now your hosts, John Furrier and Dave Vellante. Okay, welcome back everyone. We are live here in London, England. This is theCUBE, HPE Discover, HPE Discover. Make sure you get that E in there. HPE Enterprise is the first show for their official spin-out split of the two companies. I'm John Furrier with Dave Vellante. This is theCUBE. It's our flagship program. We go out to the events and extract the signal from the noise. Our next guest is Casey Choi, VP of Global Solutions, Architecture and Engineer at HPE, HPE Enterprise. Welcome back to theCUBE. Good to see you. Talk about the 10-year difference between today and 10 years ago, because microservices is really exciting. Look at the possibilities. A lot of leverage there. Costs to deploy is lower. Everything's lining up nicely for this new development application tsunami coming. 10 years ago, we had web servers. We had service-oriented architectures. We had these things, but what's different now? I'm not saying there's some cost differences, but the parent contrast, and then how that's making this today's architecture more compelling to make moves now. Yeah, John, I think it's a generational difference. We're talking almost a generation, and part of it, frankly, is a generational difference. We've got a new generation of developers. We've got a new generation of folks that are coming into this space as enterprise architects, developers, coders, and engineers that are really, they think differently, frankly. They're taught differently in terms of the computer science that's coming out today, right? And the things that we learned in terms of structured languages and the way to program for things has fundamentally changed. I think one fundamental difference is you've got a very brand new generation of people that think differently. They're thinking much more in a runtime model versus a compile model to kind of break it down that way, where versus being something that's preformed and ready to go, you're composing these things, you're composing these services, and you're delivering them through very different mechanisms. 10 years ago, we were just at the cusp of virtual machines. Now, we're at the cusp of delivering services through things like container-based technologies and offering tremendous isolation and security that we didn't have before, right? That was preformed in the services. So I think there's quite a bit of difference between what was there, the concepts that were out there. So virtualization has been a big enabler. Absolutely, yeah. And as we move forward, more of the container type technologies that are coming out from the open source community and others, and I think it's going to be that next leap forward because now you're going to be able to do this at a more granular level. You're going to be able to do some separation around the data plane aspects of it. So we're getting better and better at the composability of these services, and we're seeing that reflected everywhere. So one of the conversations we had on our crowd chats a couple of weeks ago was this notion of in the 80s and 90s with the mini computer generation, two generations, I guess three generations ago, or two generations ago, we saw the boom of applications. Now they were siloed-based applications. We pre-packaged they had some silo activity going on big data, but we saw the companies get formed, you know, Oracle, Siebel, all these companies, but they were fully integrated software. Are we going to see something similar because if you look at today's infrastructure and architecture with DevOps, you're kind of talking about this application explosion. Yeah. And you can almost tease out and say, well, based on the thesis of cloud and agile and containers, this new enablement is disruptive in a sense that there should be a slew of apps and then what's the implication, if true, what's the implications of that thesis? Yeah. So John, you're asking me on the crystal ball thing, right? That's an honest question. You know, I'm not sure. I'm not sure we're going to see, you know, the level of vertical integration that we saw, you know, in that last wave, right? Where we saw a lot of those companies form up because the stuff was complicated and required a degree of vertical integration. It required a degree of industry integration that was required to stand these up. I mean, think about the man hours it took to, you know, stand up in Oracle environment or an SAP environment or any environment for that matter, right? It was a significant effort, not only cost-wise, but time-wise. I think this next wave is different. I think it's going to be much more built on an open construct. I think it's going to be platform-based. I think it's going to be driven by, again, a set of capabilities and offerings. I mean, everything from what's available in the infrastructure stack, all the way up through the development tools. And I think it's going to be, you know, primarily based on who can provide the best ecosystem for that versus, again, being the vertical integrator of all of that. So I think the model's quite different. I think the end objectives are similar in a lot of cases, right? We're still going to need systems of record and transactional systems, but they're going to be overlaid, much more transient in the way that we look at these applications. Hold on a minute before I give back. So let's back up. It's a little pre-crystal ball because I agree with you. I think that bloated software models is pretty much over. We've seen that. But at the top of the stack, lightweight is the new thing, right? So when someone say, I want to have a lightweight software, because it's runtime, because they don't want to have a lot of stuff going on that they can reuse code, infrastructure as code, dev ops. So more of the lightweight applications seem to be emerging, whether that's an iPhone app or a native app, maybe some level of integration at the top of the stack, but not like fully integrated. Do you see that trend? I mean, I absolutely do. And a lot of it's just, again, driven by the appetite for freshness, newness, functionality. I mean, just take a look at most folks today. I heard a story that was told by one of our CTOs the other day where everyone's got these, right? Where he has young daughters and the way they select banking services today is based on really the type of applications that are available through the app store, right? And what is available? What seems to suit their needs? A lot of it's very personalized and personalization is going to drive a lot more need for much more impermanence in the application. So think about what's driving the appetite and the appetite is being driven by the fact that none of these applications last that long, right? And because of that, you are inferring a sense of lightweightness. What isn't lightweight though is the backend stuff, right? You've got to preserve that data chain of custody. You've got to have transactional integrity. You've got to have all that. So we still like to try to remind people, the Hewlett Packard Enterprise that, yes, the front end needs to be custom and it needs to be very personal, but you do have some heavy-duty, you know, transactional integrity. This is what you were saying earlier, but you've got to have that engine underneath the apps. Absolutely, yeah. And the DevOps guys want to have composable architectures where they can do a lot of fast runtime with microservices, real time. Those guys aren't worrying about configuration management. They want to actually have that provision on its own. I think they're worrying about it, but they're worrying less about it. And I think what they're doing is they're worrying about it in smaller chunks, right? So, I mean- They don't want to worry about it. It's a fast-fail mentality and it also says, and again, I'm not criticizing it. I think it's the right sort of model for what we have today. It's contemporary, right? But what it's saying is, you know, I can do this and I'm only going to be taking down a part of my application versus, you know, having a huge degree of dependency within the code. And I think it's a model for today, right? It is a continuous service delivery model, which basically says, look, I'm going to push a lot of things to production, but I'm going to do it in such a way where, you know, a lot of this doesn't have as strong a monolithic dependency as we've had in the past. And again, I think this is a contemporary model. Well, like the old software development models, we used to do our own graphics. Those were in libraries per application, vertically integrated, that went away. Now DevOps guys, they don't want to worry about it, but they might have to. But the DevOps movement says, hey, there's stuff orchestrating and automating on its behalf. So there's not so much they don't care about it. I'd like to have people look at it in a Jeffrey Moore kind of a way, right? You're going to have strong systems of engagement, right? That you're going to build on top of systems of record. Let's just make sure that you are building for the right specification. You know, systems of engagement have to move fast, right? They have to be, you know, temporal by nature. They have to be customized. But, you know, that basis for what happens on the back end side is going to be just as critical. And in many cases, a lot of that, fortunately or unfortunately, is legacy. And that binding has to be there. And I think we're in a good place because we've been able to address and kind of understand both sides of that. And honestly, I'm not sure bimodality is the right answer. I think you got to do both, right? You can't do one or the other. You have to do both. Well, and his latest is systems of intelligence, which bring together analytics and transactions. Yeah, you get the cognitive and the predictive starting to come into the model here, right? And in that sense, you're driving that further and further away. And I think it blends, you know, very well into what the industry's talking about in terms of continuous service delivery because that's probably the penultimate example, right? Because you're modifying what is happening, you know, at the production delivery side, you know, as it's being learned or as it's being utilized. You know, you know. Get foundational, have some foundational work done and then have some building blocks to work with engagement. Right, right. Casey, final question. What's your take on the show? From a customer standpoint, looking around, briefings you've been through, early customers you've talked to, or so you're feeling, what's the customer view of this show for the takeaway? Is it that they have to move now, that the architectures are in place, HP's the bridge to the future? What's the overall take? John, I think there's two things. And you know, you guys and I were together in Vegas back in the summertime. And think about back then, you know, and what we have on the floor today. I mean, this is organized very much around these transformational themes, right? We were just hinting at it back at the time. And quite honestly, a year ago, we weren't there. I think this is a pretty clear indicator of what the new company is going to be about and wants to be about, which is, I want to talk a lot more about outcomes. You know, we want to try to address, in some respects, a different audience, a different buyer. We still think IT is exceptionally important to this. And we want to make them a pivotal piece of what goes on. But you know, we all recognize that we're all going to have to move, right? To this model where the conversation is different. You know, how we look at technology and what its role is is different. But I can't think of a better response to it than to say, look around on the show floor. And this is the new HP. This is the new HP Enterprise, right? And Hewlett-Packard Enterprise. It's organized this way. And I think we're aspiring to be, you know, again that company that helps drive that. And we release that. We're excited to cover you guys. I mean, now that the whole team is together formally. Great. And you guys are focused, younger feels like, you know, splitting half, you know, I'm 50 to younger. Feels younger? All right, good. Maybe somebody will rub off on me. I appreciate that. It feels fresh. All right, good. Good to hear that. Casey Choi here inside the Cube, getting the signal from Noah. He's getting ready for the general sessions. We'll be right back with more live coverage here in London, England after this short break.