This new NodeJS framework was inspired by Laravel, with similar folder structure and includes IOC container, very similar router, service providers, middlewares, even Views similar to blade. Utilizes ES6 classes for controllers. Even has an ORM called Lucid.

I first saw Scrollback being used on Tomahawk's website. You can embed a live chatbox to your website using this nodejs app. Archives all your conversations. Admin panel allows you to moderate conversations and hide messages. Customize your Scrollback chat widget to match the branding of your website or blog. Integrate your IRC channel with your Scrollback room, which means you could include github notifications for your project as well.

Passport is authentication middleware for Node.js. Extremely flexible and modular, Passport can be unobtrusively dropped in to any Express-based web application. A comprehensive set of strategies support authentication using a username and password, Facebook, Twitter, and more.

Basic front end web pages to bootstrap the creation of your website. Built on Express. Includes an auth system (using Passport) with login (including Facebook, Twitter, Google) and forgot password/reset password, and an admin area with user and group permissions. Utilizes lots of great packages such as Bootstrap, Grunt, Jade, Backbone.js, Bower, Mongoose, Underscore.js, and Font-Awesome.

Nodejs library to easily get screenshots of a responsive site at various resolutions; in your node script just specify the site and the size of screenshots and the directory to save the screenshots to.

A great framework for starting an nodejs project, includes Express, MVC structure, bootstrap, native auth or oAuth login (via Twitter, Facebook, Google, etc), user account management, email support, and a couple basic themes to pick from.

node-webkit is an app runtime based on Chromium and node.js. You can write native apps in HTML and Javascript. It's created and open sourced by Intel. It makes it easy to package and distribute apps for Linux, Mac OSX and Windows. Popular projects built on node-webkit include LightBox and Popcorn Time.

The Sequelize library provides easy access to MySQL, MariaDB, SQLite or PostgreSQL databases by mapping database entries to objects and vice versa. To put it in a nutshell, it's an ORM (Object-Relational-Mapper). The library is written entirely in JavaScript and can be used in the Node.JS environment.

I/O Docs is a live interactive documentation system for RESTful web APIs. Open sourced by the talented API guys at Mashery. I/O Docs is a lot like Swagger except I/O Docs isn't just a spec, it's the interpreter as well and it's written in NodeJS.

We're building a highly scalable platform that will be serving multiple millions of hits per day and servicing potentially multiple thousands of concurrent user connections.

This platform will support many sites that differ in purpose and functionality. For this reason, individual sites should be decoupled from the main platform by using an API. We'll cache where we can, but a lot of the sites are going to be dynamic with notifications and streaming updates so we'd like to use Websockets to create a great experience for the end user.

We're currently a PHP (LAMP) house, and trying to decide if we should use Node.js to only power the APIs (maybe Express), or if we should build the entire platform on Node.js? How does Node.js perform with backend processes such as manipulating large amounts of images, or long-running job queues to send out emails, compared to say Python or PHP? We're also considering Python (eg. Tornado), as it can be a solid 2nd place to Node.js for reqs/second while also very strong with backend processes (or maybe HipHop so we could stay with PHP for the backend processing stuff).

Does anyone have experience with building a platform with this much traffic on Node.js? Or do you have any other ideas?