by Dariya Kursova
What exactly is Node.js and why should you use it?
Surely, this is technological stuff for programmers/coders, and some might find the language not quite apprehendable. With this in mind, we will try to make it as light-some as possible and speak in more human terms. We just want to explain what makes Node.js great and what is all the hype about.
First off, the praise is well deserved, as Node decisively eased the work of anyone building web applications. After decades of web request/response paradigm, having real-time 2-way communication is a bliss. That is a communication between the server and the client. And that, in turn, is a model to distribute workloads among service providers (server) and service requests (clients).
On board so far? Great, now some statistical info about the demand for Node.js. It is by far the fastest growing language in use, and it ranks in Top-10 most wanted developer skills. The use of Node.js is mainly for full stack, front-end, and back-end.
What is Node.js?
“a development platform aimed at building server-side applications”. And PCMag tells us that Node.js is “a platform with its own web server for better control”. That is certainly enough to grasp the main idea.
A brief summary would be as goes:
- Node.js is a server framework, and is free
- It runs on Windows, Linux, Mac OS, and so on
How does Node.js work? Taking a simple task of opening a file on a server, the sequence would be:
- A task goes to the file system
- The system is ready for next requests
- When a file is opened and read, the system sends the content to the client
In other words, with Node.js you do not have to wait and can go on with next tasks. This is one of the reasons it is so efficient. Now, what is a Node.js file:
- It contains tasks and executes them upon set events
- An event is when someone tries to access the server
- A file should be initiated on the server
- Files have ‘.js’ extension
And last but not least, what you can do with Node.js?
- Generate dynamic content
- Create, open and read, or delete files on the server
- Gather and modify data in the database
Why use Node.js
Another benefit is single-threaded event loop, that is responsible for abstracting I/O from external requests. Speaking plainly, this means that Node.js initiates the event loop at the start, processes the input, and begins the order of operations. Dev geeks interested in exploring it can read Node.js event loop.
Jim Hirschauer of Crafter Software made few realizations on why use Node.js. We think they highlight the essence and what Node.js is good for:
Translation: fast and scalable web apps in a result.
- For server-side applications
Meaning, Node.js is an event-driven model of programming, where the flow is determined by certain events (user actions, messages, etc.).
- Easier and scalable
That is, to make apps like Uber or Trello and scaling out on multi-CPU servers.
- Per-process and across servers
Translation: Node.js can scale on individual process basis spreading out the load across multi-core servers.
This all seems a bit tough, we realize. So behold a summary of coherent benefits to using Node.js.
10 main reasons to use Node.js
- It is fast, due to Google innovative technologies and the event loop
- Ability to keep data in native JSON (object notation) format in your database
- Multiple modules (NPM, Grunt, etc.) and supportive community
- Good to create real-time apps, such as chats and games
- Single free codebase
- Good for data streaming, thus for audio and video files, as example
- Sponsored by Linux Foundation, as well as PayPal, Joylent, Microsoft, Walmart
- Wide range of hosting options
Well, this should clear the picture for you a bit more. But wait, did you know NASA also uses Node.js?
Who works with it: Node cases
Showing incredible pace (close to 100% growth in use every year), Node.js has become a universal platform for web apps. Companies like PayPal, Walmart use Node for enterprise applications too. Trends building up within Node community are micro-services, real-time applications, and Internet of Things (IoT). But more on that later.
With almost 4 million users by early 2017, Node.js surely does not lack top-level companies that work with it. For instance, what was our previous reference to NASA all about? Well, this is the truth. The agency in partnership with UTC Aerospace Systems has designed end-to-end system for live data processing. It is used in astronauts’ spacesuits and has been build with Node.js.
If you’ve read our previous post about top companies using Node.js, you already know about Netflix, Microsoft, Uber and more. Though that is far from all great examples. Capital One, a huge financial corporation, runs numerous projects with Node.js because of short Node.js development cycles. Advertising agencies, like Fusion Marketing, create interactive customer experiences. Walmart in retail, Uber in transportation, Google, Twitter, GoDaddy, Skycatch… it may take hours to cover them all.
There’s also a series of Node.js Enterprise conversations, where each episode is devoted to a separate Node.js use case. Like this one, where Adam Geitgey, director of software engineering at Groupon, talks about how the platform helped them to expand.
One of the results of Node.js use at Groupon was 50% reduction of page load times. How about that! Let’s talk a bit more about Node.js success cases.
Node.js success stories: Groupon, Skycatch & Lowe’s
- for back-end services
- for API’s integration layer
- for client’s applications and websites
- for about 70 own Groupon’s apps
Skycatch is a data company working with commercial drones data. And while creating raw SQL is hard and long, Skycatch allows to do it in an easier way and simplify data extraction from websites. Andre Deutmeyer and the team of 20 developers had the task to architect and deliver data to customers quickly. They chose Node.js and basked in wins, like:
- Scalable options are better because a hurdle between front-end and back-end is gone
- Node.js back-end services are tolerated by front-end language on servers
- As AWS Lambda is using Node.js too, it allowed focusing on developing apps, not on infrastructure
Rick Adam, a team leader of 25 developers at Lowe’s, had a task to manage apps at presentations tiers. In order to rebuild a monolithic app back in 2007 company chose Node.js as in those days even minor changes in an app text required the whole app to be patched, while Node.js provided flexibility in that regard. This choice resulted in the following:
- positive brokering of web and API’s requests (plus large growth potential)
- the asynchronous model of Node.js gave an opportunity to advance app functionality and better UX
- excellent performance
- Some of the front-end skills also used in back-end programming
What is Node.js used for
We can build fast real-time apps like a chat, or an upload system, or any app that has to respond to big number of requests. And we already knew that by now, right?
So what can be Node.js used for actually? When to use Node.js and what is it good for? Well, here are few uses that you can name to clients, and examples of what could Node.js be used for.
- Streaming data
Such as file uploading in real time, file encoding while uploading, building proxies between data layers.
- Single page apps
Modern web applications, heavy on processing on the client side. Positive response times and sharing data between the server and the client make a good fit for such apps.
- Web applications
Classic web apps on the server side, using Node.js to carry HTML. One of the main benefits in this regard is more SEO-friendly content.
- Chats / RTAs
Lightweight real-time applications, like messaging apps interfaces, Twitter, chat software. A classic chat would be a great example of Node.js use. Simple, intensive on data and across multiple devices.
REST / JSON programming interfaces and exposing databases or web services through it. No worries about conversion between systems.
To deploy Node.js as proxy to handle connections in non-blocking way. Great for app working with external services, exporting and importing lots of data.
Web application or system monitoring dashboards, enabling tracking user actions. Node.js also can visualize such interactions for you in real-time.
5 less known Node.js uses
Yet, Node.js is evolving fast and not only web application building is possible. Check out these alternative Node.js projects that are still in making.
- Node-Webkit: a runtime environment for Node.js applications. Simple app packaging process — zip it, add information and deploy cross-platform.
- Log.io: a log monitoring tool, using Socket.io library. All changes you are following, you can track in real-time and in browser.
- Nodecast: an application that sends images and videos from your mobile phone to PC. Inspired by Google Chromecast.
- Nexe: a utility for Node.js app distribution by creating a single executable. Though it only works on Linux and MacOS X so far.
And that is not all, dear stoic readers who are still reading this. Enterprise-scale businesses and projects are also embracing Node.js.
Node.js for enterprise
Why go to Facebook and do PHP, when you can go to Paypal and do Node.js. — Bill Scott, VP of engineering at PayPal
So why enterprises alike go with Node.js? Reduced page load times, ease of maintaining, the number of servers reduction might hold some answers. In addition, a new architecture type of Node.js, called micro-services, helps in handling numerous changes to enterprise software. Under this approach, you can create applications from smaller pieces, and develop those pieces separately. No harm to overall functioning.
There are also developers who prefer full-stack unified solutions. In practice, top 4 technologies used along with Node.js are:
- Angular JS
What are the potential application areas of Node.js?
- Payment gateways
- Social media
- Enterprise web apps
- Backend/API for mobile apps
Basically, any business using Node.js can: employ less developers, use less servers, decrease page load times. For more thoughts on this, you may watch the next video, where CTO and architect manager of Nodesource talk about Node.js.
Node.js in production, dos and don’ts
One final thing in our trip to Nodeland are some practical advises about running this toolset. We should start with process managers to deploy applications. To make your life easier, use NPM, PM2, Adios, Strongloop or any other Node.js production manager.
Don’t do apps heavy on CPU with Node.js. Programming things like artificial intelligence (AI), video encoding software, and such software that loads the processor, better use another solution. Node.js has a 1.5 Gb memory limit, though you can apply clustering to fork processes into smaller ones.
Node.js servers are not great for computational and data-intensive tasks. Thus, it is better to split such tasks into micro-services and deploy separately.
Don’t run a Node.js app through port 80. Use a reverse proxy in front of the app, like Nginx for example. In this way you protect servers from internet traffic and spread the load balance.
Install SSL for security reasons. Always use a reverse proxy, check vulnerabilities in SSL and fix the possible issues. Do basic security checks from time to time. Do not use outdated versions of Node.js and Express.
Think of infrastructure and architecture ahead of app deployment. Experts recommend developing an application within a private network (VPN), so you can allow only trusted connections.
Thank you for reading. If you like leave some ?.
If you want to read more check out here.