Best practices of building a website using Node.js

by

To start with the bad news: As Node.js is a pretty young technique, I think you’ll find that the proces of creating a full fledged website and maintaining/operating it will be very different than what you’re currently used to.

Josh3736 adds: Once you figure out how Node.js and its various packages (Connect, Express) work, I found that you can develop new sites very quickly.

The rough edges that currently exist in Node.js, combined with the fast pace of its development and all modules involved can complicate things though, and make things less simple, fast and straightforward than you’d like.

Having that out of the way, here’s the good news:

The Node Package Manager, NPM has a lot of good tools and frameworks to expand Node.js’s bare bones functionality, making it suitable to create a webserver.

Most notably would be the Express Framework which contains almost everything you need to run a webserver (including cookies, sessions and path routing). Additionally Express supports partials, which take care of your header and footer includes.

Express is built on top of Sencha’s Connect. Cookies and sessions are actually powered by Connect. Express is what simplifies your routing and handles views/partials. So if you don’t need all bells and whistles that come with Express you could just go for Connect instead.

If you like to use templates for these partials, the Jade Template Engine can speed things up for you. Though Josh3736 points out that Jade is slow and whitespace-significant. A more complete overview can be found here, which includes his favourite, doT. (I personally use Node.js for socket.io based applications only, so he’s a better source than me when it comes to templating).

You can connect to MySQL from Node.js using the db-mysql module, but if you don’t need that because you’re accessing data connected to an already present system, I’d advise to use a more… ‘modern’ approach, which is to use a NoSQL database as most Node.js projects seem to do. MongoDB via Mongoose is the popular way to go.

Or if it’s just storing objects you’re interested in, just go for Redis instead (which you’re probably going to need at some point anyway).

Once your website is complete, you’ll have to deploy it and make sure it keeps running. There are many ways to do so, like using built-in cluster support or use the more feature-friendly forever npm module. See this SO question of mine for more information.

Conclusion:

What I’m trying to get at is this:

Asking what the best practice for building a website in Node.js is, is about the same as asking what the best way to build a website in PHP is: 100 developers will give you 100 different answers.

NPM is blessed with a variety of excellent frameworks that greatly simplify a lot of tasks involved, but it’s all based on preference which one is the way to go really.

As I’ve said, Node.js is still a pretty young technique, so none of the frameworks or additional tools have emerged as ‘defacto standard’ yet; for most things you’re trying to do there are probably various alternatives, and expect your code to break when using most of them during updates, because development of Node.js itself and most modules is fast paced. You’ll have to keep up.

Putting it all together:

As I’ve said, my main production use for Node.js is to be able to use socket.io, so I don’t have any good production examples present (And as I’m about to leave on a well-deserved vacation I don’t have the time to put one together either). There are some good examples though:

Again, the way to go (and subsequently the example to follow) depends greatly on your ultimate goals and the techniques chosen, but luckily there are plenty of resources available for all of the choices available. Most modules use well documented GitHub repositories and include examples in combination with the most popular modules (See the /examples/ dir that seems to be present in most repositories).

(thanks to Josh3736 for rectifying my errors.)

More Related Contents:

  1. How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X)
  2. Client on Node.js: Uncaught ReferenceError: require is not defined
  3. Is it bad practice to have a constructor function return a Promise?
  4. Error: request entity too large
  5. How to parse JSON using Node.js? [closed]
  6. Asynchronous exception handling with bluebird promises
  7. How to format a UTC date as a `YYYY-MM-DD hh:mm:ss` string using NodeJS?
  8. Using socket.io in Express 4 and express-generator’s /bin/www
  9. Calling a JSON API with Node.js
  10. What is the best way to limit concurrency when using ES6’s Promise.all()?
  11. getting how many people are in a chat room in socket.io [duplicate]
  12. How to convert CSV to JSON in Node.js
  13. TypeError: firebase.storage is not a function
  14. Reading Excel file using node.js
  15. How do I measure the execution time of JavaScript code with callbacks?
  16. Inserting and Querying Date with MongoDB and Nodejs
  17. Socket.io + PhoneGap
  18. How to unit test a Node.js module that requires other modules and how to mock the global require function?
  19. How do you import a javascript package from a cdn/script tag in React?
  20. Cannot find module ‘../build/Release/bson’] code: ‘MODULE_NOT_FOUND’ } js-bson: Failed to load c++ bson extension, using pure JS version
  21. Vue js error: Component template should contain exactly one root element
  22. setPresence activity type in discord.js v14 can only be set to “PLAYING”
  23. Discord.js – Cooldown for a command for each user not all users
  24. Combine json arrays by key, javascript
  25. Recursive Promises Not Returning
  26. ES6 import from root
  27. How to create a sleep/delay in nodejs that is Blocking?
  28. using await on global scope without async keyword
  29. Cannot connect to MongoDB because of wrong URI
  30. ESLint: “error Parsing error: The keyword ‘const’ is reserved”

Leave a Comment