Interesting.. :)

I don't think so. If a tool eases my job without any side effects, I will USE it.

I think the simplest thing is to do the following : Use Nginx to forward all *.logos.com requests to your Node.js app. Then use express.vhost to handle requests appropriately. Sample Code using Express vHost : var http = require('http') var vhost = require('vhost') // create main app var app = connect() app.use(vhost('mail.example.com', function (req, res) { // handle req + res belonging to mail.example.com res.setHeader('Content-Type', 'text/plain') res.end('hello from mail!') })) // an external api server in any framework var httpServer = http.createServer(function (req, res) { res.setHeader('Content-Type', 'text/plain') res.end('hello from the api!') }) app.use(vhost('api.example.com', function (req, res) { // handle req + res belonging to api.example.com // pass the request to a standard Node.js HTTP server httpServer.emit('request', req, res) })) app.listen(3000);

Completely Agreed!

The answer is no. She is doing what she has been hired for. I don't think uninstalling malware was a part of job description.

Thanks Jan. Will storing JSONs in Redis have any performance impact? I will have to stringify and store the JSON. Have you seen any negative impact?

Thanks Sean! I have 2GB of RAM now and it's working without any problem. But I am expecting spike in traffic and more concurrent users soon. That's why I am little concerned. But I guess I can start with 4GB and see if I need more.

Completely agree!

I usually like to read about high scalability stuff and love to dig more into the advanced things. It's always great to read how the author implemented something difficult by making some tweaks or how the author leveraged advanced features of technology to achieve something.

Jekyll always! It's pretty widely used and easy to manage.