 Hi, I'm Alex Williams of Silicon Angle here at the Node Summit, live with theCUBE, our world-class online new streaming service that we do at events like this here at Node Summit with James. James, Richard, how are you, sir? I'm doing great, man. It's so good to see you again. Good to see you. And it's kind of weird to be on this side of the discussion with you, having been a fellow blogger for so long. But, you know, great venue, amazing crowd here at the show. And I'm really excited to be on theCUBE again. The last time I was on was a great time, so. What's up with Node.js and kind of your perspective of the world? Well, you know, one of the aspects of Node that's really interesting came up on the panel that I moderated this morning. We had Nojitsu, and Heroku, and Azure, and Cloud Foundry represented. And we talked about Pascal, but one of the things that really came out of it is, you know, in some ways, Node is just another language in the sense that there are things it's great at. There are things it's not so great at. But I think what's really exciting about Node in the cloud space is it's a venting model and it's JavaScript-based nature really makes it something that is quite portable and quite kind of re-assembleable and componentized by nature. In fact, you heard a lot of the talkers at the show talking a lot about how Node kind of gets you to break down to the smallest denominators as quickly as possible to make event management that much easier to deal with to help with things like debugging and deployment and other things. That's kind of the nature of where the cloud's taking applications in general in a lot of ways in that because it's a very service-based environment, people are beginning to break down capabilities into smaller service units and then bring them together, compose them in different ways that may or may not have been expected up front. Node is a great representation, I think, of a language that takes this into account, not maybe not intentionally, but it does fit very nicely. And one of the things that, or in tights at Heroku, is that one of the places we're seeing the Node version of their environment use the heaviest is in machine-to-machine communication. They have a very high traffic level in machine-to-machine communication. And to me, that's really kind of the next frontier. We've done the Web 2.0 thing and it'll continue to grow. There's a lot of room to grow in that space, Facebook apps, consumerism, but really, a big growing area is going to be this machine-to-machine capability where now the automation environment that underpins a lot of, you know, the traditional automation will become much more cloud-like in that it integrates with third-party components that protects, takes information from some source that's not within the four walls of the company and begins to bring that together. And Node seems to be very well-suited to that. Yeah, it does. I mean, and talking to people about how they're using Node.js, for instance, I was talking to a FlowDoc. I think that's the name of their company, but they take group messaging and activity streams, but they take activity streams from GitHub, they take it from JIRA, they take it from email, and they're going to start adding Twitter into it. And so Node.js is really, really ideal for that, as they say. And it seems like it's, you know, we're hearing a lot of it, you know, a lot of people saying that it's great for that real-time communication, so that's what it's great at. What is it not so good at? Well, I think when you get into situations where thread control, where concurrency and managing what's happening from a concurrency perspective gets to be a little bit more detailed and a little bit more finesse-oriented, some of the kinds of things that an Erlang would do really well. I think that's the point at which Node's eventing model means it's much less predictable about what's going to happen when or whether you're even going to have work that is stacked up, intended to be completed, but it's not completed yet. There's not that serial nature to it. It's much less, it's much more about sort of the flow of information through different things taking their part of it and then passing it on to the next thing. When you get into something where you're really getting into the need to really finally work at a high performance on a given processor or just in general on computing, I think that's the point where a lot of people would say there's some things that Node does that aren't the smartest things to do in those particular architectures. That's interesting, I mean, that really then speaks to the need for really good tools, doesn't it? To really be able to see what's happening with the deployment, for instance. I mean, I think about joint and the data visualization tools that they have really to kind of see what's happening inside the network. And it's a big reason for something like Instratis to exist as well, right? Tell me, let's talk about that. Yeah, so Instratis is the leading enterprise cloud management solution. And by cloud management in this condition, the situation, what we mean is the consumption of cloud. So as opposed to being something that delivers a cloud service, we're about how do you take your applications and consume cloud services in a way that is under control, allows you to do some governance around who can do what, potentially financial controls, you're making sure that people are only consuming as much budget as they're supposed to be consuming for something. These are the problems that enterprises deal with when they look at cloud that are very, very, they're exemplified by the enterprise. A big difference being, in a Web 2.0 space, typically you have a few development teams, they have some number of processes, they're growing number, but they're still a well-managed number of processes. And the idea is they have to scale these things across hundreds or thousands of nodes. The enterprise problem is, they've got hundreds or thousands of applications. Each of which may scale on an average need of five to 10 nodes. Right. But the problem is each of those applications have different owners, they have different requirements, they have different budgets, they have different compliance constraints that they have to meet, policies they need to apply to the cloud environments that they run in. And so it's that bringing together the governance and the automation of the application from the application's perspective in a multi-team environment, in an enterprise environment that we really focus on. So we give you, basically the one way to think about it is as a console for managing and operating applications in the clouds that you consume for those applications. So managing those applications inside the enterprise, and we're hearing a lot of popularity for Node.js in the enterprise. Is that one of the, that's one you just outlined, some real reasons why it has viability there. What are some other reasons that you're seeing that they're talking about? That enterprises are talking about Node in particular? Yeah, you know, again I think the, when you look at the types of applications in enterprises, they span the full gamut end to end. One of the things that's happening is the cloud has introduced the ability to build some applications that were economically unobtainable, frankly, in the past. So a lot of big data, a lot of the excitement about big data comes from the fact that you can now experiment with processing data in certain ways.