Haven’t started building in Node.js yet?

Well, you should! Here’s why:

Firstly, because it’s cool, and we mean it! If you want to come across as a trendy, up to date programmer, you should be able to create a working system on any up-and-coming platform, basically because every other fellow computer geek such as yourself will. And you don’t want be the one who never gets the small talk during lunch break, the one that is constantly interrupting for further explanations and clarification. You don’t want to be that guy, you hate that guy. And if this wasn’t a good enough reason, we’ve got a few more compelling arguments as to why node.js should be the go-to platform for your web development projects.

It’s pretty popular and easy to learn

One of the main traits that should entice you to build in node, is the fact that it isn’t that hard to learn, and you probably already have, yet don’t know it. If you are already familiar with JavaScript, there really isn’t that much learning effort.

It makes real-time apps a piece of cake

You can finally kiss writing sockets and protocols goodbye and say hello to real-time, two-way connections, because multi-user is Node-event-loop’s cup of tea. Therefore, the server is no longer the sole data pusher, where the client is able to initiate communication just as easily, allowing both parties to exchange data freely.

It doesn’t block your code

Yes, if you haven’t wrapped your head around it just yet, we’ll raise you this one: Node is utterly event driven, which basically means most of the code is run based on callbacks, so the application becomes available for further requests instead of pausing or sleeping.

It’s got a welcoming community

Like any other popular platform or product, node.js has built around itself a great, influencing community, contributing on a daily basis to its enlargement and development from the very core. And a great community, namely means a bunch of smart people, available for constant help, support and shared opportunities.

With these and plenty other amazing features, Node.js has made a quite a name for itself in the web development world and has been gaining adherents with every passing day.

So if you’ve made it this far, welcome to the future of web development! You’re gonna love it!



SConfig – A CDN for your configuration files, built in Node

Today we’re going to talk about a very cool product made in Node.js, called SConfig.

As the title goes, it’s a CDN for configuration data and files that allows you to keep, manage and access them all in one place. SConfig is a Node.js client for encrypted configuration storage. It’s a practical service that secures your applications easily. Basically, it’s an awesome, scalable and secure way to protect your config files. You can define as many applications as you want, or any number of versions. They’re easy to access through an API call from the servers. It uses strong multi-factor authentication (from UNLOQ) and AES-256 encryption to protect your data.

SConfig uses the Thorin.js framework created by UNLOQ, we talked about them in a previous article. It’s built from the bottom up in JavaScript, front and back end. If you read about Thorin.js you know it’s a modular framework, and SConfig is built using some of the Thorin modules. It’s all made in Node.js, which is pretty amazing.

Here’s how it works:

You can check out the full presentation of SConfig here, and see their Github account here.

SConfig is a product meant for developers, meant to make accessing files easier and safer. It’s destined for small devops teams and large departments. To be able to use the service you have to download the UNLOQ app and create an account. The token that you received on the app will be used to login securely.  The entire relationship between the device (the app), the browser and the servers is dealt with encryption keys and tokens, making the data stored in your account private. File content encryption is done in the browser and the servers only get encrypted data, having no clue what it is. It uses zero knowledge proof to make sure all your data is private, even to SConfig.

Give it a try, it’s free for up to 5 applications.



How the Node.js Foundation works

Every Node developer is familiar with the Node.js Foundation, but not everybody know how it works and what are its actual activities. We’re going to shed some light on these issues.

The Foundation is on a mission to enable the adoption of Node.js on a large scale and accelerate its development. As the name entails, it doesn’t have any commercial implication, it’s not a company that markets or sales a product, it’s a foundation with an open governance model, driven by the community. The Node.js Foundation is the steward of Node.js, helping it grow and evolve on a long term basis.

You can get in depth information about the Governance, By-Laws, Trademark Guidelines and other in the Foundation section of their website.

So, who’s in charge?

The Foundation is governed by a Board of Directors composed of representatives from the corporate members. There are three tiers of corporate members, platinum, gold and silver. Each tier has a presence in the board, as follows: every platinum member gets one seat on the board, for every 3 gold members there is an election to choose a representative and for every 10 silver members the same thing happens again. If you check out the membership right now you’ll see a lot of big names there, companies that adopted Node early on and are heavily based on it. Besides the corporate members there is also on the board a representative of the Technical Steering Committee and one elected by the individual membership class.

This brings us to the individual membership issues. You can also be a part of the Node.js Foundation. The membership costs 100 $ per year, or 25 $ for students. If you are an active contributor to the Node.js projectsor in any of its sub-projects you are eligible for free membership.

The board at this time is composed of:

  • Chairperson: Danese Cooper, distinguished member of technical staff – open source at PayPal.

  • Vice-Chairperson: Scott Hammond, chief executive officer at Joyent.

  • TSC Director: Rod Vagg, chief node officer at NodeSource.

  • Gold-level Director: Charlie Robbins, director of engineering at

  • Silver-level Director: Brian McCallister, chief technology officer of platforms at Groupon.

  • Director: Todd Moore, vice president of open technology at IBM.

  • Director: Colleen Evans, principal program manager at Microsoft.

  • Director: Rich Sharples, senior director of product management at Red Hat.

  • Director: Imad Sousou, vice president and general manager at Intel.

  • Director: Ashley Williams, individual membership director.

  • Director: Feross Aboukhadijeh, individual membership director.

By checking out the Node.js board you can get a good glimpse of what companies are actively involved in node.js (a great piece of information if you’re job hunting)

Besides the Board, there is also a Technical Steering Committee that has a representative on the board. The TSC sets the technical direction of Node and handles everything related to the technical development (releases, standards, repo hosting etc)

The Node.js Foundation may seem to some like some sort of mysterious entity, but actually it’s made from the ground up from node people. No matter the company, no matter the brand, there are all developers interested in node.js, caring and growing it. Just think of it as a parent taking care of a child (the child being Node), only it’s not just one parent, there’s dozens, hundreds and more. Anybody can be a contributor to the node.js project, individuals can be nominated as collaborators by TSC members and if the nomination is approved, that person gets the actual invitation to become a node.js contributor. You can dive in the contributing process here if you’re interested to find out more.