Although Node.js is becoming increasingly popular with big companies building out services which benefit from its event driven, non-blocking characteristics, its adoption is sometimes stymied by a lack of advanced features and services. Specifically, private npm registries and a certified distribution for Linux and Windows, backed by technical support plans. In recognition of these needs, StrongLoop is excited to announce a strategic partnership with Nodejitsu to bring these features to the Enterprise.
Developers have made Node insanely popular
Why is the Enterprise getting excited about the potential for Node? It no doubt has to do with the enthusiasm and lobbying of developers, architects and even CTOs. Although Node has only been around for about four years, it has become the second most popular project on GitHub.
And, it doesn’t look like interest in Node is going to subside anytime soon. As of February 2013, Google Trends has been reporting that “Node.js” has overtaken “Ruby on Rails” in search volume.
Node runs Enterprise apps
Plenty of Enterprises have bet big on Node and many are hiring developers with Node specific skills to work on projects in the pipeline. Here’s a small sampling of those companies:
- Chatham Financial
- Condé Nast
- General Motors
- Time Warner Cable
If you want to learn more or simply need some ammo to convince your boss that your next project should be based on Node, we’ve created an infographic that dives into the details of Node’s popularity, who’s using it and who’s supporting it.
As Enterprise adoption increases, so do the challenges
We can all agree that an Enterprise is going to have a longer set of requirements and constraints for Node, than a startup just setting out. Fortunately, companies can now confidently deploy Node in an Enterprise setting with many of these considerations handled through offerings from StrongLoop and Nodejitsu.
StrongNode – A certified distribution of Node.js
The StrongNode distribution gives you a path forward to get technical support and bug fix coverage before heading into production. For developers who are new to Node, StrongNode gives you the perfect starting point. Navigating over 33,000 modules and the unique features of Node itself can be an overwhelming experience. StrongNode comes with vetted modules including:
- Express – web application framework
- Connect – rich middleware framework
- Passport – simple, unobtrusive authentication
- Mongoose – elegant mongodb object modeling
- Async – higher-order functions and common patterns for asynchronous code
- Request – a simplified HTTP request client
- Socket.IO – cross-browser WebSocket for realtime apps
- Engine.IO – transport layer for real time data exchange
- SL Task Emitter – perform an unknown number of async tasks recursively
- SL Config Loader – recursively load config files
- SL Module Loader – separate your app into modules loaded by config files
- SL MQ – MQ API with cluster integration, implemented over various message queues
Bottom line: An organization that starts development on StrongNode ensures that by the time they go to production, they will have a company and a feature set that stands behind them.
Why an Enterprise needs a private npm registry
A few weeks ago, Nodejitsu discussed how important the npm module ecosystem was to the success of Node. But, how can an organization bring the same success in-house?
Unfortunately, this is easier to accomplish in theory than in practice. This is because the same qualities that make npm incredibly useful for developers on a small scale, can become a serious hindrance in an Enterprise development setting. Here’s a few reasons why:
- Everyone shares the same public registry – By installing your Node.js packages from a dedicated private npm registry, you can greatly decrease your deployment times.
- Geographic challenges – By co-locating your private npm registry with your applications, you remove any latency concerns when deploying.
- All packages are public – If you’re not running a private npm registry today, that means that anything your developers publish to npm is public. By switching to a private npm registry you can securely install all of your packages from a single, easy to manage location.
- Unexpected wildcards – All Node packages use [semantic versioning][semver] to specify their dependencies. The one downfall of semantic versioning is inconsistent dependencies for a single application deployed at different times. In a large enough organization you want to be sure that simple developer errors do not cause defects in your applications.
- Managing users is painful – The Nodejitsu Enterprise npm registry can automatically replicate your developer’s npm.org authentication information. This saves you and your team from the tedious process of managing user accounts.