 Okay, we're here live back at the Velocity Conference here live in Santa Clara, California. I'm John Furrier, the founder of SiliconANGLE. This is theCUBE, our flagship program. We go out to the events, we check the ceiling from the noise, and Al Sargent is here. He's the director of product marketing Pivotal on the app fabric. As you know, Pivotal has been covered extensively by SiliconANGLE, and of course on the research side with wikibon.org. Recently announcing all the new data around the industrial cloud, and we were at the Pivotal, Amazon and GE event on Tuesday this week. All that footage is available on SiliconANGLE's YouTube page, youtube.com, so it's SiliconANGLE. And this brings up the VMware conversation, VMware recently spun out Pivotal as a separate company to go out on its own and to go out and pioneer what really is the high demand. And that's being talked about here at Velocity Conference. So Al, welcome to theCUBE. Thank you John, good to be here. So you know, obviously the performance discussion is really about, you know, web performance, mobile performance, it's all going to kind of be blend in, the word mobile won't be even talked about in just a year or two, in my opinion, and being talked about here. But really open source is driving it. You guys have spun out all the elements of what was once VMware, Spring, Cetus, Green Plum, Pivotal, all rolled into one. To really go after that developer market, and that's what's here at Velocity. So what's your take here about Velocity and what are you guys doing here? Yeah, I think it's a great question. You know, I think really what the mission of Pivotal is to enable the consumer internet and basically take these best practices that you have in consumer internet companies and drive them into the enterprise. So you can basically have, you know, your own Google grade or Yahoo grade or Facebook grade type of infrastructure. And so when you look at what we're doing at Pivotal, one of the things we're focusing on is Pivotal One. And Pivotal One splits into three different parts. You have your Pivotal application fabric, Pivotal data fabric and Pivotal cloud fabric. And so essentially what you have is the way the different buckets, the things that fit in there. You have Spring, things like Spring and RabbitMQ in the application fabric, things like Cetus and Pivotal HD and Green Plum in the data fabric and then things like Cloud Foundry in our cloud fabric. So when you look at how all that applies to, you know, in terms of the mission of Velocity, building a faster and stronger web, there's a huge amount of alignment because what a lot of these consumer web companies have to do is they have to run quickly. They have to run 24-7. They have hundreds of millions of users. And so we're all about taking those best practices and applying them to the enterprise. And again, that's exactly the mission. So our mission and Velocity's mission really are in alignment. Yeah, obviously I wrote a lot, essentially about the Pivotal spin-out of VMware. Obviously we had Leo Spiegel on theCUBE. And he was the mastermind behind that with Paul Moritz, obviously Pat Gelsinger and Joe Tucci, kind of the Federation, if you will. But what's interesting is that in 2010, Paul Moritz laid out VMware when he was the CEO of VMware. The architecture of, he called the software mainframe, some call it others things, but at the end of the day, the cloud and what we're seeing today. But the top of the stack just didn't materialize within VMware, mainly because there's a lot of stuff going on in the business. I mean, hypervisor commoditization, cloud was very competitive, but by bringing Pivotal out separately, you're decoupling that in a good way and making it very cohesive. Meaning, from an opportunity standpoint, you now can go after and compete and win with product and that developer community. What are you guys doing that's really the most relevant and you could share to really help the developers who want to build a great UX, great user experience and yet be competitive in a DevOps world. Yeah, I think there's a couple of things that we're doing. First thing is, we have an incredibly deep focus on the spring Java framework. And spring has been around for 10 years or so and it might not be the thing that first comes to mind, but one of the things we're doing with spring four that we're going to be announcing, actually here at the Santa Clara Convention Center in September and going into detail on, is we're going to be talking about how spring enables you to build applications easier than ever before with very small amounts of configuration with easy connectivity into big data programming models. And that last one, we have a project called Spring HD and what we do is we see a really big parallel to what was happening a decade ago with the Enterprise Java Bean or EJB programming model where it's just complete pain for developers and spring arose out of that as an easier way to build applications without all the pain of EJB. What we see today is something similar where with Hadoop it's really, really difficult to program against. Spring XD is going to make that a lot easier to program. So we're going to be detailing that and that's going to be a really critical thing for developers. How do you make it easier and faster to build applications that go against these big data data sources? So that's one thing. Another thing is that Pivotal Labs with a very strong focus in terms of not just Java but other languages like Ruby, Python, Node, et cetera. And then you're also seeing a lot of focus in terms of being polyglots. So for instance, RabbitMQ, Redis, these are two Pivotal products. Those can work not only with Java, not only with C-Sharp.net, but also Node, Ruby, Python, Scala, you name it. So lots of things we're doing for developers to make them more productive. What do you see that's important that you could articulate to the audience out there about what the Velocity Conference is trying to do here? Because it's not a one trick pony. It's not a one thing. It's not a cloud show. It's not a DevOps show. It's not just a UX show. What is it about Velocity that makes it unique that really points to this modern era of computing the data center service providers, developers? Yeah, I think what I like about Velocity is the fact that it's focused on solving a particular problem, building a faster and stronger web. I mean, that's probably one of the most, you know, in my mind anyway, most compelling types of taglines for a conference because it's not all about, you know, XYZ database type solution or XYZ language. It's, hey, let's up level it into the needs of the user, the needs of the business, the needs of IT and how do we solve these problems for each of those three different groups of users? And so what that means is performance and resilience and SLA compliance and all that, that cuts across a wide range of things. So it is going to be a type of show where you're going to have a company like Pivotal with application servers and Hadoop distributions. Here at the show with New Relic and AppDynamics, for instance, who do monitoring, who are going to be with other people who focus on other aspects of performance. Because really at the end of the day, performance covers a wide range of different types of categories of products and services. What is the update with Pivotal? Give us some insight into the Pivotal execution because it's on people's minds and one thing I pointed out on Tuesday when I was talking about the amazing announcement was is that you had Pivotal on stage with Amazon with GE and that's a great relapse to GE put in $105 million into Pivotal, so that kind of helps. But if Pivotal is part of VMware, you probably wouldn't have seen them on stage with Amazon. So we did point that out, but it's a whole new era for you guys. So what's going on at Pivotal? Share some color, what's it like? There's been real high satisfaction from the employee side. They've been a good vibe. Obviously stock options and again, Leo the corp dev guy laid this all out. You have stock options for the employees on both sides and just what's happening with Pivotal? Yeah, so I think, well first of all, one thing is that we are very much multi-cloud. So obviously we're going to have a very strong focus on vSphere from VMware and work really excellently, work very well on VMware's infrastructure. Obviously we're going to work well on Amazon, cloudfoundry.com, our hosted service runs in AWS and expect us to run on other types of infrastructure as well, such as OpenStack. So we are really very much looking at a multi-cloud type of focus and frankly that's something that is much more difficult to do at VMware because VMware's rightful mission is to promote vSphere. So that's one thing we are very much in terms of multi-cloud. Another thing is that we are very much focused very hard on employee satisfaction. Our new offices in San Francisco are a great place to work, lots of great programs for the employees. We realize that it's a very competitive market from a recruiting side. We have to be up there in the game as well. The third thing is that we're really driving hard towards Pivotal One, which we're going to be discussing later, hopefully, don't take this as a guarantee, but the hope is that we can talk about this. You know, towards the end of the year. Of course you're going to talk about Pivotal One, it's the main product. Yeah, yeah, yeah. So we're basically, you know, rolling everything into the Pivotal One banner and really driving towards one single team. And you think about, right, the history of this, right, we have people coming from VMware, we have people coming from EMC, we have Pivotal Labs people, and so really we're driving hard towards, you know, becoming one team. And Pivotal One is really the banner under which we're all moving and we're saying, hey, how do we make Pivotal One, give us, you know, one common platform, one unified product set? So talk about the software-defined data center. Obviously that is the, I'd say the dream, the moonshaw, that's where everyone's trying to build the ladder to get to. And I say hype in a good way. I don't mean to kind of put a diss on you guys or VMware. I mean, I love the software-defined data center because that's really a destination. You know, software-defined networking with VMware bought this year. Obviously we had Martin Casada on at VMworld and that has just been an amazing geek revolution where you're reaching virtualization. But now you guys are now going to be part of that whole open-source, scale-out developer community. So what's your view from that perspective of the software-defined fill-in-the-blank? Software-defined storage, software-defined servers, software-defined networking, and now I'll say software-defined applications are, or applications that take advantage of that converged infrastructure, or in this case DevOps. Well, I think you're hitting the nail in the head. I mean, you do have software-defined networking with Necessari, you have software-defined storage. You have, obviously with VMware, you have, you know, our core product has been all about software-defined, you know, compute and memory. And what you can think of the way Pivotal fits into the software-defined data center is Pivotal provides software-defined application and data infrastructure, or software-defined application and data fabric, where all of our stuff layers on top of this, the software-defined data center components that VMware provides, and, you know, provides additional capabilities, you know, in terms of application containers, and, you know, Hadoop for querying, RabbitMQ for messaging, and so forth. So what's the developer mindset? I mean, because obviously DevOps is obviously important. They don't want to do any infrastructure coding. Pivotal's gotten a reputation as a company, and you guys got bought by VMware now, part of the Pivotal initiative, gopivotal.com, as the website, but, you know, that's the brand umbrella for a lot of other components of Pivotal. But how do you guys look at the developer community? What are you guys messaging to them? What is the key products that you're bringing to market? Yeah, so developers are incredibly important to us. And with the Spring Framework, you're going to see from us a renewed focus on Spring. Again, Spring 4 is something that we're driving towards. You know, I've talked about Spring XD, for instance. Spring Cloud to make Spring run better on Cloud Foundry. So you're going to see a lot of stuff where we're making Spring better and better and better for developers. And at the same time, one of the things we want to do is we want to make Spring the getting started experience of Spring as easy as the getting started experience that you'd have for a Ruby or a Python or a Node. I think, you know, Spring has gained a lot of traction by being, you know, better than JEE or easier to get started with than JEE. That's what people tell us. And so we're, you know, of course, we want to continue to do that and continue to maintain our lead over JEE. But what we also want to do is we want to, you know, look at these other newer interpreted languages that I just mentioned and make sure that our getting started experience is at least as good as theirs. Because at the end of the day developers, I mean, Paul Muritz always says, developers are the new key makers and we've taken that to heart where at the end of the day it's their hands and the keyboard, it's their hands that determine what stuff gets used and determines what servers are getting deployed into production. So are you guys still going to be invited to VMworld? Yes, we are. They haven't kicked us out yet. Not yet. We're going to see you there. theCUBE will be at the VMworld. So we're excited to have more conversations with you. Al Sargent, who's director of product marketing. I'll see you on the app fabric, but they got the app fabric, cloud fabric, data fabric. Great vision. We'll see how it plays out again. Vision without execution is hallucination as was said on theCUBE last week in Las Vegas. Good luck with that. Thanks for coming on theCUBE. This is Silicon Angles theCUBE. I'm John Furrier. We'll be right back with our next guest after this short break. Thank you, John.