Node Interactive NA As I look forward to Node.js Interactive next week, I’d like to elaborate upon one of the themes I touched upon in my last post. What has driven the Node.js community and ecosystem growth, and what insights can we learn and apply from understanding the root causes of that growth? Upon reflection, I believe that one of the key reasons for Node.js’ success has been a steady focus on the needs of the end user. (In this context, let’s consider “end user” to include Node.js application developers and the users of Node.js applications.) I also think that those needs have been evolving over time, so it’s a good time to pause and reflect on what today’s priorities should be. When a new platform technology emerges, at first (and quite naturally) the community’s emphasis is on building out the technical base—the runtime itself, its language bindings, core libraries, development tools, and so on. Once that is achieved, however, gaining true pervasive industry adoption requires the community and its vendors to address the entire community’s broader needs. What are those broader end user needs? My last post I touched upon two: monitoring and problem determination, and ensuring users can get the most out of Node.js by improved package discovery. But there are other needs that the community has only recently begun to apply itself to. For example, we need seamless deployment in a cloud-based, continuous integration environment, higher level tools to accelerate application development, and Enterprise-class service and support offerings based on the LTS option provided by the community. Finally, with ever more Enterprise-class workloads being deployed on Node.js, it’s important that Node.js’ performance at scale be consistent while improving each release, which is the focus of the the Node.js Benchmarking Workgroup (facilitated by IBM). You probably have your own list of needs or “pain points,” and perhaps they’re different from mine. Regardless, it’s possible these pain points are impeding your adoption of Node.js. That’s why I am looking forward to Node Interactive, where we can focus the discussion on end user needs and their relative priorities, and how the community should address them. Leading members of IBM’s Node.js and StrongLoop development and developer advocacy teams will be present at the conference. Please seek us out individually or visit us at the IBM booth to continue the discussion. At the booth, we’ll highlight IBM’s new initiatives in this arena. Finally, don’t forget to attend the official conference reception, sponsored by IBM, on Wednesday evening at the Steamworks Brewing company. I’ll be present and would welcome hearing your thoughts regarding how to accelerate the growth of Node.js. See you in Vancouver!

3 comments on"Addressing The Broader Needs of Node.js End Users"

  1. […] This year at Node Interactive, and the collaborator summit which follows, I look forward to hearing (and talking about in the case of N-API)  about some of the new ideas that we’ll see taking shape over the next few years.  One thing I’d like to see is getting more input from end users as we can never hear enough from those who use Node.js to solve their problems.  Node Interactive should be a good opportunity to start some of these discussions and I’m hoping we can follow this up through initiatives in the Community Committee like this one.  For some additional thoughts on this topic you can also read a recent blog by Todd Moore which is available here. […]

  2. […] one of many starter project options and set up a DevOps toolchain. As Todd Moore discussed in his pre-Node Interactive blog post, monitoring and problem determination are essential to our end-users’ productivity. App […]

  3. […] Read Todd’s article, “Addressing the broader needs of Node.js end users.” […]

Join The Discussion

Your email address will not be published. Required fields are marked *